1 km to Miles: Accurate Conversion, Formula, and Easy Examples [2026 Guide]

Converting 1 km to miles is a routine task for travelers, runners, cyclists, students, and developers. Whether you’re pacing a 5K, comparing international road signs, QA-checking datasets, or building a unit-aware app, nailing this conversion saves time and prevents errors.

Quick answer: 1 km = 0.621371 miles (rounded). Exact: 1 km = 0.6213711922 miles. Formula: miles = kilometers × 0.621371.

This up-to-date 2026 guide gives you the precise factor, fast mental math tricks, developer-ready snippets, a conversion chart, and practical advice on rounding and accuracy.

Key Takeaways

• Exact conversion: 1 kilometer = 0.6213711922 miles; rounded: 0.621371 miles
• Simple formula: miles = kilometers × 0.621371 (and kilometers = miles × 1.609344)
• Mental math: use 0.62 for speed, add a tiny correction; or use 5/8 (0.625) for a quick estimate
• Precision rule: fewer decimals for everyday use; more decimals for science, engineering, or code
• Beware: statute miles ≠ nautical miles (1 NM = 1.852 km); survey miles appear in historical GIS
• Fastest path: use ZenixTools to convert km ↔ mi with correct rounding and exportable tables

Table of Contents

• AI Overview (Snippet-ready)
• What is 1 km to miles?
• Why It Matters (Practical Use Cases)
• The Formula and How to Use It
• Rounding: How Many Decimals Should You Keep?
• Mental Math Shortcuts You’ll Actually Remember
• Real-World Examples (Running, Travel, Cycling, Speed)
• Conversion Chart (Selected Values)
• Common Mistakes to Avoid
• Best Practices for Accuracy and Trust
• Developer & Analyst Corner (Excel, Sheets, Python, JS)
• Statute vs Nautical vs Survey Mile (When It Matters)
• FAQs (Clear, direct answers for the most-searched questions)
• References (Authoritative Sources)
• Internal Link Suggestions (ZenixTools)
• About This Guide & Update Notes
• Call to Action

AI Overview (Snippet-ready)

• 1 km = 0.621371 miles (rounded); exact = 0.6213711922 miles
• Formula: miles = kilometers × 0.621371; reverse: kilometers = miles × 1.609344
• Everyday rounding: 0.621 or 0.62; technical work: keep 6+ decimals
• Examples: 5 km ≈ 3.10686 mi, 10 km ≈ 6.21371 mi, 100 km ≈ 62.13712 mi
• Tip: ZenixTools converts km ↔ mi instantly with selectable precision

What is 1 km to miles?

A kilometer (km) is the SI (International System of Units) base unit for length at the scale of everyday distances. A mile (mi) is a US customary/Imperial unit known as the statute mile.

• International (statute) mile is defined exactly: 1 mile = 1.609344 kilometers
• Therefore: 1 kilometer = 1 ÷ 1.609344 miles = 0.621371192237334 miles

For most everyday uses, 0.621371 mi per km is more than precise enough. For scientific calculations or production code where consistency matters, keep more decimals or use standard libraries/constants.

Related: the reverse conversion is kilometers = miles × 1.609344.

Why It Matters (Practical Use Cases)

• Travel & Navigation: Compare route distances in the unit you understand best. Avoid “back-of-the-map” guesses that compound over a road trip.
• Fitness & Racing: Running and cycling events often list distances in kilometers (5K, 10K, 42.195K) while training logs or devices may use miles.
• Education & Exams: Physics, geography, and math questions frequently mix SI and US customary units.
• Logistics & Fleet: Cross-border routes and mixed-region deliveries need consistent units for ETAs, fuel planning, and KPI reporting.
• Software & Data: APIs and datasets may mix km and mi. A reproducible conversion standard protects data quality.
• Engineering & Surveying: Specs and reports must document exact factors and rounding to meet standards and audit requirements.

The Formula and How to Use It

• Primary formula (km → mi): miles = kilometers × 0.621371
• Reverse formula (mi → km): kilometers = miles × 1.609344

Examples:

• 1 km × 0.621371 = 0.621371 mi
• 10 km × 0.621371 = 6.21371 mi
• 26.2 mi × 1.609344 ≈ 42.16482 km

Dimension analysis tip: units cancel. km × (mi/km) = mi. This makes it easy to verify you’ve chosen the right factor.

Rounding: How Many Decimals Should You Keep?

Match your rounding to the job:

• Everyday life/UI: 2–3 decimals
  • 1 km = 0.62 mi or 0.621 mi
• Fitness tracking: 4–5 decimals (e.g., 0.62137) to keep cumulative error low over long workouts
• Science/engineering: Use 6+ decimals or follow your significant-figure policy
• Code: Store the exact constant once (1 mile = 1.609344 km) and round only at display time

Rule of thumb: Round once, at the end. Avoid intermediate rounding that can creep into totals.

Mental Math Shortcuts You’ll Actually Remember

