When to Send Wedding Invitations and Save-the-Dates

A groom named Eli once told me, three months after his wedding, the thing he'd do differently: "I'd send everything a month earlier. All of it. That's the whole list."

Not the venue, not the band, not the open-bar decision his uncle tested thoroughly. The mail. Because Eli and his wife followed the classic advice on when to send wedding invitations, six to eight weeks before, by the book, and spent the final month of their engagement doing RSVP collections like a small-town debt agency. Fourteen unanswered invites at the caterer's deadline. His wife cold-calling a cousin she hadn't spoken to since 2019. Romance!

The old timeline isn't wrong, exactly. It was written for an era when your guests lived in the same area code and "destination wedding" meant the next county over. Here's the timeline I actually give friends now, and the reasoning, because the dates only stick when you understand what each one is protecting you from.

When to send wedding invitations: the short version

For a hometown-ish wedding where most guests drive:

• Save-the-dates: 8 months out.
• Invitations: 10–12 weeks out.
• RSVP deadline: 5–6 weeks out.

For a destination wedding, or any wedding where most guests fly:

• Save-the-dates: 10–12 months out.
• Invitations: 14–16 weeks out.
• RSVP deadline: 8 weeks out.

Notice both invitation windows are earlier than the traditional 6–8 weeks. That's deliberate. Now the reasoning, because the reasoning is where couples either save themselves or become Eli.

Save-the-dates: the date claim

A save-the-date does one job: it plants a flag on a weekend before your guests' lives fill it with something else. Modern calendars book up brutally far ahead, school years, work travel, other people's weddings, and the save-the-date is you getting there first.

Eight months is the sweet spot for a local wedding. Earlier than a year and people can't emotionally process it ("we'll think about that in the future, when we are different people"). Later than six months and you're already losing the guests with complicated lives, which are exactly the guests you most want to lock down.

Ten to twelve months for destination or holiday-weekend weddings, because you're not just claiming a date, you're claiming vacation days and a travel budget. Include the city and a hotel hint even if nothing else is decided.

Two opinions while we're here. First: everyone on the save-the-date list must end up on the invitation list. A save-the-date is a promise, and "we trimmed the list" is not a conversation you want to have with someone who already requested the time off. Send save-the-dates to your sure list; the bubble people wait for the invitation round. Second: save-the-dates are the single best place to go digital even if your invitations will be paper, they're informational, they're early, and they benefit most from actually being seen. The full case is in my digital save-the-date guide, but the short version is that a save-the-date that lands as a text gets opened today, not discovered behind a pizza coupon in March.

Invitations: the headcount machine

One reframe fixes everything: the invitation send date has less to do with your guests than with your caterer's final-count deadline, and you build backward from it.

Most vendors want final numbers two to three weeks before the wedding. You want your RSVP deadline a solid two to three weeks before that, because, and this is the iron law of hosting, a chunk of your guest list will not answer by the deadline no matter what the deadline is. Eli's fourteen stragglers weren't an anomaly; they were the standard tax. You don't beat the stragglers. You budget time to chase them.

So the chain runs: vendor deadline at 3 weeks out → RSVP deadline at 5–6 weeks out → invitations at 10–12 weeks out, giving guests a month-plus to respond and you a buffer that absorbs the human race being itself.

The traditional 6–8 week send compresses all of that into a panic. Send at six weeks, set RSVPs due at three, and you've got zero chasing room before the caterer calls. That's the math that put Eli on the phone with his cousin.

Don't send earlier than about 14 weeks for a local wedding, though. Counterintuitive, but real: an invitation that arrives four months out feels unanswerable ("who knows what April-me is doing") and gets set aside, and set-aside invitations die. The save-the-date already did the early work. The invitation should arrive when an answer is actually possible.

The special cases

Holiday-weekend weddings: treat as destination timing for everyone, even locals. You're competing with traditions and trips that rebook themselves annually.

Very small weddings (under 30): you can run tighter, invitations at 8 weeks, because you'll personally know everyone's status anyway. The formal timeline exists to manage scale; twenty guests don't need a machine.

A B-list (and yes, almost everyone has one): send the A-list at 12 weeks, set their RSVP date at 8 weeks, and the declined seats free up with a comfortable 6+ weeks to invite round two, enough time that nobody feels like an obvious alternate. A B-list invitation that arrives three weeks before the wedding fools no one.

International guests: invitations at 16 weeks minimum, and flag visa lead times if relevant. Their save-the-date should've gone out around the one-year mark.

Where the timeline actually breaks, and the fix

Every couple plans the send dates. Almost no one plans the response collection, and that's the half that breaks. Paper RSVPs return at the speed of guests finding stamps, which is to say geologically. Email invites land in promotions folders. And the couple ends up keeping the master count in a spreadsheet fed by texts, voicemails, and one RSVP card returned with no name on it (this happens at nearly every wedding; identifying the anonymous "2 attending, chicken" card becomes a family mystery).

This is the part I'd hand to software even if everything else stayed traditional. A wedding invitation on Lemonvite goes out as a text, gets opened essentially immediately, and the RSVP is one tap, no stamps, no promotions tab, no anonymous chicken. The dashboard separates the confirmed, the declined, and, crucially for your follow-up week, the viewed-but-silent, so your reminders go only where they're needed. When the shuttle time changes in the final week, one broadcast to the yes-list handles it.

Plenty of couples run a hybrid: paper invitations for the keepsake, Lemonvite for save-the-dates and RSVP collection. That's a legitimate best-of-both. What's not legitimate is the spreadsheet-and-cold-calls plan, ask Eli.

Work backward from the caterer. Pad every deadline for the slow responders. And whatever your dates end up being, set up the RSVP machine before the first invite leaves, so the last month of your engagement gets to be about the wedding, not the mail.