Example 01
120 invitations · everyone within an hour's drive Local: 120 × 85% = 102 expected yes Expected declines: 18 Realistic range: 96–108 Invite-to-attendance ratio: 85 per 100 Seat the room for 108. Cater near 102.
All-local listPersonalize
Wedding RSVPs
What percentage of wedding guests decline?
Plan on roughly 15% of your local guests declining, 20–25% of your out-of-town guests and 25–40% for a destination wedding — which puts a normal mixed list at 80–85% attendance, or about 123 guests from 150 invitations. Run the same rates backwards and seating 100 people takes 118–128 invitations, most likely 122. The published averages disagree by more than ten points and the reason is always the same: who is on the list, not how the list was counted.
Which rate applies to you?
Pick your list, not an average
A single blended percentage is only right for a list that happens to match whoever's data produced it. Find the row that describes yours, then work the segments separately.
1
Everyone on the list lives within about an hour
Use 12–15% decline — expect 85–88% of them. Guests who can drive home the same night have almost nothing to organize, so the declines you get are real conflicts rather than logistics. Use 12% if literally nobody needs a hotel, 15% if a handful do. The calculator's mostly-local preset carries 12%.
2
A local core with a scattering of flights — the common case
Use 18% blended, but split the list and check it. 18% is what a two-thirds local, one-third traveling list works out to at 15% and 25%. If your split is anywhere near that, the blended number is fine. If it is not, the blend will be wrong in the direction you least want.
3
Half the list is booking flights and hotels
Use 22–25%, and always split the segments. At this ratio a blended rate hides the problem rather than solving it: the local half barely moves while the traveling half swings by twenty points, so the total range gets wide. Work the two halves separately and add them.
4
A destination weekend guests can drive or short-hop to
Use 25–35% decline, and move the reply-by date out. A beach three states away is a long weekend and a hotel, not an expedition. Plan for a third to say no, and give them eight weeks to answer instead of four — the reply-by date is the other thing destination actually changes.
5
Overseas, or anything that costs a week off work
Plan on 40–50% declining, and use the bottom of every range. This is the case Zola's ~35% attendance figure describes. Your own number depends almost entirely on whether the trip is one people were already inclined to take, so plan against the pessimistic end and be pleasantly surprised rather than the reverse.
6
A holiday weekend, or three weeks after another family wedding
Use the pessimistic end of whichever band you picked. There is no published adjustment for this and inventing one would be dishonest. What is true is that competing commitments push a list towards the bad end of its range, so plan against that end rather than the midpoint.
Forwards
📈 Your list, and how many actually come
Split the list into local, out-of-town and long-haul, apply a rate to each, then add them up. Local runs 12–17% decline, out-of-town 20–25%, anything needing a flight and a hotel week considerably more. The tables below sit at 15% for local, the middle of that band; the calculator's presets are one blended rate per list type — 12% mostly local, 18% mixed, 25% mostly traveling, 32% destination — so the same list can come back a few guests higher there. Copy a table and swap in your own counts.
Example 02
150 invitations · 100 local, 50 out-of-town Local: 100 × 85% = 85 Out-of-town: 50 × 75% = 38 Expected yes: 123 · declines: 27 Blended rate: 82% attending, 18% declining Realistic range: 113–134 Seat the room for 134. Cater near 123.
One in three travelingPersonalize
Example 03
200 invitations · 70 local, 110 out-of-town, 20 long-haul Local: 70 × 85% = 60 Out-of-town: 110 × 75% = 83 Long-haul: 20 × 65% = 13 Expected yes: 156 · declines: 44 Blended rate: 78% attending, 22% declining Realistic range: 144–164 The blended number here is 22%, not the 20% rule of thumb. That two-point gap is four guests — four plates, four chairs and four welcome bags.
Travel-heavy listPersonalize
Example 04
60 invitations · close family and the inner circle Local: 60 × 88% = 53 expected yes Expected declines: 7 Realistic range: 50–56 Blended rate: 88% attending, 12% declining Short lists run high — a 60-name list is people who rearrange things for you. Use the optimistic end of the local band, and remember WeddingDive's own worked example puts a 50-invite list at 91%.
Short list, high ratePersonalize
The estimate stops mattering the moment real replies land
Every number on this page is a placeholder for data you do not have yet. The couples who beat their estimate are the ones who got replies quickly — Text My Wedding texts each household its own RSVP link and the yes, no and party size land automatically, so by week two you are working from your list instead of somebody else's average.
Backwards
🔁 Your headcount, and how many to invite
The same arithmetic in reverse: divide the number of people you want in the room by the share you expect to attend. Round up, then hold the last few names back as a B-list rather than posting every invitation at once.
Example 05
Target: 100 guests in the room Mixed list, 18% expected decline 100 ÷ 0.82 = 122 invitations If mostly local (15% decline): 118 If a quarter are flying (22% decline): 128 Send 118 now and hold 4–10 names as a B-list. That way the target survives whichever end of the range you land on.
Seat 100Personalize
Example 06
Target: 150 guests in the room Mixed list, 18% expected decline 150 ÷ 0.82 = 183 invitations If mostly local (15% decline): 177 If travel-heavy (25% decline): 200 The spread between those two is 23 invitations. Which segment your list is made of matters far more than which published average you use.
Seat 150Personalize
Example 07
Target: 60 guests · intimate, everyone local 12% expected decline 60 ÷ 0.88 = 69 invitations Range: 65 invitations if only 7% decline, 71 if 15% do On a list this size one family of four is nearly 7% of the room, so build the plan around whole households rather than the decimal.
Seat 60, intimatePersonalize
Example 08
Target: 200 guests · half the list is flying 25% expected decline 200 ÷ 0.75 = 267 invitations But check the top of the range first: if only 17% decline, 267 invitations returns 222 yeses. If your venue seats 210, do not send 267. Cut the list until the TOP of the range fits the room.
Seat 200, travel-heavyPersonalize
Travel and destination
✈️ When the list has to get on a plane
Destination changes exactly two numbers: the decline rate goes up and the reply-by date moves out to about eight weeks, with invitations mailing around fourteen. Everything else on this page works the same way. Note that "destination" covers two very different weddings — a short flight to a beach town, and a week overseas — and the published figures are arguing about which one they mean.
Example 09
Destination · 120 invitations · a short flight and two nights 120 × 68% = 82 expected yes Expected declines: 38 Realistic range: 70–94 Blended rate: 68% attending, 32% declining Reply-by: 8 weeks before the wedding, not 4 Invitations mail: about 14 weeks before A range of 70–94 is 24 guests wide. Book the venue for 94 and cater near 82.
Drivable destinationPersonalize
Example 10
Target: 50 guests at a destination wedding 32% expected decline 50 ÷ 0.68 = 74 invitations Range: 64 invitations if only 22% decline, 87 if 42% do The B-list barely works here: by the time declines land you are eight weeks out and a second wave cannot book flights. Invite the full 74 in one go and accept the wider range.
Destination, in reversePersonalize
Example 11
Overseas · 90 invitations · a week away, passports needed Regional: 20 × 85% = 17 Domestic flight: 30 × 65% = 20 Overseas: 40 × 45% = 18 Expected yes: 55 · declines: 35 Blended rate: 61% attending, 39% declining Realistic range: 45–65 This is the case Zola's ~35% destination figure is describing. If the trip is one your people were already inclined to take, use the top of the range; if you are asking for a week of vacation time, use the bottom.
Overseas, a week awayPersonalize
Using the number
🍽️ Which number each vendor gets
One estimate produces several different numbers, and handing the wrong one to the wrong vendor is how couples end up either short of chairs or paying for empty ones. The rule: plan capacity against the top of the range, plan consumables against the expected figure.
Example 12
One estimate, five vendor numbers Expected 123 · range 113–134 Caterer's planning number: 123 Seating, tables, place settings: 134 (top of range) Bar and drinks: 134 — running dry is the failure mode Welcome bags and favors: 123 Shuttle seats: 123, rounded up to whole vehicles None of these is the final count. That number is confirmed yes replies, and it is submitted 7–14 days out.
Estimate to vendor numbersPersonalize
Example 13
What ten more invitations actually cost Mixed list, 18% expected decline 10 extra invitations → 8 expected extra guests Catering: 8 plates at your quoted per-head price Bar, rentals and stationery: 8 more of each At $85 a plate plus roughly $25 a head across bar and rentals, ten names is about $880 — and cutting ten names saves the same, because only eight of them were ever coming.
The marginal ten namesPersonalize
Example 14
Estimate against venue capacity Venue capacity: 130 seated Invitation list: 150 (100 local, 50 traveling) Expected: 123 · range: 113–134 Top of range is 4 over capacity. Either cut 6 names, or find out whether 130 is a fire-code limit (immovable) or a seating-plan limit (sometimes movable). Do not invite on the assumption the estimate holds — the range is what you plan against.
Capacity checkPersonalize
Whose number is it?
Five numbers, and only two are yours
An attendance estimate sits in the middle of a chain of numbers, most of which somebody else controls. Confusing them is what turns a reasonable estimate into an expensive one.
1
The number you invite
You do · fixed the week invitations mail, six to eight weeks out. This is the only number on the list you fully control, and it is effectively irreversible once the envelopes are posted. Hold a handful back as a B-list rather than deciding it is final on mailing day.
2
The expected-attendance range
Nobody — it is an estimate you chose to trust · before you sign the venue, and again the week you mail. Nothing enforces it, which is exactly the danger. Treat the range as the plan and the midpoint as a guess; a couple that books against the midpoint has quietly bet that half the possible outcomes will not happen.
3
Your venue's capacity
The venue, and often the fire code above it · fixed the day you sign the contract. You cannot negotiate with a fire marshal. If the top of your attendance range exceeds this number, the list is too long — the estimate does not get to be the thing that flexes.
4
The caterer's minimum guaranteed count
Your catering contract · written in at signing, billed at the final count. You pay for the minimum whether or not those people come, which means under-inviting costs money too. Check this number before you decide the list is short enough — it may be cheaper to invite ten more.
5
The final count you submit
You do, on the caterer's date · typically 7–14 days before the wedding. By then the estimate is irrelevant: you submit confirmed yes replies, not a percentage. Do not pad it down for no-shows — most contracts bill the guaranteed number or the number who attend, whichever is higher.
The number this page produces is an input somewhere else — most directly into the free wedding guest list template, whose capacity field takes exactly this answer: it counts your households against the invitations you can send and flags a family layer that has gone out half-invited. Deciding who belongs in those seats in the first place is worked through circle by circle on who to invite to your wedding. Feed the top of your range into the wedding alcohol calculator — the bar is the one line item you size against the top of the range rather than the middle. When you are ready to turn the estimate into real replies, automatic RSVP reminders do the chasing, the phrasing for the reply card itself lives in RSVP card wording, and a QR code straight to your RSVP page gets printed invitations answered in seconds rather than weeks.
The published figures
Four sources, four different answers
Everyone quotes a percentage and almost nobody agrees. Here is what the widely-cited pages actually say, checked in August 2026, and why the gap between them is larger than the gap you are trying to estimate.
1
The Knot: 20% decline as a rule of thumb
Its decline-rate guide calls 80% attendance the sweet spot and 20% a rule of thumb wedding professionals broadly agree on. It also cites a 60–85% range and an 83% confirm figure in the same article — a 25-point span presented alongside a single planning number.
2
RSVPify: 83% yes, 17% no
Measured from replies collected on its own platform, so it is real data rather than a rule of thumb. It is also a blended figure across whatever mix of weddings its users happened to run, which is not necessarily yours.
3
Zola: 85% local, 55% out-of-town, 35% destination
The only widely-cited source that segments, and the reason this page does. Its headline is 75–85% overall, but the split underneath it is where the useful information is — and its 55% for out-of-town guests is far harsher than most blended averages imply.
4
WeddingDive: 91% on 50 invitations, 70% on 400
Its worked examples put 50 invitations (40 local, 10 out-of-state) at about 91% attendance and 400 invitations (300 local, 100 out-of-state) at about 70%. The list-size effect is real: a short list is your inner circle.
5
Why they disagree by more than ten points
Put the flat rules of thumb next to the one segmented source and the gap is not subtle: The Knot's guidance is to plan on 20% of the list declining, while Zola's own split puts out-of-town guests at 55% attending — 45% declining, more than double the rule of thumb, and twenty-five points below Zola's own 80% blended headline. A source can disagree with itself here without either number being wrong, because they are averaging different lists. Composition is the variable, not the rate, which is why a blended number you did not build yourself is the weakest input you can use.
Avoid these
Five ways the estimate goes wrong
The arithmetic is easy. Almost every expensive mistake here is about which number was used, not how it was calculated.
✕
Applying one blended rate to a lopsided list
If 60% of your list is flying, an 18% blended rate will overstate attendance by ten or more guests. Split the list first. It takes two minutes and it is the single highest-value thing on this page.
✕
Booking against the midpoint
The midpoint is the most likely single outcome and it is still a coin flip. Size the room and the bar against the top of the range, size catering near the middle, and know what the bottom of the range does to your minimum spend.
✕
Inviting past capacity because "20% won't come"
This works right up until it does not, and the failure mode is guests you invited having nowhere to sit. If the top of your range does not fit the venue, the list is too long — no percentage makes that safe.
✕
Shaving no-shows off the estimate
No-shows are a different calculation entirely, they happen after replies are in, and most catering contracts bill the guaranteed number or actual attendance, whichever is higher. Trimming an estimate for them saves nothing and risks a short kitchen.
✕
Still quoting a published average once replies are landing
Once 40% of your list has answered, your own returns are better evidence than anybody's national figure. Recalculate from what you actually have — expected yes from the remaining silent households, added to the yeses in hand — and let the published rate go.
Free, and it runs in your browser
Run your own list, forwards and backwards
Enter your invitation count and a target headcount and it returns both directions at once: expected attendance with a realistic range, the invite-to-attendance ratio, and the number of invitations your target actually needs. The presets carry one blended rate per list type — 12% mostly local, 18% mixed, 25% mostly traveling, 32% destination — so if your list is lopsided, work the segments from the tables above and compare.
Wedding RSVP deadline calculatorFree · no sign-up · runs entirely in your browser
Turn an invite list into an expected headcount, or a target headcount into the number of invitations to send.
Leave it blank and every answer below still works — you just get “four weeks before the wedding” instead of a printed date.
The common case: a local core plus a scattering of guests who need a flight or a hotel.
Private by design: every date and number here is worked out in your browser, and the dates and counts you enter never leave this page. We count anonymous usage — which mode people pick, nothing they type. Close the tab and it's gone, so copy your dates somewhere safe.
How many will actually come
98 guests
Based on a 18% decline rate for a a mix guest list.
- Guests you should expect98from 120 invitations
The common case: a local core plus a scattering of guests who need a flight or a hotel.
- Expected declines22about 18% of the list
Planning estimate, not a measurement — your own list will land somewhere in the range below.
- Realistic range90–107±7 percentage points
Book the venue for the top of the range and budget the catering near the middle.
- Invite-to-attendance ratio82 per 100
For every hundred people you invite, roughly this many walk in.
- To seat 100, invite122the same decline rate, run backwards
Do not send all of them at once — hold the last few as a B-list and see who declines first.
- Your target needs about 122 invitations and your list has 120. Either widen the list or lower the target.
Decline, reply, and no-show rates here are planning estimates built from the ranges wedding vendors publish — useful for sizing a list, not a survey result.
Want the replies to chase themselves?Text My Wedding texts the invitation, collects the RSVPs, and nudges the households that go quiet — so the list is done before your caterer asks.
See the app →✓
Keep exploring
More on collecting wedding RSVPs
How to collect wedding RSVPsFour ways to gather replies, compared→The final headcountWhen the caterer needs a number, and which number→Wedding B-list invitationsTiming a second wave so nobody can tell→Plus-one rulesWho gets one, and fixing a reply that added guests→Online vs paper RSVPsFour channels compared on speed and chasing→Wedding RSVP questionsTwenty fields worth collecting, and what each costs→
Good to know
Questions about wedding attendance rates
What percentage of wedding guests decline?
Plan on about 15% of local guests, 20–25% of out-of-town guests and 25–40% for a destination wedding, which puts a typical mixed list at 15–20% declining overall. The published figures cluster around the same place: The Knot uses 20% as a rule of thumb, RSVPify measured 17% declining across replies on its own platform, and Zola quotes 75–85% attendance overall.
How many people should I invite to get 100 guests?
Between 118 and 128, and 122 is the sensible middle. Divide your target by the share you expect to attend: 100 ÷ 0.82 = 122 for a mixed list. If almost everyone is local, 118 is enough; if a quarter of the list is flying, budget 128. Send about 118 and hold the rest as a B-list.
What percentage of out-of-town guests attend a wedding?
This is where the published sources disagree most: Zola puts it at about 55%, and the flat rules of thumb elsewhere imply something much closer to 80%. The distinction that matters is effort, so we plan it in two bands rather than one: for guests within a few hours' drive, 75–80% attending, and for guests who need flights, a hotel and time off work, 55–65%. Those are our planning bands, not a published figure — if your out-of-town half is genuinely all short drives, use the top of the range and say so in your own notes.
Is the 80% rule accurate?
It is a reasonable starting point and a poor finishing point. 80% is about right for a list that is mostly local with some travel, which is the most common shape — but it is meaningfully wrong for an all-local list (too pessimistic) and badly wrong for a destination wedding (too optimistic). Use it to sanity-check a segmented estimate, not to replace one.
Do smaller guest lists have higher attendance rates?
Generally yes. WeddingDive's own examples put a 50-invitation list at about 91% attendance and a 400-invitation list at about 70%. The reason is composition rather than size: a short list is close family and the inner circle, who rearrange plans to come, while a long list reaches further into colleagues, distant relatives and plus-ones with weaker ties.
What percentage of guests attend a destination wedding?
Zola publishes about 35%, which describes a genuine expedition — overseas, several nights, time off work. For a destination guests can drive to or reach on a short flight, 65–75% attendance is more realistic. Whichever applies, move your reply-by date to about eight weeks before the wedding and mail invitations around fourteen weeks out.
Should I invite more people than my venue holds?
Not past the top of your expected range. Work out what happens if declines come in at the optimistic end — if that number is above the venue's capacity, cut the list. Capacity is often a fire-code limit, which means it cannot be negotiated on the day, and the failure mode is guests you invited with nowhere to sit.
You picked the date.
Let us collect the replies.
Text My Wedding sends the invitation by text, records every RSVP against the right household, and nudges the ones who go quiet — so your caterer gets a number instead of a guess.