How to Cut Down Your Wedding Guest List (Without a Family Argument)

To cut down a wedding guest list, sort every name into three tiers — must-have, should-have, would-be-nice — using one honest test: would we still make time for this person this year if the wedding weren't happening? Cut from the bottom tier first, split the remaining seats evenly between both families instead of arguing name by name, and hold a short wave-two list back rather than deleting anyone outright.

Last updated: August 2026

A guest list rarely starts too big. It grows — a cousin here, a parent's colleague there, someone's plus-one who becomes a plus-two — until one day it is fifty names past what the hall, the caterer, or the budget can hold, and nobody remembers agreeing to any of it. Every name on that list has a price. It is not the invitation itself; forwarding a link costs nothing. The price is the seat, the meal, and the door — and that is exactly where a guest list needs to be cut.

How do I cut down my wedding guest list?

Work top-down through tiers, not name-by-name arguments. Here is the method:

1. List every name, then sort into three tiers. Must-have (immediate family, the people who raised you, your closest handful), should-have (extended family, close friends, people you see regularly), would-be-nice (everyone else — distant relatives, work acquaintances, "we should probably invite them" names).
2. Run the dinner test on the should-have and would-be-nice tiers. For each name, ask: would we have dinner with this person this year if the wedding weren't happening? If the honest answer is no, they move down a tier.
3. Set a hard number for the room, then cut from the bottom up. Would-be-nice goes first, in full, before a single should-have name is touched. Only move into should-have once would-be-nice is exhausted and the number still isn't met.
4. Cut in pairs, not singles. If a colleague is cut, cut the colleague's spouse too rather than leaving one half of a couple on the list — half-cuts are what get noticed and cause hurt feelings.
5. Agree the two families' allocations before either side touches a name. Split the remaining seats by a number, not a fight (see below).
6. Hold a short wave-two list, and keep the link private. Anyone cut for room reasons rather than relationship reasons can still get a private, un-indexed invitation later if a seat opens up — see the FAQ below on how that works without anyone finding out.

Who should we cut first?

Cut the would-be-nice tier first, in full — distant relatives you haven't spoken to in years, work acquaintances, "we should probably invite them" names that came from politeness rather than closeness. These are the names that came onto the list without anyone deciding they belonged there, which makes them the easiest and least painful to take back off.

The should-have tier — extended family, close friends, people you actually see — should be the last resort, not the first move. If cutting the whole would-be-nice tier still leaves the list over the number the room and the budget can hold, that is real information: the number itself may need to move, or the venue does, before any should-have name gets touched.

Never cut a name just because it's easy to cut. A name that arrived by accident (a parent added it without asking) is a different cut from a name that arrived on purpose (you invited them and changed your mind) — the first is a simple correction, the second deserves more thought than a spreadsheet row.

What is the "would we have dinner with them" test?

For any name on the fence, ask one question: would we have made time to see this person this year even if the wedding weren't happening? If the honest answer is yes, they belong on the should-have tier regardless of how distant the relationship looks on paper — a cousin who calls every month outranks a cousin who doesn't, whatever the family tree says. If the answer is no, the name belongs on would-be-nice, even if it feels awkward to admit that about a relative.

This test works because it separates "closeness" from "obligation," which is where most bloated guest lists actually come from. Nobody adds a stranger to a wedding list; they add people they feel they owe an invitation to. The dinner test cuts through the owing and asks about the relationship as it stands today, not as it stood at a family gathering five years ago.

How do we handle a guest list that two families both add to?

Agree a number for each side before either family starts naming names, and let each family fill its own allocation rather than negotiating over a shared pool. If the room holds 300 and both families are contributing guests, split it by an agreed ratio — often even, sometimes weighted by who is hosting or who has the larger extended family — and give each side full authority inside their own number.

This turns "why is your cousin in and my cousin out" into a non-issue, because nobody is comparing across families — each side is only managing its own list against its own budget of seats. The tiering method above (must-have, should-have, would-be-nice) still applies inside each family's allocation; it just runs twice, independently, instead of once as a joint argument.

Put the numbers in writing early — even a one-line message ("we're each working with 150 seats") — before either side starts building their list. Most guest-list conflict isn't about who gets invited; it's about a number nobody agreed to.

