Unit Converter

They are different. A kilobyte (kB) is 1000 bytes, the decimal unit drive makers and network speeds use; a kibibyte (KiB) is 1024 bytes, the binary unit operating systems use when they report file and memory sizes. The same distinction applies to MB vs MiB, GB vs GiB and TB vs TiB, and the gap grows at each step.

Celsius, Fahrenheit and Kelvin scales have different zero points, so a single multiplier cannot convert them. The tool applies the proper formulas — Fahrenheit is (°C × 9/5) + 32, Kelvin is °C + 273.15 — which is why −40 °C and −40 °F come out equal.

Conversions use exact standard factors and are shown to about six significant figures, with trailing zeros trimmed and scientific notation for very large or very small values. The year unit is a flat 365 days.

Ten: length, mass, temperature, area, volume, speed, data size, time, pressure and energy — the everyday SI and imperial/US units in each (metres and miles, kilograms and pounds, litres and US gallons, kilopascals and psi, kilocalories and BTU). The list favors units people actually convert day to day over encyclopaedic completeness; specialist units like troy ounces are one fixed factor away from any calculator.

Exact standard factors, full floating-point precision, displayed to about six significant figures: 26.2 miles returns 42.1648128 km, 98.6 °F returns exactly 37 °C, and exact integers print in full rather than rounding away. Nothing is sent to a server, and no factor silently updates behind you — a conversion produces the same answer today and tomorrow.

Its scales differ in zero point, not just in step size, so one multiplier cannot convert them. The tool applies the offset formulas directly — °F = (°C × 9/5) + 32, K = °C + 273.15 — which is why −40 reads identically in Celsius and Fahrenheit, and why converting 'naively' by scale alone is wrong by tens of degrees every time.

They are different quantities: a gigabyte is decimal — 1,000,000,000 bytes, the unit drive makers and network speeds use — while a gibibyte is binary — 1,073,741,824 bytes, the unit operating systems report for memory and files. A new '1 TB' drive showing about 931 GiB is the same gap at scale, not lost bytes. The other magnitude pairs (MB/MiB, TB/TiB) drift the same way, and the tool keeps them explicit so a data-cap calculation never mixes them.

No — that needs a density (water is 1 kg/L, honey about 1.42), and a converter that guessed one would be wrong for every substance except water. The tool rejects cross-category requests for the same reason it rejects 'watts to BTU per hour' confusion: dimensions must match. Convert the units within a category here, apply the physics constant yourself at the edge.

A flat 365 keeps time-unit conversions simple and reproducible: a year is exactly 31,536,000 seconds, with no leap-day wobble. That is the right semantics for durations — a 3-year warranty, a half-year of interest. For calendar questions (what date is 3 years from today), that convention is the wrong tool; the date tools count real calendar years.

Through scientific notation, cleanly: a mebibyte in kilobytes is exactly 1.048576, while values beyond 1e15 or below 1e-4 display as a trimmed exponential rather than a wall of zeros. The underlying arithmetic stays float-exact for the factors involved — the display layer, not the math, is what changes at the extremes.