Calculate tips quickly and split bills easily among any number of people.
$
%
Tipping Guide
RESTAURANT SERVER
15-20%
Standard for sit-down dining
BARTENDER
$1-2 per drink
Or 15-20% of tab
FOOD DELIVERY
15-20%
$3-5 minimum
HAIR STYLIST
15-20%
Of total service cost
Tip Breakdown
Results
Tip Amount
$0.00
Total tip
Total Bill
$0.00
Bill + tip
Tip Per Person
$0.00
Each person's tip share
Total Per Person
$0.00
Each person pays
Bill Split Summary
Original Bill$0.00
Tip (20%)$0.00
Total to Pay$0.00
Add this calculator to your website or share with others
Key Takeaways
Standard restaurant tip in the US is 15-20% for good service, 20%+ for excellent service
Always tip on the pre-tax bill amount, not the total including tax
Service workers often earn below minimum wage and rely on tips for their income
When splitting bills, ensure the total tip is still appropriate, not just individual portions
International tipping customs vary greatly - research local norms when traveling
How to Calculate a Tip
Calculating a tip is straightforward: multiply your bill by the tip percentage. For a 20% tip on a $50 bill: $50 × 0.20 = $10 tip, making your total $60.
Quick mental math tricks:
10% tip: Move the decimal point one place left ($50 → $5.00)
15% tip: Calculate 10%, then add half of that ($5 + $2.50 = $7.50)
20% tip: Calculate 10%, then double it ($5 × 2 = $10)
25% tip: Calculate 20%, then add a quarter of that
Pro Tip: Pre-Tax Tipping
Calculate your tip on the pre-tax subtotal, not the total including tax. You shouldn't tip on sales tax! Look for the subtotal line on your receipt.
Tipping Guidelines by Service
Service
Standard Tip
Great Service
Notes
Restaurant Server
15-18%
20-25%
On pre-tax subtotal
Bartender
$1-2/drink
$2-3/drink
Or 15-20% of tab
Takeout/Counter
0-10%
10-15%
Optional but appreciated
Food Delivery
15-20%
20%+
$3-5 minimum
Rideshare/Taxi
15-20%
20%+
More for luggage help
Hair Stylist
15-20%
20-25%
Of total service
Hotel Housekeeping
$2-5/night
$5-10/night
Leave daily, not at checkout
Valet Parking
$2-5
$5-10
At pickup
When to Tip More
Large parties (6+ people) - some places add automatic gratuity
Complex orders or special requests
Bad weather (delivery drivers)
Holidays or very late/early hours
Exceptional, personalized service
International Tipping Customs
Tipping culture varies significantly around the world:
Japan: Tipping is generally not expected and can even be considered rude
Europe: Service charge often included; small additional tip (5-10%) appreciated
Canada: Similar to US, 15-20% standard
Australia: Tipping not expected but appreciated for good service (10%)
Middle East: 10-15% typical when service charge not included
Frequently Asked Questions
Technically, you should tip on the pre-tax subtotal since you're tipping for service, not paying extra tax. However, many people tip on the total for convenience, and the difference is usually small. Either approach is acceptable.
Leaving no tip is generally discouraged since servers often earn below minimum wage and depend on tips. For poor service, consider leaving 10-15% and speaking with management. Zero tips should be reserved for truly egregious situations. Sometimes poor service is due to kitchen issues, not your server.
Tipping on takeout is optional but increasingly appreciated, especially post-2020. A tip of 10-15% acknowledges the staff who prepared and packaged your order. Many people round up or leave $1-5 depending on order size.
Tipping at coffee shops and fast food is optional. If there's a tip jar or digital prompt, many people leave $1-2 or round up for complicated orders. For counter service where you pick up your own food, tipping is appreciated but not expected.
There are two common approaches: split the entire bill (including tip) evenly, or have each person calculate tip on their individual portion. The first method is simpler; the second is fairer if orders varied significantly. Always double-check the total tip is appropriate regardless of method.
Automatic gratuity (usually 18-20% for large parties) is your tip - you don't need to add more. However, you can add extra for exceptional service. Always check your bill for included gratuity before calculating an additional tip.
Quick Tip Calculations Made Easy
Never second-guess your tip again. Calculate instantly for any bill amount.
20%Standard good service
$17Tip on $85 bill
$102Total with tip
Helpful products for this plan
General picks that support planning, focus, and follow-through.
Questions, pitfalls, and vocabulary for Tip Calculator
Use this section as a practical companion to Tip Calculator: quick answers, then habits that keep results trustworthy.
Frequently asked questions
How precise should I treat the output?
Treat precision as a property of your inputs. If an input is a rough estimate, carry that uncertainty forward. Prefer ranges or rounded reporting for soft inputs, and reserve many decimal places only when measurements justify them.
What should I do if small input changes swing the answer a lot?
That usually means you are near a sensitive region of the model or an input is poorly bounded. Identify the highest-impact field, improve it with better data, or run explicit best/worst cases before deciding.
When should I re-run the calculation?
Re-run whenever a material assumption changes—policy, price, schedule, or scope. Do not mix outputs from different assumption sets in one conclusion; keep a dated note of inputs for each run.
Can I use this for compliance, medical, legal, or safety decisions?
Use it as a structured estimate unless a licensed professional confirms applicability. Calculators summarize math from what you enter; they do not replace standards, codes, or individualized advice.
Why might my result differ from another Tip tool or spreadsheet?
Different tools bake in different defaults (rounding, time basis, tax treatment, or unit systems). Align definitions first, then compare numbers. If only the final number differs, trace which input or assumption diverged.
Common pitfalls for Tip (other)
Silent double-counting (counting the same cost or benefit twice).
Anchoring to a “nice” round number instead of measurement-backed values.
Comparing options on different time horizons without normalizing.
Ignoring correlation: two “conservative” inputs may not be jointly realistic.
Skipping a sanity check against a simpler estimate or known benchmark.
Terms to keep straight
Assumption: A value you accept without measuring, often reasonable but always contestable.
Sensitivity: How much the output moves when a specific input nudges.
Scenario: A coherent bundle of inputs meant to represent one plausible future.
Reviewing results, validation, and careful reuse for Tip Calculator
The sections below are about diligence: how a careful reader stress-tests output from Tip Calculator, how to sketch a worked check without pretending your situation is universal, and how to cite or share numbers responsibly.
Reading the output like a reviewer
A strong read treats the calculator as a contract: inputs on the left, transformations in the middle, outputs on the right. Any step you cannot label is a place where reviewers—and future you—will get stuck. Name units, time basis, and exclusions before debating the final figure.
A practical worked-check pattern for Tip
For a worked check, pick round numbers that are easy to sanity-test: if doubling an obvious input does not move the result in the direction you expect, revisit the field definitions. Then try a “bookend” pair—one conservative, one aggressive—so you see slope, not just level. Finally, compare to an independent estimate (rule of thumb, lookup table, or measurement) to catch unit drift.
Further validation paths
For time-varying inputs, confirm the as-of date and whether the tool expects annualized, monthly, or per-event values.
If the domain uses conventions (e.g., 30/360 vs actual days), verify the convention matches your obligation or contract.
When publishing, link or attach inputs so readers can reproduce—not to prove infallibility, but to make critique possible.
Before you cite or share this number
Before you cite a number in email, a report, or social text, add context a stranger would need: units, date, rounding rule, and whether the figure is an estimate. If you omit that, expect misreadings that are not the calculator’s fault. When comparing vendors or policies, disclose what you held constant so the comparison stays fair.
When to refresh the analysis
Revisit Tip estimates on a schedule that matches volatility: weekly for fast markets, annually for slow-moving baselines. Tip Calculator stays useful when the surrounding note stays honest about freshness.
Used together with the rest of the page, this frame keeps Tip Calculator in its lane: transparent math, explicit scope, and proportionate confidence for other decisions.
Blind spots, red-team questions, and explaining Tip Calculator
After mechanics and validation, the remaining failure mode is social: the right math attached to the wrong story. These notes help you pressure-test Tip Calculator outputs before they become someone else’s headline.
Blind spots to name explicitly
Another blind spot is category error: using Tip Calculator to answer a question it does not define—like optimizing a proxy metric while the real objective lives elsewhere. Name the objective first; then check whether the calculator’s output is an adequate proxy for that objective in your context.
Red-team questions worth asking
What would change my mind with one new datapoint?
Name the single observation that could invalidate the recommendation, then estimate the cost and time to obtain it before committing to execution.
Who loses if this number is wrong—and how wrong?
Map impact asymmetry explicitly. If one stakeholder absorbs most downside, treat averages as insufficient and include worst-case impact columns.
Would an honest competitor run the same inputs?
If a neutral reviewer would pick different defaults, pause and document why your chosen defaults are context-required rather than convenience-selected.
Stakeholders and the right level of detail
Stakeholders infer intent from what you emphasize. Lead with uncertainty when inputs are soft; lead with the comparison when alternatives are the point. For Tip in other, name the decision the number serves so nobody mistakes a classroom estimate for a contractual quote.
Teaching and learning with this tool
If you are teaching, pair Tip Calculator with a “break the model” exercise: change one input until the story flips, then discuss which real-world lever that maps to. That builds intuition faster than chasing decimal agreement.
Treat Tip Calculator as a collaborator: fast at computation, silent on values. The questions above restore the human layer—where judgment belongs.
Decision memo, risk register, and operating triggers for Tip Calculator
This layer turns Tip Calculator output into an operating document: what decision it informs, what risks remain, which thresholds trigger a different action, and how you review outcomes afterward.
Decision memo structure
Write the memo in plain language first, then attach numbers. If the recommendation cannot be explained without jargon, the audience may execute the wrong plan even when the math is correct.
Risk register prompts
What would change my mind with one new datapoint?
Name the single observation that could invalidate the recommendation, then estimate the cost and time to obtain it before committing to execution.
Who loses if this number is wrong—and how wrong?
Map impact asymmetry explicitly. If one stakeholder absorbs most downside, treat averages as insufficient and include worst-case impact columns.
Would an honest competitor run the same inputs?
If a neutral reviewer would pick different defaults, pause and document why your chosen defaults are context-required rather than convenience-selected.
Operating trigger thresholds
Operating thresholds keep teams from arguing ad hoc. For Tip Calculator, specify what metric moves, how often you check it, and which action follows each band of outcomes.
Post-mortem loop
After decisions execute, run a short post-mortem: what happened, what differed from the estimate, and which assumption caused most of the gap. Feed that back into defaults so the next run improves.
The goal is not a perfect forecast; it is a transparent system for making better updates as reality arrives.