QR codes for heritage trails and outdoor walks
Weather works on a trail post every day a gallery panel never sees. There's no mains power out on a trail, so the code is the only piece of technology at that stop, not a screen with a code as a backup. Mobile signal is patchy and different at every stop along a route, not a single known quantity for the whole building. And a post standing alone on a public path is a target for vandalism in a way a panel in a staffed gallery isn't.
| Material | Weatherproof? | Vandal resistance | Typical lifespan | Notes |
|---|---|---|---|---|
| Laminated paper on a post | Only briefly; laminate lifts within a season outdoors | Low, easily torn or scratched off | Under a year outdoors | Fine for a temporary trial trail, not a permanent one |
| UV-stable vinyl decal, recessed | Good, several years | Moderate; hard to peel if recessed into the post | 3-5 years | The realistic default for most funded trails |
| Engraved or etched metal plate | Excellent, effectively permanent | High, nothing to peel or tear | 10+ years | Higher upfront cost; right for a flagship trailhead or a listed site |
A static code decodes with no signal at all, because the destination is baked into the pattern and the phone's camera reads it locally. What happens next is a separate question: if that destination is a URL, opening it still needs a connection, exactly the way a rural venue or a lift shaft does for any code. A dynamic code needs a connection at the moment of the scan no matter what, because it has to resolve a redirect before it can send a visitor anywhere. The full version of this trade-off, including which payload types genuinely work with zero signal, is in the offline QR code guide.
Use static wherever a stop is a known not-spot
Walk the route before deciding. Where a stop reliably has no signal, use a static code with settled content: it works regardless. Save dynamic codes for stops nearer signal, typically the trailhead, car park or visitor centre, where there's a real chance you'll need to correct the destination later.
Planning a trail's codes end to end:
Walk the route with a phone
Note where signal actually drops as you go; don't assume from a coverage map, which is measured very differently from a scan at ground level under tree cover.
Number the stops and settle a convention
"Stop 04 - Oak Wood" sorts correctly and reads clearly on a printed contact sheet, the same idea as the exhibit convention but with its own vocabulary.
Choose material by how long the trail needs to last
Not by the cheapest option available today; a laminated sign reprinted every year costs more in the end than a vinyl decal that lasts five.
Decide static or dynamic per stop
Based on the signal survey and how settled that stop's content is, not a single rule for the whole trail.
Mount above splash height and recessed where possible
Standing water and casual vandalism both target a sign at knee height; higher and recessed loses less to both.
A bilingual trail is exactly the same shape of problem as a multilingual exhibit set, stops times languages instead of exhibits times languages, and the same spreadsheet-then-paste method applies with "Stop" in place of "Exhibit". See the multilingual exhibit set page for the exact method.
A twelve-stop trail is nine codes over the free allowance the moment any of it needs to be dynamic, so a full trail rollout is a Pro decision, £9/month, in the same way a full exhibit set is. A short pilot trail of two or three stops, kept static while the route and content are still being tested, costs nothing at all.