QR codes for church translation: where to place them, how big to print, how to test
Put translation QR codes where guests already look, print them big enough to scan from real seats, add a typed fallback link, and know when worn or outdated codes need replacing.

Where should a church put translation QR codes?
A church should put translation QR codes where guests look before the service starts: on the screen during the walk-in, at each entrance, on seat backs or pew cards, and in the bulletin. Print each code large enough to scan from where people will actually stand or sit, add a short typed link under it, and test every placement with several phones before Sunday.
Making the code is the easy part, because SermonLingo provides a printable QR code and a shareable listener link that opens in the phone's browser, with no church translation app to install. The hard part is the last few feet between a guest and the code. A code nobody notices, or one that only scans from a few inches away, might as well not exist.
Which placements work best, and for whom?
| Placement | Who it reaches | Tips |
|---|---|---|
| Main screen before the service | Everyone already seated | SermonLingo's stage display (Standard plan and above) opens on a welcome slide with a large QR code; keep it up through the walk-in |
| Entrance signs | Guests arriving, especially first-timers | At eye level beside a greeter, with the language names written in each language |
| Seat-back or pew cards | Latecomers and anyone who missed the screen | One card every two or three seats, on matte card so stage lights don't glare |
| Printed bulletin | People who read the bulletin before the service | A smaller code is fine here because it's held in the hand |
| Welcome desk | Guests who ask for help | A greeter can scan alongside the guest and show the language picker |
| Website and emails | People planning ahead | Share the link instead, since a code is awkward to scan on the phone you're reading it on |
Use at least two placements. The screen catches most people at once, while cards and signs catch everyone who arrives late, sits behind a pillar or simply wasn't looking. For everything beyond print, see our listener link best practices.
How big should a translation QR code be?
A practical starting point is to make the code about one tenth as wide as the distance it will be scanned from. Then test it, because phone cameras, lighting and print quality all vary.
| Where it's scanned | Typical distance | Starting code width |
|---|---|---|
| Bulletin or handout | In the hand, about 25 cm (10 in) | 2.5 cm (1 in) or larger |
| Seat-back or pew card | Arm's length, about 50 cm (20 in) | 5 cm (2 in) |
| Entrance sign | About 1.5 m (5 ft), walking past | 15 cm (6 in) |
| Lobby poster | About 3 m (10 ft) across the room | 30 cm (12 in) |
| Projected welcome slide | The back row | As large as the design allows; test it from the furthest seat |
Size isn't the only thing that stops a scan. Check these before every print run:
- Contrast: print a dark code on a white or very pale background. Some phone cameras struggle with light-on-dark (inverted) codes and with low-contrast brand colors.
- Quiet zone: leave a clear margin around the code at least four of its small squares wide. Text or borders that crowd the code can stop it scanning.
- Finish: use matte paper or matte lamination, because gloss reflects stage lights straight into the camera.
- Logos: if a designer puts a logo in the middle, test it on several phones. QR codes tolerate some damage, but a large logo uses up most of that tolerance.
- Source file: resize in proportion and print from the original high-resolution or vector file, never from a screenshot.
How do you test scanning from real seats?
Test on a weekday with the room set up as it will be on Sunday, then again at your final walk-through. Bring at least three phones: a recent iPhone, an Android phone and the oldest phone you can borrow, because some guests will carry one.
- Use each phone's built-in camera app rather than a scanner app, since that is what guests will reach for.
- Scan the projected code from the back row, the far side seats and any balcony, with the lights as they will be during the walk-in.
- Scan a seat card from the seat behind it, and an entrance sign while walking past at a normal pace.
- Time it. Going from raised phone to language picker should take a few seconds; if people have to step closer or try twice, the code is too small or too glossy.
- Check the destination. It must open your listener page for the right service, not last month's special event.
- Try both church Wi-Fi and mobile data, especially in corners of the room where signal is weak.
Write the results down with the date. When someone asks next year why the cards are that size, you'll have the answer.
What does a guest see after scanning?
Scanning opens the SermonLingo listener page in the phone's browser, with no app to install and no account to create. The guest picks a language, can make the text bigger or smaller, and can change language at any point. Once the service is live, captions appear a phrase at a time, normally a second or two after the words are spoken. Right-to-left languages such as Arabic, Persian, Hebrew and Urdu display right to left.
In 13 languages guests can also turn on a natural AI voice and listen through earphones; the voice comes with the Standard plan and above. It is labeled as AI, it doesn't clone the preacher's voice, and captions stay on screen while it plays. Guests can switch the audio off whenever they like.
Walk your greeters through the listener page before Sunday using the scripted demo service, so they can show a guest exactly where to tap.
What should the sign or seat card say?
A bare QR code asks guests to trust a mystery. A few words around it tell them what they'll get. This layout works for seat cards and signs:
- Headline: "Live translation" in your main language, with the same phrase underneath in each listener language, written by a fluent speaker.
- Language names in their own scripts: Español, Português, 한국어, Tiếng Việt, العربية. People look for the name of their own language, not an English word.
- Three steps: Open your camera. Scan the code. Choose your language.
- Reassurance: No app needed, and nothing to pay.
- Fallback link: the short link in large, clear type.
- Optional extras: the Wi-Fi network name if guests should use it, and "Bring earphones to listen" if your plan includes the AI voice.
A card supports a welcome; it doesn't replace one. For a fuller routine for first-time guests, see newcomer orientation translation.
Why every code needs a short fallback link
Some phones won't scan: an old camera, a cracked lens, a QR setting that's switched off, or a guest who would simply rather type. Print a short link under every code and read it aloud during the welcome.
The most durable option is an address on your own church domain, such as yourchurch.org/translate, that redirects to the SermonLingo listener link. You control where it points. If the listener link ever changes (a special event, a different room), you update the redirect once and every card and sign keeps working. Put that same redirect address inside your QR codes too, not only in the typed link.
Be wary of free link shorteners for printed material. Some show ads before redirecting or stop working when an account lapses, and Easter morning is a bad time to find out. Whatever you use, test it from a phone after every change.
When should you refresh printed codes?
- When the destination changes. If a code points straight at a listener link and you start using a different link, reprint, or move the code onto your own redirect so it doesn't happen again.
- When you add or drop a language. The card's language list should match what guests will actually find.
- When cards get tired. Bent corners, coffee rings and sun-faded ink all make scanning slower.
- Before big Sundays. Easter, Christmas and special events bring the most first-time guests, so put fresh cards out the week before.
- On a schedule. Once a quarter, scan a sample of cards and signs and check they still lead to the right place.
Put a tiny version date in the corner of each design (for example, "v. Oct 2026") so volunteers can tell old cards from new ones at a glance. When you retire a code, collect every copy: an old card left in a hymnal rack can send guests to the wrong page for years. If you also show the code on screen, the projector captions guide covers the welcome slide and screen layout.
Questions
Can one QR code work for every Sunday service?
One translation QR code can serve every Sunday if the link behind it stays the same. Before printing in bulk, scan last week's code to confirm it still opens your listener page. Encoding a redirect on your own church website, such as yourchurch.org/translate, lets you keep one printed code even if the listener link changes later.
What should a greeter do when a guest's phone won't scan the QR code?
When a guest's phone won't scan the translation QR code, a greeter can type the short fallback link into the guest's browser, or open it on their own phone to show what to expect. On some Android phones, QR scanning is a camera setting or a Google Lens feature that needs switching on, which a greeter can help with.
Is it better to show the translation QR code on screen or in print?
Showing the translation QR code on screen and printing it work best together. The screen reaches everyone already seated before the service, while seat cards and entrance signs catch latecomers and anyone who missed the screen. A code in the printed bulletin adds a third chance for guests who read it before the service begins.
Do guests need church Wi-Fi to use a translation QR code?
Guests need an internet connection after scanning a translation QR code, either the church Wi-Fi or their own mobile data. If mobile signal is weak inside your building, print the Wi-Fi network name next to the code, and test both connections from the corners of the room during your scan test.






