Play sand calculator

Measure the sandbox interior and choose a safe fill depth

Send length, width, and depth as strictly positive finite numbers; aliases such as L, len, and sandbox_length for length, W and sandbox_width for width, and d, depth_inches, fill_depth, and thickness for depth are accepted so spreadsheets and typed forms can reuse familiar column names. Zero, negative, or non-numeric values raise invalid_input and are not charged, because a non-positive dimension cannot define a physical fill. Extremely small or huge values outside the published stability range are also rejected so floating-point results stay meaningful on a Worker isolate. Irregular or L-shaped boxes can still use this tool: compute an equivalent rectangle outside the API or sum multiple rectangular zones and pass each zone separately if your app tracks zones independently.

Volume, density, bags, tons, and how to read the response

Weight depends on bulk density: dry play sand is often near one hundred pounds per cubic foot in home-estimator rules of thumb, while damp or compacted product can run heavier, so prefer the supplier data sheet when you have one. Optional density defaults to one hundred pounds per cubic foot with aliases rho, bulk_density, sand_density, and lb_per_cu_ft. Optional bag_weight defaults to fifty pounds, the common retail bag, with aliases bag_lb, bag, bag_size_lb, and pounds_per_bag. The response echoes length, width, depth, density, and bag_weight; returns volume_cu_ft, volume_cu_yd, weight_lb, weight_tons, and bags; labels unit tags; and sets method to sandbox_play_sand_bags_tons with a short formula string so downstream code can branch without sniffing product types. Identical inputs always produce identical JSON because the path is pure arithmetic with no network, random seed, or wall clock.

API usage, pricing, playground workflows, and practical limits

Call the free in-browser play sand calculator for weekend builds, HOA playgrounds, school PTO sandboxes, and classroom volume demos without opening a spreadsheet. Remember that supplier bulk density and bag net weight can differ from textbook defaults—prefer the product sheet for the play sand you will buy, and re-measure interior length and width after installing seats or rounded corners. Send a JSON body with required length, width, and depth, plus optional density and bag_weight when defaults do not match your product. Use the prepaid API when a renovation app, playground planner, daycare facilities tool, or property-management pipeline needs a stable contract under KIT balance at $0.002 per successful item; validation failures never consume balance after the engine rejects the request. Pair this endpoint with unit converters when drawings use metres while bag labels use pounds, or with lumber and liner helpers when the sand layer is only one line in a larger bill of materials. Authors shipping SDKs can map bags and weight_tons straight into order lines while showing formula and method as explanatory detail for the buyer or the site supervisor reviewing the ticket. Keep metric bag sizes and non-US ton definitions out of scope unless you convert outside the API; this contract is feet, inches, pounds, and US short tons for the common North American DIY and facilities search intent.