About Everyday Converters
Each of the three has a trap. Roman numerals carry no zero and no place value, a kilobyte means 1,000 or 1,024 bytes depending on who is counting, and fuel economy inverts between the two systems — a higher MPG is better while a higher L/100km is worse.
Convert data sizes between bytes, KB, MB, GB and TB using 1024-based steps — useful for sizing files, downloads and storage quotas. The conversion runs locally in your browser.
Convert numbers to and from Roman numerals, change data sizes between bytes, kilobytes, megabytes, gigabytes and beyond, and translate fuel economy across MPG, L/100km and km/L. It bundles three common conversions you reach for surprisingly often.
Everything works offline in your browser. Decode a Roman numeral on a monument, size a file or download, or compare a car's fuel efficiency between regional standards in seconds.
Roman numerals have no zero and no place value, which is why they are read by addition and subtraction rather than by position. A smaller numeral before a larger one is subtracted — IV is four, IX is nine — and only certain pairs are permitted in the standard form, which is why 1999 is MCMXCIX rather than the tidier-looking MIM. That constraint is the usual reason a hand-written conversion disagrees with a correct one.
Data sizes are ambiguous by convention rather than by error. Drive manufacturers count a gigabyte as 1,000,000,000 bytes while many operating systems report binary gibibytes of 1,073,741,824, and the gap widens as the units grow — which is the entire explanation for a 1 TB drive showing up as roughly 931 GB with nothing missing and nobody at fault. Fuel economy carries a different trap: MPG and L/100km run in opposite directions, so a higher number is better in one and worse in the other.
Common use cases
- Working out why a drive shows less capacity than advertised
- Converting a download speed into a realistic transfer time
- Checking whether a file fits a storage or upload quota