The Complete Guide to Unit Conversion: Metric, Imperial, Data and Cooking Units
Every day, people all over the world translate one measurement language into another. A recipe written in cups has to become grams. A hard drive advertised as one terabyte shows up as 931 gigabytes on the computer. A weather report says 95°F and you need to know whether that is dangerously hot or merely warm. Unit conversion is the quiet plumbing of modern life, and a good unit converter removes the friction in seconds.
At its core, converting a unit is simple arithmetic: multiply by a conversion factor. One mile is defined as exactly 1,609.344 meters, so ten miles is 16,093.44 meters. The difficulty is never the multiplication. It is remembering which factor applies, keeping decimal and binary data units straight, and knowing that a cup of flour and a cup of honey are not remotely the same weight. This guide walks through every family of units that UnitShift converts — length, weight, temperature, area, volume, speed, digital data, and cooking — with the facts, formulas and gotchas that search engines and textbooks often bury.
Why the world still uses two measurement systems
The metric system, formalized in France in the 1790s and now maintained as the International System of Units (SI), is used officially by nearly every country. The United States, Liberia and Myanmar are the famous holdouts, and the UK lives in a hybrid world of miles on the road and liters at the petrol pump. Imperial and US customary units evolved organically — the foot was once literally a foot, the mile a thousand Roman paces — which is why their conversion factors look so arbitrary: 5,280 feet in a mile, 16 ounces in a pound, 4 quarts in a gallon.
Metric units, by contrast, scale by powers of ten. A kilometer is a thousand meters, a milligram a thousandth of a gram. That regularity is why science, medicine and international trade run on metric. But imperial units are deeply embedded in construction, aviation, cooking and everyday speech in the US, so fluent conversion between the systems is a practical skill. When in doubt, convert with a tool rather than memory: the cost of a wrong factor in engineering or medicine is far higher than the seconds it takes to check.
Length: the workhorse category
Length conversions are the most searched of all, and the anchor conversions are worth memorizing. One inch is exactly 2.54 centimeters. One meter is about 3.28084 feet, and one kilometer is about 0.621371 miles — which is why the rough rule "multiply kilometers by 0.6 to get miles" works for quick estimates. A nautical mile, used in aviation and shipping, is defined as exactly 1,852 meters, corresponding to one minute of latitude. Precision matters here: the inch was redefined in 1959 as exactly 25.4 millimeters by international agreement, so modern length conversion is exact, not approximate.
Weight and mass: grams to pounds without the guesswork
The pound is defined as exactly 0.45359237 kilograms, and the ounce as exactly 28.349523125 grams. The stone, still common in the UK and Ireland for body weight, is 14 pounds or about 6.35029 kilograms. One common trap: the metric tonne (1,000 kg) versus the US short ton (2,000 lb, about 907 kg) versus the long ton (2,240 lb). They differ by roughly ten percent, which matters enormously in shipping and commodities. Always confirm which "ton" a document means before converting.
Temperature: the only category that needs a formula, not a factor
Temperature is special because the scales do not share a zero point. You cannot convert Celsius to Fahrenheit by multiplication alone; you need an offset. The formulas are: °F = °C × 9/5 + 32, and °C = (°F − 32) × 5/9. Kelvin, the SI unit, starts at absolute zero: K = °C + 273.15. A few landmarks help calibration: water freezes at 0°C (32°F, 273.15K) and boils at 100°C (212°F, 373.15K). Human body temperature is about 37°C (98.6°F). Note that below −273.15°C nothing can exist — a converter should refuse results colder than absolute zero, and UnitShift does.
Area and volume: squares and cubes multiply the confusion
Area and volume units are the squares and cubes of length units, which means their factors grow fast. One square mile is about 2.59 square kilometers; one acre, the classic real-estate unit, is 4,046.86 square meters or about 0.4047 hectares. For volume, the US customary system is a thicket: 3 teaspoons make a tablespoon, 2 tablespoons a fluid ounce, 8 fluid ounces a cup, 2 cups a pint, 2 pints a quart, 4 quarts a gallon. A US gallon is 3.78541 liters — importantly different from the imperial gallon of 4.54609 liters still referenced in some Commonwealth contexts. When a recipe says "gallon," US sources almost always mean the US gallon, but fuel-economy figures from the UK use imperial gallons, a classic source of confusion.
Speed: from kilometers per hour to knots
Road speeds are the everyday case: 1 mile per hour equals exactly 1.609344 kilometers per hour, and 1 kilometer per hour equals about 0.621371 mph. The meter per second is the SI unit, handy because 1 m/s equals exactly 3.6 km/h. Knots — one nautical mile per hour, or about 1.852 km/h — dominate aviation and maritime use because they tie directly to charts measured in minutes of latitude. A useful mental benchmark: 100 km/h is about 62 mph, and a typical highway cruise of 120 km/h is roughly 75 mph.
Digital data: the MB vs MiB problem, finally explained
Data units are where most converters quietly get it wrong, because there are two competing systems. The decimal (SI) system uses powers of 1,000: 1 kilobyte (KB) = 1,000 bytes, 1 megabyte (MB) = 1,000,000 bytes, 1 gigabyte (GB) = 1,000,000,000 bytes. This is what storage manufacturers print on boxes. The binary (IEC) system uses powers of 1,024: 1 kibibyte (KiB) = 1,024 bytes, 1 mebibyte (MiB) = 1,048,576 bytes, 1 gibibyte (GiB) = 1,073,741,824 bytes. This is how operating systems and RAM actually count.
That mismatch is exactly why a "1 TB" hard drive shows about 931 GiB in Windows: the drive holds 1,000,000,000,000 bytes (decimal terabytes), but the OS divides by 1,073,741,824 (gibibytes). The gap widens with size — about 2.4% at kilo scale, 4.9% at mega, 7.4% at giga, 10% at tera. A converter that treats KB and KiB as the same unit will give you subtly wrong answers for RAM, disk partitions and network planning. UnitShift keeps both systems separate and labels them, so converting 16 GiB of RAM to GB gives the honest 17.18 GB rather than a hand-waved 16.
Bits versus bytes is the other classic trap. Network speeds are quoted in bits (100 Mbps), while file sizes are quoted in bytes (a 100 MB download). Since one byte is eight bits, a 100 Mbps connection downloads at about 12.5 MB/s in ideal conditions — not 100. Divide any "bps" figure by eight before comparing it to a file size.
Cooking conversions: why cups do not equal grams
Volume-to-weight conversion in the kitchen depends on density, and density depends on the ingredient. One US cup is always 236.588 milliliters — that part is fixed. But a cup of all-purpose flour weighs about 120 grams, a cup of granulated sugar about 200 grams, a cup of butter about 227 grams, and a cup of honey about 340 grams. Same cup, wildly different weights, because flour is fluffy and honey is dense. This is why professional bakers weigh ingredients: volume measures space, and space includes air.
UnitShift's cooking mode handles this with a density table for fourteen common ingredients, from flour and sugar to oil, milk, oats, rice and salt. Pick the ingredient, enter cups, tablespoons or milliliters, and get grams — or go the other way when a European recipe gives grams and your kitchen thinks in cups. Two caveats keep you honest. First, densities vary with how you fill the cup; "spooned and leveled" flour can differ from scooped flour by 20% or more, so published values are references, not laboratory constants. Second, brown sugar is usually measured packed, which is why its cup weight (about 220 g) exceeds granulated sugar's. For bread and pastry where precision decides the outcome, a ten-dollar kitchen scale beats every converter ever built — UnitShift just makes the days without one far less painful.
How to get the most out of UnitShift
Start by picking the measurement family on the switch bank — length, weight, temperature, area, volume, speed, data, or cooking. Type a value, choose the source and target units, and the result appears instantly on the output display. The big round knob swaps the two units with one tap, which is handy when you realize you set the conversion backwards. The precision control sets how many decimal places appear; two decimals suit money and cooking, six suit engineering homework. Below the deck, the full instrument readout shows your value in every unit of the family at once — useful when you want to see miles, feet and inches together instead of converting three times.
Two features deserve special mention. The cooking mode, described above, is something most general converters simply do not offer; they convert cups to milliliters and leave the grams question unanswered. And the recent-conversions history, saved privately in your own browser, lets you tap any past conversion to reload it instantly — no account, no tracking, nothing leaving your device. Everything runs locally in the page, which also means UnitShift keeps working with the numbers you have already typed even if your connection drops.
A final word on accuracy: UnitShift uses exact defined factors (the 1959 inch, the 1959 pound, the 1,852-meter nautical mile, the IEC binary prefixes) rather than rounded approximations, and it formats results without silently rounding the underlying value. Copy the result with the copy button when you need the full precision in a document or spreadsheet. Whether you are scaling a recipe, sizing a hard drive, checking a fever, or converting a road trip from miles to kilometers, the goal is the same: the right number, in the right unit, in under five seconds.