Most wedding wording guides were written for a card in an envelope, then lightly edited for email. That leaves a gap. A digital invitation has no reply card, no return address and no stamp, but it can carry something paper never could: several functions, several guest lists and several RSVP deadlines on one screen.
This page is a swipe file. Every example below sits in its own block with real line breaks, so you can copy it, paste it, and swap the bracketed parts. You get the four tone sets every guide has, plus the sets almost nobody publishes: wording for a five-function wedding weekend, wording that asks each guest to reply only to the functions they are actually invited to, and wording for a video invitation, including a spoken script with timing marks.
Three things change: the RSVP mechanism, the length, and how many dates one invitation can carry. Everything else about wedding wording holds.
On paper, every element is a separate printed object. The reply card is a card. Directions are an insert. A second function means a second card in the same envelope. In a digital invitation those objects collapse into lines, links and buttons, which is why copying a paper wording template usually leaves you with instructions nobody can follow. Anything that references mailing, stamping, enclosing or returning has to go.
| Element | Paper wording | Digital wording |
|---|---|---|
| Reply instruction | "The favour of a reply is requested. Reply card enclosed." | "Tap RSVP below by [date]." |
| Return address | Printed on the reply envelope | Delete. Nothing is mailed. |
| Reception details | Separate reception card | Subhead on the same screen |
| Directions and hotels | Printed insert | One labeled link: "Travel and hotels" |
| Extra functions | One card per function | One invitation, one block per function, one RSVP per function |
| Dress code | Lower right corner | Its own line, directly above the RSVP |
| Registry | Never on the invitation | Still never on the invitation. Link it from your website. |
| Help for a guest who is stuck | Host's phone number, word of mouth | A named phone number in the invitation body |
What does not change: the couple's names come first, the host line sets the register, formal dates are spelled out, and the invitation face stays free of gift talk. If you want the full conventional rules before you adapt them, our complete guide to wedding invitation wording covers host lines, name order and honorifics in detail. This page is the digital-specific half.
Length is the second real change. A card is read standing at a kitchen counter. A digital invitation is read on a phone, mid-scroll, and the parts below the fold get skimmed. Use these as working limits rather than rules.
| Channel | Practical length | First thing to cut |
|---|---|---|
| Email or event-page invitation | 90–120 words | The paragraph about how you met |
| Uploaded designed card plus caption | 40–60 words of caption | Anything already printed on the card |
| Video invitation | 55–75 spoken words (15–30 seconds) | The street address. Put it in the caption. |
| Text message or DM | Under 300 characters | The dress code. Link it. |
| Save-the-date | 25–40 words | The venue name, if it is not booked |
Six elements make an invitation complete, and a seventh appears only when you are hosting more than one function.
| # | Element | What it must contain | Example line |
|---|---|---|---|
| 1 | Who is marrying | Both full names, in the order you have agreed | "Amara Ellison and Daniel Reyes-Cho" |
| 2 | Who is hosting | The host line, which sets the formality | "Together with their families" |
| 3 | Date, time, place | Day, date, start time, venue name, city, map link | "Saturday, June 13, 2026 at 5:30 in the evening" |
| 4 | Dress code | A named code, not a vibe | "Black tie optional" |
| 5 | RSVP action and deadline | The verb, the destination, the date | "Tap RSVP by May 1" |
| 6 | Details and a human fallback | One link, one phone number | "Travel details: [link]. Trouble replying? Call [name] at [phone]." |
| 7 | Scope, if you have multiple functions | Which functions this guest is invited to | "You are invited to the events listed below." |
Element six is the one couples skip, and it is the one that saves you the most work. A named phone number in the body means the four or five guests who cannot make a form work call a person instead of going silent. Element seven is the one no paper template has, because paper solved it with extra cards.
Element four deserves a note. "Dressy casual" and "garden formal" make guests text each other for a week. Pick a named code, then add a five-word gloss if you want: "Cocktail attire. Suits and midi dresses."
A save-the-date has one job: get the date onto a calendar. It does not need a venue, a time, a dress code or a finished website. Send it six to eight months ahead, and closer to nine or ten months if guests are flying or you are hosting a full weekend.
The digital version has one advantage worth using. Because you are not paying per card, you can tell guests upfront that the wedding is a weekend rather than a day, which is the single most useful thing a save-the-date can do for someone booking flights. For the paper-versus-digital timing question and what belongs on each, see our save-the-date and invitation timeline.
Formal wording works perfectly well in a digital invitation, because the register lives in the language, not the paper stock. Spell out the date and time, use third person, skip contractions, and keep the RSVP instruction as plain as the rest is ornate. "Kindly reply by the first of May using the button below" is not a contradiction. It is just accurate.
One spelling note: the traditional formal line is "request the honour of your presence", with the British spelling, and it conventionally signals a ceremony in a house of worship. "Request the pleasure of your company" is the traditional line for a ceremony elsewhere. American English "honor" is entirely acceptable, and plenty of couples use it. Pick one and be consistent across the save-the-date, the invitation and the reminders. For a wider bank of traditional constructions, our wedding invitation wording examples collection runs through the classic host-line variations.
Casual wording is not lazy wording. It carries the same six elements in fewer words. The failure mode is vagueness: "drinks and dinner, details soon" reads friendly and generates a week of questions. Name the time, name the place, name the deadline, and then be as relaxed as you like about everything else.
Humor is the one register where you should read the draft out loud to someone who is not in the joke. An inside reference that lands with eleven friends will confuse the eighty other people on your list. Keep the joke in the first two lines and let the logistics be sober.
The host line is the first line of the invitation and the one families argue about. It answers a practical question: who is issuing this invitation. Traditionally that meant who is paying, but that convention has loosened, and "together with our families" is now the most common solution because it credits everyone without ranking anyone.
Digital changes nothing here except the space. You have room to name four sets of parents on one screen without a layout problem, which is genuinely useful for blended families.
These four situations share one problem: the standard template implies something that is not true. It assumes first marriage, no children, a local guest list and a full-size reception. Each of the sets below fixes one assumption with a single line.
For a second marriage, drop the parental host line and let the couple host. Nothing needs explaining and no wording should apologize. For a blended family, name the children in the invitation if they are part of the ceremony, because guests will look for them. For a destination wedding, add money and logistics honesty: the invitation is also a travel brief. For an intimate wedding, say the number, so nobody assumes they were forgotten. If travel is the main variable, our destination wedding invitation guide covers timing and hotel-block phrasing in more depth.
Start with the schedule, then write the copy around it. A wedding weekend is usually four or five functions with four or five different guest lists, and the wording problem is not describing them. It is making the guest lists feel like logistics rather than a ranking.
The rule that solves most of it: describe every function neutrally and let each guest see only the ones that apply to them. Never write "the main events" or "immediate family and wedding party only" in a document that also goes to people who are not immediate family. Write the function, the time, the place and the dress code, and stop.
| Function | Typical guest scope | Suggested RSVP deadline | Wording note |
|---|---|---|---|
| Welcome party (Friday) | Out-of-town guests, often everyone | 6 weeks out | Say "drop in" if it is come-and-go. Guests plan flights around it. |
| Rehearsal dinner (Friday) | Wedding party, immediate family, sometimes officiant and readers | 6 weeks out | Name the arrive-by time, not the start time |
| Ceremony (Saturday) | Everyone invited | 4 weeks out | This is the one date that goes in every reminder |
| Reception (Saturday) | Everyone invited | 4 weeks out | Include the end time. Guests booking rides need it. |
| After-party (Saturday, late) | Anyone who wants it | No RSVP needed | Write "no reply needed, just come" |
| Farewell brunch (Sunday) | Everyone still in town | 4 weeks out | Give a window, not a seating time, and mention checkout |
Sending separate invitations for each function is the common workaround, and it is the thing guests complain about: three emails, three links, three deadlines, and no single place to see the weekend. One invitation with per-function blocks solves it. If the rehearsal dinner is doing heavy lifting in your weekend, our rehearsal dinner invitation guide has wording for the host line and the arrive-by time.
Answer the mechanics in the copy, not in a follow-up text. A per-function RSVP needs three sentences: what you are asking for, how many answers you need, and by when. The wording below covers each variation, including the awkward ones like plus-ones that apply to some functions and children who are welcome at some but not others.
The phrase that does the most work is "the events you are invited to". It is accurate, it is neutral, and it implies without stating that not everyone has the same list. Compare it with "the main events", which tells a guest they got the smaller version.
Work backward from whoever needs numbers first, which is almost never the reception caterer.
| Function | Who needs the number | Deadline, counting back from the wedding |
|---|---|---|
| Rehearsal dinner | Restaurant, often on a private-room minimum | 6 weeks |
| Welcome party | Bar or venue, per-head bar package | 6 weeks |
| Ceremony and reception | Caterer's final count, plus seating chart | 4 weeks |
| Farewell brunch | Venue, usually flexible | 4 weeks |
| Room block release | Hotel | 6 to 8 weeks |
This is where a per-function invitation stops being a wording exercise and becomes a tracking one. On Lumhe, each function is a separate sub-event inside one event: its own date, time, venue, guest list and RSVP. Different guests can be invited to different functions, so the guest sees only their own list and replies to each function independently, and you see a live count per function rather than one blended number. That is what makes the sentence "please reply to the events you are invited to" true rather than aspirational. Reminders go only to the people who have not answered that specific function, so the guest who already said yes to Saturday does not get nudged about it while you are chasing Friday. If you want the general mechanics of collecting replies rather than the wording, our online RSVP guide for weddings covers the tracking side.
Most digital wording advice assumes one format: an email with a button. In practice couples send four. A designed card made in Canva and uploaded as a JPG. A PDF from a stationer. A short video, filmed on a phone or animated. A plain text message to the group that needs no ceremony at all. Each one needs different words, and the reason is simple: the format decides what the words have to carry.
A designed card already contains the names and the date, so the caption should carry the RSVP instruction and the deadline instead of repeating what is printed. A video cannot be re-read, so it should carry the emotion and the date and let the accompanying message carry the address. A text message has no visual hierarchy, so it needs the deadline in the last line where the eye stops.
| Platform | Invitation formats it accepts | Per-function / multi-event RSVP |
|---|---|---|
| Lumhe | Upload your own image (JPG/PNG), video, PDF or typed text. No template library yet. | Yes. Each function is a sub-event with its own date, venue, guest list and RSVP |
| Mixily | Event page with an image and typed text | Not per function. One event, one RSVP |
| Evite | Template gallery, with image upload on some designs | Not per function. One event, one RSVP |
| Paperless Post | Template gallery, card-style designs | Not per function. Separate cards for separate events |
| Greenvelope | Template gallery, some custom design upload | Not per function. Separate mailings for separate events |
| Zola | Template gallery plus wedding website and registry | Website can list multiple events; RSVP is questionnaire-style |
Verify format support and any pricing directly with each platform before you commit, because feature sets and plans change. On price: Mixily states its free tier covers up to 40 RSVPs and that "for a 100-guest wedding, Mixily Pro is $29/month". Mixily's own post also cites Greenvelope at "$99+ per mailing" and Paperless Post at "$84–$114 for a fully-dressed 100-guest send". Those are Mixily's published figures for those tiers, not ours, and all four should be re-verified before you plan a budget around them. On Lumhe, event creation, invitations, per-function RSVP tracking and Moments are free forever, with no per-event or per-guest charge. The only paid extra is optional themed Digital Lifafa envelope designs at $0.49 to $1.99.
Whatever you design, it uploads to Lumhe unchanged: the image, the video, the PDF or just typed text. Nothing is redrawn or reformatted, and the event details and per-function RSVP sit around it.
Keep a video invitation between 15 and 30 seconds. Under 15 and it feels like a teaser with no information. Over 30 and people stop watching before the date appears, which is the one thing the video exists to deliver. Say the date twice, once spoken and once on screen.
| Timing | What happens | Words |
|---|---|---|
| 0:00–0:03 | Faces, no text yet | The greeting and the names |
| 0:04–0:09 | Warm line | Why you are calling, in one sentence |
| 0:10–0:15 | Date and city, spoken and on screen | The date, said out loud |
| 0:16–0:22 | The functions, if you have more than one | Day names only, no times |
| 0:23–0:28 | The ask | "RSVP by [date] at the link below" |
| 0:29–0:30 | Sign-off on a still frame | Names and the date again, on screen |
Put the website URL in exactly two places: once as a labeled line in the body, once as a button near the RSVP. Two is enough. Three or more turns the invitation into a link farm, and guests start tapping the wrong one.
Label the link by what is behind it rather than by what it is. "Travel and hotels" gets more taps than "our website", because it answers a question the guest already has. Never put the URL in the subject line, and never print the raw address if the platform supports link text.
QR codes deserve a straight answer: if the invitation is already digital, you do not need one. A QR code exists to move someone from paper to a screen, and your guest is already on the screen. Three places a QR code still earns its space: inside a PDF you are attaching, on a small batch of printed cards you are mailing to guests who prefer paper, and on signage at the venue itself. In all three, one line of label text is enough.
Say each of these once. Gift wording on an invitation goes wrong when it is repeated, hedged or explained. One sentence, no apology, no justification, and the registry lives on your wedding website rather than on the invitation face.
Photo wording is newer and most couples get the timing wrong. A line asking guests to add their photos belongs in two places: a short mention on the invitation so people know a shared album exists, and a real prompt the day after, when everyone still has 200 pictures on their phone and has not yet forgotten. A hashtag alone no longer collects anything usefully, because half your guests are not posting publicly.
On Lumhe, the last one is Digital Lifafa. You add your own payment ID, whether that is Venmo, Zelle, Cash App, PayPal or a bank transfer, and the guest sends money from whichever app they already use and uploads the receipt. It arrives wrapped in an occasion-themed digital envelope you open. Lumhe never touches the money. It is a direct transfer between your guest and you.
No, and the wording is what settles it. A guest reads the register before the medium: "request the honour of your presence" on a screen signals a formal wedding, and "come eat, come dance" signals a backyard one. Where digital does create real questions is around older relatives, a paper subset for a handful of guests, and hybrid sends where some people get a card and some get a link. We cover all of that separately in our guide to digital wedding invitation etiquette, including who still gets paper and how to run a hybrid send without two guest lists drifting apart. For the wording itself, the only rule is the one in the section above: include a phone number so nobody is stuck.
Send the photo prompt the day after, and the thank-you notes within about three weeks. The day-after message is the highest-yield message of the whole wedding, because guests are still on their phones, still sentimental, and have not yet cleared their camera roll. Wait a month and you get a fraction of the photos.
Thank-you wording follows one rule: name the specific thing. "Thank you for the gift" reads like a form letter. "Thank you for the cast-iron pan, which has already made three dinners" does not. Send a different note to guests who could not come, because they usually sent something and heard nothing back.
Photos are the part of a wedding that usually scatters. Some land in a group chat that scrolls away, some in a Story that expires in a day, some on a hashtag half your guests never used. Lumhe's Moments is a shared photo timeline attached to the event itself: guests upload, everything collects in one organised place, and it does not expire or close after the wedding. If you want to compare the options first, we reviewed the best wedding photo sharing apps.
Put it in two places: one labeled line in the body, and one button near the RSVP. Label it by what is behind it, such as "Travel and hotels" or "Weekend schedule", because a descriptive label gets tapped more than "our website". Keep it out of the subject line, and do not repeat the URL a third time.
Drop the word "online" and name the action instead. "Tap RSVP below by May 1" tells the guest what to do and when, which is all the sentence needs to carry. Then add the line most invitations forget: replying to the email does not count toward your headcount.
List each function as its own block with a day, a time, a venue and a dress code, then add one scope line above them: "below are the events you are invited to, please reply to each one". Do not label functions as main or secondary, and do not send three separate invitations. One invitation with per-function blocks means guests see the whole weekend in one place and reply once.
Ask for a yes or no per function and say why the numbers are separate: different caterers need counts at different times. If deadlines differ, list them by function rather than burying two dates in a paragraph. This only works cleanly on a platform where each function has its own guest list and its own RSVP, otherwise you are reconciling replies by hand.
Between 15 and 30 seconds, with the date spoken out loud and shown on screen. Under 15 seconds you cannot fit the date and the ask. Past 30 seconds, viewers drop off before the information arrives. Put the street address in the accompanying message rather than the video, because nobody can rewind a phone video to catch an address.
No. A QR code bridges paper to a screen, and a digital invitation is already on the screen, so the button does that job. Use one only in an attached PDF, on a small batch of printed cards for guests who prefer paper, or on signage at the venue, with a single line of label text such as "Scan to see the details and reply".
Yes. Formality lives in the language, not the paper. Spell out the date and time, write in the third person, use "request the honour of your presence" or "request the pleasure of your company", skip contractions and emoji, and keep the RSVP instruction plain. A black-tie wedding reads as black tie on a screen when the words carry the register.
Send it anyway with a line like "our website goes live in March at [url], bookmark it now". The save-the-date's only job is the date, and waiting for a finished website is how save-the-dates go out too late. Add a phone number for anyone who needs to ask about travel before the site exists.
Planning a wedding weekend? Upload the invitation you already made to Lumhe, whether that is an image, a video, a PDF or typed text, then find and connect with your guests by name, phone number or email inside Lumhe and send it to them directly. Add each function separately, so the rehearsal dinner and the reception have their own guest lists and their own RSVPs, and you always know the headcount for each one. After the wedding, everyone's photos collect in Moments, a shared timeline that does not expire. Guests who want to send money instead of a gift can do it through Digital Lifafa: you add your payment ID, they pay from whichever app they already use and upload the receipt, and it arrives wrapped in a digital envelope you open. Lumhe never touches the money. You can also share your invitation link on WhatsApp, iMessage, Instagram or any other platform. Explore Lumhe.
SEO keyword table
| Keyword | Type | Placement |
|---|---|---|
| digital wedding invitation wording | Primary | H1, intro, "What Changes When the Invitation Is Digital", FAQ |
| digital wedding invitation wording examples | Secondary | Intro, "Modern-Casual and Warm-Humorous Wording", example bank headings |
| how to word an online RSVP on a wedding invitation | Secondary | "How to Phrase Per-Function RSVP So Guests Only Reply to What They Are Invited To" and FAQ |
| where to put wedding website url on invitation | Secondary | "Website URL, QR Code and 'Do Not Reply to This Email' Lines" and FAQ |
| QR code wording wedding invitation | Secondary | "Website URL, QR Code and 'Do Not Reply to This Email' Lines" and FAQ |
| digital save the date wording | Secondary | "Digital Save-the-Date Wording" and FAQ |
| formal digital wedding invitation wording | Secondary | "Formal and Semi-Formal Digital Wedding Invitation Wording" and FAQ |
| casual wedding invitation wording templates | Secondary | "Modern-Casual and Warm-Humorous Wording" |
| multi-event wedding weekend invitation wording | Long-tail | "Multi-Event Wedding Weekend Wording: Welcome Party Through Farewell Brunch" |
| video wedding invitation script | Long-tail | "Video Invitations, Uploaded Cards, PDFs and Text Sends: Wording by Format" and FAQ |
Find and connect with guests by name, phone, or email. Manage multi-event schedules with individual RSVP headcounts for each ceremony or gathering, collect shared memories in permanent Moments timelines, and receive blessings through Digital Lifafa wrappers.
Explore Lumhe for FreeDesign a beautiful event invitation in seconds and share it with a link — free, no app needed.
You have a guest count and a card you like. You want one number. The reason you cannot find one is that the Paperless Post cost for a wedding is quoted three di
An online RSVP is a link that asks one question and stores the answer where you can count it. That is the whole idea. Everything else in this guide is about the
Here is what to do when wedding guests don't RSVP: work backwards from the earliest final-count date in your vendor contracts, set one guest-facing deadline at