Limestone calculator
A 20 by 10 foot pad with a 6 inch base of crushed limestone at 95 pounds per cubic foot is 100 cubic feet and 4.75 short tons. Enter your pad and the density your quarry quotes before you order. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Length
- 20
- Width
- 10
- Depth
- 0.5
- Density
- 95
- Area ft2
- 200
- Volume ft3
- 100
- Volume yd3
- 3.7037037037
- Weight lb
- 9,500
This limestone calculator turns a rectangular pad into the cubic yards of crushed stone you must order and the US short tons that stone will weigh. Enter length, width, and depth in feet together with the bulk density of the limestone in pounds per cubic foot. The engine forms cubic feet as length times width times depth, divides by twenty-seven for cubic yards, multiplies cubic feet by density for pounds, then divides by two thousand for short tons. The work is pure deterministic arithmetic with no network calls, no sampling, and no date-dependent shortcuts.
How limestone volume and weight are computed
A rectangular limestone pad, driveway base, or walkway sub-base is modelled as a right prism whose plan is length times width and whose thickness is the placed depth, all measured in feet. Cubic feet of bulk stone equal that product: volume in cubic feet is length multiplied by width multiplied by depth. Weight uses the bulk density of the limestone as sold or as placed, in pounds per cubic foot: pounds equal cubic feet times density.
US short tons follow by dividing pounds by two thousand, the statutory short-ton factor used on North American tickets. Bulk density already folds the voids between particles for the product you buy; it is not the solid mineral density of a single limestone fragment unless your supplier quotes that figure for the same packing. Typical crushed limestone sits roughly between seventy-five and one hundred ten pounds per cubic foot depending on gradation, moisture, and how tightly the stone is placed.
The product is the net geometric volume and the corresponding bulk mass; it does not add waste for compaction, spillage, or an uneven subgrade, and it does not convert metres, millimetres, or inches for you. All four inputs must be strictly positive: a zero or negative length or width cannot cover ground, a non-positive depth is not a layer, and a non-positive density is not a physical material.
Mixing square metres of plan with inches of depth silently produces a meaningless cubic product; convert everything to feet and pounds per cubic foot first, then call.
Units to use and what happens with invalid values
A six-inch base is sent as 0.5 feet, a four-inch walkway as about 0.333 feet; do not send inches unless you have already divided by twelve. String forms of numbers are accepted when they match a strict finite numeric pattern. A zero or negative dimension fails with a message that the named length, width, depth, or density must be a positive number, matching the rule that a pad with no extent cannot consume stone.
On success the body echoes the parsed dimensions and density, plan area in square feet, volume in cubic feet and cubic yards, weight in pounds and US short tons, the conversion constants twenty-seven and two thousand, a short formula string, a method tag, a one-line English message, and steps as an ordered substitution log. Failed validation is not billed. Prefer sending numbers rather than pre-formatted strings when you control the client; when you must send strings, avoid unit suffixes or thousand separators that would fail the finite-number pattern.
Where a limestone calculator earns its keep
Homeowners meet this calculation when a crushed-limestone driveway, RV pad, or garden path must be ordered from a quarry by the ton, not by the decorative bag, and a wrong depth either starves the base of stone or leaves a pile in the rain. Small contractors use the same numbers to turn a parking pad or a walkway sub-base into a limestone ticket before the truck is called, then apply their own compaction or waste factor on top of the pure take-off.
Estimators embed the contract in take-off tools so a table of length, width, depth, and supplier density becomes cubic yards and short tons without a spreadsheet full of hidden cells and mixed units. Product and education tools show learners why a twenty-by-ten-foot pad six inches deep at ninety-five pounds per cubic foot is one hundred cubic feet, about 3.70 cubic yards, and 4.75 short tons, and why a denser crusher-run product jumps the weight for the same prism.
This is not a gravel, sand, or topsoil calculator, not an agricultural-lime bag count, and not a concrete mix take-off: those are different search intents with different inputs. Pair it with square-feet-to-cubic-yards helpers when you already have area instead of length and width, and keep engineering judgement for drainage, geotextile, and compaction that your pad requires beyond the pure limestone identity.
What you can do with it
Order crushed limestone for a driveway base
Homeowners enter driveway length, width, base depth in feet, and supplier bulk density to get cubic yards and US short tons before calling a quarry.
FAQ
How is limestone volume and weight calculated?
Volume in cubic yards is length × width × depth in feet divided by 27. Weight in US short tons is cubic feet times density in lb/ft³ divided by 2000. All four inputs must be positive.
What happens if length, width, depth, or density is zero or negative?
Non-positive dimensions cannot define a physical limestone pad, so the tool never invents a cubic-yard ticket or a tonnage.
What units should I send for depth and density?
Send length, width, and depth in feet (a 6-inch layer is 0.5 ft) and density in pounds per cubic foot. Convert inches, metres, or tons-per-yard figures before you call.
Does this add compaction or waste?
No. It returns pure geometric cubic yards and short tons.
What does the limestone calculator cost?
It is free in your browser on this page.
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/limestone \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"length":20,"width":10,"depth":0.5,"density":95}'const res = await fetch("https://api.kit.forhosting.com/build/limestone", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"length": 20,
"width": 10,
"depth": 0.5,
"density": 95
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/build/limestone",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"length": 20,
"width": 10,
"depth": 0.5,
"density": 95
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/build/limestone", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"length":20,"width":10,"depth":0.5,"density":95}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"length":20,"width":10,"depth":0.5,"density":95}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/build/limestone", 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": 20,
"width": 10,
"depth": 0.5,
"density": 95
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "build.limestone",
"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 | 1000000000 |
min_pos | 1e-15 |
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
Every dimension and the density must be a finite positive number: zero or negative length, width, depth, or density is rejected as invalid_input instead of a hollow ticket. Use it free in the browser for a driveway base or patio pad, or call the API at $0.002 per successful request when estimating software needs reproducible quarry tickets.
How limestone volume and weight are computed
North American landscape yards and quarries bill crushed limestone by the cubic yard, so the engine divides cubic feet by the exact identity that twenty-seven cubic feet equal one cubic yard and publishes volume_yd3.
Input contract, units, API, and error behaviour
POST a JSON body with four required fields. length, width, and depth are the rectangular pad dimensions in feet and must each be a finite strictly positive number; aliases include l, length_ft, w, width_ft, and d, thickness, height, depth_ft for depth. density is the bulk density in pounds per cubic foot and must be a finite strictly positive number, with aliases rho, bulk_density, limestone_density, and density_lb_ft3. Missing fields, empty strings, non-finite values, and magnitudes above the supported ceiling fail with invalid_input naming the field. Pricing is a flat $0.002 per successful request with unit item.
Where a limestone calculator earns its keep
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 — lets you move from a phone check at the quarry gate to an automated pipeline without changing the mathematical result.
Integration use cases
Quote a parking pad or walkway sub-base
Contractors feed pad dimensions and limestone density into the API and attach volume_yd3, weight_tons, and steps to a transparent material quote.
Golden fixtures for construction apps
Developers generate known-good cubic-yard and tonnage cases plus deliberate non-positive input rejections for unit tests and CI.