I run creative for a church with campuses in four towns, and I've printed a lot of QR codes that nobody used. Some of that was the code. Most of it was where it went and what it asked for.
Here's what I've learned, sorted by whether it's worth your time.
The ones that work
Giving
This is the single highest-value code in a church building, and it belongs in the seat back or on the pew, not only in the bulletin. Someone deciding to give in the middle of a service is not going to hunt for a folded paper.
Make it dynamic. Giving platforms get switched, links change format after a platform update, and the last thing you want is a permanent sign pointing at a dead form. A dynamic code lets you repoint it without touching the printed piece, and it tells you whether anyone actually scans it.
Add a caption. "Give" alone is worse than "Scan to give." People need to know a scan is what's being asked.
Connect cards and first-time guest forms
A digital connect card gets more completions than a paper one, mostly because nobody has to find a pen or hand anything to a stranger.
Put the code in three places: the seat back, the guest table, and the last slide of announcements. Different people notice different surfaces.
Keep the destination form short. Name, contact, one checkbox. Every additional field is a drop in completion rate, and asking a first-time guest for their address on a phone in a crowded room is asking a lot.
Event registration
Codes on event promo actually convert, because the ask and the action are in the same moment. Somebody sees the retreat graphic, they're interested right now, and typing a URL is enough friction to lose them.
These can be static if the flyer is disposable. If the code goes on a banner you'll reuse for next year's retreat, dynamic, and repoint it annually.
Guest WiFi
Especially in student ministry spaces and lobbies. A WiFi QR code removes the "what's the password" conversation entirely. It has to be static because the credentials live in the pattern, so use a guest network with a password you don't rotate, on a segment that reaches nothing important.
Sermon notes and series pages
Works, but only if you're consistent. If notes are behind a code every week, people learn to look for it. If it's there half the time, nobody bothers.
The ones that mostly don't
The bulletin code that points at your homepage. No ask, no reason. A code needs a specific destination and a specific verb. "Scan for this week's schedule" works. A naked code next to your logo does not.
Six codes on one page. People scan zero. Decision fatigue is real and a page full of codes reads as visual noise. One code per printed piece, two if they're clearly separated and clearly labeled.
Codes on the screen during worship. Contentious, and I'll say what I actually think: they work poorly. The lights are down, people don't have phones out, the slide is up for eleven seconds, and half the room is too far back for the code to resolve. If you do it, put it up for a full minute minimum and size it for the back row, which by the ten-to-one rule means enormous.
Codes on vehicle magnets and trailer wraps. Nobody is scanning a moving van. Put a short, memorable URL there instead.
Anything requiring an app download after the scan. The scan is one step of goodwill. Spending it to get to an App Store page burns the whole thing.
The three reasons church codes fail
They're too small. Bulletin layouts are cramped and codes get shrunk to fit. A code someone scans from a lap, roughly 12 to 18 inches, needs to be about 1.2 to 1.8 inches wide. Most bulletin codes I see are under an inch.
They point at something that moved. Static codes on permanent signage, printed once and forgotten, and the giving platform changed URL structure in a software update eighteen months later. This is why the permanent ones should be dynamic.
There's no reason to scan. The code is there but the copy doesn't say what happens. Add a verb and an outcome: "Scan to give," "Scan to register," "Scan to join the guest WiFi."
A setup that works for a multi-site church
If you run more than one campus, generate a separate dynamic code per campus for the same purpose. Same giving form, different code per location.
You lose nothing and you gain the ability to see which campus is actually using it. When one location shows almost no scans on the giving code, that's usually a placement problem you can fix in an afternoon, not a spiritual crisis.
For the printing itself, batch generation matters more than it sounds like it should. Twenty seat-back cards across four campuses is eighty pieces, and doing them one at a time is a lost morning. Paste a list, get a print-ready sheet with trim lines and captions, send it to the printer.
Design notes for church print
Brand colors are fine as long as the code's foreground stays genuinely dark. A deep navy or forest green on white scans. A warm tan on cream does not, and I've watched a beautiful bulletin come back from the printer completely unscannable for exactly that reason.
Put your mark in the center if you want it, under 20 percent of the width, with a light plate behind it. Then let the verification step confirm it still reads at small sizes before you commit to a print run.
Export SVG for anything going to a commercial printer. PNG for slides and social.
What to actually track
If your permanent codes are dynamic, look at scans per weekend rather than the raw total. The useful comparisons are between placements and over time.
You're not going to learn who scanned, and you shouldn't want to. But you will learn whether the lobby table beats the seat back, and whether announcing the code from stage moves the number. Both of those are worth knowing.
FAQ
Should church giving QR codes be static or dynamic? Dynamic. Giving platform URLs change and the printed piece is usually permanent. A static code there is a slow-motion dead link.
How much do dynamic codes cost? Starter is $9.99 a month for up to 25 dynamic codes, which covers most single-site churches comfortably. Unlimited is $19.99 a month for multi-site setups. Both include a week free. Static codes are free and unlimited if you don't need editing or tracking.
Where should the giving code go? Seat backs or pews first, guest table second, bulletin third. Give people a code where they already are when they decide.
Can I put our logo in the code? Yes, keep it under 20 percent of the code's width with a light plate behind it, and confirm it still scans small before printing.
How big should a bulletin QR code be? At least 1.2 inches wide. Most are printed too small.
Build your codes at gmqr.dev. Static codes are free forever, no account needed.