Pounds and ounces
75 ounces is 4 pounds and 11 ounces, not 4.6875 lb. Enter a total in ounces and get the whole pounds plus the leftover ounces that baby books, shipping labels and butcher tickets expect. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Ounces
- 75
- Result
- 4 lb 11 oz
- Pounds
- 4
- Remaining ounces
- 11
- Formatted
- 4 lb 11 oz
A total weight written only in ounces is awkward on baby-book pages, shipping labels, butcher tickets, veterinary charts, and warehouse tickets that expect a mixed avoirdupois pair: whole pounds plus leftover ounces that do not fill another pound. This pounds and ounces converter takes a single finite nonnegative mass in ounces and splits it with the exact identity that one pound equals sixteen ounces. Seventy-five ounces becomes four pounds and eleven leftover ounces; sixteen ounces becomes one pound with nothing left over; zero stays zero pounds and zero ounces.
How a total ounce count becomes whole pounds and leftover ounces
People often record a mass as one number of ounces because a kitchen scale, a parcel scale, a spreadsheet cell, or a hospital chart holds a single figure. Everyday speech and most United States forms do not stop there: they want a mixed pair of whole pounds plus leftover ounces that stay strictly below sixteen. The conversion is therefore an integer split against an exact constant, not an approximate lookup table and not a decimal-pound result such as 4.6875 lb.
One avoirdupois pound is sixteen ounces by definition, so divide the given total by sixteen, take the integer number of complete groups as pounds, and keep the remainder as leftover ounces. Seventy-five ounces is four complete pounds and eleven leftover ounces because four times sixteen is sixty-four and eleven remain. Thirty-two ounces is exactly two pounds with zero leftover ounces.
Twenty and a half ounces is one pound and four and a half leftover ounces. Zero ounces converts to zero pounds and zero leftover ounces, which is the honest empty-weight case for a cleared field. This capability never converts kilograms, never uses troy ounces of precious metal, never treats fluid ounces as volume, never rounds to the nearest half-ounce as a hidden default, and never invents a second input unit.
The same identity appears in the formula field so a student or a user interface can reprint the working next to the answer without reconstructing the arithmetic from scratch.
Where a pounds-and-ounces split earns its keep, and what it costs
Newborn wards, pediatric clinics, and parent apps often store birth weight or check-in mass as a single ounce count from a scale and must print the mixed pair that charts, baby books, and discharge summaries still use. Shipping desks convert ounce-based scale readings into a spoken pounds-and-ounces label when a carrier form and a warehouse ticket disagree on notation. Butchers, delis, and kitchen prep lists convert a leftover-ounce remainder so a cook who thinks in pounds can compare a cut, a batch, or a yield at a glance.
Veterinary charts and livestock tickets do the same when a scale reports ounces and the record wants four pounds eleven ounces instead of seventy-five. Keep this landing focused on the search intent pounds and ounces—total ounces in, mixed avoirdupois pair out—and use a dedicated ounces-to-pounds decimal converter when the pipeline only needs a single pound magnitude, or a generic mass table when the unit is not this split. Source inputs follow the same retention rules as other KIT parse items; nothing is stored after the task completes.
What you can do with it
Newborn and pediatric weight charts
Split a scale reading recorded as total ounces into the whole-pounds plus leftover-ounces pair that baby books, discharge summaries, and clinic charts still print.
Shipping and warehouse labels
Turn an ounce-based parcel scale into a readable pounds-and-ounces label when carrier forms and warehouse tickets expect the mixed pair instead of a decimal pound.
Butcher, kitchen, and veterinary tickets
Convert a leftover-ounce remainder from a single ounce count so cooks, cut lists, and vet charts that think in pounds can compare a yield or a patient weight at a glance.
FAQ
What happens if the ounce value is negative or not a finite number?
Weight must be a finite nonnegative number; missing, empty, NaN, Infinity, negative values, and non-numeric strings are rejected and are not billed.
Why return leftover ounces instead of only a decimal number of pounds?
Search intent for pounds and ounces is the mixed avoirdupois pair people write on forms (for example 4 lb 11 oz), not 4.6875 pounds. The original total is still echoed as ounces for callers who need it.
Is sixteen ounces per pound exact, and does this use troy or fluid ounces?
Yes, one avoirdupois pound equals sixteen ounces by definition. This split never converts troy ounces of precious metal or fluid ounces of volume; those share a name with different sizes.
How many pounds and ounces is 75 ounces?
4 pounds and 11 ounces. Four complete pounds use 64 ounces, because each pound holds 16, and the 11 ounces that remain are too few to make another pound.
Can I enter a fractional number of ounces?
Yes. 20.5 ounces becomes 1 pound and 4.5 ounces. The leftover keeps its decimals and is never rounded to the nearest half ounce behind your back, so you decide how to round it.
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/pounds-ounces \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"ounces":75}'const res = await fetch("https://api.kit.forhosting.com/conv/pounds-ounces", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"ounces": 75
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/pounds-ounces",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"ounces": 75
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/pounds-ounces", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"ounces":75}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"ounces":75}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/pounds-ounces", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"ounces": 75
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.pounds_ounces",
"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.
Limits
max_ounces | 1000000000000 |
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 values and non-numeric input fail with invalid_input and are not billed. Successful API calls cost $0.002 per item.
How a total ounce count becomes whole pounds and leftover ounces
Leftover ounces are rounded to twelve decimal places only so JSON goldens stay stable across runtimes; if that rounding would land on sixteen, the extra pound is carried so the remainder stays in the half-open interval from zero inclusive to sixteen exclusive.
Input contract, response fields, and error behaviour
Zero is a valid mass and returns zero pounds and zero leftover ounces. The formatted field writes the mixed unit as N lb M oz, and result repeats formatted for callers that look for a single primary string. Formula restates pounds equals floor of ounces divided by 16, with leftover ounces as the modulo. A short message and a steps array walk through the input, the sixteen-ounce definition, and the split, which tutoring software can show verbatim. Do not send mixed strings such as four-pound-eleven in quotes: parse the total ounce count first, then call this split. POST a JSON body with the required field ounces, a finite nonnegative number or a plain numeric string. Aliases oz, ounce, value, weight, mass, and total_ounces are accepted so forms, spreadsheets, and SDKs can use the name that already exists in the source record. Negative values, NaN, Infinity, empty strings, and non-numeric text fail with invalid_input naming the field, and those failures are not billed. Magnitudes above one trillion ounces are rejected so Worker isolates stay safe. On success the body echoes the parsed ounces value, returns pounds as a whole number, and returns remaining_ounces as the leftover remainder in the half-open interval from zero inclusive to sixteen exclusive. The constant ounces_per_pound 16 travels with the payload so a client can cache the identity without hard-coding it. Pair the numbers with your own rounding for a baby-book card if you need a half-ounce display; this endpoint keeps twelve-decimal leftovers so automation can round last, not first.
Where a pounds-and-ounces split earns its keep, and what it costs
Successful API calls bill as one item at $0.002; invalid_input is free, so you can validate a form field without burning balance.
Technical questions
How do I convert a total weight in ounces into pounds and leftover ounces?
Send a finite nonnegative number in the ounces field (aliases oz, ounce, value, weight, mass, total_ounces). The API takes whole pounds as floor of that total divided by 16 and returns remaining_ounces as the leftover remainder.
What does the pounds and ounces converter cost?
The browser tool is free. API requests use prepaid KIT balance at $0.002 per successful call; invalid input is not billed.