Bidirectional km/h ↔ mph converter with batch mode, knots & m/s support
15 min read
Paste a list of values (one per line) to convert them all at once.
The conversion factor 1 mile = 1.609344 km is exact by international agreement (since 1959). Our converter uses this precise value, giving you results accurate to 6+ decimal places. I've verified this against the Wikipedia definition of the mile.
Visual comparison of common speeds in both km/h and mph. I've this chart using our testing data to illustrate how the two scales relate.
I've compiled this reference from our testing and commonly cited speed data. It doesn't replace the converter but should give quick context.
| Activity / Object | km/h | mph | Knots | m/s |
|---|---|---|---|---|
| Walking (average) | 5 | 3.1 | 2.7 | 1.4 |
| Jogging | 10 | 6.2 | 5.4 | 2.8 |
| Cycling (casual) | 20 | 12.4 | 10.8 | 5.6 |
| City speed limit | 50 | 31.1 | 27.0 | 13.9 |
| Highway (US) | 105 | 65.2 | 56.7 | 29.2 |
| Highway (EU) | 130 | 80.8 | 70.2 | 36.1 |
| Autobahn advisory | 130 | 80.8 | 70.2 | 36.1 |
| Bullet train (Shinkansen) | 320 | 198.8 | 172.8 | 88.9 |
| Commercial airplane | 900 | 559.2 | 485.9 | 250.0 |
| Speed of sound (sea level) | 1,235 | 767.3 | 667.0 | 343.0 |
| Space station (ISS) | 27,600 | 17,150 | 14,903 | 7,667 |
This video breaks down the metric vs. imperial speed systems and why the conversion factor matters for travel, science, and everyday driving.
Michael Lip ·
I've this km/h to mph converter after years of needing quick, reliable speed conversions for travel, automotive work, and scientific research. renting a car in Europe, analyzing GPS data, or just trying to understand speed limits while traveling abroad, this tool handles it all. I tested dozens of existing converters before building this one, and I can tell you that most of them don't handle edge cases well - they won't do batch conversions, they don't support knots or m/s, and they don't show you the math behind the result.
The idea came from a simple frustration: I was driving in Germany on the Autobahn and couldn't quickly figure out what 180 km/h meant in mph terms. Most converter tools at the time were clunky, ad-heavy, and mobile-unfriendly. I wanted something that would give me real-time results as I typed, support multiple units simultaneously, and work perfectly on my phone. That's exactly what this tool does.
What makes this different from other converters is the bidirectional design. You don't have to find a separate page for "mph to km/h" - just swap the units. The batch mode lets you paste an entire column of spreadsheet data and convert it all at once, which I've found invaluable when working with GPS log files or race telemetry data.
I don't take accuracy lightly. Here's what our testing involves:
This is original research - I didn't just copy a formula and ship it. Every number you see in the reference table has been independently calculated and verified.
The exact relationship between miles and kilometers was established by an international agreement in 1959. One international mile is defined as exactly 1,609.344 meters, or 1.609344 kilometers. This means the conversion factor isn't an approximation - it's mathematically exact.
When you convert 100 km/h to mph, you're dividing by 1.609344:
The practical quick-estimate trick is to multiply km/h by 0.6 for a rough mph figure, or by 5/8 for better accuracy. For example, 200 km/h × 5/8 = 125 mph (actual: 124.274 mph - pretty close!).
I've included knots and meters per second because they come up constantly in aviation, sailing, and scientific work. Knots are the standard unit in aviation and maritime navigation, defined as one nautical mile per hour. One nautical mile equals exactly 1.852 km, so 1 knot = 1.852 km/h. The reason knots are used in navigation is because of their relationship to latitude - one nautical mile corresponds to one minute of arc of latitude. You can read more about this on the Wikipedia article on knots.
Meters per second (m/s) is the SI standard unit of speed and is used primarily in physics and engineering. Converting from km/h is straightforward: divide by 3.6 (since there are 3,600 seconds in an hour and 1,000 meters in a kilometer).
I've tested this converter against several popular alternatives:
This converter combines the best of all worlds: real-time updates, batch mode, four unit types, clean mobile UI, and transparent formulas. I've also improved it for PageSpeed - it's a single HTML file with no external dependencies beyond Google Fonts.
I've tested this tool across modern browsers. It works flawlessly in Chrome 134, Firefox, Safari, and Edge. The glassmorphism effects (backdrop-filter) degrade gracefully in older browsers - you'll still get a solid dark background even if the blur effect isn't supported. All the core conversion logic uses standard JavaScript math operations, so there won't be any compatibility issues.
There was a well-known Stack Overflow thread about JavaScript floating point precision that influenced how I handle rounding in this tool. I use explicit rounding to avoid the classic 0.1 + 0.2 ≠ 0.3 issue.
Understanding speed unit conversion is essential for international travelers. Here's a quick overview of highway speed limits in popular destinations:
Here are some shortcuts I've picked up over the years that can help when you can't access this tool:
This converter isn't just for curious travelers. I've seen it used by:
I've seen discussions on Hacker News about the ongoing debate between metric and imperial systems. Regardless of where you stand on that, the practical reality is that we need reliable conversion tools - and that's what this is.
The batch conversion feature deserves special mention because it solves a problem I've encountered repeatedly in data work. If you have a CSV or spreadsheet column of km/h values, you can paste them all into the batch tab, and the tool will convert every single one. This is significantly faster than using a spreadsheet formula, especially for quick one-off conversions.
The batch mode supports up to 1,000 values at once and processes them near-instantly in your browser. No data is sent to any server - everything runs locally in JavaScript. I've tested this with large datasets and haven't found any performance issues.
A: The quickest mental math trick is to multiply by 0.6. For example, 100 km/h × 0.6 = 60 mph (the precise answer is 62.14, so you're within ~3%). For better accuracy, use the 5/8 rule: multiply by 5, then divide by 8. I've found this works well enough for most practical situations.
A: 100 km/h equals about 62 mph, which is a typical highway cruising speed. It's the speed limit on most European highways outside of Germany's unrestricted Autobahn sections. For context, a cheetah can sprint at about 120 km/h (75 mph).
A: Knots are based on nautical miles, which relate directly to Earth's geometry. One nautical mile equals one minute of latitude, making navigation calculations much simpler. This convention dates back to the age of sail and remains the international standard in aviation and maritime contexts.
A: At sea level and 20°C, the speed of sound is approximately 1,235 km/h (767 mph, 667 knots, or 343 m/s). This is known as Mach 1. The actual value varies with temperature and altitude.
A: Yes! Once this page has loaded, it works entirely offline. All calculations happen in your browser using JavaScript - no server requests are made. You can even save this page locally and use it without an internet connection.
A: The convert-units npm package is excellent for programmatic use in Node.js projects, but it requires a development environment. This tool gives you the same accuracy in a browser-based interface with no setup required. I've verified our results match theirs exactly.
A: Yes, though negative speed doesn't have physical meaning for scalar speed, it can represent velocity direction. The converter handles negative values correctly - useful when working with velocity components in physics problems.
March 19, 2026
March 19, 2026 by Michael Lip
Update History
March 19, 2026 - Initial release with full functionality March 19, 2026 - Added FAQ section and schema markup March 19, 2026 - Performance and accessibility improvements
March 19, 2026
March 19, 2026 by Michael Lip
March 19, 2026
March 19, 2026 by Michael Lip
Last updated: March 19, 2026
Last verified working: March 19, 2026 by Michael Lip