Kilograms to Pounds Converter

What this converter does

It turns a mass expressed in kilograms — the unit almost the whole world weighs in — into pounds, the unit the United States still uses for body weight, shipping, produce and gym plates. The arithmetic is a single division by an exactly defined constant, and because that constant is a legal definition rather than a measurement, the conversion itself carries no error at all. The only approximation on this page is the rounding you choose for display.

The formula, and where it comes from

To convert kilograms to pounds, divide by 0.45359237 — or multiply by 2.20462262185, which is the same thing to twelve significant digits.

The number 0.45359237 is worth a moment of respect. Until the middle of the twentieth century, the pound was defined separately in different countries, and the definitions disagreed in the sixth decimal place: the US pound and the UK pound were not quite the same object. The 1959 International Yard and Pound Agreement ended that by defining one avoirdupois pound as exactly 0.45359237 kilograms for every signatory. Since then, converting between the two systems has been pure arithmetic — there is no better or worse measurement of the factor, because the factor is the law.

Worked examples

A person weighing 70 kg: 70 ÷ 0.45359237 = 154.3236 lb, which anyone would state as 154 pounds. Going the fast way with the rule of thumb — 70 × 2.2 = 154 — lands within half a pound, which is why “multiply by 2.2” survives as mental arithmetic. The rule of thumb runs 0.2% low of the true 2.20462, so it degrades on big numbers: a 1,000 kg pallet is 2,204.6 lb, not 2,200.

A checked bag packed to 23 kg: 23 ÷ 0.45359237 = 50.706 lb. This is the airline trap. Many carriers publish 50 lb and 23 kg as if they were the same limit; they are 0.7 lb apart, and a bag weighed at exactly 23 kg is over a strict 50 lb scale. If you fly a US carrier with a 50 lb rule, pack to 22.6 kg.

Reading the precision controls

The default display shows up to twelve significant digits of the true decimal expansion. That is more than any physical scale justifies — a bathroom scale resolves perhaps 0.1 kg, a shipping scale 0.5 lb — so the fixed two-decimal setting is right for nearly everything human-scale. The extra digits exist because this is also the page people use to check other converters, spreadsheets and firmware, and for that you want the reference value, not a rounded one.

One detail matters to anyone doing that checking: the widely circulated figure 2.2046226218487757 is not the true factor. It is the closest 64-bit floating-point number to it. The true decimal continues 2.20462262184877580722…, so at seventeen significant digits the correct rounding ends in 758, not 757. This converter computes in exact decimal arithmetic, so what it shows at any precision is the true expansion — if your spreadsheet disagrees in the sixteenth digit, the spreadsheet is showing you its binary approximation.

Kilograms, pounds, and which one is “weight”

Strictly, the kilogram is a unit of mass and the pound as used here is too. Weight, in the physics sense, is a force — mass times local gravitational acceleration — and is measured in newtons. Nothing on this page needs gravity, because converting kg to lb is converting mass to mass. The distinction becomes practical exactly once: if an engineering problem asks for weight in newtons or pound-force, that is a different calculation requiring a gravity value, and a converter that silently did it for you would be guessing which planet, altitude and convention you meant.

Common mistakes

Three come up constantly. First, using 2.2 for anything contractual — fine for conversation, 0.2% wrong, and 0.2% of a freight invoice is real money. Second, confusing the direction: dividing by 2.2046 instead of multiplying, which produces a number about five times too small and is surprisingly easy to miss when the units are not written down. Writing the units through every step catches it immediately. Third, treating pounds-and-ounces figures as decimal pounds: 7 lb 11 oz is 7.6875 lb, not 7.11 — for that format use the dedicated pounds-and-ounces converter linked below.

Benchmarks worth memorising

1 kg = 2.2046 lb. 5 kg = 11.02 lb (a bag of flour and a bit). 10 kg = 22.05 lb. 20 kg = 44.09 lb (a typical budget-airline hold bag). 23 kg = 50.71 lb (the standard checked bag). 50 kg = 110.23 lb. 70 kg = 154.32 lb (a typical adult). 100 kg = 220.46 lb. 1,000 kg = 2,204.62 lb, which is one metric tonne and conveniently close to — but 10% more than — the US short ton of 2,000 lb.

Accuracy and limits

The conversion factor is exact; results are exact until rounded; and the tool accepts scientific notation for values far outside everyday range. What it does not do is judge sense: it will convert 10²⁰ kg to pounds faithfully, though nothing you can weigh justifies the digits. And it converts mass only — for newtons, gravitational context is required and deliberately out of scope here.

How the kilogram itself is defined

The pound leans on the kilogram, so it inherits the kilogram’s story. From 1889 to 2019 the kilogram was a physical object — a platinum-iridium cylinder in a Paris vault — and the world’s masses were traceable to whatever that artefact happened to weigh, drift included. In 2019 the SI redefined the kilogram by fixing the numerical value of the Planck constant, making it reproducible from physics rather than from a lump of metal. None of this changed any conversion on this page: the pound’s 0.45359237 factor is a ratio, and ratios survive redefinitions untouched. It does mean that when this page shows twelve digits, those digits rest on a definition stable to parts in a billion — better than any artefact ever managed.

Using the factor in spreadsheets and code

For a spreadsheet column of kilograms, the conversion is =A2/0.45359237 — prefer dividing by the exact constant over multiplying by a truncated 2.2046, because the truncation you choose becomes an error you keep. In code, the same rule: store 0.45359237 as the single source of truth and derive the reciprocal at use, never hard-code both, or the two will disagree in the last digit and a reconciliation script will one day flag phantom discrepancies. If your language offers decimal arithmetic (Python’s Decimal, SQL’s NUMERIC), use it for stored weights; binary floats are fine for display and dangerous for ledgers.