Save the Dates: When to Send, What to Say, What to Skip

My friend Layla sent save the dates eleven months before her wedding in Vancouver. They featured a black-and-white photo of her and her fiancé on a beach in Tofino, the date, and the phrase "Save the date!" in a handsome serif. They were beautiful. They cost $412 including postage.

Three months later, she moved the wedding. Work visa issue, her fiancé's employer, long story. She then had to notify 140 guests by email that the date had changed. About 30 of them had already booked flights.

Save the dates are not the most important piece of wedding communication. But they are the first one, which makes them disproportionately memorable and disproportionately likely to cause downstream problems if you get them wrong. Here is what I actually know about them, after five family weddings and many more I've advised on.

Table of Contents

• What Save the Dates Are Actually For
• When to Send Them
• What to Include
• What to Leave Off
• Paper vs. Digital
• Cultural Variations
• Multi-Event Weddings
• The Wedding Website Question
• Common Mistakes
• Frequently Asked Questions
• Sources and Further Reading

What Save the Dates Are Actually For

They do one job: tell guests to block the date.

Not invite them. Not explain your wedding. Not collect RSVPs. Not communicate the registry. Not sell you on the theme. Just: date, location (city, usually not venue), "save it."

Every problem with save the dates comes from overloading them. If you remember one thing from this piece, remember that.

When to Send Them

Local weddings, within a guest's driving range: 6 to 8 months before.

Regional weddings, requiring a flight for most guests: 8 to 10 months.

Destination weddings, international or requiring multi-day travel: 10 to 12 months, minimum.

Peak-season weddings (May through October in most of North America): Add an extra month to the above.

Holiday-weekend weddings: Add two months. People book holiday travel early.

Here is what nobody tells you: sending too early is worse than sending a little late. If you send save the dates at 14 months out, some guests will literally forget by the time the invitation arrives. They put the card on the fridge, a new magnet goes on top, and by month 8 it's forgotten. The sweet spot is late enough that it feels imminent, early enough that travel can be booked.

My own rule: send save the dates the same month you finalize the venue contract. That way you know the date is real and you are not going to have to retract.

What to Include

The minimum:

• The couple's full names (not nicknames; this is the legal-ish first communication)
• The wedding date
• The city and state or province
• Your wedding website URL
• The phrase "formal invitation to follow"

That's it. That's the whole card.

Optional, if it helps your specific guests:

• "Destination wedding" or "Black tie" note, if you know early
• A photo, if you like (most couples do)
• A mention of multiple events if you're having them ("Join us for a weekend of celebration")

What to Leave Off

• The venue name. You might change it. Even if you don't, guests don't need it yet.
• Registry information. This is tacky on save the dates. Put it on the website.
• The ceremony time. Things shift. Put it on the invitation.
• Dress code. Put it on the website or invitation.
• RSVP request. You are not asking for RSVP at this stage.
• Hotel blocks and travel details. Put them on the website.
• "Adult only" or "no kids" policies. This is an invitation-level communication, and honestly, a save-the-date-level communication (people need to arrange childcare). Actually, wait. If you are doing adults-only, you do want to flag it now. Include it in small text.

Paper vs. Digital

This is more a question of culture than correctness.

Paper save the dates are the traditional choice in Western weddings and are still the norm for formal affairs. Pros: tangible, displayed on friends' fridges, signals that the wedding is a big deal. Cons: cost ($200 to $600 for a wedding of 150+), slower to produce, harder to update if details change.

Digital save the dates (email, Paperless Post, a shared wedding website link) are increasingly common and are particularly good for:

• Couples with a large proportion of out-of-country guests (Persian, Indian, Chinese families often have heavy international contingents)
• Destination weddings, where you need to send detailed travel info alongside the save the date
• Couples who want to save $300 to $600 for other line items
• Environmentally conscious couples

Pros: free or nearly free, fast, can be updated, links to a website. Cons: doesn't have the physical presence, some older relatives may not see an email in time, feels less formal.

Hybrid approach (what I did and what I usually recommend): digital to everyone under 50 and everyone international, paper to older relatives and immediate family. Costs less, hits the formality for the people who care about it, and is faster to send.

Cultural Variations

A quick tour of how save the dates work across cultures:

