Quarts to liters converter
A US quart is 0.946352946 L and an imperial quart 1.1365225 L, nearly a fifth more: choose the quart your recipe uses and convert to liters or back without skewing the batch. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Numeric volume to convert
- 2
- Quart size system: us
- us
- Result
- 1.892705892
- From
- quarts
- To
- liters
- System label
- US liquid quart
Soup stocks, dairy cartons, and canning recipes often list volume in quarts while metric kitchens and product labels prefer liters. A quarts to liters conversion is not one universal factor: the US liquid quart is one quarter of a US liquid gallon, about zero point nine four six liters, while the imperial quart used in older British and Commonwealth recipes is one quarter of an imperial gallon, about one point one three seven liters. Using the wrong quart size skews broths, brines, and batch yields by roughly twenty percent. This capability converts a volume between quarts and liters for a chosen quart system using those fixed published sizes, so the same inputs always return the same result with no network lookup and no random packing guess. You send an amount, a system of us or imperial, and optionally whether the amount is already in quarts or liters; the engine multiplies or divides by the liters-per-quart factor and returns both units plus a clear system label. Unknown quart systems fail with invalid input instead of silently assuming US liquid measures.
Why quarts to liters needs a quart system, not one factor
Volume conversion between quarts and liters only works when you name which quart you mean. A US liquid quart is exactly one fourth of a US liquid gallon, which equals zero point nine four six three five two nine four six liters. An imperial quart, still seen in older United Kingdom and Commonwealth cookbooks and some dairy packaging references, is one fourth of an imperial gallon, or one point one three six five two two five liters.
Treating every quart as the same size is how a stock pot scaled from a US recipe underfills a metric jug, or how a UK canning formula overflows a US quart jar mark by nearly twenty percent. This product keeps a published fixed table of those two liquid quart sizes and never invents a third on the fly. Conversion is simply liters equals quarts times liters per quart for the resolved system, or the reverse divide when the source is already in liters.
Negative amounts and missing fields are rejected as invalid input, and zero correctly yields zero in both units for empty optional ingredients in generated shopping lists or step templates. Dry US quarts used for some produce measures are outside this contract; the engine targets liquid kitchen volumes only.
Using quart conversions in the kitchen
Use the free in-browser quarts to liters converter when scaling a single soup or brine at the counter, checking a blog post that mixes US quart jars with metric jugs, or teaching students why liquid quart definitions differ across regions. Remember that dry-goods packing still differs from liquid volume; this tool converts pure liquid volume using published quart sizes and does not replace an ingredient density table for flour or honey.
Authors shipping SDKs can map the response into a two-column UI of quarts and liters with the system label as the row subtitle, matching how home cooks already compare jar marks and metric jugs on paper. When a recipe source is ambiguous about US versus imperial quarts, show both system results side by side so the cook can pick the jar size that matches their pantry.
What you can do with it
Scale US quart recipes into metric liters
Home cooks convert stock, milk, and brine listed in US quarts into liters for metric jugs and packaging, choosing the us system so results match American liquid quart jars.
FAQ
What is the difference between US and imperial quarts?
A US liquid quart is about 0.946353 L and an imperial (UK) quart is about 1.136523 L. The engine uses those fixed sizes so the same quart count yields different liters per system.
Is the quarts to liters converter free?
The browser tool runs free on your device.
Can I convert liters back to quarts?
Yes. Set from to liters (or litre, L) and amount to the liter volume.
How many liters are 2 US quarts?
2 US liquid quarts are 1.892705892 L. The same 2 quarts in the imperial system come to noticeably more, so check which quart the recipe means before you fill the pot.
Can I convert dry quarts of berries or produce?
No. Only liquid quarts are covered, the US liquid quart and the imperial quart. Dry US quarts used for some produce measures are a different size and are left out.
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/quarts-liters \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"amount":2,"system":"us"}'const res = await fetch("https://api.kit.forhosting.com/cook/quarts-liters", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"amount": 2,
"system": "us"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/cook/quarts-liters",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"amount": 2,
"system": "us"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/cook/quarts-liters", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"amount":2,"system":"us"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"amount":2,"system":"us"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/cook/quarts-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": 2,
"system": "us"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "cook.quarts_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.
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
Why quarts to liters needs a quart system, not one factor
Case-insensitive names and friendly aliases such as usa, uk, british, and us liquid normalize to the same canonical keys so form UIs stay friendly while the JSON contract stays stable.
How to call the converter and read the response fields
Optional field from defaults to quarts so a quarts-to-liters search lands on the expected path; set from to liters when you are converting the other direction. Non-finite amounts, empty system strings, and missing required fields follow the same error path. Send a JSON body with the required number field amount set to a non-negative finite volume, and the required string field system naming us or imperial. Aliases value, quantity, and qty are accepted for the amount field; quart_system, quart, and standard are accepted for the system field when your client already uses those labels. Use result alone when a simple display is enough; use liters_per_quart when you want to show users why two US quarts is not the same as two imperial quarts in liters; use system_label when rendering multi-language shells that still need English kitchen names for the English landing. An unknown quart system such as metric or a typo that does not match any alias fails with invalid_input and is not charged after validation rejects the request.
Practical kitchen workflows, limits, and API pricing
Use the prepaid API when a meal-planning app, smart scale companion, recipe CMS, canning label tool, or localization pipeline must convert many lines under a stable KIT contract at $0.002 per successful item. Pair this endpoint with a milliliters-to-cups converter when the next step is cup measures rather than liters, or with a general volume converter when you need gallons, milliliters, or cubic metres without a quart system.
Integration use cases
Recipe apps and CMS importers
Content pipelines normalize mixed unit blog recipes into structured JSON with quarts and liters side by side for US or imperial audiences without embedding a live unit API.
Culinary classrooms and regional unit drills
Students compare US liquid and imperial quarts for the same amount; graders pin expected liters and expect invalid_input on unknown quart systems.
Technical questions
How do I convert quarts to liters?
Send JSON with amount set to the quart value (for example 2) and system set to us or imperial. From defaults to quarts. The response returns liters using the fixed liters-per-quart size for that system.
What happens if the quart system is unknown?
The request fails with invalid_input. Only us, imperial, and their documented aliases are accepted; unknown systems are not charged after validation fails.