How to Split a Restaurant Bill Between 6 People — Every Method, Explained

Method 1: Even split — when it works and when it doesn't

The even split is the default for most friend groups, and for good reason: it's fast, requires no argument, and avoids the awkward itemization process. Everyone pays the same amount regardless of what they ordered.

It works well when the group ordered similarly — roughly comparable entrees, similar drinks, no wildly different consumption levels. Six friends at a casual dinner where everyone got a burger and two drinks? Even split is fine and fair enough.

It breaks down when there's a significant spread in order sizes. If one person got a $12 salad and no drinks, and another got a $38 steak and three cocktails, an even split makes the salad person pay for roughly $15-$20 of the steak person's meal. At a table of close friends, some people absorb this without complaint. At a table of newer acquaintances or coworkers, it creates quiet resentment.

Method 2: Itemized split — the fair approach for mixed orders

Itemized splitting means everyone pays for what they ordered plus their proportional share of the tip. This is objectively fairer when there are meaningful differences in order value — but it requires a bit more work.

Here's how it works for a group of 6 on a $180 bill:

Person A pays $26.40 and Person E pays $45.60 — a $19.20 difference. In an even split, both would have paid $36. The itemized method fairly reflects what each person actually consumed. The uneven split calculator automates this calculation for any group size.

Method 3: Hybrid split — food even, alcohol itemized

This is the method many groups land on naturally, though they rarely name it explicitly. The idea: split the food portion of the bill evenly (it's usually close enough for a fair estimate), but keep alcohol separate and charge it only to those who ordered it.

Practical scenario: $120 in food shared by 6 people equally = $20 each. $60 in alcohol consumed by 3 of the 6 people = $20 each for those three. Add 20% tip proportionally. Non-drinkers pay $20 food + $4 tip = $24. Drinkers pay $20 food + $20 drinks + $8 tip = $48. This feels intuitively fair to most people and doesn't require itemizing every dish.

The practical question: who pays and how?

For a group of 6, the most seamless approach is usually one person pays the whole bill on their card, and everyone else Venmo/Zelle/Cash App their share. This avoids the server having to split a check multiple ways (which can create errors or slow things down significantly), and it's fast.

Decide the split method before the meal ends. Get agreement on the total each person owes while everyone is still at the table with the receipt in hand. Once people walk out the door, getting payment becomes significantly harder — especially for the odd couple of dollars someone thinks they shouldn't owe.

If your group regularly dines together, using a shared expense tracker is worth considering. The group expense splitter guide covers tools and methods for ongoing groups. For one-off dinners, the restaurant bill splitting guide has the full methodology for different social dynamics.

What to do when someone forgets their wallet or can't cover their share

This happens. Someone left their card at home, someone's genuinely short this month. The socially graceful move: the group covers the difference without making a production of it. One or two people chip in a bit more, the person who couldn't pay pays them back later. Keep the IOU specific and time-bound — "I'll get you next week" is more binding than a vague "I owe you."

For recurring situations, the who owes who tracker lets you log these informal debts so they don't get forgotten. Most friendship-damaging money disputes start as small, unresolved IOUs that accumulate over time.

For research on how dining-related social dynamics affect tipping behavior, Cornell's Center for Hospitality Research has published useful work — including findings on how group size affects tipping percentages. The Cornell Hospitality Research archive is worth a look if you're curious.