Tablespoons to ml converter
Two US tablespoons are 29.5735295625 ml, while a metric tablespoon holds 15 ml and an Australian one 20 ml. Choose the spoon system of your recipe, enter tablespoons or milliliters and get the exact conversion with its factor. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Numeric quantity to convert
- 2
- Tablespoon size system: us
- us
- Source unit: tbsp
- tbsp
- Target unit: tbsp
- ml
- Result
- 29.5735295625
- System label
- US
- Ml per tbsp
- 14.7867647813
- Direction
- tbsp → ml
A tablespoons to milliliters converter turns a kitchen amount into the volume number your scale, recipe card, or overseas cookbook actually needs. Enter how many tablespoons or milliliters you have, pick the tablespoon system—US legal (half a US fluid ounce), metric fifteen-milliliter, or Australian twenty-milliliter—and choose the target unit; the tool returns the converted value, the exact ml-per-tablespoon factor for that system, a short formula line, and ordered substitution steps you can copy into a test or worksheet.
Why tablespoon size depends on the culinary system
A tablespoon is not a single universal volume. In the United States the legal tablespoon used for nutrition labeling is exactly half a US fluid ounce, which equals 14.78676478125 milliliters; many American measuring-spoon sets stamp that volume even when casual recipes round it to fifteen. In metric cooking countries—most of Europe, Canada’s metric labels, and modern UK kitchen practice—the standard measuring tablespoon is defined as exactly fifteen milliliters, which is easy to teach and matches SI-friendly recipe cards.
Australia (and some New Zealand kitchenware) uses a larger twenty-milliliter tablespoon as the national standard measuring spoon, so an Australian “two tablespoons of oil” is thirty-three percent more liquid than the same words under the metric-fifteen system and more still than a strict US legal spoon. If you convert without naming the system, a sauce, marinade, or baking liquid can drift by several milliliters per spoon—enough to throw off emulsions, yeast dough hydration, or medication-style kitchen dosing when recipes cross borders.
Teachers, recipe importers, and automated graders can therefore assert exact numbers: two US tablespoons become 29.5735295625 milliliters, two metric tablespoons become thirty milliliters, and two Australian tablespoons become forty milliliters, each with the same formula shape and no hidden rounding until the shared twelve-decimal publish step.
Practical tips, limits, and related searches
Always pick the system that matches the recipe’s origin or the measuring spoons in your drawer: US legal for American nutrition-style spoons, metric for fifteen-milliliter European and Canadian sets, and Australian for twenty-milliliter Aussie spoons. Prefer sending numbers rather than pre-formatted strings when you control the client; string numbers are accepted only when they match a strict finite numeric pattern. When teaching or writing tests, pair examples across systems with the same spoon count—two tablespoons under each system—to show how result milliliters diverge while the formula stays identical.
This landing targets people searching for a tablespoons to ml converter, tbsp to milliliters, or Australian tablespoon size online; it is not a general volume converter for cups and fluid ounces, not a teaspoon converter, and not a density-based grams tool for flour or sugar. Prefer this capability when you already know the regional tablespoon standard and only need tbsp versus milliliters; if your source uses cups, convert cups first with a dedicated cup tool, then map residual tablespoons here.
Round-trip checks are easy: convert tablespoons to milliliters and back with the same system and confirm you recover the original amount within twelve-decimal rounding, and confirm that switching only the system from metric to australian changes a one-tablespoon result from fifteen milliliters to twenty.
What you can do with it
Port overseas recipes into metric milliliters
Home cooks convert US or Australian tablespoon measures into milliliters so a digital scale or metric jug can follow a foreign recipe without guessing spoon size.
Classroom demos of regional kitchen standards
Teachers show how two tablespoons differ across US, metric, and Australian spoons while the conversion formula stays a single multiply or divide by a fixed factor.
FAQ
Can I convert milliliters back to tablespoons?
Yes. Set from to ml and to to tbsp with the same system; the result is amount divided by that system’s ml-per-tablespoon factor.
Does this convert teaspoons or cups?
No. It only converts between tablespoons and milliliters under the three regional tablespoon standards. Use a dedicated tool for teaspoons, cups, or general volume units.
Is the tablespoons to ml converter free?
The browser tool is free and runs locally.
How many milliliters is an Australian tablespoon?
An Australian tablespoon holds 20 ml, the national standard there and on some New Zealand kitchenware. That is larger than the metric tablespoon of 15 ml and the US legal tablespoon of 14.78676478125 ml.
Which tablespoon system should I choose?
Pick the one that matches where the recipe comes from or the spoons in your drawer: US for American nutrition-style spoons, metric for 15 ml European and Canadian sets, and Australian for 20 ml spoons.
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/tbsp-ml \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"amount":2,"system":"us","from":"tbsp","to":"ml"}'const res = await fetch("https://api.kit.forhosting.com/cook/tbsp-ml", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"amount": 2,
"system": "us",
"from": "tbsp",
"to": "ml"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/cook/tbsp-ml",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"amount": 2,
"system": "us",
"from": "tbsp",
"to": "ml"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/cook/tbsp-ml", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"amount":2,"system":"us","from":"tbsp","to":"ml"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"amount":2,"system":"us","from":"tbsp","to":"ml"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/cook/tbsp-ml", 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",
"from": "tbsp",
"to": "ml"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "cook.tbsp_ml",
"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 | 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
Unknown systems are rejected with a clear invalid_input error instead of silently assuming metric, so a typo or unsupported regional name never becomes a wrong sauce ratio.
Why tablespoon size depends on the culinary system
This converter forces an explicit system on every call, applies one fixed factor, and never invents a fourth standard.
How to call the API and what comes back
Accepted system tokens include us, usa, american, metric, eu, canadian, australian, au, aus, and compact forms such as 15 ml or 20 ml; accepted unit tokens include tablespoon, tablespoons, milliliter, millilitre, ml, and cc. Send a JSON body with four required fields: amount (aliases value, qty, quantity, n)—a finite number whose absolute value stays within one trillion—system (aliases tbsp_system, region, standard, size) naming the tablespoon standard, from (aliases from_unit, unit_from, source) as tbsp or ml, and to (aliases to_unit, unit_to, target) as tbsp or ml. On success the response echoes rounded amount, the canonical system id and system_label, from and to, result as the converted number, ml_per_tbsp as the factor for that system, formula describing multiply or divide by the factor (or identity when units match), direction as a short from-arrow-to string, message as an English summary, and steps as an ordered array of substitution lines. Converting tablespoons to milliliters multiplies amount by ml_per_tbsp; converting milliliters to tablespoons divides by the same factor; when from equals to the amount is returned unchanged but the factor is still reported so callers can log the standard they used. Failed validation—missing fields, non-finite numbers, values outside absolute limits, an unknown system, or an unknown unit—returns invalid_input and is never charged. Pricing is a flat $0.002 per successful request with unit item and zero marginal unit price.
Practical tips, limits, and related searches
Keep absolute amounts inside the published trillion limit so intermediate products stay finite in IEEE double precision on the Worker and in the browser. Failed tasks that return invalid_input do not consume prepaid balance, which keeps exploratory scripts cheap when you deliberately send an unknown system such as imperial_old to verify error handling.
Integration use cases
Deterministic tests for recipe apps
Developers generate golden tbsp↔ml pairs for US, metric, and Australian systems, plus deliberate unknown-system rejections, for unit tests and CI fixtures.
Technical questions
How many milliliters are in one tablespoon?
It depends on the system: US legal is 14.78676478125 ml, metric is 15 ml, and Australian is 20 ml. This tool requires you to choose the system so the answer is unambiguous.
What happens if I send an unknown system?
The API returns invalid_input naming the unsupported system. Only us, metric, and australian (plus documented aliases) are accepted.