Persian weddings: Traditional Persian weddings often skip save the dates entirely. The custom is a formal invitation (dastbandun) closer to the event, usually 6 to 8 weeks out. For Persian-Canadian or Persian-American couples with a mixed guest list, a hybrid works: digital save the dates for non-Persian guests who need more notice, formal paper invitation for everyone closer to the event.

Indian weddings: Save the dates are now common, especially for destination weddings in Goa, Jaipur, or Udaipur, which foreign guests need to plan 10 to 12 months ahead. Traditional invitation cards (often three or four inserts for mehndi, sangeet, ceremony, reception) still come later.

Chinese weddings: Save the dates are uncommon in traditional Chinese weddings. The formal red invitation (typically sent 4 to 6 weeks out) is the main communication. For Chinese-Western couples, save the dates are increasingly used.

Sikh weddings: Varies widely. Diaspora Sikh weddings (Canada, UK, US) often use save the dates, especially for multi-day events. Gurdwara-based weddings with strong community attendance often rely on word-of-mouth plus formal invitation.

Jewish weddings: Save the dates are standard, especially because Jewish weddings cannot be held on Shabbat or major holidays, which limits the calendar and makes early notice helpful.

If you are blending traditions, go with the more generous timeline. Sending save the dates "the Western way" does not offend the other side. Not sending them, and expecting international family to fly on 8 weeks notice, does.

Multi-Event Weddings

If you are doing a multi-event wedding (which most cultural weddings are), your save the dates should signal this. One line is enough:

"Join us for our wedding weekend in Vancouver, September 18 to 20, 2026. Full schedule and details at [website]."

Do not try to list every event on the save the date. Do not try to explain the aghd or the sangeet. Link to the website, where all of that can live with proper context.

What you want the save the date to do is flag "this is a multi-day event, clear more time on your calendar than you'd normally allocate for a wedding." That signal is what matters. Details follow.

The Wedding Website Question

You need a wedding website by the time you send save the dates. This is non-negotiable in 2026. Save the dates point to the website. The website carries the weight of all the information you didn't put on the card.

A good wedding website at the save-the-date stage has:

• Couple's story or brief intro
• Event date and location (city, potentially region)
• A rough schedule if multi-day
• Travel information (airport, suggested hotels, car vs. transit)
• FAQ (especially important for cultural weddings: "What is a sofreh? What do I wear to a sangeet? Is the ceremony in English?")
• Placeholder for RSVP, which will open closer to the invitation date

You can build this on The Knot, Zola, Squarespace, or a planning platform like RSVP'd (which has the advantage of tying the website to your RSVP tracking and vendor coordination, so you're not maintaining three separate tools). For cultural weddings I particularly recommend platforms that let you create event-specific pages, because the sangeet and the aghd might have different dress codes, different venues, and different guest lists.

Common Mistakes

Sending to people you haven't confirmed you want on your guest list. Once a save the date is sent, you cannot un-invite that person without real social cost. Only send to people you are 100 percent certain about. The B-list stays on the B-list for now.

Sending before you've nailed the venue. I know couples who have had to re-send save the dates because the venue fell through. It's mortifying and expensive. Confirm the venue contract first.

Forgetting address collection. Before you send paper save the dates, you need mailing addresses. Most couples realize this the week they are trying to send and have to ask their parents to forward every aunt's address. Do this earlier. A shared Google Form sent to your parents in month 8 works.

Making the save the date into an invitation. Restate: save the dates tell people to hold the date. Invitations invite them. Different jobs, different documents, different timing.

Skipping save the dates because you're doing paper invitations anyway. If you are mailing paper invitations 8 weeks before the wedding, many of your guests will have made travel plans before then. For destination or multi-day weddings, save the dates are functionally a necessity.

Forgetting to communicate the wedding website URL on the save the date. The card is a traffic-driver. If guests don't know where to learn more, they will text you, and you will spend the next six months answering the same questions.

Frequently Asked Questions

Sources and Further Reading

• Emily Post Institute: wedding invitation and save the date etiquette
• Paperless Post and The Knot 2024 wedding stationery trends reports
• "Digital First: How Modern Couples Communicate About Their Weddings" (Wedding Industry Research Council, 2024)
• Persian, Indian, and Chinese wedding etiquette guides from the Diaspora Wedding Project
• Case studies from the author's family and friends, some of whom will recognize themselves