Tile planner

Enter rectangular surface dimensions or a measured net area for a floor or wall, already excluding openings. Tile sides are actual dimensions in cm. The area model ignores joint spacing for tile purchase: tile area = width × length / 10000 m²; required tiles = ceil(surface / tile area × (1 + reserve/100)). It estimates equivalent tile area, not a cut plan or guaranteed installed count. Pattern, borders, cuts and reusable offcuts can change the need. Choose your reserve; 10 % is an example.

Optional whole tiles per box: boxes = ceil(required tiles / box count); excess tiles are box contents beyond the reserve-inclusive requirement. Empty means no box calculation. Tiny floating-point noise near a positive integer is corrected before rounding up; fractional need still rounds up. No arbitrary box size is assumed.

Joint volume is optional and independent of tile reserve and box excess. For an ideal repeating rectangular grid, sides a,b and joint width w in mm give joint fraction f = 1 − ab/((a+w)(b+w)). Crossings are counted once. Volume in L = installed m² × filled depth in mm × f. Filled depth is the actual empty joint to fill, not automatically tile thickness. This is a geometric estimate without room edge joints, cut layout, bevels, voids or application losses; not a manufacturer consumption formula or dry bag mass.

For buying grout, optionally enter the specific product consumption in kg/m² for these tiles/joints and optional bag mass in kg. Mass = installed area × rate; bags round up. No volume-to-mass conversion, density assumption or automatic tile-reserve surcharge. Product data must match geometry and include any allowance you choose. LATICRETE grout FAQ explains why coverage varies with joints, tile and installation.

Calculate or Enter; edits and mode changes clear old results. Reset restores examples and closes optional sections. Zero tile reserve, joint width, filled depth or product rate is allowed. Tile dimensions and surface are positive, box count is a positive integer, bag mass positive. Field bounds are software limits; unsafe counts and nonfinite results are rejected. No storage or uploads.