A QR code for the wedding album, RSVP or registry

Paste the link you already have — album, form, schedule or registry — and print the code on the invitation, the table cards or the sign by the guest book.

A missing scheme is filled in as https://. Only http and https links are accepted.

Style

Dot color
Background color
Dot shape
Corner shape

Adding a logo below automatically raises this to High.

PNG, JPEG, or SVG up to 512 KB. The file is read in your browser and never uploaded. Error correction is raised to High so the code still scans.

Shown under the code in the preview and in both downloads. Keep it short — it prints small. The QR content is unchanged.

Your wedding QR code

What you can do with the code now

  • Static or dynamic?The code above is static — your address is baked into the squares. If that link ever changes, the only fix is a new print run.
  • Match your brandColors, dot shapes and a center logo: what still scans reliably on paper and what does not.

Something wrong?Report it— opens your mail app with the page path and browser details pre-filled. Nothing you typed into the generator is included.

  • In your browser
  • Never uploaded
  • No account

Before you print

  • Scan it first — open the exported PNG on your phone and check it reads before sending anything to a printer.
  • Keep the white margin — the quiet zone around the code is what a camera needs to lock on. Cropping it is the most common reason a printed code fails.
  • Dark on light reads best — inverted colors look stylish on screen but older phone cameras struggle with them on paper.

Print size at a glance

  • 2 cmSticker, business card, table tent
  • 4 cmFlyer, menu insert, small poster
  • 8 cmWall sign, door plate

A wedding code is a link in a nice dress. It encodes whatever URL you paste and nothing else — no guest list, no tracking, no photo hosting. That also means the album must already exist before you print: a code cannot create the destination.

One code per job, not one code for everything

Example album link

A demo photo-album URL encoded here, so you can see how a link of this length looks at print size before you commit to card stock.

The print budget is the real constraint

Wedding stationery is small. A place card is barely 9 cm wide, and by the time the designer has added a monogram, a name and a menu line there is often room for a code of 2 cm or less. That size works for a short link and fails for a long one: photo-album URLs from Google Photos, Dropbox and iCloud are among the longest links people encode, and a long link means a denser grid.

Two practical fixes. First, shorten the link before encoding — a short address cuts the module count sharply and makes a 2 cm code genuinely scannable. Second, put the dense codes on the items with room: the invitation, the welcome sign, the table card with a plain back side. Reserve the tiny place cards for the one short link you really need there.

Print at 300 dpi or supply the vector file. A code that looks crisp on a screen can be mushy in print — paper, ink spread and lamination all soften the edges. Laminated codes on outdoor signs are the usual casualty.

Design rules that keep it scannable

1

Contrast, not decoration

Dark modules on a light background. Pale gold on cream, white on sage, foil on metallic card stock — all of them look beautiful in a proof and scan badly. If the stationery palette is light, keep the code a deep ink colour.

2

Keep the quiet margin

Four empty modules on every side. Designers crop to the edge of the black squares because it looks tidier; scanners need that white ring to lock on. Put the code on a white panel if the card is coloured.

3

A logo is a tax, not a feature

A monogram in the middle of the code eats modules and forces a higher error-correction level. A small mark is survivable at 4 cm and above; at place-card size it is the fastest way to a code that half the guests cannot scan.

4

Test on paper, in the room

Scan the proof under the venue's actual lighting — dim reception halls and bright marquees are both hostile. Then photograph the printout and scan the photo, because that is how a guest at the back of the room will use it.

The link lives in the code and in your hands. Everything happens in your browser: paste a URL, get an image file. Nothing is uploaded, no guest data passes through us, and there is no dashboard to log into because there is no account.

Codes for the other wedding jobs

JobWhat to encodeBest placementWatch for
Photo sharingShared album linkTable cards, welcome sign"Anyone with the link" exposure
RSVPGoogle Form or registry RSVPInvitation, save-the-dateDeadline passing while codes stay printed
Gift registryRegistry store linkInvitation insertRegistry page retiring after the date
DirectionsVenue pinInvitation back, signagePin dropped at the wrong gate
ContactsvCard of the couple or plannerVendor card, thank-you notesPhone number going public

Sequenced well, these codes do something paper cannot: they turn the stationery into the entry point for the digital half of the wedding, and they keep working long after the day — the album code on a printed card is still scannable in five years, provided the album stays online.

Wedding QR code questions

What can a wedding QR code point to?

Any link you can paste: a shared photo album, an RSVP form, the ceremony schedule, a gift registry, the venue pin, or a playlist. One code per destination — a separate code for photos and for RSVP is clearer than one code that opens a hub page you had to build.

Where do guests actually scan it?

Three places do most of the work: the invitation or save-the-date (for RSVP and the registry), a table card at each place setting (for photos), and one large sign near the entrance or guest book (for everything in one place). Codes on seating cards get scanned; codes buried in a printed programme usually do not.

Will a code printed on a dark card still scan?

Only if the modules stay dark and the background light. A white-on-black "aesthetic" code fails on many scanners. If the card must be dark, print the code on a white or cream panel inside it, and keep the quiet margin — a code cropped tight by the designer is the most common wedding-print failure.

Do older guests know how to scan it?

Not always, and that is a design problem rather than a code problem. Put one short line of instructions next to the code ("Open your camera, point it here") and make sure the album or RSVP page has a plain typed URL as a fallback. A code with no alternative excludes the people most likely to print the album.

Can I change the album link after the invitations are printed?

The code is static: whatever link is inside it stays inside it. Print after you have the real album URL in hand, or point the code at a short address you control (a redirect on your own domain) so the destination can be repointed later. Without that, a changed link means reprinted cards.

Do the photos people upload stay private?

That depends on the album service, not on the code. A shared Google Photos album or Dropbox folder link is "anyone with the link", which is effectively public once it is printed on 120 cards. If privacy matters, use a service with a passcode and print the passcode separately or on the sign only.

Other codes

Same generator, different target.

Wedding page: the code this page produces

Wedding page — example code produced by this pageStatic QR code, error correction level M, 29 by 29 modules. Generated in your browser.
Link to a wedding site — drawn by this site's own encoder from the payload below, at build time. It is not a stock image and no QR service is contacted.

What it encodes: https://mywifiqr.com/qr-code-for-wedding/

Point a phone camera at it to confirm it opens. Change the fields in the generator above and the result changes with them — the code shown here is only a sample.