Tip and split calculator
A bill of 86.4 with an 18% tip split four ways comes to a 15.55 tip, a 101.95 total and 25.49 per person. No napkin maths at the table, just an even split rounded to the cent. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Bill amount before tip
- 86.4
- Tip
- 18
- People
- 4
- Total
- 101.95
- Tip
- 15.55
- Per person
- 25.49
- Currency decimals
- 2
Splitting a restaurant check should not require a napkin full of mental arithmetic or a spreadsheet on your phone. This tip and split calculator takes three everyday numbers—the bill before gratuity, the tip percentage you want to leave, and how many people are sharing the cost—and returns the tip amount, the grand total including tip, and each person's equal share, all rounded cleanly to two decimal places. Zero people is rejected with a clear invalid input error, because dividing a bill among nobody is not a valid split.
How tip, total, and per-person share are computed
The core formulas are the ones people already use by hand. Tip is bill times tip percent divided by one hundred. Total is bill plus that tip.
Per person is total divided by the people count. Intermediate products use ordinary floating-point arithmetic, then every money field is rounded half-up to two decimal places so results look like currency on a receipt rather than long binary fractions. Example: a bill of eighty-six point four, eighteen percent tip, and four people yields a tip of fifteen point five five, a total of one hundred one point nine five, and a per-person share of twenty-five point four nine after rounding.
Equal split is intentional product scope: weighted shares by who ordered which entrée would be a different search intent and a different contract.
What you can do with it
Restaurant and bar checks
Diners enter the printed subtotal, choose a tip percent, and instantly see how much each person owes when the table splits evenly.
Group trips and shared housing
Travelers and roommates divide a shared bill with a service tip or cleaning fee percentage into clear per-person amounts for reimbursement chats.
FAQ
What happens if people is zero?
At least one person is required; dividing by zero is not a valid split and is not charged.
Is the tip and split calculator free?
The browser tool runs free on your device.
Can people pay unequal shares?
No. This product returns an equal per-person share of the tipped total. Weighted splits by order are out of scope for this contract.
How much does each person pay, tip included?
Each share is the total with tip divided by the number of people. A bill of 86.4 with an 18% tip comes to 101.95, so four people pay 25.49 each, rounded to two decimals.
Is the tip worked out before or after splitting the bill?
Before. The tip percentage is applied to the whole bill, it is added to give the total, and only then is that total divided equally among everyone at the table.
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/life/tip-split \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"bill":86.4,"tip_percent":18,"people":4}'const res = await fetch("https://api.kit.forhosting.com/life/tip-split", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"bill": 86.4,
"tip_percent": 18,
"people": 4
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/life/tip-split",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"bill": 86.4,
"tip_percent": 18,
"people": 4
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/life/tip-split", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"bill":86.4,"tip_percent":18,"people":4}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"bill":86.4,"tip_percent":18,"people":4}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/life/tip-split", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"bill": 86.4,
"tip_percent": 18,
"people": 4
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "life.tip_split",
"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. |
Technical notes
Inputs: bill, tip percent, and people count
Negative bills and negative tip percentages fail validation because they do not describe a normal check. Tip percent is capped at a generous upper bound so accidental thousand-fold typos fail loudly instead of inventing absurd totals. People must be a whole number: fractional heads at the table are not modeled. All validation happens before any money math, so bad requests never produce half-filled tip rows. Send a JSON body with three required fields. The bill is the pre-tip amount as a non-negative finite number or numeric string; aliases amount, bill_amount, and subtotal are accepted when your client already names the field differently. Tip percent is the gratuity rate expressed as a percentage of that bill—for example eighteen means eighteen percent—not a decimal fraction; aliases tip, percent, gratuity, and tip_pct map to the same value so form builders can keep familiar labels. People is the integer count of diners or roommates who will pay equal shares; aliases persons, n, party, party_size, and split are supported. When people is zero, the engine raises invalid_input with a message that at least one person is required—the classic divide-by-zero trap for split calculators. Missing any of the three fields also fails with invalid_input naming the missing key.
How tip, total, and per-person share are computed
The response echoes the normalized bill, tip percent, and people count, then returns tip, total, and per_person, plus currency_decimals equal to two and method equal to tip_split for stable client branching. Use tip alone when you only need the gratuity line; use total when a payment app needs the charged amount; use per_person when a group chat needs each person's contribution. Identical inputs always produce identical JSON because the path is pure arithmetic with no network, no random seed, and no wall clock.
API usage, pricing, workflows, and practical limits
Call the free in-browser tip and split calculator for dinners, rideshares, vacation rentals, and office lunch orders without installing another app. Keep bill sizes within ordinary commercial ranges; extremely large amounts are rejected so isolate math stays bounded. The product promise is equal split with an explicit tip percentage, not itemized tax, service fees, or automatic local tipping customs—those belong in specialized tools with different SEO intent. Use the prepaid API when a hospitality bot, expense tracker, travel planner, or point-of-sale helper needs a stable KIT contract at $0.002 per successful item; validation failures never consume balance after the engine rejects the request. Pair this endpoint with currency converters only if you already know amounts in a single currency—this capability does not convert FX or apply tax lines. Authors shipping SDKs can map tip, total, and per_person directly into receipt UIs and settlement messages.
Integration use cases
Expense bots and hospitality apps
Bots and mini-apps call a stable prepaid endpoint instead of reimplementing tip math and zero-people guards in every language.
Technical questions
How do I calculate tip and split a bill?
Send JSON with bill (pre-tip amount), tip_percent (for example 18), and people (how many share). The response includes tip, total, and per_person rounded to two decimals.
Is the tip percentage of the bill before or after tax?
You choose what to put in bill. The calculator multiplies that amount by tip_percent / 100; it does not add tax lines or detect local customs.