Sheet metal gauge converter
Turn a gauge callout into a real thickness and back: 16 gauge steel is 0.0598 in, or 1.51892 mm, from the steel Manufacturer's Standard Gauge table for gauges 3 to 38, so quotes and nest lists agree. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Value
- 16
- Source unit
- gauge
- Target unit
- mm
- Result
- 1.51892
- From label
- Manufacturer's Standard Gauge (steel)
- To label
- millimetres
- Mm
- 1.51892
A sheet metal gauge converter turns a Manufacturer's Standard Gauge number or a thickness written in millimetres, inches, mils, or related units into any other unit in that set without hunting printed gauge charts or rebuilding spreadsheet factors.
Supported units, the MSG steel table, and how conversion works
The converter accepts seven families under stable canonical codes: gauge for Manufacturer's Standard Gauge on uncoated steel, mm for millimetres, in for inches, mil for thousandths of an inch, um for micrometres, cm for centimetres, and m for metres. When the source is a gauge number, the engine looks up the published decimal-inch thickness for that gauge in the steel MSG table covering gauges three through thirty-eight, then scales to the target unit with exact inch-to-millimetre factors.
When both ends are linear thickness units, the path multiplies by the millimetres-per-unit factor for the source and divides by the factor for the target, using one inch equals twenty-five point four millimetres exactly, one mil equals zero point zero zero one inch, and SI prefixes for micrometre, centimetre, and metre. When the target is gauge, thickness is converted to inches and the nearest table entry is returned so slightly rounded shop measurements still resolve to a useful gauge label.
Because linear routes share one millimetre intermediate, converting A to B and B to A is consistent up to the published twelve-decimal rounding, and there is no pairwise matrix that can drift out of sync. Wire AWG, Birmingham wire gauge, and separate galvanized or aluminum gauge charts are intentionally out of scope so sheet-metal users get predictable steel MSG results under one clear convention.
Gauge conversions on the shop floor and in quotes
Use the free in-browser sheet metal gauge converter when you need a quick gauge-to-millimetres, millimetres-to-gauge, or inches-to-mils check while reading a drawing, nesting nest report, or supplier email. Open the page, enter the number and units, and copy the result without installing a spreadsheet, a CAD plugin, 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, formula, and intermediate mm or inches fields directly into cards that show both the number and the conversion path fabricators expect on paper.
What you can do with it
Fab quotes and nest lists
Convert drawing gauge callouts to millimetres or inches so quotes and nesting software share one thickness without hand-written charts.
ERP and job-shop estimators
Normalize mixed gauge and metric thickness fields so inventory, BOM, and pricing pipelines compare sheet stock consistently.
FAQ
How do I convert 16 gauge sheet metal to millimetres?
The response includes result in millimetres plus intermediate inches from the MSG steel table.
Which sheet metal units are supported?
Canonical units are gauge, mm, in, mil, um, cm, and m.
What happens if I send an unknown unit?
The error message names the bad field and lists supported units; validation failures are not charged.
Is the sheet metal gauge converter free?
The browser tool runs free on your device.
Which gauge table is used?
Manufacturer's Standard Gauge for uncoated steel, gauges 3–38, with the exact international inch of 25.4 mm for linear thickness conversion.
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/sheet-metal-gauge \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"value":16,"from":"gauge","to":"mm"}'const res = await fetch("https://api.kit.forhosting.com/conv/sheet-metal-gauge", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"value": 16,
"from": "gauge",
"to": "mm"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/sheet-metal-gauge",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"value": 16,
"from": "gauge",
"to": "mm"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/sheet-metal-gauge", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"value":16,"from":"gauge","to":"mm"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"value":16,"from":"gauge","to":"mm"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/sheet-metal-gauge", 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": 16,
"from": "gauge",
"to": "mm"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.sheet_metal_gauge",
"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 pipelines need the same contract from servers and automation.
Supported units, the MSG steel table, and how conversion works
Friendly aliases such as ga, msg, standard gauge, inch, inches, thou, micron, and µm are normalized case-insensitively so forms and APIs can pass either short codes or full names.
Request shape, response fields, and unknown-unit or gauge errors
The error message names the bad field and lists the supported set or the valid gauge range so clients can correct forms without guessing. Zero and negative thicknesses are rejected when converting to gauge because no positive table match exists; linear thickness conversions allow signed values when you need deltas in a pipeline. 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, quantity, thickness, and gauge 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, intermediate mm and inches fields, an optional dimensionless factor when the path is linear or gauge-to-thickness, a short formula line suitable for UI display, the method tag sheet_metal_msg_steel, gauge_table manufacturer_standard_steel, the fixed gauge_range, and the list of units_supported. When converting to gauge the payload also includes nearest_gauge, table_inches, and delta_inches so you can see how far the input sits from the published table value. Missing value, non-finite numbers such as NaN or Infinity, missing unit fields, any token that does not map to a supported unit, non-integer gauge inputs, and gauge numbers outside three through thirty-eight 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 table lookup and arithmetic with no randomness, no remote catalog, and no dependence on the wall clock, which makes the endpoint safe to pin in continuous-integration goldens and SDK contract tests.
Browser use, API pricing, and fab-shop or manufacturing workflows
Switch to the prepaid API when a job-shop estimator, sheet-metal ERP, nest optimizer, e-commerce metal storefront, or manufacturing pipeline must convert mixed gauge and metric thickness 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 length or mass converters when a cut-and-bend pipeline needs several measure families, or call it alone when search traffic is specifically for sheet metal gauge conversion—standard gauge, millimetres, and inches—rather than a general unit switchboard.
Integration use cases
Metal storefronts and QA checks
Call a prepaid, deterministic sheet metal gauge API from product pages and inspection tools with clear invalid_input on unknown units.