Ounces to Kilograms Converter

What this converter does

It converts avoirdupois ounces to kilograms — the direction needed when an American specification, product listing or postal figure has to be expressed for a metric context. The constant is exact and the arithmetic is a single multiplication, but the ounce carries enough near-namesakes that knowing which ounce you hold is more important than the calculation itself.

The formula

Multiply ounces by exactly 0.028349523125. That constant is the defined ounce expressed in kilograms: the international pound is exactly 0.45359237 kg, and the avoirdupois ounce is exactly one sixteenth of it. A useful consequence is that 16 oz converts to exactly 0.45359237 kg — the pound, recovered with no rounding at all, which makes it a good self-test for any converter you are checking.

Worked examples

A 12 oz product is 0.34 kg. A 32 oz container is 0.907 kg, which is two pounds. A 5 oz portion is 0.142 kg. And the whole-pound multiples land on recognisable values: 48 oz is 1.361 kg, 64 oz is 1.814 kg, and 160 oz is 4.536 kg — each one the pound constant scaled up, which is why the digits 4536 keep reappearing throughout this cluster.

Where this conversion is needed

Import and export paperwork leads: American products specified in ounces need metric declarations for customs and for labelling in most of the world. Freight is second, since shipping outside the US is charged on kilograms while the goods were speced in ounces. Third is the everyday case of fitness and food logging, where American scales, supplements and packaged foods report ounces while apps and health records increasingly expect kilograms.

Fluid ounces are not this unit

The most common category error on any ounce page. A fluid ounce measures volume — about 29.6 mL in US usage — and cannot be converted to mass without knowing the density of what fills it. The confusion persists because water is nearly the coincidence case: one fluid ounce of water weighs about 1.04 ounces, close enough that the error hides. It stops hiding immediately with anything denser or lighter. If the ingredient is a liquid and the recipe is American, assume fluid ounces and find the millilitres instead.

Converting pounds-and-ounces figures

A weight given as pounds and ounces cannot be typed as a decimal: 3 lb 8 oz is not 3.8 of anything. Convert it to total ounces first — pounds times 16, plus the ounces — so 3 lb 8 oz becomes 56 oz, which is 1.588 kg. Better still, use the pounds and ounces to kilograms converter linked below, which takes the two numbers in separate boxes and performs the sixteen-to-one carry itself. Doing that arithmetic by hand is where most errors in this direction originate.

Precision and disagreement between sources

The factor is exact, so two correct converters cannot disagree — any difference is one of them rounding earlier. The usual culprit is the 28 g ounce from US nutrition labelling, which is 1.2 percent light. A chart built on it will show 16 oz as 448 g rather than 453.6 g, and the discrepancy grows with quantity. Where a figure will be invoiced, audited or declared, use the exact constant; where it is a serving size, the rounding is immaterial.

Common mistakes

Reading fluid ounces as weight, as above. Treating a troy figure as avoirdupois, which understates precious metal by nearly ten percent. Typing a pounds-and-ounces weight as a decimal. And double-converting: recipes and listings republished across markets sometimes carry both an ounce figure and an already-rounded metric one, and converting the ounces again produces a third number that agrees with neither. When a source gives both, prefer the metric figure and stop there.

Benchmarks

1 oz is 0.028 kg. 4 oz is 0.113 kg. 8 oz is 0.227 kg. 12 oz is 0.340 kg. 16 oz is 0.454 kg, one pound exactly. 24 oz is 0.680 kg. 32 oz is 0.907 kg. 64 oz is 1.814 kg. 160 oz is 4.536 kg, ten pounds. The sixteen-ounce pound at 0.4536 kg is the anchor everything else scales from.

Accuracy and limits

Exact factor, exact decimal arithmetic, display-only rounding, and a parser that refuses ambiguous input rather than guessing at it. Avoirdupois weight only: troy ounces have their own pages, fluid ounces are a volume this tool will not pretend to convert, and mass is not force, which is why no gravity value is ever requested.

Sanity-checking an ounces conversion

Divide the ounces by thirty-five to approximate the kilograms: 32 oz gives about 0.91, and the true figure is 0.907. Anything off by a factor of ten indicates a misplaced decimal, and anything off by about sixteen indicates a pound-ounce confusion somewhere in the chain. The approximation is far too coarse for paperwork but ideal for catching the gross errors, which are the ones that actually cause problems — fine errors get absorbed by tolerances, while a tenfold error does not.

Ounces on nutrition and portion labels

American serving sizes are frequently given in ounces, and converting them is how imported nutrition data becomes comparable with local panels stated per 100 g. A 3 oz portion is 85 g, which is a common protein serving; a 6 oz portion is 170 g. Because most non-US panels are per 100 g, converting the serving first and then scaling the panel is the order that keeps the arithmetic simple and the units traceable at every step.

Bulk conversions and keeping the source

Converting a catalogue of ounce weights into kilograms follows the same discipline as any bulk conversion: keep the ounce column untouched, add a kilograms column computed from the exact constant, and round only in a third column meant for display. Overwriting the source figure destroys the ability to re-derive it, and repeated re-conversion of already-rounded values drifts steadily in one direction. The measured number is the asset; the converted one is a view of it.

The sixteen-ounce pound as a self-test

This conversion carries a built-in check that is worth knowing. Sixteen ounces must return exactly 0.45359237 kg, because that is the definition of the pound from which the ounce is derived. Any converter, spreadsheet or piece of firmware that returns 0.4536 for that input has truncated its constant, and any that returns 0.45359236999 is doing binary floating-point arithmetic and rounding late. Neither is wrong at two decimal places, but knowing which one you are using tells you exactly how far its digits can be trusted — and this page returns the exact value, which makes it a usable reference for that test.