fl oz: US vs UK
1 fl oz (US)=29.5735 mL(US customary)— US recipes, drink portions, FDA nutrition labels.1 fl oz (UK)=28.4131 mL(imperial)— UK pubs, Commonwealth recipes — about 4% larger than US fl oz.
All processing runs in your browser — no files or inputs are uploaded to a server.
Three measurement systems still appear in daily software. The International System of Units (SI) is the metric system most of the world standardized on, anchored at seven base units (metre, kilogram, second, ampere, kelvin, mole, candela) and using decimal prefixes for every other quantity. US customary units are a separate system grounded in old English measures — inches, pounds, gallons, Fahrenheit — and used almost exclusively inside the United States. Imperial units are a third system, used historically in the British Commonwealth and still surviving in UK road signs, pub measures, and weather forecasts; they overlap with US customary in name but not always in value.
The tool above lets you flip between them. Two practical points follow. Multiplying within one system is safe (1 km is 1,000 m, always). Crossing systems is not — 1 fl oz of milk in a US recipe is not the same volume as 1 fl oz in a British one, and software that ignores the difference can drift far enough in recipe scaling or freight pricing to break the result.
SI prefixes scale a base unit by powers of 1,000. The same prefix attaches to any base — kilometre, kilogram, kilowatt, kilobyte (when used in the SI sense) — and means the same multiplier everywhere. This regularity is the practical reason SI dominates scientific publishing.
| Symbol | Name | Power | Factor |
|---|---|---|---|
| k | kilo | 10^3 | 10³ |
| M | mega | 10^6 | 10⁶ |
| G | giga | 10^9 | 10⁹ |
| T | tera | 10^12 | 10¹² |
| P | peta | 10^15 | 10¹⁵ |
| E | exa | 10^18 | 10¹⁸ |
These pairs catch teams that build internationally — same name on each side of an ocean, different value. The numbers below match what the tool above uses internally.
1 fl oz (US)=29.5735 mL(US customary)— US recipes, drink portions, FDA nutrition labels.1 fl oz (UK)=28.4131 mL(imperial)— UK pubs, Commonwealth recipes — about 4% larger than US fl oz.1 gal (US)=3.78541 L(128 US fl oz)— US fuel pumps, milk jugs.1 gal (UK)=4.54609 L(160 UK fl oz)— UK fuel duty and historical Canadian recipes — about 20% larger than US.1 metric ton (t)=1,000 kg(SI)— International trade, ISO documents, every non-US country.1 short ton (US)=907.185 kg(2,000 lb)— US weights and measures act.1 long ton (UK)=1,016.05 kg(2,240 lb)— Royal Navy displacement, UK shipping.Temperature is not a linear quantity in the way length or mass are. "Twice as cold" has no fixed meaning because the scales start from different points. Celsius zero is the freezing point of water; Fahrenheit zero is roughly the freezing point of a salt brine the 18th-century instrument-maker Daniel Fahrenheit calibrated against; Kelvin zero is absolute zero, the lower limit of thermodynamic temperature.
That means conversion is affine, not multiplicative. The formula C → F is F = C × 9/5 + 32; C → K is K = C + 273.15. Multiplying a Celsius temperature by a factor produces nonsense (3 × 25°C is not "three times hotter," just a new Celsius value that may not match any physical quantity). When subtracting temperatures to get a difference, however, the offset cancels: the temperature difference 10°C → 25°C is 15 K, full stop.
For decades "kilobyte" meant 1,024 bytes inside an operating system and 1,000 bytes on a hard-drive box. The International Electrotechnical Commission resolved the ambiguity in 1998 by introducing binary prefixes — KiB, MiB, GiB — that explicitly mean 2^10, 2^20, 2^30 bytes. Strict usage today: kB/MB/GB for powers of 1,000, KiB/MiB/GiB for powers of 1,024. The discrepancy grows with size.
In practice, storage and network speeds advertise SI values (a "1 TB drive" is 10^12 bytes), while RAM and operating systems mostly report binary (Linux and macOS show file sizes in binary, Windows reports binary but labels the numbers with the SI suffix "GB," which is what causes the "my new 500 GB drive only has 465 GB" complaint — it's 500 × 10^9 bytes shown as 465 × 2^30, not missing space).
| SI (decimal) | IEC (binary) | Binary excess |
|---|---|---|
| kB1,000 B | KiB1,024 B | +2.4% |
| MB1,000,000 B | MiB1,048,576 B | +4.9% |
| GB1,000,000,000 B | GiB1,073,741,824 B | +7.4% |
| TB10¹² B | TiB1,099,511,627,776 B | +10.0% |
| PB10¹⁵ B | PiB1.126 × 10¹⁵ B | +12.6% |
Pick a category (length / weight / temperature / time / area / volume / speed / data size), enter a number in any unit, and every other unit in that category updates simultaneously. Swap input units freely — the math is symmetric, so entering 1 meter or 39.37 inches produces the same row of conversions, just with the focus on a different cell.
Reach for this for everyday conversions where remembering the constant is overkill: cm ↔ inches for a screen size, kg ↔ lbs for a recipe scaled across regions, °C ↔ °F for travel weather, m² ↔ ft² for apartment listings, MB ↔ MiB ↔ GB when reading both decimal and binary storage figures. The conversion factors are based on the SI definitions (2019 revision); for currency, exchange rates are not included because they change minute-to-minute and a static value would be misleading — use a dedicated FX tool that pulls live rates.
category: length input: 5.75 ft (or 69 inches)
meters: 1.7526 centimeters: 175.26 millimeters: 1752.6 inches: 69.0 yards: 1.917
A typical height conversion. 5'9" is 69 inches, which is 1.7526 meters or about 175 cm. The exact conversion is 1 inch = 2.54 cm by international agreement (1959 yard-and-pound agreement), so the math is bit-exact at any practical precision — no rounding drift.
category: temperature input: 100 °F
°C: 37.78 K: 310.93 °R: 559.67
Temperature is the awkward one — `°C = (°F − 32) × 5/9` is an affine transformation, not a linear one, because the zero points differ. Body temperature 100°F = 37.78°C; freezing 32°F = 0°C; absolute zero −459.67°F = −273.15°C = 0 K. Kelvin and Celsius share scale (1 K = 1 °C step), Rankine and Fahrenheit share scale (1 °R = 1 °F step), but each pair has a different offset.
category: data input: 1 GiB
bytes: 1,073,741,824 KB (decimal): 1,073,741.824 KiB (binary): 1,048,576 MB (decimal): 1,073.741 MiB (binary): 1,024 GB (decimal): 1.074 TB (decimal): 0.001074
The decimal-binary gap is the source of the "my 1 TB drive only shows 931 GB" complaint. Disk manufacturers sell decimal TB (10^12 bytes); operating systems display binary TiB (2^40 = 1.0995 × 10^12 bytes). The ratio is 1024^3 / 1000^3 ≈ 1.074 for GB, growing to 1.0995 for TB. IEC binary prefixes (KiB / MiB / GiB / TiB, 1998) made the distinction explicit, but software keeps mixing them. Network speeds are always decimal (a 1 Gbps link transfers 10^9 bits per second).
The US gallon is 3.785 liters (228 in³); the UK / Imperial gallon is 4.546 liters (277.42 in³) — about 20% bigger. The fluid ounce also differs (US 29.57 mL vs UK 28.41 mL), and other "common" volume units like pint and quart inherit the same split. A US recipe scaled to UK measurements without conversion ends up with the wrong proportions. The same word "gallon" on a fuel pump in Texas and a fuel pump in London is two different volumes — fuel efficiency comparisons "mpg" should always specify which.
1 inch is *exactly* 2.54 cm by international agreement, so 1 meter = 100 / 2.54 = 39.37007874... inches. The converter shows 4 significant digits because that is typically enough for everyday work; for engineering use, increase precision via the "decimals" setting if available, or compute manually. Rounding to 39.4 saves a digit but loses accuracy at the 0.08% level — not material for clothing sizes, very material for machining.
Exchange rates change minute-to-minute and a static converter would lie. A reasonable currency tool needs a live FX feed (oanda, fixer.io, ECB, Open Exchange Rates), per-currency precision rules (JPY has no decimals, BHD has 3), and ideally support for bid/ask spreads. That is enough complexity to deserve its own dedicated tool with its own data source disclosure — bolting it onto a units converter would be misleading. For one-off conversions Google search (`100 USD in JPY`) is usually fine; for repeated use, use a financial API client.
The seven SI base units (meter, kilogram, second, ampere, kelvin, mole, candela) are the agreed-upon foundation from which every other unit is derived. Since the 2019 SI revision, all seven are defined in terms of physical constants (the kilogram via Planck's constant, the meter via the speed of light, the second via cesium atomic transitions) — no more physical artifacts in vaults. The benefit for unit conversion is exactness — converting kg ↔ lb is now a fixed rational number (1 lb = 0.45359237 kg by international agreement) that does not drift with how well a reference kilogram in Paris is preserved.
For most pairs, exact within the displayed digits — the conversion factors are international-treaty constants stored as JavaScript Numbers (IEEE 754 double, ~15 significant decimal digits). The output rounds to a sensible number of decimals (typically 4–6) for readability, but the internal math runs at full Number precision. For exotic units (cubits, light-years, Planck length) the source value itself may be uncertain — `1 light-year` rounds to `9.461 × 10^15 meters` but the IAU's exact definition uses the Julian year. For engineering work needing arbitrary precision, use a CAS like Mathematica or Python with `Decimal`.
A knot is 1 nautical mile per hour, used in maritime and aviation. 1 knot = 1.852 km/h ≈ 1.151 mph. The nautical mile (1852 meters) was originally defined as 1 minute of latitude, which makes it convenient for navigation by sextant — moving 60 nautical miles is moving one degree of latitude along a meridian. Other less-common speed units the converter handles: **Mach** is the speed of sound (~1235 km/h at sea level, but altitude-dependent), **c** (speed of light) is 299,792,458 m/s exactly. Use the units your domain expects rather than mechanically converting.
Unit systems are conventions for measuring physical quantities, and the world runs two big ones plus stragglers. The **SI** (Système international d'unités, 1960, updated 2019) is the international scientific standard, used by every country except the US, Liberia, and Myanmar for everyday measurement, and used by every country including the US for scientific work. The **US customary** and **imperial** systems share roots but diverge — the US "gallon" is smaller than the British, the US "ton" (2000 lbs short ton) differs from the British "ton" (2240 lbs long ton) and from the metric tonne (1000 kg). Conversion tools mostly bridge these three families.
The **2019 SI redefinition** quietly fixed a long-standing scientific embarrassment: until then, the kilogram was defined by a literal platinum-iridium cylinder in a vault in Sèvres, France. Variations in the cylinder's mass over time were detectable. Since 2019, all seven SI base units are defined in terms of fundamental physical constants — the Planck constant, the speed of light, the cesium atomic transition frequency, Avogadro's number, the elementary charge, the Boltzmann constant, and the luminous efficacy. Conversions between SI units are now exact rational numbers tied to these constants rather than tied to an artifact.
Three adjacent concepts shape the day-to-day. **Decimal vs binary prefixes**: kilo / mega / giga are 10^3 / 10^6 / 10^9 in SI, while kibi / mebi / gibi (KiB / MiB / GiB, IEC 60027-2, 1998) are 2^10 / 2^20 / 2^30 in computing. Drive manufacturers use decimal, operating systems use binary, network engineers use decimal — explaining "why my 1 TB drive only has 931 GB". **Temperature offset vs scale**: most unit conversions are scalar multiplications, but temperature requires an affine transformation because the zero points differ (0°C is not 0°F is not 0 K). **Currency** lives outside this — exchange rates fluctuate, so currency belongs in its own category with live data, not in a static unit converter.
Format and validate JSON. Indented or minified output, with clear error messages.
Encode text to Base64 or decode Base64 back to text. UTF-8 safe.
Percent-encode or decode URL components.
Decode JWT header and payload locally. Signature is not verified — paste tokens at your discretion.