Section modulus converter
Move a section modulus between the six length-cubed units found in steel handbooks and design guides: 1 in³ is exactly 16.387064 cm³, so metric and imperial section tables can be compared in one step. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Value
- 100
- Source unit
- cm3
- Target unit
- in3
- Result
- 6.1023744095
- From label
- cubic centimetre
- To label
- cubic inch
- Cubic metres
- 0.0001
A section modulus converter turns an elastic section-modulus value written in one length-cubed unit into another without hunting handbook tables or rewriting spreadsheet factors.
Supported units and how the conversion is computed
The converter accepts six section-modulus families under stable canonical codes: m3 for the SI cubic metre, dm3 for the cubic decimetre, cm3 for the cubic centimetre, mm3 for the cubic millimetre, in3 for the cubic inch, and ft3 for the cubic foot.
Factors follow SI and the international inch definition: one cubic decimetre is exactly one thousandth of a cubic metre, one cubic centimetre is exactly one millionth, one cubic millimetre is exactly one billionth, one cubic inch is exactly zero point zero two five four metres cubed (one point six three eight seven zero six four times ten to the minus five cubic metres), and one cubic foot is zero point three zero four eight metres cubed.
Because the intermediate is always cubic metres, converting A to B and B to A is consistent up to the published rounding of twelve decimal places, and there is no pairwise matrix that can drift out of sync. Mass moments, plastic section modulus formulas from geometry, and second-moment-only tables are intentionally out of scope so beam and column users get predictable length-cubed conversion under one clear convention.
Where section modulus conversions come up
Use the free in-browser section modulus converter when you need a quick cubic-centimetres-to-cubic-inches, cubic-metres-to-cubic-millimetres, or cubic-feet-to-cubic-centimetres check while reading a steel handbook, cold-formed section catalogue, timber design guide, or strength-of-materials homework problem. Open the page, enter the number and units, and copy the result without installing a spreadsheet, a unit library, or a desktop calculator pack. Source inputs follow the same retention rules as other KIT parse items, and results are safe to cache because the algorithm is fully deterministic.
Authors shipping mobile apps or chatbots can map the result and formula fields directly into cards that show both the number and the conversion path students, engineers, and detailers expect on paper.
What you can do with it
Steel and aluminium section catalogues
Convert manufacturer tables listed in cm³ or in³ into SI m³ (and back) so FEA imports, bolt checks, and Eurocode/AISC worksheets share one unit view without hand-written factors.
CAD and structural analysis pipelines
Normalize section-modulus fields from mixed imperial and metric model exports before stress checks, selection scripts, and automated report generation.
FAQ
Which section-modulus units does this converter support?
Cubic metres (m3), cubic decimetres (dm3), cubic centimetres (cm3), cubic millimetres (mm3), cubic inches (in3), and cubic feet (ft3).
How many cubic centimetres is one cubic inch of section modulus?
Exactly 16.387064 cm³ under the international inch (0.0254 m).
What happens if I send an unknown unit?
The message names the field and lists supported units. Validation failures are not charged.
Is the section modulus converter free?
The browser tool runs free on your device.
Why do cm³ and m³ values differ by a factor of a million?
Because the length step is cubed. A metre is 100 centimetres, so a cubic metre holds a million cubic centimetres, and a cubic millimetre is one billionth of a cubic metre.
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/section-modulus \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"value":1,"from":"cm3","to":"in3"}'const res = await fetch("https://api.kit.forhosting.com/conv/section-modulus", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"value": 1,
"from": "cm3",
"to": "in3"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/section-modulus",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"value": 1,
"from": "cm3",
"to": "in3"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/section-modulus", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"value":1,"from":"cm3","to":"in3"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"value":1,"from":"cm3","to":"in3"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/section-modulus", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"value": 1,
"from": "cm3",
"to": "in3"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.section_modulus",
"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
The browser tool runs free on your device; the prepaid API charges $0.002 per successful item when structural pipelines need the same contract from servers and automation.
Supported units and how the conversion is computed
Friendly aliases such as cubic metre, cubic meters, cubic centimetre, cubic centimeter, cubic millimetre, cubic inch, cubic inches, cubic foot, cubic feet, cm³, mm³, in³, ft³, m^3, cm^3, in^3, cc, and cu in are normalized case-insensitively so forms and APIs can pass either short codes or full names. Every request multiplies the input value by the exact cubic-metres-per-unit factor for the source, then divides by the cubic-metres-per-unit factor for the target.
Request shape, response fields, and unknown-unit errors
The error message names the bad field and lists the supported set so clients can correct forms without guessing. Negative values are allowed when you need signed section-modulus components in engineering pipelines; zero converts cleanly to zero in every target unit. Send a JSON body with three required fields: value as a finite number, from as the source unit string, and to as the target unit string. Aliases amount and quantity are accepted for value; unit_from and source for from; unit_to and target for to. On success the response echoes the canonical from and to codes, human-readable from_label and to_label strings, the converted result, the intermediate cubic_metres quantity, the dimensionless factor from source to target, a short formula line suitable for UI display, the method tag section_modulus_si, and the fixed list of units_supported. Missing value, non-finite numbers such as NaN or Infinity, missing unit fields, and any token that does not map to a supported unit fail with invalid_input and are not charged after the engine rejects the request. Identical inputs always yield identical JSON because the path is pure arithmetic with no randomness, no remote lookup, and no dependence on the wall clock, which makes the endpoint safe to pin in continuous-integration goldens and SDK contract tests. Millimetre-scale results and metre-scale results share the same code path, so extreme magnitude pairs remain well-defined as long as IEEE double precision can represent the intermediate cubic-metres product.
Browser use, API pricing, and everyday workflows
Switch to the prepaid API when a CAD plugin, structural-analysis pipeline, steel-detailing tool, finite-element pre-processor, materials LIMS, or beam-selection checker must convert section modulus at scale under a stable KIT contract at $0.002 per successful item; validation failures that raise invalid_input do not consume balance after rejection. Pair this endpoint with force or second-moment converters when a product pipeline needs several structural measure families, or call it alone when search traffic is specifically for section-modulus conversion—cubic metres, cubic centimetres, cubic millimetres, cubic inches, and cubic feet—rather than a general unit switchboard.
Integration use cases
Homework and code-compliance checkers
Convert mm³, cm³, and in³ for class problems and code minimum-S checks with a prepaid, deterministic API and clear invalid_input on unknown units.
Technical questions
How do I convert 100 cm³ to cubic inches?
Send JSON with value: 100, from: "cm3", to: "in3". The response includes result, cubic_metres intermediate, factor, and a readable formula.