How to Stop Uninvited Guests From Crashing Your Wedding

Uninvited guests at a wedding get in because most weddings have no way to tell an invited face from an uninvited one once the door is open. The fix isn't stricter invitations — a forwarded link or a passed-along card is normal, not a leak. The fix is a checkpoint: every accepted guest gets a pass, and only a scanned pass gets someone through the door.

Last updated: August 2026

That distinction matters more than it sounds. Most advice about wedding gatecrashers focuses on locking down the invitation itself — fewer people to send it to, warnings not to forward it, RSVPs chased by phone. All of that fights the wrong battle. An invitation is supposed to travel; that's how a family actually spreads word of a wedding. The place to draw the line is the door, and the tool for drawing it is a pass that only works once.

How do I stop uninvited guests at my wedding?

1. Stop treating the invitation link as the security boundary. It isn't, and trying to make it one just makes the invitation harder to share with people who were actually invited. Let it spread freely inside the family.
2. Turn on RSVP so every guest is identified before the day. An invitation with online RSVP means you know, by name, who said yes — not a rough headcount from a phone call two weeks out.
3. Issue a QR entry pass to every guest who accepts. Each accepted RSVP gets its own pass, tied to that guest, sent back to them automatically. Nobody has to ask for one.
4. Put someone at the door with a scanner, not a clipboard. A phone that scans passes is faster than checking names against a printed list, and it doesn't rely on anyone recognizing faces at a wedding with three hundred guests.
5. Let the scanner do the judgment call. A valid pass scans clean. A pass that's already been used shows exactly that — used, and when. A guest with no pass at all shows up as no pass. None of that requires anyone at the door to decide who "looks" like they belong.
6. Handle the no-pass guest quietly, off to the side. Have one answer ready (below) and use it the same way every time, so it never turns into a public confrontation.

Is a forwarded invitation link a security problem?

No — a forwarded link is the invitation working as intended, not a leak to plug. Families don't invite people through a single controlled channel; someone sends the link to their group chat, someone else forwards it to a cousin, and that's exactly how word of a wedding is meant to travel. Trying to stop it — one-time links, warnings not to share, tracking who forwarded what — fights the way invitations actually get used, and it doesn't solve the real problem anyway: anyone with a paper card can hand it to someone else too.

What actually controls the door is that opening the link, or even RSVPing through it, doesn't get anyone in. Only a scanned, unused entry pass does. A friend can forward the invitation to fifty people; all fifty can read it, see the schedule, admire the design. None of that puts a body through the door. That happens once, at check-in, when a specific pass gets scanned — and a wedding invitation card with QR entry passes is built around exactly that separation: the link is for sharing, the pass is for admitting.

How does a QR pass actually stop someone at the door?

A pass admits exactly once. Every guest who RSVPs "yes" is issued their own QR pass, and that pass is checked against every previous scan at the door. Scan it the first time and the guest walks in. Scan it a second time — because someone screenshotted it and sent it to a friend, or because the guest genuinely lost track and scanned twice by accident — and the scanner shows it was already used, and when. It doesn't quietly let the second person through; it flags the duplicate on the spot, before anyone's past the door.

That's the entire mechanism, and it's also why the invitation link itself doesn't need to be locked down. The link gets someone to the RSVP. RSVPing gets them a pass. The pass, once used, is spent — a screenshot of it doesn't create a second working copy, it just creates a copy of something that will fail the second time it's scanned. The couple never has to guess who forwarded what; the scanner already knows.

Passes are issued the moment a guest RSVPs, and the first fifty are included in the one-time publish. A longer guest list adds passes by the hundred rather than per head, so the cost tracks the size of the door, not the size of the group chat the invitation ended up in.

What do I say to someone who arrives without a pass?

Say it's a quick check, not an accusation — "let me just find you on the list" works, said the same way to everyone, invited or not. Nobody wants to be the person turning a relative away in front of a hall full of guests, and that fear is usually why the whole "checking guests" idea gets dropped before the wedding. The answer is to make the check itself unremarkable: the person at the door isn't deciding who belongs, they're scanning a code, the same as they would for the person in front of them and the person behind. When someone doesn't have one, they get pulled aside calmly while someone finds them on the RSVP list or checks with a parent — not turned around at the threshold in front of everyone.

Frequently asked questions

Is it rude to check guests in at the door?

No, not when it's done quietly and applied to everyone the same way. A scan takes a second and looks the same for a first cousin as it does for a stranger — nobody feels singled out, because nobody is. What reads as rude is a visible argument at the entrance, which is exactly what a quiet, consistent check-in process is designed to avoid.

What do I say to someone who arrives without a pass?

Keep it light and procedural: "let me just double-check the list," then step them aside rather than blocking the doorway. Most of the time it resolves in under a minute — they RSVPed under a different name, or a parent brought them as a plus-one nobody logged. Reserve any harder conversation for after they're off to the side, away from other arriving guests.

Can a guest forward their invitation to someone else?

Yes, and that's fine — forwarding the invitation link doesn't get anyone into the venue. It only lets someone see the invitation and, if they RSVP, receive their own pass. The door only opens for a scanned, unused pass, so passing the link around never bypasses check-in.

Does everyone need to be checked in?

For it to actually stop uninvited guests, yes — a door that scans some guests and waves others through has a hole in exactly the place people will find it. The scan itself is fast enough that it doesn't slow arrivals down noticeably; it's a tap, not a conversation, for the guests who have a pass.

Keep the invitation open and the door closed

A wedding invitation is meant to travel through a family; a wedding entrance isn't. Building the control into the door instead of the link means the RSVP stays welcoming, the link stays shareable, and the guest list that actually walks through is the one that actually said yes. Design your wedding invitation card with online RSVP and a QR entry pass for every guest, and hand the door someone can check without a single awkward conversation.

Once the door is covered, the rest of the guest-list work gets easier: see how to get an accurate wedding headcount for tightening RSVPs before the day, how to cut down your wedding guest list if the list itself needs trimming first, and wedding guest entry passes and QR check-in for how the passes and scanner work end to end.