CM to feet converter
152.4 cm is exactly 5 feet, because one foot is defined as 30.48 cm. Convert heights, room sizes or furniture dimensions from centimetres to feet with that exact factor rather than a rough divide-by-30. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Cm
- 30.48
- Result
- 1 ft
- Converted
- 1
- Feet
- 1
- From unit
- cm
A centimetres-to-feet converter turns a metric length into the international foot value used on US construction drawings, height charts, room dimensions, product size tables, and body-measurement notes sold or quoted in feet. Approximate mental shortcuts such as divide by thirty are rejected in favour of the 1959 yard and pound agreement constant, so homework checks and product tables match engineering definitions.
Why centimetres and international feet still meet at 30.48
Centimetres belong to the SI family of length units used on metric construction drawings, medical height charts outside the United States, clothing size tables, school science labs, and most international product specifications that report small-to-medium lengths in centimetres rather than metres. International feet remain standard on US architectural plans, building height labels, room dimensions, furniture catalogs, human height notes in imperial countries, and many clearance notes that still quote imperial length.
The bridge between them is not a survey approximation: since the 1959 international yard and pound agreement, one international foot is defined as exactly zero point three zero four eight metres, which is exactly thirty point four eight centimetres because one metre equals one hundred centimetres. Equivalently, one inch is two point five four centimetres and twelve inches make one foot, so twelve times two point five four is thirty point four eight.
That makes the conversion a single exact division, feet equals centimetres divided by thirty point four eight, or equivalently centimetres times the reciprocal factor one over thirty point four eight. Teachers and trades often still teach the rough rule of thumb divide by thirty, but that introduces a scale error that shows up immediately on a one-hundred-eighty-centimetre height reading or a two-hundred-centimetre furniture height.
Practical tips, checks, and related searches
Round-trip sanity checks are easy: convert a known textbook value such as thirty point four eight centimetres and confirm you receive exactly one foot after rounding, or convert one hundred centimetres and confirm roughly three point two eight zero eight feet. Convert one hundred fifty-two point four centimetres to confirm five feet when teaching height conversions. When teaching, pair the exact path with the mental shortcut so students see the drift on long lengths.
Stay inside the absolute range so the division cannot overflow into a non-finite result the solver must reject. This landing targets people searching for cm to feet, convert centimeters to feet, centimetres to feet, or an exact thirty point four eight calculator; it is not a general multi-unit length hub, not a feet-to-centimetres primary form, not a metres-to-feet tool, not an inches converter as its primary purpose, and not an astronomical distance converter.
Prefer this capability when the input is already in centimetres and you only need international feet; if you must convert among many units in one call, use a broader unit converter instead. If your source data is already in metres, prefer a metres-to-feet converter rather than multiplying by one hundred first, unless you deliberately want centimetre precision in the intermediate step.
What you can do with it
Height charts and body measurements
Turn metric height readings in centimetres into international feet for US-facing medical notes, sports profiles, and clothing size guides with the same exact factor every row.
Furniture and product size tables
Merchants convert centimetre product dimensions to feet and compare hand work against deterministic steps before publishing imperial size charts.
FAQ
What formula converts cm to feet?
Feet = centimetres ÷ 30.48. One international foot is defined as exactly 30.48 centimetres (0.3048 metres) by the 1959 international yard and pound agreement.
Is 30.48 exact or approximate?
Exact. This tool uses the international foot definition (12 × 2.54 cm), not a US survey foot or a rough divide-by-30 estimate.
Can I convert feet back to centimetres?
This capability is centimetres → feet only. Multiply feet by 30.48 on your side, or use a bidirectional length converter for other units.
Is the cm to feet converter free?
The browser tool is free and runs locally.
Why not just divide by 30?
Because that shortcut gives a slightly larger result than the real one, and the error shows up right away on a 180 cm height or a 200 cm wardrobe. The converter always divides by the exact 30.48.
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/cm-to-feet \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"cm":30.48}'const res = await fetch("https://api.kit.forhosting.com/conv/cm-to-feet", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"cm": 30.48
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/cm-to-feet",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"cm": 30.48
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/cm-to-feet", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"cm":30.48}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"cm":30.48}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/cm-to-feet", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"cm": 30.48
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.cm_to_feet",
"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
Invalid or missing input fails with a clear invalid_input error instead of inventing a number.
How to call the API and what comes back
Absolute values must stay within the published limit of one trillion. Send a JSON body with one required finite number field named cm. Aliases centimeters, centimetres, value, length, cm_value, and distance are accepted so SDK clients and form posts can use the name that fits the product. On success the response echoes rounded cm, sets feet, result, and converted to the same rounded foot magnitude, unit to the token ft, from_unit to cm and to_unit to ft, factor to the rounded reciprocal one over thirty point four eight, cm_per_foot to the exact constant thirty point four eight, formula to the string feet equals cm divided by thirty point four eight, message to a short English summary, and steps to an ordered array of substitution lines. Failed validation—missing fields, non-finite numbers, bare plus or minus signs, non-numeric strings, 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 and zero marginal unit price. Prefer bare numeric JSON when you control the client; string numbers are accepted only when they match a strict finite numeric pattern without unit suffixes, thousand separators, or currency symbols.
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 cm or pass text.
Integration use cases
Homework and unit-test fixtures
Students and engineers convert classroom centimetre readings to feet and pin golden JSON so browser and API arithmetic never drift.
Technical questions
What happens on missing or non-numeric input?
The API returns invalid_input naming the problem (for example a missing cm field). Failed tasks are not charged.