
Halloween QR code ideas
A spooky playlist, a clue trail, a costume vote and a pumpkin patch map, and dark designs that still scan at night.
Guides
How to make QR codes that work in the real world: what goes inside them, how big to print them, which colours scan, and when a code you can edit later is worth paying for. Useful whichever generator you use.
Codes for Halloween and the Christmas markets, with sizes and designs that work outdoors and after dark.

A spooky playlist, a clue trail, a costume vote and a pumpkin patch map, and dark designs that still scan at night.

Payment links, your shop page, a WhatsApp code for orders, stall sign sizes, and signs that survive cold and glare.
The format, the size and the colours: what decides whether a code scans.

The exact WIFI: format, WPA, WEP and open networks, hidden networks, and what to do when the password changes.

Minimum sizes, the distance ÷ 10 rule, the quiet zone and error correction, with a table of real codes.

Contrast ratios with real examples, inverted codes, gradients, logos and what printing does to colour.

The shortest working address, https and the final URL, UTM tags without bloat, and why static is enough on your own domain.

Error correction H, how big the logo can be, what it must never cover, a plate behind it, and testing the smallest size.

Where to host the file, keeping its address when you update it, a phone-friendly PDF, and when a web page is better.

Minimum label sizes, how far a code can wrap round a jar, links that outlive the print run, and ink on kraft or clear labels.
Which kind of code to buy, if any, how to change an Editable code, and how to use one for a menu or a wedding.

What each kind is, when you need a dynamic code, what it costs and what happens when you stop paying.

Where your manage link is, changing the destination step by step, testing it, and what happens if the year lapses.

Where to host the menu, web page or PDF, table tent sizes, accessibility and the printed backup.

RSVP links, save-the-date calendar codes, the venue pin, a shared album, signs, and testing on guests’ phones.

Why static codes can’t expire, how links inside them die, when dynamic codes stop, and how to tell which you have.

How ticket codes are checked at the door, what a static code can’t do, and the codes that do help around an event.
Reviews, Instagram, maps, texts, emails and calendar events: what each code holds and how to make it work.

Where to find the review link, where to put the code, Google’s rules on asking, and a test that it opens the review box.

The profile link vs Instagram’s own code, what people without the app see, and sizes for packaging and cards.

geo: coordinates or a map link, which phones open what, exact coordinates, and why to pin the entrance.

The SMSTO: format, message length, keyword opt-ins, phone and carrier differences, and consent wording.

The mailto: format with a subject and body, when it beats a form, density, and phones with no mail app.

What the VEVENT holds, iPhone and Android, floating local time, all-day events, density, and when to link instead.
Ready-made pages: WhatsApp codes Contact cards Property signs Guesthouse Wi‑Fi cards
How people scan a code, and how to check yours works before you print a batch.

The camera on iPhone and Android, Google Lens, codes in screenshots, what to try when nothing happens, and safe tapping.

A ten-minute checklist, a table of common failures and their causes, and when to test again after a reprint.
Free codes are made in your browser, with no sign-up, on any of 25 3D islands.