Should we do an A-list and a B-list?

A two-tier "A-list, B-list" system where B-list invitations only go out if A-list guests decline is common advice, and it can work, but it runs on a strict timeline: A-list invitations need to go out with enough lead time that declines come back and B-list invitations can still arrive with a reasonable RSVP window, not two weeks before the wedding. Anyone who receives an obviously late invitation and does the math tends to notice.

A gentler version works better for most couples: build the must-have and should-have tiers as your actual, final list — the one you send first — and treat would-be-nice as a private wave-two list you hold privately, only sending if seats genuinely open up from declines, and only using a link that was never made public in the first place (see the next question). This avoids the "did they only invite me because someone said no" problem entirely, because nobody outside your household ever needs to know a wave-two existed.

What if we cut someone and they find out?

If a cut is handled as a genuine room-and-budget decision rather than a personal one, most people accept it without much drama — guest lists having limits is common knowledge, and most adults have been on both sides of that limit before. The situations that actually cause hurt are the ones where a cut guest finds out through the invitation itself: a public link shared in a group chat that reaches people who were never meant to see it, or a group RSVP page that visibly lists who's attending.

This is where how you send the invitation matters as much as who's on the list. A private link that is only as public as you make it — never indexed by search engines, never posted anywhere public — means a name you left off the list has no way to stumble onto the page. If a seat opens up later and you want to invite from your would-be-nice tier, that same privacy is what lets a wave-two invitation go out quietly, without it reading as an obvious afterthought to anyone comparing notes.

The part of the list that actually costs money

Every extra guest on a wedding list is a seat and a meal — that reasoning holds regardless of venue or catering style, which is why the tiering method above focuses on the room and the budget, not a specific dollar figure. But it's worth being precise about which part of a wedding invitation actually scales with guest count and which part doesn't, because couples sometimes trim names to save money in the wrong place.

The invitation and the RSVP process should never be why a list gets cut. On MumenLabs' wedding invitation, the link can be forwarded without limit and every RSVP reply is free, however many arrive — a list of 50 costs the platform exactly the same as a list of 500. The only part that scales is entry passes at the door: the first 50 are included in the $99 publish, and beyond that they're added by the hundred (+150 for $75, +400 for $180, +1,000 for $400). If you're not checking anyone in at the door, you never buy a pass pack at all. That means the hard tiering decisions above should be driven by the room, the caterer, and family dynamics — not by a per-guest invitation fee, because there isn't one.

Frequently asked questions

Who should we cut first?

Cut the would-be-nice tier first and in full — distant relatives, work acquaintances, and politeness invitations — before touching a single should-have name. These are names that landed on the list without anyone deciding they belonged, which makes them the least painful cut.

How do we handle a guest list that two families both add to?

Agree a fixed number of seats for each family before either side starts naming names, then let each family manage its own allocation independently using the same must-have/should-have/would-be-nice tiering. This replaces name-by-name comparison with two separate, smaller decisions.

Should we do an A-list and a B-list?

A staged A-list/B-list system can work if there's enough lead time for declines to come back before B-list invitations go out, but a private wave-two list — held quietly and only sent if seats open up — avoids the risk of a late invitation looking like a leftover.

What if we cut someone and they find out?

Most guests accept a room-and-budget cut without hard feelings, as long as they don't discover it through the invitation itself. Keeping the invitation link private — never posted publicly, never indexed by search engines — is what prevents a cut guest from stumbling onto a page they weren't sent.

Cut the list, not the closeness

A tiered list, a clear number for each family, and a private link do more to prevent a guest-list fight than any amount of arguing over individual names. Once your list is set, build your wedding invitation and publish once for $99 — the link, the RSVP replies, and 18 months online never cost more however the final count lands, and passes at the door only scale if you're checking guests in.

Two more guides worth reading while you're planning the list: how to get an accurate wedding headcount once RSVPs start coming in, and how to stop uninvited guests from crashing your wedding if a trimmed list is exactly what you're trying to protect. If you're also weighing what the invitation itself should cost, how much does a digital wedding invitation cost breaks down the real numbers.