Convert oz to t

An ounce is a sixteenth of a pound. It is not the fluid ounce, which measures volume, and the two are only loosely related — a fluid ounce of water weighs about an ounce, which is where the name came from and where the confusion starts.

A tonne is 1,000 kilograms, and it is not the same as either the US short ton (907 kg) or the UK long ton (1,016 kg). Where the difference matters, this one is sometimes written "metric ton".

The factor is 0.000028, and almost nobody carries that around. Rounded to 0.000028 it is off by 1.2 % — which stays invisible on small numbers and turns into a whole unit somewhere around 100 oz.

That is the number worth knowing before you round: not the error itself, but where it stops being ignorable. Below that point the shorter factor is the sensible one; above it, use the field above, which never rounds until it prints.

This page uses the metric tonne, which here is 35273.96195 oz. The US short ton is 32000 oz, 9.3 % lighter; the UK long ton is 35840 oz, 1.6 % heavier. Three units, one letter between two of their names.

Where the figure came from usually settles which one it is: tonnes for shipping, freight and emissions nearly everywhere, short tons in American industry, long tons in older British sources. Write "metric ton" where it has to be unambiguous — of the three it is the only name that cannot be read as one of the others.

The ounce has been defined in metric terms since the international yard and pound agreement of 1959, and in this page's units that comes out at 0.0000283495231 t to one. The definition is exact by stipulation — it was not measured, and it cannot be refined by measuring it better. The decimal above is not the whole of it, though: this page stops at nine significant digits and the ratio carries on past them.

Before that agreement the US and the British versions differed slightly, and old survey figures still carry the older definition. For anything outside land surveying the difference is far below the precision anybody is working to.

A single ounce is 0.0000283 t, a number that answers nothing. This conversion only becomes useful multiplied: a per-item weight, a per-pack weight or a per-unit material figure recorded in ounces, times the number of units, expressed as the tonnage a form asks for. The interesting arithmetic is the multiplication, and the conversion is the smaller half of it.

That changes what care means here. On a one-off conversion the risk is a misplaced decimal; on an aggregation the risk is that the per-unit figure was rounded before it was multiplied, and the conversion faithfully carries the rounding all the way up. The digits to protect are the ones in the ounce figure, before anything is scaled.

Extended producer responsibility schemes, packaging returns and materials disclosures all ask for tonnes placed on a market in a year. The data underneath is per-item: a bottle weighs 0.9 oz, a carton 2.4 oz, a mailer 1.1 oz. Multiplying by annual volumes and converting gives the reported figure, and it is usually the first time anybody has looked at those small weights closely.

The weakness is nearly always in the item weight rather than in the volume. Volumes come out of a sales system and are exact; item weights come from weighing one sample, often on a scale that steps in tenths of an ounce, often before a supplier changed the material. A tonnage that has to be defended is worth rebuilding from a fresh sample of ten items, not from the figure in last year's return.

Central bank reserves, mine production and national holdings are published in tonnes. Every price and every trade is in troy ounces. That means the two units at the ends of this page are exactly the two units the bullion market uses — and the ounce in the market is not the ounce in this converter.

A troy ounce is 31.1034768 g against the ordinary ounce's 28.349523125, so it is 9.71 per cent heavier. A tonne is 32,150.75 troy ounces, not 35,273.96. Using this page's factor on a bullion figure understates the metal by nearly a tenth, which at any price at all is a large number; the check is the source. If the figure carries a price per ounce, it is troy.

Scale resolution is the quiet source of error in every aggregation of small weights. A tenth of an ounce is 2.835 g, and across a million units that is 2.835 t. Across ten million it is 28.35 t, which is the difference between reporting bands in several schemes and between two quite different material purchase forecasts.

The way out is to weigh in bulk rather than to weigh better. A hundred items on a scale that reads to a tenth of an ounce gives a per-item weight good to a thousandth, because the resolution is divided across the count. That single change usually removes more error from a tonnage than any amount of care in the conversion itself.

An ounce is a shopping unit and a tonne is a freight unit, and putting both in one document asks the reader to hold a factor of thirty-five thousand in their head. Columns like that are where a figure entered in the wrong row goes unnoticed: 0.5 and 0.5 look identical, and one of them is a bottle and the other is half a lorry.

The fix is to keep the intermediate unit visible. Ounces to grams for per-item weights, grams or kilograms for a batch, tonnes for the annual figure — three columns with three unit labels, each within a factor of a thousand of its neighbour. It is the same discipline that keeps a spreadsheet of file sizes honest, applied to mass.

The safe route between these two units has two stops on it. Ounces to grams multiplies by 28.3495 and lands on a number that describes a real object; grams to kilograms and kilograms to tonnes are two divisions by a thousand, each of which is a decimal point. Every stage is checkable by eye, and the exponent cannot go astray without something visibly implausible appearing.

Doing it in one move with a remembered 35,274 is faster and offers no such protection. Five significant figures is more than anyone reliably recalls, the factor differs from the troy one by a similar-looking amount, and an answer that comes out a thousand times wrong is indistinguishable from a correct answer for a business of a different size. Where an aggregation is being built once and used for a year, the intermediate columns are worth their space.

This pair exists because two systems meet in one organisation. Product and packaging specifications in the United States are held in ounces because that is what the labels and the suppliers use; the returns those specifications feed — European packaging schemes, group sustainability reporting, customs statistics — are in tonnes. Neither side is going to change, so the conversion lives permanently in the middle.

The stable arrangement is to hold the source data in its native unit and convert at the reporting boundary, once, in code or in a documented step. The alternative, where each analyst converts what they need when they need it, produces a set of figures that are individually defensible and do not add up — and the discrepancies surface at exactly the moment somebody outside the organisation is looking at them.

Three cases justify the whole conversion. Packaging and materials reporting, where the obligation is expressed in tonnes placed on a market. Food and consumer goods manufacture, where per-unit weights in ounces become annual raw material purchasing in tonnes. And bullion, where the two ends of this page are literally the two units the market uses, with the troy ounce standing in for the ordinary one.

Outside those, an answer in tonnes is usually a sign that a template asked for a unit it should not have. A single item, a shipment, a batch — none of these is a tonne-scale quantity, and expressing them that way produces figures that cannot be compared or checked. The conversion is exact and always available; whether it should be applied is a separate question, and the answer above is the number rather than the recommendation.