Ideas & unconventional uses
QR in museums and exhibitions: not a link to an article
A bad museum QR sends the visitor to a page they could have found at home. A good one shows what the glass case cannot: how the object sounded, how heavy it was in the hand, what stood on this exact spot a century ago.
The visitor is standing, not browsing
That single fact decides almost everything. Someone in a gallery is on their feet, holding the phone in one hand, in lighting that was designed for the objects rather than for screens, and they have given the code about fifteen seconds of patience. There are no headphones and usually no wish to put any on.
So the format is short or it is nothing. A page that has to load a video, accept cookies, ask for a login or be scrolled to the interesting part is a page that will be closed. What survives that posture is a single paragraph, a single image, or a single sound.
What belongs behind the code
The test is simple: does the code show something the visitor cannot see by standing where they are already standing? If the answer is no, the code is decoration.
If you can only do one of those, do the sound. Audio is the only medium that lets a visitor keep looking at the object while they receive the information, which is the whole point of standing in front of it.
One code per object, not one per room
A single code for a whole hall is cheaper to produce and worse in every other way. You cannot tell which object people were standing in front of, you cannot change one story without reprinting the room, and a visitor who scans it gets a list to choose from at the exact moment they wanted a single answer.
A code per object fixes all three. It gives you a ranking of what people actually approach — which is the most useful planning document for the next exhibition, and it is written by visitors rather than by the curator’s memory of which piece is best.
Keep a small number of separate codes for the room itself: the floor plan at the entrance, the way out, and the full catalogue near the exit. Those are three jobs, not twenty.
The label is half the work
When a museum code does not work, the problem is almost always in the printing, not in the code. The three usual causes are worth naming, because each one is a printing decision rather than a content decision.
Stuck on the glass
The case reflects every ceiling light in the room. The code photographs beautifully and scans badly. Put it on the plinth face or the caption board, on matte stock, never on the glazing.
Down at knee height
Nobody crouches to scan. The code belongs at the same height as the label text that people are already reading, and tilted slightly towards them if the surface allows.
Inside the caption block
Bottom corner of the printed label, same size as the object number, with the sentence “scan for the sound of this instrument” beside it. This is the version that gets used.
Thick walls, no signal
Stone halls, basements and converted industrial buildings routinely have no usable mobile signal, and the visitor is standing in front of the object getting nothing at all. This is the most common complaint about museum codes and the least often designed for.
Three things help. Keep the destination page tiny — text and one audio file, no video, no web fonts, no tracking scripts that block rendering. Say on the label that the audio is small enough to work on a weak connection. And if the hall has Wi-Fi, put a separate code for the network next to the entrance, because a visitor who cannot connect will not try a second code afterwards.
If neither works, the honest answer is a device: a small player or a tablet fixed to the wall, with the code as an alternative rather than the only route.
Audio people will actually use
Never autoplay. A sound that starts by itself in a quiet gallery is a sound that gets muted in a hurry, and the visitor has lost the moment. One large play button, nothing else competing with it.
Put the transcript directly below the player. It serves visitors who are deaf or hard of hearing, visitors who forgot headphones, and visitors in a room where sound is inappropriate — and it costs one extra block of text. The same transcript is what search engines will index, which is a useful side effect rather than the reason to do it.
Record in the room if you can. The faint echo of the actual hall does more for a sense of place than a cleaner recording made in a studio.
One question instead of a paragraph
The strongest museum codes end with something to look for rather than something to know. “Did you notice the repair near the handle?” sends the visitor back to the object with a task. A paragraph of provenance sends them to the next case.
This also tells you whether the code worked. If the question is specific, people come back and look; if it is vague, they read and move on. The difference is visible in how long they stay in front of the same object.
Accessibility is not a separate page
Large text by default, not after a settings toggle. Contrast that survives the dim lighting of a gallery. Alt text on every image, because the image is often the entire content. Tap targets that are comfortable for someone holding a phone in one hand.
The harder rule: never let the code be the only way to reach a piece of information. Not every visitor has a working phone, and a school group of thirty will not have thirty of them. If the story matters, some version of it belongs on the printed label too.
What to measure instead of scans
Scan counts in a museum mostly measure how long people stood in front of the case, not how interested they were — a busy room inflates everyone in it. The numbers worth keeping are different.
Audio completion is the honest one: how many people who pressed play reached the end of a fifty-second clip. Twenty-five per cent is a good result for a museum, and it is a real behaviour rather than a click. Per-object rankings are the second: which pieces get approached, and whether that matches what the curators expected. The third is the catalogue at the exit — a download rate that moves after a change is the only clean comparison you will get.
What a finished set looks like
Twenty objects, twenty codes, one naming scheme that a volunteer can follow, a single printed sheet listing every code and where it points, and one person responsible for it. That is the whole system. Exhibitions fail on codes not because the technology is hard but because nobody owns the redirect and the label was printed before the page existed.
Build the pages first, test them on the oldest phone in the building, and only then send the labels to print. The reverse order is how a gallery ends up with forty codes pointing at a site that was never published.
Common mistakes
- A code that opens the museum’s homepage instead of the object in front of the visitor.
- Video on the first screen, in a hall with no signal.
- One code for the whole room, so nothing can be attributed or changed.
- The code stuck to the glass, catching every ceiling light.
- No instruction line, so the visitor has to guess what scanning does.
- Labels printed before the destination pages were written and tested.
How to build it in practice
In the QR generator, create one dynamic code per object and give each its own destination. Dynamic matters here more than anywhere else: an exhibition changes, an object goes back into storage, a story gets rewritten after a visitor correction — and reprinting forty labels because a link moved is a cost no museum needs.
In QR Studio, put the code into the caption artwork itself, at label height, on a matte background with a generous quiet zone. This is where most museum codes are quietly ruined: the layout gets tightened, the white margin disappears, and the code stops reading in the one lighting condition it will ever be used in.
Then use the QR scanner inside the actual gallery, at the actual distance, with the actual lighting, on the oldest phone in the building — before the print run is approved. A code that scans perfectly in the office and not in the hall is a reprint, not a tweak.