Sound absorption converter
100 sabins are 9.290304 metric sabins. Convert an absorption area between sabins, metric sabins and square metres, feet, centimetres or yards when a room report, a datasheet and a building note use different units. 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
- sabin
- Target unit
- metric_sabin
- Result
- 9.290304
- From label
- sabin (imperial)
- To label
- metric sabin
- Metric sabins
- 9.290304
A sound absorption converter turns an equivalent absorption area written in one acoustics unit into another without hunting tables for sabins, metric sabins, or square metres of open-window absorption.
What an absorption area in sabins tells you
Acousticians often express how much sound a room soaks up as an equivalent area: the size of an open window that would absorb the same amount. The imperial sabin counts that area in square feet, while the metric sabin counts it in square metres. Converting between them is therefore an area conversion, built on the exact international foot of 0.3048 metres, which makes one square foot exactly 0.09290304 square metres. That is why 100 sabins become 9.290304 metric sabins. Square centimetres and square yards are handled the same way, so a figure copied from an older catalogue or a homework sheet can join the rest of your numbers without a hand-typed factor.
Keeping US and metric documents consistent
The common trouble starts when a material schedule in square feet meets a reverberation spreadsheet in square metres, and someone types a rounded factor from memory. Here every conversion passes through metric sabins, so going from one unit to another and back again agrees up to twelve decimal places, and no table of pairs can drift out of step. Keep in mind what the tool does not do: it does not estimate a room's absorption from its surfaces or predict reverberation time. Use it to put manufacturer data, inventory totals and drawings on the same unit before you run those calculations elsewhere.
Everyday uses in room acoustics
Use the free in-browser sound absorption converter when you need a quick sabins-to-metric-sabins, square-feet-to-square-metres, or centimetres-to-metric-sabins check while reading a room-acoustic report, product datasheet, building-code note, or 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, consultants, and facility engineers expect on paper.
What you can do with it
Room acoustic inventories
Convert total absorption between imperial sabins and metric sabins so US and SI drawings, material schedules, and RT60 spreadsheets stay consistent without hand-written area factors.
Product datasheets and catalogues
Normalize manufacturer absorption areas from square feet or square metres into sabins or metric sabins for comparison tables and procurement APIs.
FAQ
Which sound absorption units does this converter support?
Imperial sabin, metric sabin, square metres (m2), square feet (ft2), square centimetres (cm2), and square yards (yd2).
What is the difference between a sabin and a metric sabin?
One sabin is the absorption of one square foot of a perfectly absorbing surface. One metric sabin is the absorption of one square metre. Exactly 1 ft² = 0.09290304 m² using the international foot.
What happens if I send an unknown unit?
The message names the field and lists supported units. Validation failures are not charged.
Is the sound absorption converter free?
The browser tool runs free on your device.
Does it calculate reverberation time or absorption coefficients?
No. It converts an absorption area you already have from one unit to another. Material coefficients, room volumes and reverberation formulas are deliberately left out, so the conversion stays predictable under one clear convention.
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/sound-absorption \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"value":100,"from":"sabin","to":"metric_sabin"}'const res = await fetch("https://api.kit.forhosting.com/conv/sound-absorption", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"value": 100,
"from": "sabin",
"to": "metric_sabin"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/sound-absorption",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"value": 100,
"from": "sabin",
"to": "metric_sabin"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/sound-absorption", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"value":100,"from":"sabin","to":"metric_sabin"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"value":100,"from":"sabin","to":"metric_sabin"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/sound-absorption", 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": 100,
"from": "sabin",
"to": "metric_sabin"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.sound_absorption",
"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 acoustic pipelines need the same contract from servers and automation.
Supported units and how absorption conversion is computed
Factors follow the exact international foot: one foot is exactly zero point three zero four eight metres, so one square foot is exactly zero point zero nine two nine zero three zero four square metres, and one square yard is exactly zero point eight three six one two seven three six square metres. Because the intermediate is always metric sabins, 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. Material absorption coefficients, room volumes, and reverberation formulas are intentionally out of scope so laboratory and design users get predictable unit conversion under one clear SI-foot convention. The converter accepts six absorption families under stable canonical codes: sabin for the imperial or English sabin, metric_sabin for the metric sabin, m2 for square metres of absorption, ft2 for square feet of absorption, cm2 for square centimetres, and yd2 for square yards. Friendly aliases such as sabins, imperial sabin, metric sabins, square metre, square meter, square foot, square feet, sq m, sq ft, and common hyphen or underscore spellings are normalized case-insensitively so forms and APIs can pass either short codes or full names. By definition one imperial sabin equals the absorption of one square foot of a perfectly absorbing surface, and one metric sabin equals the absorption of one square metre of a perfectly absorbing surface; therefore sabin and ft2 share the same magnitude factor, and metric_sabin and m2 share magnitude one. Every request multiplies the input value by the exact metric-sabins-per-unit factor for the source, then divides by the 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 absorption deltas 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, quantity, and absorption 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 metric_sabins quantity, the dimensionless factor from source to target, a short formula line suitable for UI display, the method tag sound_absorption_si_foot, 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. Extremely large magnitudes are rejected above a published safety cap so Worker isolates stay bounded while still covering every practical room-acoustic inventory.
Browser use, API pricing, and everyday acoustic workflows
Switch to the prepaid API when an acoustic consultancy tool, auditorium design app, classroom HVAC noise pipeline, material catalogue, or homework checker must convert absorption areas 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 sound-pressure level conversion when a product pipeline needs both absorption area and decibel SPL, or call it alone when search traffic is specifically for sabins, metric sabins, and square metres of absorption rather than a general unit switchboard.
Integration use cases
Homework and design checkers
Acoustics courses and consultancy tools call a prepaid deterministic endpoint to convert absorption units and get clear invalid_input on unknown tokens.
Technical questions
How do I convert 100 sabins to metric sabins?
Send JSON with value: 100, from: "sabin", to: "metric_sabin". The response result is 9.290304, plus a metric_sabins intermediate and a readable formula.