Pints to liters converter
One US pint is 0.473176473 L and one UK pint is 0.56826125 L, about 20% more: choose the pint your recipe or menu means and convert to liters or back. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Amount
- 1
- Conversion direction
- pints_to_liters
- Result
- 0.473176473
- System
- us
- From unit
- pt
- To unit
- L
This pints to liters converter turns kitchen and bar volumes between pints and liters using the two pint sizes people actually meet: the US liquid pint of 0.473176473 liters and the imperial (UK) pint of 0.56826125 liters. Enter a non-negative amount, choose direction (pints to liters or liters to pints), and pick the pint system; the engine scales with a fixed factor and returns the result with the factor and unit labels. Small checks include one US pint equaling about 0.473 liters and one imperial pint equaling about 0.568 liters—almost twenty percent larger than the US measure.
What the converter returns and which pint systems it uses
A pint is not a single universal volume. In the United States, liquid recipes, dairy cartons, and bar pours treat one pint as sixteen US fluid ounces, which is exactly 0.473176473 liters (sixteen times 29.5735295625 milliliters). In the United Kingdom and other imperial-measure contexts, one pint is one eighth of the post-1963 imperial gallon of 4.54609 liters, which is exactly 0.56826125 liters—about twenty percent larger than the US liquid pint.
Mixing those conventions is a common source of off-by-a-fifth errors when a British ale recipe is scaled with American measuring cups, when a US ice-cream label is compared to a UK scoop size, or when a travel app assumes “a pint of milk” without naming the system. This tool makes the choice explicit: system us applies the NIST-consistent US liquid factor, and system imperial applies the UK imperial factor.
There is no density conversion, no weight of flour or cream, and no cup or fluid-ounce path as the primary contract: those belong on dedicated pages. Invalid cases include a missing amount or direction, non-finite numbers, amounts above the documented ceiling, unknown direction tokens, any negative amount, and—importantly—an unknown pint system such as metric or custom, because the engine only supports the two documented conventions.
Where pint and liter conversion fits in cooking, pubs, and software
Home cooks meet this conversion when a US family recipe lists two pints of stock and a metric measuring jug only shows liters, or when a British cake formula in milliliters must be followed with American pint cartons. Pub menus and brewery apps convert draft pours so a “pint of lager” is labeled correctly for US versus UK visitors. Teachers and culinary students use fixed factors for worksheet keys without trusting opaque calculator apps that silently switch between zero point four seven and zero point five seven liters.
Product teams call the same contract from scripts to seed deterministic test vectors for recipe importers, to normalize user-entered pint and liter fields before scaling a batch, or to satisfy programming-challenge statements that demand a documented US or imperial factor rather than a hand-waved half liter.
What you can do with it
Recipe adaptation US ↔ UK
Convert pint measures in family recipes to liters (or back) using the correct US liquid or imperial pint size.
Pub menus and brewery apps
Label draft pours and bottle sizes so US and UK pint servings are not confused by travelers or importers.
FAQ
What does the pints to liters converter cost?
It is free in your browser on this page.
How many liters are in one pint?
US liquid: 0.473176473 L per pint. Imperial (UK): 0.56826125 L per pint. Choose system us or imperial.
Does this convert cups or gallons?
No. It only converts pints and liters under the chosen system. Use a dedicated volume tool for other kitchen units.
How much bigger is a UK pint than a US pint?
About 20% bigger: 0.56826125 L against 0.473176473 L. Mixing the two is a common off-by-a-fifth error when a British recipe is followed with American measures.
Which pint does it use if I do not choose one?
The US liquid pint. If your recipe, carton or menu is British, switch to the imperial pint before converting, or the result will be off by about a fifth.
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/cook/pints-liters \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"amount":1,"direction":"pints_to_liters"}'const res = await fetch("https://api.kit.forhosting.com/cook/pints-liters", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"amount": 1,
"direction": "pints_to_liters"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/cook/pints-liters",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"amount": 1,
"direction": "pints_to_liters"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/cook/pints-liters", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"amount":1,"direction":"pints_to_liters"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"amount":1,"direction":"pints_to_liters"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/cook/pints-liters", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"amount": 1,
"direction": "pints_to_liters"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "cook.pints_liters",
"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_abs_amount | 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
Use it free in the browser while adapting family recipes or beer servings, or call the API at $0.002 per successful request when your app must convert pints and liters without re-implementing the factors.
What the converter returns and which pint systems it uses
You send amount and direction, and the response echoes the normalized amount, the canonical direction and system, the numeric result, from_unit and to_unit strings, the liters_per_pint factor used, a short system_label, the precision applied, a method tag, and a formula reminder. If validation fails you get invalid_input with a clear message and the request is not charged.
How amount, direction, and system are read so results stay reproducible
Optional leading plus signs and scientific notation on amount strings are accepted when they parse as finite decimals; embedded spaces, hex prefixes, and non-numeric tokens are rejected so a bad cell does not become a silent wrong volume. Zero amount is valid and returns zero in the target unit. The preferred fields are amount for the magnitude, direction for pints_to_liters or liters_to_pints, and optional system for us or imperial. Aliases such as value, quantity, n, and qty map to amount; dir, convert, mode, and way map to direction; pint_system, standard, size, and convention map to system, so spreadsheets, query strings, and typed forms can reuse the same contract without renaming columns. Direction aliases include pt2l, to_liters, pints_to_l, l2pt, and liters_to_pints; system aliases include usa, american, uk, british, and imp for the larger imperial pint. An optional precision field, with aliases decimals and dp, chooses how many decimal places to expose for amount, result, and liters_per_pint, defaulting to ten and capped at fifteen so JSON goldens stay stable across runs. Pair the free browser run on this page with the priced API when you need the identical mathematical result inside an automated pipeline without re-implementing the pint factors yourself.
Where pint and liter conversion fits in cooking, pubs, and software
On this page the work runs entirely in your browser; through the API each successful lookup costs $0.002, failed validation is not charged, and nothing is stored after the response returns. That split — free interactive exploration and a priced, identical API — matches the rest of the KIT tier-A catalog and lets you move from a kitchen demo to an automated pipeline without changing the mathematical result. Pair it with broader unit tools when you need cups or gallons, and keep this endpoint when the search intent is specifically pints to liters with an explicit US versus imperial choice.
Integration use cases
Deterministic test fixtures
Generate reproducible pint↔liter results for unit tests, recipe importers, and CI assertions without re-coding factors.
Technical questions
What happens if the pint system is unknown?
The input is rejected with invalid_input. Only us and imperial (with documented aliases) are supported.
Can I convert liters back to pints?
Yes. Set direction to liters_to_pints (aliases such as l2pt and to_pints are accepted) and provide the liter amount.