Unit Converter
Length, weight, temperature, volume, speed, data, area, time — type in either box.
Length, weight, temperature, volume, speed, data, area, time — type in either box.
Unit Converter quickly converts length, weight, temperature, volume, speed, data size, area, time and more. Type a value into either box and the other updates instantly, with no extra buttons to press. Precision is adjustable (three to twelve decimals) and every conversion can be shared through its own link. It's handy in the kitchen, at school, while traveling and at work.
Yes. The result updates whichever box you type in.
Conversions use standard factors. For scientific or engineering work, check how many decimals are shown.
A megabyte (MB) is 1,000 × 1,000 bytes, while a mebibyte (MiB) is 1,024 × 1,024 bytes. Operating systems often mix them up, so it helps to know which one you're looking at.
The five minutes that save you from the unit bugs that survive code reviews. · 6 min read
SI prefixes are case-sensitive: k = kilo (1000), K = kelvin (temperature), m = milli (1/1000) while M = mega (1,000,000). One mis-set case turns a millisecond timer into megaseconds or a kilobyte into a kelvinbyte, and both bugs have shipped in production systems. The prefixes above kilo step by 1000 (M, G, T), and below milli by 1/1000 (μ, n).
Storage vendors quote decimal units: 1 MB = 1,000,000 bytes, 1 TB = 10¹² bytes. Operating systems often report binary units: 1 MiB = 1,048,576 bytes (2²⁰). A '1 TB' drive therefore reports as about 931 GiB — no space is missing; the labels are just counting in different bases. The same trap lives inside code: bandwidth math is nearly always decimal, memory math is nearly always binary, and mixing them inflates or shrinks results by up to 7.4%.
The IEC prefixes (KiB, MiB, GiB, TiB) exist precisely to disambiguate. If you are writing an SLA or a spec, prefer them for binary quantities; if you must write MB, say in a footnote which base you mean.
Temperature is the odd one out: Celsius and Fahrenheit differ by an offset, not just a factor (°F = °C × 9/5 + 32), which is why 'multiply by 1.8' alone is always wrong. Wind speed has a hidden context too: aviation reports knots, meteorology often uses metres per second or km/h, and US forecasts use mph. Converting the wrong pair gives plausible-looking nonsense, which is the most dangerous kind of unit bug.
Fuel economy is a double trap: mpg is inverted between US (miles per gallon) and imperial gallons, and l/100km runs in the opposite direction (bigger number = thirstier), so 'higher is better' flips when you cross units.
Converting does not create precision: 2 inches is exactly 5.08 cm, but a measurement recorded as '2 inches' was probably 5.1 cm at best. Report conversions with roughly the same significant figures as the source (three or four), and let the converter's precision setting match the instrument, not your hopes. For engineering work, note the rounding convention once and keep it consistent across the document.