Tablespoons to milliliters converter
2 US tablespoons are 29.5735295625 mL, because one US tablespoon is exactly 14.78676478125 mL. Convert American recipe and label amounts into millilitres without quietly swapping in the 15 mL metric spoon. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Tablespoons
- 2
- Milliliters
- 29.5735295625
This US tablespoons to milliliters converter turns a non-negative volume into a metric measurement using the fixed relationship one US tablespoon equals 14.78676478125 milliliters. Enter the tablespoon amount as a finite number and receive the corresponding volume in milliliters. The calculation is deterministic and performs no network request, estimation, or ingredient-dependent adjustment. That makes it useful for recipes, kitchen labels, data normalization, and automated tests where a stable numerical result matters. Negative amounts, missing values, infinity, and non-numeric input are rejected clearly instead of producing a misleading measurement.
Understand the US tablespoon used by this converter
A tablespoon is not one universal volume in every country, so the unit definition matters before any conversion begins. This capability specifically uses the US customary tablespoon. One US tablespoon is three US teaspoons, one half of a US fluid ounce, and exactly 14.78676478125 milliliters under the fixed unit relationship used for the calculation.
The converter therefore multiplies the submitted tablespoon amount by 14.78676478125. It does not silently substitute the 15 milliliter metric tablespoon commonly used in many recipes, and it does not use the 20 milliliter Australian tablespoon. Those alternatives can create noticeable differences when several spoonfuls are involved.
For example, treating four US tablespoons as four metric tablespoons would round the result to 60 milliliters instead of preserving the more precise US conversion. Always check the source of a recipe, label, or dataset when the word tablespoon appears without a regional qualifier. If the source is American or explicitly says US tbsp, this converter uses the appropriate definition.
A zero input is valid and returns zero milliliters, while negative volumes are rejected because this capability models a physical quantity rather than a signed change or accounting adjustment.
Send a valid value and interpret the result
The value may be an integer or a decimal, so quantities such as one, two and a half, or one eighth can be represented directly. The number must be finite and at least zero. The core calculation does not apply display-oriented rounding, because downstream callers may need the available precision for totals, comparisons, or their own formatting rules.
A user interface may choose to show fewer decimal places, but stored data and chained calculations should retain enough precision for the intended job. The execution is pure arithmetic: it does not inspect a recipe ingredient, infer density, consult a remote service, read the clock, or introduce randomness. Volume-to-volume conversion does not require density; density becomes relevant only when converting a volume into mass, such as tablespoons of flour into grams.
Invalid requests are rejected by the input path rather than being converted into a plausible but incorrect zero.
Use precise conversions in recipes and software
For ordinary cooking, the number of decimal places you display depends on the measuring equipment and the recipe's tolerance. A medicine syringe or laboratory pipette may justify more precision than a marked kitchen jug, while a sauce recipe may work perfectly with a practical rounded value. Keep the exact converter output during calculation and round only at the final presentation step to avoid compounding small errors across multiple ingredients or servings.
In software, document that the source unit is US tablespoons, store the canonical unit beside the value, and avoid reusing a field named tablespoon for metric or Australian measurements. Also test a negative number and a non-finite or non-numeric value to confirm validation remains active. If an input comes from prose such as “two heaped tablespoons,” first decide what numerical volume that phrase represents, because heap size is not standardized.
What you can do with it
Convert an American recipe
Turn numeric US tablespoon measurements into milliliters before following a recipe with metric measuring tools.
Normalize kitchen data
Store imported US volume measurements in milliliters while preserving a consistent, documented conversion factor.
FAQ
How many milliliters are in one US tablespoon?
One US tablespoon equals 14.78676478125 milliliters in this converter.
Is a US tablespoon exactly 15 milliliters?
No. Fifteen milliliters is the metric tablespoon convention. A US tablespoon converts to 14.78676478125 milliliters.
Does this support Australian tablespoons?
No. An Australian tablespoon is commonly 20 milliliters, while this capability accepts US tablespoons only.
Do I need to know the ingredient, like flour or oil?
No. Tablespoons to millilitres is volume to volume, so density plays no part. Density only matters when you turn a volume into a weight, such as tablespoons of flour into grams.
How many teaspoons are in a US tablespoon?
Three US teaspoons, which is also half a US fluid ounce. This converter returns millilitres only, but those relations help when a recipe mixes spoon sizes.
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/tbsp-to-ml \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"tablespoons":2}'const res = await fetch("https://api.kit.forhosting.com/conv/tbsp-to-ml", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"tablespoons": 2
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/tbsp-to-ml",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"tablespoons": 2
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/tbsp-to-ml", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"tablespoons":2}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"tablespoons":2}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/tbsp-to-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
{
"tablespoons": 2
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.tbsp_to_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.
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
Send a valid value and interpret the result
Provide one JSON number in the tablespoons field; the shorter alias tbsp is also accepted for callers that already use common kitchen abbreviations. Missing fields, text strings, null, NaN, positive or negative infinity, and negative quantities fail with an invalid_input error. On success, the response contains milliliters as a JSON number. Each successful API request costs $0.002.
Use precise conversions in recipes and software
This capability handles one quantity per request and returns milliliters only; it is not a general recipe parser, serving scaler, mass converter, or bidirectional unit engine.
Integration use cases
Build reliable test fixtures
Generate deterministic expected milliliter values for cooking, nutrition, or measurement software tests.
Technical questions
Can I submit a fractional tablespoon?
Yes. Submit any finite non-negative JSON number, including decimals such as 0.5 or 1.25.
What does the API request cost?
Each successful API request costs $0.002. The same deterministic conversion can run free in the browser.