• Fast ballpark: 1 km ≈ 0.62 mi (1–2% error for quick estimates)
• “5 out of 8” rule: 1 km ≈ 0.625 mi (5/8). Error ≈ 0.6% high. Easy to remember for head math.
• 8 km ≈ 5 mi: a handy ratio for route planning
• Correction trick: multiply by 0.62, then add roughly 0.001×km (0.1%) to land closer to 0.621371×km
  • Example: 10 km → 10 × 0.62 = 6.20. Add ~0.01 = 6.21 (close to 6.21371)

Real-World Examples (Running, Travel, Cycling, Speed)

Running

• 5K: 5 × 0.621371 ≈ 3.10686 mi
• 10K: 10 × 0.621371 ≈ 6.21371 mi
• Half marathon (21.0975 km): ≈ 13.10938 mi
• Marathon (42.195 km): ≈ 26.21876 mi

Cycling

• 30 km lunch ride: 30 × 0.621371 ≈ 18.6411 mi
• 160 km gran fondo: 160 × 0.621371 ≈ 99.4194 mi (about a century)

Road Trips

• 120 km: ≈ 74.5645 mi
• 300 km: ≈ 186.411 mi

Speed (km/h ↔ mph)

• 100 km/h × 0.621371 ≈ 62.1371 mph
• 60 mph × 1.609344 ≈ 96.5606 km/h

Pace (min/km ↔ min/mi)

• min/mi = (min/km) × 1.609344
  • Example: 5:00 min/km → 5 × 1.609344 = 8.04672 min/mi (~8:03/mi)
• min/km = (min/mi) ÷ 1.609344

Conversion Chart (Selected Values)

Rounded column shows 2 decimals; exact shows 6 decimals.

Notes:

• For long distances, small rounding differences can add up. Choose precision based on context.

Common Mistakes to Avoid

• Over-simplifying: Using 1 km ≈ 0.6 mi creates large errors at scale
• Mixing mile types: nautical miles (NM) and survey miles are not the same as statute miles
• Rounding too early: Round only at the end to avoid compounding error
• Dropping unit labels: Always include units in UI, reports, and charts
• Using outdated or inconsistent factors: Adopt a single source of truth for constants
• Ignoring significant figures: Match your input data’s precision
• Confusing pace vs speed conversions: Pace (time per unit) inverts the direction of unit conversion

Best Practices for Accuracy and Trust

• Memorize the anchor: 1 mile = 1.609344 km; 1 km = 0.621371 mi
• One constant to rule them all: Store the exact factor centrally (e.g., constants.ts, settings.py)
• Round once, at the end: Display rounding should reflect your UX and domain needs
• Validate regularly: Include unit tests (e.g., 42.195 km → 26.21876 mi; 100 km/h → 62.1371 mph)
• Document your policy: State the factor and rounding approach in README/data catalog
• Label everything: Every number should carry its unit to prevent misinterpretation
• Cite standards: Reference NIST/BIPM so stakeholders know you follow authoritative definitions

Developer & Analyst Corner (Excel, Sheets, Python, JS)

Excel

• Multiply directly: =A2*0.621371
• Native convert: =CONVERT(A2, "km", "mi")
• Round to 3 decimals: =ROUND(CONVERT(A2, "km", "mi"), 3)

Google Sheets

• Multiply: =A2*0.621371
• CONVERT function: =CONVERT(A2, "km", "mi")
• ROUND: =ROUND(CONVERT(A2, "km", "mi"), 5)

Python

from decimal import Decimal, getcontext
getcontext().prec = 28  # high precision for technical work
KM_TO_MI = Decimal('0.621371192237334')  # derived from 1/1.609344
MI_TO_KM = Decimal('1.609344')

def km_to_mi(km: Decimal) -> Decimal:
    return km * KM_TO_MI

def mi_to_km(mi: Decimal) -> Decimal:
    return mi * MI_TO_KM

# Example
print(km_to_mi(Decimal('1')))        # 0.621371192237334
print(mi_to_km(Decimal('26.21876'))) # ≈ 42.195

JavaScript/TypeScript

export const MI_TO_KM = 1.609344 as const;
export const KM_TO_MI = 1 / MI_TO_KM; // 0.621371192237334

export const kmToMi = (km: number, dp = 6) =>
  Number((km * KM_TO_MI).toFixed(dp));

export const miToKm = (mi: number, dp = 6) =>
  Number((mi * MI_TO_KM).toFixed(dp));

// Sanity checks
console.assert(kmToMi(1) > 0.62137 && kmToMi(1) < 0.621372);
console.assert(miToKm(1) === 1.609344);

API/Data Pipelines

• Normalize units on ingestion (e.g., store km internally) and convert on output as needed
• Log both value and unit; keep metadata on rounding policy
• Add regression tests with known pairs (e.g., 100 km → 62.137119 mi)

Statute vs Nautical vs Survey Mile (When It Matters)

• Statute mile (the default “mile”): exactly 1,609.344 meters. Use this for roads, racing, fitness, and everyday distances.
• Nautical mile (NM): exactly 1,852 meters. Used in aviation, maritime navigation, and meteorology.
  • 1 NM = 1.852 km ≈ 1.15078 statute miles
