Cubic yards to tons converter
10 cubic yards of gravel at 1.4 tons per yard weigh 14 US short tons, or 28,000 pounds: multiply a measured bed or load by the supplier's bulk density to see what the quarry or scale ticket will show. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Cubic yards
- 10
- Density
- 1.4
- Result
- 14
- Tons
- 14
- Weight tons
- 14
- Pounds
- 28,000
A cubic-yards-to-tons converter turns a bulk volume into a shipping or purchase weight once you know the material density. Contractors, landscapers, and estimators buy gravel, sand, topsoil, crushed stone, and concrete by the cubic yard at the pit, then pay haulage or mix plants by the ton. This calculator multiplies cubic yards by a chosen bulk density in US short tons per cubic yard and returns the weight in tons, plus the equivalent pounds from the exact two-thousand-pound short-ton definition.
What cubic yards to tons means and why density is required
Bulk materials occupy space and they have mass. A cubic yard is a cube three feet on a side, twenty-seven cubic feet, the yardage unit used on dump tickets and landscape quotes in the United States. A ton in this converter is the US short ton of exactly two thousand avoirdupois pounds, the unit that appears on highway weight tickets and most US aggregate invoices.
The identity that connects them is mass equals volume times density, written here as tons equals cubic yards times density, where density is expressed in short tons per cubic yard so the units cancel cleanly. Typical bulk densities used in the field are about one point one tons per yard for loose topsoil, one point three to one point four for damp sand or gravel, and about two for ordinary concrete or asphalt. If your supplier quotes pounds per cubic yard, divide by two thousand to obtain tons per yard.
If they quote pounds per cubic foot, multiply by twenty-seven then divide by two thousand.
Where a cubic-yards-to-tons converter earns its keep
Landscape crews use a cubic-yards-to-tons converter when a quarry quotes stone by the ton but the bed was measured in cubic yards from area times depth. Ready-mix and demolition haulers convert yardage into axle loads before a truck leaves the site so they stay under bridge and highway limits.
Pin the rounded tons in tests, keep the density unit visible next to the input, and document that wetness and compaction change bulk density so a lab or supplier figure beats a rule of thumb when money or legal axle weights are on the line.
What you can do with it
Landscape and aggregate orders
Turn a measured cubic-yard bed of gravel, sand, or topsoil into the tonnage a quarry or landscape yard will invoice, using the supplier's bulk density.
Haulage and axle-load checks
Convert dump-truck yardage into US short tons and pounds before leaving the site so loads stay under highway and bridge limits.
FAQ
How do I convert cubic yards to tons?
Multiply the volume in cubic yards by the material bulk density in US short tons per cubic yard.
What density unit does the converter expect?
Density is in US short tons per cubic yard. If you have pounds per cubic yard, divide by 2000. If you have pounds per cubic foot, multiply by 27 then divide by 2000.
What happens if density is zero or negative?
Material density must be strictly positive; a non-positive density is not billed.
Is the result in metric tons or US short tons?
In US short tons of exactly 2,000 pounds, the ton used on US weight tickets and most aggregate invoices. The converter also shows the weight in pounds, which is the tons figure times 2,000.
What density should I enter for gravel, sand or topsoil?
Use the bulk density your supplier gives in tons per cubic yard. Typical field figures are about 1.1 for loose topsoil, 1.3 to 1.4 for damp sand or gravel and about 2 for concrete or asphalt, but wetness and compaction change them.
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/cubic-yards-to-tons \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"cubic_yards":10,"density":1.4}'const res = await fetch("https://api.kit.forhosting.com/conv/cubic-yards-to-tons", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"cubic_yards": 10,
"density": 1.4
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/cubic-yards-to-tons",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"cubic_yards": 10,
"density": 1.4
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/cubic-yards-to-tons", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"cubic_yards":10,"density":1.4}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"cubic_yards":10,"density":1.4}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/cubic-yards-to-tons", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"cubic_yards": 10,
"density": 1.4
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.cubic_yards_to_tons",
"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
Density must be strictly positive; a negative volume is rejected as invalid_input rather than a signed mass.
What cubic yards to tons means and why density is required
Those two quantities are not interchangeable without density: a yard of dry mulch is far lighter than a yard of wet gravel or ready-mix concrete. This endpoint does not guess a material for you; you choose the density so the result matches the product you are actually hauling, compacted or loose, dry or wet, as your supplier measured it.
Input contract, response shape, and error behaviour
Numeric strings that match a finite number pattern are accepted; empty strings, NaN, Infinity, and non-numeric text are not. Failed validation is not billed. Example: ten cubic yards at one point four tons per yard returns fourteen tons, which is twenty-eight thousand pounds. POST a JSON body with two required finite numbers. cubic_yards is the volume in cubic yards; it may be zero, which converts to zero tons, but it must not be negative because a negative bulk volume has no meaning on a delivery ticket. Aliases volume, yd3, cubic_yard, yards, and cu_yd are accepted. density is the material bulk density in US short tons per cubic yard and must be strictly positive—zero and negative densities fail with invalid_input naming the field. Aliases rho, material_density, tons_per_yd3, and bulk_density map the same value. On success the response echoes rounded cubic_yards and density, sets tons, weight_tons, and result to the same rounded short-ton weight, pounds to that weight times two thousand, unit to US short ton, density_unit to ton/yd³, formula to the identity tons equals cubic_yards times density, plus a short message and substitution steps. Pair the numeric result with your own moisture and compaction notes; this endpoint converts units, it does not sample the pile.
Where a cubic-yards-to-tons converter earns its keep
Estimating software needs a deterministic API that will not invent a default gravel density when the user omitted it, and that will fail loudly if someone pastes a negative excavation volume from a signed cut-fill sheet.
Integration use cases
Estimating pipelines and widgets
Call a deterministic cubic-yards-to-tons API from takeoff software or a free on-page widget so quotes and invoices share one formula.
Technical questions
Can the volume be zero or negative?
Zero cubic yards converts to zero tons. A negative volume is rejected as invalid_input because bulk delivery tickets do not use signed yardage as mass.
What does the cubic yards to tons converter cost?
The browser tool is free. API requests use prepaid KIT balance at $0.002 per successful call; invalid input is not billed.