Welcome sign
The default. Beside the entrance, at eye level, with a line of instruction next to it.
Feature
QR Code Seating Chart
A QR code seating chart puts one small sign at the door instead of a board everybody has to queue for. A guest scans it, types their name, and sees their table.
The part that matters is not the scanning. It is that the code points at the plan rather than containing it, so moving a guest the night before costs nothing.
Last updated
Scan this one. It is real.
It opens the demo guest page for a sample event: a search box, a name, a table. That is the whole experience a guest has, and it is the same page a real event publishes.
No phone to hand? Open the same page in this tab.
How it works
Four steps, and only the first takes any real time.
01Build the seating plan
Draw the room, load the guest list, assign tables. The free seating chart maker does this with no account.
02Publish the guest page
Saving to a free account produces a public page for the event. Your first event publishes free through 250 guests.
03Download and print the code
Pick a color that suits the event, keeping real contrast against its background, and download the image at print resolution.
04Place it where people pause
Beside the entrance, on the welcome table, or on the back of the order of service. Anywhere an arriving guest already stops.
What guests see
The event name and a search box. They type two or three letters, and the page shows their table, their seat where you have assigned one, and who else is at their table if you have chosen to show it.
No app, no account, no password. The phone camera opens it, and the page is built for one hand in a queue rather than for a laptop.
What they do not see is anybody else's assignment. It is a name search that returns one result, not a browsable directory of everyone attending, and that is worth saying plainly to hosts who worry about it.
Printing and placement options
A QR code fails for boring reasons: too small, too low contrast, or somewhere nobody looks. All three are avoidable.
Size it for the reading distance. A code read from arm's length wants to be at least 1.2 inches square; one read from six feet away on an easel wants to be four inches or more. When in doubt, print it larger - there is no aesthetic penalty that outweighs a code that will not scan.
Keep a dark code on a light plain background, and leave a clear margin of at least four modules around it. Gold on ivory looks beautiful and scans badly. Test the actual printed piece, not the file, with both an iPhone and an Android phone before the print run goes out.
Beside the printed chart
The board handles the photographs, the code handles the queue behind it.
On the order of service
Guests already hold it. Costs nothing to add and reaches everyone.
On the escort card table
For anyone whose card has been picked up by mistake, which happens at every wedding.
Put a line of text beside the code saying what it does. "Scan to find your table" converts far better than a bare code, which people assume is a wifi password.
Updating seats after printing
This is the actual argument for a QR code, and it is worth stating on its own.
A printed seating board contains the plan. When the plan changes, the board is wrong, and your options are a reprint, a visible correction, or a member of staff standing beside it explaining.
A QR code points at the plan. When the plan changes, the code is still correct, because it never held the answer in the first place. Move a guest at 4pm and the sign printed three weeks ago shows the new table on the next scan.
For a wedding, where something changes in the final week at nearly every one, that difference is worth more than any feature on the page.
When a guest has no phone
Some guests will not scan the code. Older guests without a smartphone, guests whose battery has died, guests standing in a spot with no signal, and guests who simply do not want to.
Plan for them rather than hoping. Keep one printed guest list at the door with tables on it, and have someone able to look a name up. That is a single sheet of paper and it removes the entire failure mode.
This is also why we suggest the code beside a printed display rather than instead of one at most weddings. The code is the fast path, not the only path. The door team workflow is on event check-in app.
Try it free
Build a plan in the free seating chart maker, publish it, and scan your own code before you commit to anything. Your first event publishes free through 250 guests, and building costs nothing regardless.
There is also a live demo with a working guest page if you would rather see the guest side before building anything.
Frequently asked questions
Do guests need an app to scan the code?
No. Every current iPhone and Android camera reads QR codes without any app, and the page it opens works in the browser the phone already has. There is no guest account and nothing to install.
Can I change seats after the QR code is printed?
Yes, and this is the main reason to use one. The code points at the event rather than at a fixed chart, so moving a guest updates what the same printed sign shows on the next scan.
How big should the QR code be?
At least 1.2 inches square for arm's length, and four inches or more for a sign read from several feet away. Leave a clear margin around it and keep it dark on a light plain background.
Can the code match my wedding colors?
Yes, within reason. There is a color picker, and the constraint is contrast rather than taste: a dark code on a light background scans reliably, and a low-contrast pairing like gold on ivory often does not. Always test the printed piece.
Will guests see the whole guest list?
No. The page is a name search that returns one result, not a browsable list of attendees.
What about guests without a smartphone?
Keep one printed guest list at the door and have someone able to look up a name. The code is the fast path for the majority, not a replacement for a human being.
Continue from here
Print one small sign instead of a board.
And keep the right to change your mind about the seating afterwards.
Build your chart freeNo account needed to buildFirst event free through 250Paid events refundable until 7 days after the day