Tile spacer calculator
This tile spacer calculator estimates how many plastic or rubber spacers you should buy before laying floor or wall tiles.
Run — free
You enter the number of tiles, how many spacer pieces sit at each tile corner, how many corners each tile has, how many corners share one physical spacer, and an optional waste percentage for spares. Cross-shaped spacers usually serve four meeting corners in a grid interior, so the share factor defaults to four and the estimate is often close to one spacer per tile before waste. Wedge or horseshoe spacers that do not share corners use a share factor of one and need roughly four pieces per rectangular tile. The engine multiplies tiles by corners and spacers per corner, divides by the share factor, then ceilings the result after applying waste. It is pure arithmetic with no network calls, no sampling, and no date-dependent shortcuts. Use it free in the browser for DIY shopping lists and contractor take-offs, or call the API at $0.002 per successful request when estimating software, spreadsheets, or CI fixtures need the same deterministic count every time.
How to use it
Enter your values in the form above. The tool checks them before calculating and shows the result on the same page.
Check your inputs
Use the labels and units shown next to each field. If something is missing or outside the allowed range, the page points to the field to fix.
Use it again or automate it
Use the browser tool for individual checks and the API when you need the same capability in an automated workflow.
What you can do with it
Get an answer now
Enter one set of values and see the result without building a spreadsheet or script.
Compare scenarios
Change one value at a time and rerun the calculation to understand what affects the result.
Automate repeated work
Use the API when the same calculation needs to run inside your product or workflow.
FAQ
How do I use this capability?
Complete the fields above and run it on this page. The form highlights anything that needs attention.
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/home/tile-spacers \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"tiles":100}'const res = await fetch("https://api.kit.forhosting.com/home/tile-spacers", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"tiles": 100
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/home/tile-spacers",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"tiles": 100
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/home/tile-spacers", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"tiles":100}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"tiles":100}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/home/tile-spacers", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"tiles": 100
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "home.tile_spacers",
"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. |