Lbs to g converter
Multiply pounds by exactly 453.59237 and get grams: 1 lb is 453.59237 g, fixed by the 1959 international agreement. For nutrition labels, postage scales, kitchen recipes and lab notebooks. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Lbs
- 1
- Result
- 453.59237 g
- Converted
- 453.59237
- G
- 453.59237
- From unit
- lb
A pounds-to-grams converter turns an avoirdupois mass into the SI gram used on nutrition labels, laboratory notebooks, postage scales, kitchen recipes, and customs packing lists. Approximate mental shortcuts such as four hundred fifty-four grams per pound are unnecessary here because the factor is a fixed legal constant, not a survey estimate that needs rounding judgment.
Why pounds still convert to grams at an exact factor
Pounds remain everyday mass units across the United States and in many trade contexts that still quote avoirdupois weight, while grams are the SI unit printed on food labels, pharmacy vials, laboratory sample tickets, and small-parcel postage. Kitchen scales may show pounds for bulk ingredients and grams for spices, courier forms for light goods often ask for grams, classroom problems almost always teach that one international pound equals 453.59237 grams, and recipe databases store SI masses even when shoppers still think in pounds.
That rule comes from the nineteen fifty-nine international yard and pound agreement: the avoirdupois pound is defined exactly in terms of the kilogram, and one kilogram is one thousand grams, so conversion is a single exact multiply—grams equals pounds times 453.59237—with no leftover uncertainty and no dependence on local survey factors. This landing stays on the mass path only.
It does not convert troy pounds of precious metal, apothecary pounds used in some historical pharmacy contexts, or force units such as pound-force; those share a name with different meanings and would mislead searchers who typed pounds to grams for groceries, shipping, or lab work. Zero pounds maps cleanly to zero grams.
Practical checks, limits, and related searches
Prefer sending bare numbers when you control the client; string numbers are accepted only when they match a strict finite numeric pattern without units, thousand separators, or currency symbols. Round-trip sanity checks are easy: convert one pound and confirm you receive 453.59237 grams after rounding, convert two point two pounds and confirm nine hundred ninety-seven point nine zero three two one four grams within the published twelve-decimal fields, or convert zero and confirm zero.
When teaching, show that dividing the published grams by the factor recovers the original pounds within the same twelve-decimal rounding used for published fields. Stay inside the absolute range so the multiply cannot overflow into a non-finite result the solver must reject. This landing targets people searching for lbs to g, convert pounds to grams, or an exact 453.59237 factor calculator; it is not a general multi-unit mass hub, not a grams-to-pounds primary form, not a kilograms or ounces input path, and not a force converter.
Prefer this capability when the input is already in pounds and you only need grams; if you must convert among many mass units in one call, use a broader unit converter instead.
What you can do with it
Nutrition labels and recipe scaling
Convert pantry weights recorded in pounds into grams for nutrition labels, recipe databases, and kitchen scales that display SI mass.
Laboratory sample tickets
Turn pound-based receiving weights into grams for lab notebooks, sample IDs, and reagent logs that require SI mass units.
Small-parcel postage and customs
Express light shipments quoted in pounds as grams for carrier forms, postage bands, and customs packing lists that list gram limits.
FAQ
How many grams are in one pound?
Exactly 453.59237 grams. The international avoirdupois pound has been defined as that mass since the 1959 yard and pound agreement, so one pound is not rounded to 454 g here.
Why not use 454 grams per pound?
454 g is a classroom shortcut. This converter multiplies by the exact legal factor 453.59237 so labels, tests, and postage math match the SI definition rather than an estimate.
Can I convert a negative number of pounds?
No. A physical mass cannot be negative. Zero pounds converts to zero grams.
Does this accept kilograms or ounces as input?
Input is always avoirdupois pounds; the output is grams.
What does the lbs to g converter cost?
The browser tool is free and runs locally.
Related tools
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/conv/lbs-to-g \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"lbs":1}'const res = await fetch("https://api.kit.forhosting.com/conv/lbs-to-g", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"lbs": 1
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/lbs-to-g",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"lbs": 1
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/lbs-to-g", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"lbs":1}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"lbs":1}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/lbs-to-g", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"lbs": 1
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.lbs_to_g",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |
Technical notes
Negative, missing, infinite, or non-numeric input fails with a clear invalid_input error instead of inventing a mass.
How to call the API and what comes back
The mass must be non-negative and stay within the published limit of one trillion. Do not send unit strings inside the numeric field; strip the letters lb on the client and send the magnitude alone. Send a JSON body with one required finite number field named lbs. Aliases pounds, pound, lb, value, mass, weight, and lbs_value are accepted so SDK clients and form posts can use the name that fits the product. On success the response echoes rounded lbs, sets g, result, and converted to the same rounded gram magnitude, unit to the token g, from_unit to lb and to_unit to g, factor and grams_per_pound to 453.59237, formula to the string g equals lbs times 453.59237, message to a short English summary, and steps to an ordered array of substitution lines that show the international avoirdupois definition. Failed validation—missing fields, negative masses, non-finite numbers, bare plus or minus signs, non-numeric strings, values outside absolute limits, or a non-finite converted result—returns invalid_input and is never charged. Pricing is a flat $0.002 per successful request with unit item and no extra per-unit fee. Prefer a JSON number; numeric strings are accepted only when they match a strict finite decimal pattern without thousand separators.
Practical checks, limits, and related searches
Failed tasks that return invalid_input do not consume prepaid balance, which keeps exploratory scripts cheap when learners deliberately omit lbs, pass text, or try a negative mass.