Oz to cc converter
Turn a US fluid-ounce volume into the cc marked on syringes and glassware: 1 fl oz is 29.5735 cc, so a cup of 8 fl oz is 236.588 cc, never a weight ounce or a UK ounce by mistake. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Oz
- 1
- Result
- 29.5735 cc
- Converted
- 29.5735
- Fl oz
- 1
- Fluid ounces
- 1
An ounces-to-cubic-centimeters converter turns a volume written in US fluid ounces into the cubic-centimeter (cc) scale printed on syringes, laboratory glassware, mould notes, and engine plates.
Why US fluid ounces convert to cubic centimeters at 29.5735
A US fluid ounce is a customary volume; a cubic centimeter is an SI-derived volume written as cc or cm³ on syringes, pipettes, mould cavities, and small-engine plates. Those two names are not interchangeable without a factor, and this landing uses the conventional four-decimal factor that people type when they search oz to cc: one US fluid ounce equals 29.5735 cubic centimeters.
That figure is the everyday rounding of the exact US liquid definition—one US gallon is two hundred thirty-one cubic inches with the international inch exactly 2.54 centimeters, hence 3.785411784 litres, and that gallon divides into one hundred twenty-eight US fluid ounces, giving 29.5735295625 millilitres exactly. Because one millilitre is one cubic centimeter by SI identity, the same number is the cubic-centimeter equivalent.
Searchers who type oz to cc almost always want that US fluid-ounce path printed as cc, not an avoirdupois weight ounce of 28.349523125 grams and not the imperial (UK) fluid ounce of 28.4130625 millilitres, which would understate a US pour. This page therefore stays on US fluid ounces to cubic centimeters only. Zero ounces maps cleanly to zero cubic centimeters.
Negative volumes are rejected because a physical pour cannot be negative, and values that are not finite numbers are rejected so the multiply never invents a volume from text, NaN, or Infinity.
Practical tips, checks, and related searches
Round-trip sanity checks are easy: convert one US fluid ounce and confirm you receive 29.5735 cubic centimeters after rounding, convert eight fluid ounces—one US cup—and confirm 236.588 cubic centimeters, convert sixteen fluid ounces—one US pint—and confirm 473.176 cubic centimeters, or convert zero and confirm zero. When teaching, show that dividing the published cubic centimeters by 29.5735 recovers the original fluid ounces within the same twelve-decimal rounding used for published fields, which makes the factor visible instead of hiding it behind a mysterious coefficient.
Stay inside the non-negative range so a kitchen or clinic typo cannot produce a negative pour the solver must reject, and never send a weight in avoirdupois ounces hoping the tool will treat dry ounces as fluid volume. This landing targets people searching for oz to cc, convert fluid ounces to cubic centimeters, or a calculator that states one fl oz equals 29.5735 cc; it is not a general multi-unit volume hub, not an imperial-fluid-ounce path, not a millilitres-to-cc identity converter, and not a grams-by-density path.
Prefer this capability when the input is already in US fluid ounces and you only need cubic centimeters; if you must convert among many kitchen systems in one call, use a broader cooking converter instead. Pin the rounded cc in tests, keep the 29.5735 factor visible next to the input, and document that a legal metrology lab may prefer the longer 29.5735295625 millilitre definition when custody transfer is on the line.
What you can do with it
Syringe and medicine-cup dosing
Turn US fluid-ounce marks on bottles, cups, and oral syringes into cubic-centimeter (cc) labels for pharmacy notes and dosing sheets with the same 29.5735 factor every row.
Lab glassware and mould-cavity notes
Convert a US fluid-ounce fill volume into metric cc for pipettes, mould cavities, and workshop notes that print cubic centimeters instead of customary ounces.
FAQ
What formula converts oz to cc?
Cubic centimeters = US fluid ounces × 29.5735. This landing uses that conventional four-decimal factor; one millilitre equals one cubic centimeter, so the result is also millilitres.
Is this US fluid ounces or weight ounces?
US fluid ounces only. Input is a volume, not an avoirdupois weight ounce of 28.349523125 g, and not the imperial (UK) fluid ounce of 28.4130625 ml.
Why 29.5735 and not a shorter 30 cc rule of thumb?
Kitchen slogans that treat one ounce as thirty cubic centimeters are about one and a half percent high. This converter multiplies by 29.5735 so a one-ounce pour is 29.5735 cc, not 30.
Is the oz to cc converter free?
The browser tool is free and runs locally.
How many cc are in a US cup or a pint?
One US cup of 8 fluid ounces is 236.588 cc, and one US pint of 16 fluid ounces is 473.176 cc. Both come from the same factor of 29.5735 cc per fluid ounce.
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/oz-to-cc-converter \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"oz":8}'const res = await fetch("https://api.kit.forhosting.com/conv/oz-to-cc-converter", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"oz": 8
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/oz-to-cc-converter",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"oz": 8
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/oz-to-cc-converter", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"oz":8}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"oz":8}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/oz-to-cc-converter", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"oz": 8
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.oz_to_cc_converter",
"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
A negative volume or a value that is not a number fails with a clear invalid_input error instead of inventing a result.
How to call the API and what comes back
Prefer bare numbers when you control the client; string numbers are accepted only when they match a strict finite numeric pattern without unit symbols, thousand separators, or currency marks attached to the value. Send a JSON body with one required non-negative finite number field named oz. Aliases fl_oz, fluid_ounces, fluid_oz, value, and volume are accepted so SDK clients and form posts can use the name that fits the product. Absolute values must stay within the published limit of one trillion, and a negative ounce value is rejected with invalid_input rather than treated as a signed delta. On success the response echoes rounded oz, fl_oz, and fluid_ounces as the same magnitude, sets cc, cubic_centimeters, result, and converted to the same rounded cubic-centimeter magnitude, unit to the token cc, from_unit to fl_oz and to_unit to cc, factor and cc_per_fl_oz to 29.5735, formula to the string cc equals oz times 29.5735 with the US fluid-ounce identity in parentheses, message to a short English summary, and steps to an ordered array of substitution lines that show the definition and the multiply. Failed validation—missing fields, non-finite numbers, bare plus or minus signs, non-numeric strings, negative ounces, values outside absolute limits, or a non-finite converted result—returns invalid_input and is never charged. Pricing is a flat $0.002 per successful request with unit item.
Practical tips, checks, and related searches
Failed tasks that return invalid_input do not consume prepaid balance, which keeps exploratory scripts cheap when learners deliberately omit oz or pass plain text instead of a number.
Integration use cases
Homework and unit-test fixtures
Students and engineers convert classroom fluid-ounce readings to cubic centimeters and pin golden JSON so browser and API arithmetic never drift.
Technical questions
What happens if oz is negative or not a number?
The API returns invalid_input naming the problem (for example a negative oz value or a volume that is not a finite number). Failed tasks are not charged.