Paver sand calculator

Zero or negative area or depth are rejected with a clear invalid_input error instead of inventing a delivery ticket from impossible sizes. Successful API calls use the published base of $0.002 per item.

How cubic yards of paver sand are computed

It is not the compacted gravel or crushed-stone base under that sand, not polymeric joint sand sold in bags to fill the gaps between pavers, and not a density-based tonnage unless you apply a supplier conversion after the call. On success the response echoes the rounded inputs, publishes depth in feet, cubic_feet and cubic_yards, unit labels, and formula as the string yd3 equals area times depth over three hundred twenty-four.

How to call the API and what comes back

All numeric fields must be finite; string forms of numbers are accepted when they match a strict finite numeric pattern. 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. A two-hundred-square-foot patio at one inch of bedding sand is two hundred over three hundred twenty-four cubic yards, a little more than six-tenths of a yard; a four-hundred-square-foot walkway at one and a half inches is six hundred over three hundred twenty-four cubic yards. Measure length times width of the rectangle you will pave, or sum rectangles for an L-shaped patio, then pass the total square footage and the specified sand depth. Send a JSON body with two required fields: area in square feet (aliases plan_area, paved_area, patio_area, surface, sq_ft, square_feet, A) and depth in inches of sand (aliases sand_depth, bedding_depth, thickness, depth_inches, D). On success the response sets area, depth, depth_ft as depth divided by twelve, cubic_feet, cubic_yards, unit labels for area depth and volume, and formula as described above. Failed validation—missing fields, non-finite numbers, zero or negative area or depth, or values outside absolute limits—returns invalid_input and is never charged. Pricing is a flat $0.002 per successful request with unit item.

Practical tips, typical depths, and related searches

Measure plan area from drawings or by length times width of the rectangle you will pave, and depth as the finished sand thickness the paver manufacturer specifies, using square feet and inches as this calculator expects. Most interlocking-paver sheets call for about one inch of coarse concrete sand as the setting bed, screeded level over a compacted aggregate base; do not confuse that thin course with the four-to-eight-inch gravel base, and do not treat polymeric joint sand as a layer volume. Keep inputs inside the published absolute range so products cannot overflow into non-finite results the solver must reject. Prefer this capability when you already know the square footage and the sand depth in inches and only need yards to order. If the yard quotes sand by the ton, multiply cubic_yards by the bulk density they publish after the call; this tool intentionally returns yards so quotes stay transparent in the unit suppliers use for bulk sand tickets. When teaching or writing tests, pair a two-hundred-square-foot patio at one inch with a second case at one and a half inches, and include a deliberate zero depth to prove the invalid_input path. This landing targets people searching for a paver sand calculator, cubic yards of bedding sand for a patio, paver base sand from area and depth, or how much sand under pavers; it is not a general sand-weight tool with free-form density, not a count of individual paver stones, not a gravel-base estimator, and not a joint-sand bag count. Failed tasks that return invalid_input do not consume prepaid balance. Round-trip checks are easy: recompute area times depth over three hundred twenty-four by hand and confirm cubic_yards matches within the same twelve-decimal rounding used for all numeric fields.