The humble QR code has quietly solved one of the oldest problems in multilingual worship: how do you get translation to a room full of people without handing out a hundred devices? The answer turns out to be the device everyone already carries, and a square of black and white on a card.
It sounds trivial. In practice the details of how you print it and where you put it decide whether half your visitors ever use it.
What the attendee experiences
A visitor sees a small sign — on the wall, in the bulletin, on the screen. They point their phone camera at it, tap the link that appears, and choose a language from a list. Within a second or two of the speaker talking, subtitles start scrolling in their language.
No app to download. No account to create. Nothing to hand back at the end, and nothing to explain to anyone. The whole transaction takes about fifteen seconds and involves speaking to nobody, which for a nervous visitor is the most important feature on this page.
Why this beats the old way
- No hardware to buy, charge, clean, count or lose. Receiver sets cost money up front and money every year in batteries, repairs and replacements for the ones that go home in a coat pocket.
- No sign-up friction. The moment you ask a visitor to install an app, most of them stop — and the ones who do not stop are still standing in your foyer waiting for a download over a poor connection.
- It scales to any size. Ten people or a thousand, the same code works. There is no box of receivers that runs out at Christmas, which is precisely the service where you would run out.
- It costs nothing to add a language. The code does not change when the list behind it does.
Printing it properly
This is where most churches get it wrong, and the failure is invisible: people simply do not scan, and nobody reports why.
- Size it for the distance. A reliable rule of thumb is that the code should be about a tenth of the distance it will be scanned from. Read from three metres away, that is a code roughly thirty centimetres across — much bigger than the postcard most churches print.
- Dark on light, always. Inverted codes — light on dark — fail on many phones. So do codes printed over a photograph.
- Leave the white border. The quiet margin around the outside is part of the code, not decoration. Trimming it to fit a design is a common and fatal edit.
- Matt, not gloss. A glossy laminate under church lighting reflects straight back into the camera.
- Print the address underneath as text. Some people cannot scan, will not scan, or do not know they can. A short web address they can type is a free fallback.
Where to put it
Put it where eyes already land, and put it in more than one place.
- A permanent sign by the door, framed, at eye level. This covers every week's visitor without anyone remembering to do anything.
- On the order of service or the weekly notices, which is where people look while they are sitting and waiting — the ideal moment.
- On a slide before the talk, but never only there.
- In the side rooms: the parents' room, the overflow hall, the foyer.
The single most common mistake is putting the code only on the welcome slide. That slide is replaced by song lyrics four minutes into the service and never returns, which locks out precisely the anxious latecomer who most needed it.
Because it does not change, you can frame it
A code that stays the same week to week can be printed once, framed, and forgotten. This is a genuine advantage over systems that generate a new link each session: nobody has to remember to update anything, and a member can point a visitor at the sign without knowing how any of it works.
Say something out loud, once
A sign alone gets perhaps half the people who would use it. One sentence from the front doubles that.
Keep the wording neutral. "If you'd rather follow in another language, there's a code on your notice sheet" is an offer anyone can take. "For those who don't speak English well" identifies people and will be ignored by exactly the people it names.
It works for hearing, too
The same code that serves other-language visitors serves people who are deaf or hard of hearing — they read the captions in the main language. In a building with poor acoustics it also serves anyone at the back who simply cannot make out the preacher.
One small sign quietly makes your service more accessible in three ways at once, and only one of them is about language.
Test it like a stranger
Before you rely on it, do this once: hand a phone to somebody who has never used it, from the seat furthest from the sign, and say nothing. Watch how long it takes and where they hesitate.
You will usually learn one of three things — the code is too small, the sign is in the wrong place, or the guest Wi-Fi is asking them to sign in first. All three are fixable in a week, and none of them would have been reported by a visitor.
Try it at your next service
InMyTongue gives each church a code that does not change, streaming live subtitles and spoken translation to every attendee's phone in the language they choose, straight from a browser with nothing to install — and the panel will print you a proper A4 sign. New accounts include free credit. See how it works.