Gravel driveway calculator
A 50 by 12 foot driveway with 4 inches of gravel takes 7.4074 cubic yards, about 10.3704 tons at 1.4 tons per yard. Measure the run and the lane, pick a depth and order the right load. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Length
- 50
- Width
- 12
- Depth
- 4
- Length ft
- 50
- Width ft
- 12
- Depth inches
- 4
- Area sqft
- 600
A gravel driveway is bought as cubic yards of crushed stone and weighed in tons, but it is measured as a rectangle: length along the run, width of the travel lane, and compacted depth of aggregate. This calculator converts those three driveway dimensions into the bulk volume a quarry quotes and the short-ton weight a dump truck typically carries. Length and width are feet; depth is inches, the unit most residential specs use for a four-to-six-inch base. Cubic feet equal length times width times depth divided by twelve; cubic yards divide that result by twenty-seven; tons multiply yards by bulk density.
What the calculator returns and how driveway gravel volume is defined
Driveway gravel volume here is the bulk crushed-stone or aggregate needed to fill a rectangular driveway to a uniform compacted depth, expressed in cubic feet and cubic yards, plus a short-ton weight derived from bulk density. Cubic yards are the unit bulk yards and dump-truck brokers use for crusher run, number fifty-seven stone, recycled concrete, and similar driveway products; cubic feet help you cross-check bag labels when a short patch stays on the retail aisle.
The conversion is the identity used on every driveway take-off sheet: one cubic yard equals twenty-seven cubic feet, and depth in inches must be divided by twelve before multiplying by length and width in feet. Equivalently, cubic yards equal length times width times depth in inches divided by three hundred twenty-four, because twelve times twenty-seven is three hundred twenty-four.
Weight in short tons multiplies that cubic-yard figure by the supplier’s bulk density in tons per cubic yard; the default of one point four approximates many dry crushed driveway stones, but wet rock, dense basalt, or compacted crusher run may sit higher, and lightweight recycled product may sit lower. Treat the result as a planning estimate and round up slightly for irregular edges, turnout flares, or a modest waste allowance your supplier recommends.
Where driveway gravel estimates fit for DIY, quotes, and software
Homeowners meet this problem when a new gravel driveway needs four to six inches of compacted stone over a prepared subgrade, when a long rural run is measured in feet but the bulk yard quotes tons, or when bagged product at the store must be compared against a dump-truck delivery of the same yardage.
Trade estimators use the same identity across dozens of jobs: measure length and width, pick a depth from the civil or landscape schedule, convert to yards for the delivery truck, and multiply by the quarry density sheet for tons so the gate scale and the material take-off stay aligned. Teachers and vocational trainers can pre-generate answer keys for modest driveway sizes without trusting opaque mobile apps that switch units mid-form or forget that depth is inches while length and width are feet and bulk weight is tons per yard.
Developers call the same contract from scripts to seed deterministic test vectors for driveway calculators, to normalise user-entered sizes before a cart suggests yardage or tonnage, or to satisfy programming-challenge statements that demand cubic yards and tons rather than a hand-waved “about eight yards.” Product tools use the rewrite when a homeowner types fifty feet by twelve feet by four inches and the UI must show yardage and a clean ton total before checkout.
Pair it with unit converters when your tape is metric, with landscape-bed or generic area helpers when the same property will receive mixed finishes, and with other build helpers when you are assembling a small lab of free, deterministic planning tools for outdoor construction.
What you can do with it
New residential gravel driveway takeoff
Enter length and width in feet plus a four-to-six-inch depth to know cubic yards for bulk delivery and tons for the yard ticket.
Contractor driveway gravel quotes
Feed measured length, width, specified compacted depth, and supplier density from a civil schedule to produce reproducible yardage and tonnage for bids.
FAQ
How is driveway gravel volume and tonnage calculated?
Cubic feet = length (ft) × width (ft) × depth (inches) / 12. Cubic yards = cubic feet / 27 (or length × width × depth / 324). Tons = cubic yards × bulk density in tons per cubic yard (default 1.4).
What happens if length, width, or depth is zero, negative, or missing?
Any dimension that is not a positive number cannot define a physical driveway layer, so the tool never invents yardage or tons.
What density should I use for driveway gravel?
Use your supplier’s bulk density in short tons per cubic yard when available. The default 1.4 is a common planning figure for dry crushed stone; wet or denser crusher run may need a higher value.
Does this add compaction, waste, crown, or slope correction?
No. It returns pure geometric volume and density-based tons only.
Is the gravel driveway calculator free?
The browser tool is free and runs locally.
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/build/gravel-driveway \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"length":50,"width":12,"depth":4}'const res = await fetch("https://api.kit.forhosting.com/build/gravel-driveway", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"length": 50,
"width": 12,
"depth": 4
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/build/gravel-driveway",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"length": 50,
"width": 12,
"depth": 4
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/build/gravel-driveway", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"length":50,"width":12,"depth":4}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"length":50,"width":12,"depth":4}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/build/gravel-driveway", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"length": 50,
"width": 12,
"depth": 4
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "build.gravel_driveway",
"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
Any dimension that is not a positive number fails with invalid_input so a typo never invents a free load. The same arithmetic powers the free browser tool and the API at $0.002 per successful request.
What the calculator returns and how driveway gravel volume is defined
The calculator multiplies length by width by depth over twelve for cubic feet, divides by twenty-seven for cubic yards, multiplies by density for tons, and returns JSON that echoes length_ft, width_ft, depth_inches, area_sqft, density_tons_per_yd3, volume_cu_ft, volume_cu_yd, tons, unit tags, the method tag, and a short formula string. There is no brand database, no crown or slope correction, no compaction or waste factor, and no shopping cart: the page answers only the volume and tonnage questions with stable numbers suitable for worksheets, contractor quotes, and API consumers that must match goldens run after run.
How inputs are read, validated, and kept reproducible
Always convert a tapered or L-shaped apron into simple rectangles first—sum the pieces—because the solver never triangulates polygons or reads CAD files. Preferred fields are length for the run in feet, width for the travel-lane width in feet, and depth for compacted gravel thickness in inches, plus optional density in short tons per cubic yard when you are not using the default one point four. Aliases such as driveway_length, length_ft, and l for length; driveway_width, width_ft, and w for width; depth_inches, inches, thickness, and gravel_depth for depth; and tons_per_yd, tons_per_cu_yd, bulk_density, or density_tons for density are accepted so spreadsheets, query strings, and typed forms can reuse the same contract without renaming columns. Every numeric field must be finite; any dimension that is zero, negative, missing, or non-numeric is rejected with invalid_input so a zero-depth form field cannot silently claim free stone and a blank length cannot invent a driveway. An optional precision field, with aliases decimals and dp, chooses how many decimal places to expose for lengths, volumes, and tons, defaulting to four and capped at fifteen so JSON goldens stay stable across engines. Pair the free browser run on this page with the priced API when you need the identical mathematical result inside an automated pipeline without re-implementing the driveway gravel formula yourself.
Where driveway gravel estimates fit for DIY, quotes, and software
On this page the work runs entirely in your browser; through the API each successful lookup costs $0.002, failed validation is not charged, and nothing is stored after the response returns. That split — free interactive exploration and a priced, identical API — matches the rest of the KIT tier-A catalog and lets you move from a Saturday sketch to an automated quoting pipeline without changing the mathematical result.
Integration use cases
Golden fixtures for driveway apps
Developers generate known-good cubic-yard and ton cases plus deliberate non-positive dimension rejections for unit tests and CI.