• U.S. survey mile: historically 5,280 survey feet (≈ 1,609.347219 m). It’s retired from official use, but you’ll still see it in legacy GIS/survey datasets. The difference from the statute mile is tiny (~3.219 mm per mile) but relevant for high-precision geodesy.

If your domain is mapping or surveying, confirm which “mile” your data uses.

FAQs

1. How many miles is 1 km?

• 1 km equals 0.621371 miles (rounded). Exact: 0.6213711922 miles.

2. Which is longer, 1 mile or 1 kilometer?

• 1 mile is longer. 1 mile = 1.609344 km.

3. What’s the formula to convert kilometers to miles?

• miles = kilometers × 0.621371 (exactly derived from 1 mi = 1.609344 km).

4. How do I convert miles to kilometers?

• kilometers = miles × 1.609344.

5. How many miles is 5 km?

• 5 km ≈ 3.10686 miles.

6. How many miles is 10 km?

• 10 km ≈ 6.21371 miles.

7. What about 1.5 km to miles?

• 1.5 km ≈ 0.932057 miles.

8. Is 0.62 good enough for quick mental math?

• Yes for estimates. For precise results, use 0.621371 or more decimals.

9. What’s the difference between miles and nautical miles?

• Nautical miles are used for air/sea navigation: 1 NM = 1.852 km ≈ 1.15078 statute miles.

10. Why do some datasets use “survey mile” or “U.S. survey foot”?

• They’re legacy measurements in older GIS/survey data. The survey mile is slightly longer than the statute mile. Modern standards prefer the international (statute) mile.

11. How long does it take to walk 1 km?

• About 10–15 minutes at a comfortable pace (varies by fitness, terrain, and conditions).

12. How many feet is 1 km?

• 1 km ≈ 3,280.84 feet.

13. How do I convert running pace from min/km to min/mi?

• Multiply by 1.609344. Example: 5:30 min/km → 5.5 × 1.609344 ≈ 8.851 min/mi (~8:51/mi).

14. What precision should my app display?

• Fitness/consumer UI: 2–3 decimals. Technical/scientific: 6+ decimals. Consistency matters more than the specific choice.

15. Can I trust search assistants for conversions?

• Generally yes (“1 km in miles”), but standardize your app on a documented constant for reproducibility.

16. Why does rounding differ across platforms?

• Platforms may round to different decimal places (and rounding modes). Specify your rounding policy (e.g., half-up, 3 decimals) to align outputs.

17. How do I avoid cumulative rounding error in code?

• Store raw values, convert with high precision, and round only for display. Avoid repeated round-trip conversions.

References (Authoritative Sources)

• NIST Special Publication 811: Guide for the Use of the International System of Units (SI) (nist.gov)
• International Yard and Pound Agreement (1959) – defines yard as exactly 0.9144 m; statute mile = 1,760 yards = 1,609.344 m (nationalphysical laboratory and NIST summaries)
• BIPM – The International System of Units (SI) Brochure (bipm.org)
• National Oceanic and Atmospheric Administration (NOAA) – Nautical mile definition (noaa.gov)

Internal Link Suggestions (ZenixTools)

• ZenixTools Length Converter (km ↔ mi)
• Miles to Kilometers Converter (reverse lookup)
• Speed Converter (km/h ↔ mph)
• Running Pace Calculator (min/km ↔ min/mi)
• Batch Unit Converter (bulk CSV/JSON conversions)
• Unit Rounding & Formatting Guide (developer documentation)

About This Guide & Update Notes

• Expertise: Prepared by the ZenixTools Editorial Team specializing in measurement standards, technical writing, and developer documentation. Reviewed for 2026 with current definitions and best practices.
• Accuracy policy: Factors sourced from international definitions (NIST/BIPM). We show rounded and exact values, and we recommend a single source-of-truth constant in code.
• Update (2026): Clarified survey vs statute mile impacts for GIS, added pace conversion tips, expanded developer snippets, and refined mental math methods.

Call to Action

Need fast, accurate conversions without the guesswork? Open ZenixTools’ Length Converter to convert km ↔ mi instantly, choose your precision, copy results, or export a neatly formatted table. Perfect for trip planning, race training, homework, and production apps.

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "How many miles is 1 km?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "1 km equals 0.621371 miles (rounded). Exact: 0.6213711922 miles."
      }
    },
    {
      "@type": "Question",
      "name": "What is the formula to convert kilometers to miles?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Use miles = kilometers × 0.621371. For exactness, 1 mile = 1.609344 km, so 1 km = 0.6213711922 mi."
      }
    },
    {
      "@type": "Question",
      "name": "Which is longer, a mile or a kilometer?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "A mile is longer. 1 mile equals 1.609344 kilometers."
      }
    },
    {
      "@type": "Question",
      "name": "What’s the difference between a statute mile and a nautical mile?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "A statute mile is used on land (exactly 1,609.344 m). A nautical mile is used for air/sea navigation (exactly 1,852 m), about 1.15078 statute miles."
      }
    },
    {
      "@type": "Question",
      "name": "How many miles is 10 km?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "10 km is approximately 6.21371 miles."
      }
    }
  ]
}