What a memorial QR code should open, and how to keep it open for decades

OpenQR

What a memorial QR code should open, and how to keep it open for decades

Ask what goes wrong with memorial QR codes and the answer is almost never the code: stone survives, engraving is a solved craft, error correction handles the weather. What fails is the other end of the scan. Tribute platforms close, funeral director pages move, photo albums reach their storage limit, and the domain nobody renewed quietly lapses in year four. This page is about the destination: the realistic options, which of them survive decades, and the lifecycle that keeps a code honest while the family is still deciding.

OpenQR does not host tribute pages

This is the page where a hosted memorial profile would be convenient, so it is worth saying plainly: we do not host tribute pages, memorial profiles or photo collections, and we have not decided to build that. What we provide is the code and, for dynamic codes, the redirect. Where the code points is a decision for the family, the mason or the funeral director, and this page is guidance for making it well.

The realistic options, and how long each one lives

DestinationWho controls itDecade risk
Funeral director's tribute pageThe funeral business, which may be sold, rebrand or retire its siteMedium: the business is motivated to keep families' pages, but its website will be rebuilt at least once
Memorial or tribute platformA third-party company with investors and running costsHighest: subscription products shut when growth stops, and take the pages with them
Shared photo album or drive folderThe family's own accountLow while the account lives; dies with the account holder's email or a storage quota
The family's own domainThe family, directlyLowest: a renewed domain outlives platforms, and renewal is the only thing to remember

None of these are wrong choices, and the honest one is whatever the family will actually maintain. But the control column is the one that predicts whether the code still opens in ten years, because a QR code has no memory of its destination: it encodes a string, and if the string stops resolving, the stone is pointing at nothing. Every memorial code decision is therefore really a decision about who is on the hook for keeping a page alive.

The strongest guarantee is a domain the family renews

If the memorial matters for generations, the durable pattern is cheap and boring: a domain in the family's name, set to auto-renew, pointing at whatever page exists today. Domains cost little a year, they survive website rebuilds, platform changes and funeral businesses changing hands, and renewal can be handed to the next generation as part of the paperwork of the estate. Point the code at that domain, and let the domain forward to whichever tribute page, album or memorial site is real at the time. When the underlying page moves, one DNS or forwarding change fixes every plaque ever cut, which is the property none of the hosted options have.

Dynamic while it settles, static once it is certain

The dynamic code is the right tool for the period when nothing is settled: the tribute page is still being built, the family has not chosen between the funeral director's page and their own album, and the stone is being cut on a schedule that will not wait. A dynamic code can be repointed at any time, from the dashboard, without touching the memorial. Then, once the destination is genuinely settled, bake the final answer into a static code for anything that is cut into the stone itself, because static needs no account, no redirect service and no company to stay alive: it encodes the destination directly and works for exactly as long as the destination does. The permanence section of the memorials guide covers why that matters for something going on stone for good. Proof and engrave from the static file, and the stone never needs to care what happens to any account.

The handover pack: what the family should be left with

  1. 1

    Where the code points

    The actual URL, written down, not just in someone's bookmarks.

  2. 2

    Who owns what

    Which account holds the code, whose email the account is on, and where the password recovery goes.

  3. 3

    How to change the destination

    For a dynamic code, the dashboard link and the two clicks it takes; for a static code, the honest answer that the stone's code does not change.

  4. 4

    What costs what

    If the destination involves a subscription or a domain, the renewal amount and date, and what happens if it lapses.

  5. 5

    The static fallback

    The final static code file, kept with the memorial paperwork, so a replacement plaque can be cut without anyone reconstructing the design.

What belongs on the page itself

Scanners arrive on a phone, often outdoors, often in a place with one bar of signal, so the page should be light and fast before it is anything else: a name, dates, a photograph, a few paragraphs, a way to leave a message, and if the family wants it, a donations link. Heavy galleries, autoplaying music and analytics scripts all cost a visitor with a weak connection, which is who a graveside visitor usually is. Privacy deserves a deliberate answer too: a page reachable by anyone who scans is a page indexed by search engines, and some families want exactly that while others want it unlisted. Decide it out loud rather than discovering the default.

No. OpenQR generates the QR code and, for dynamic codes, runs the redirect to wherever the family has chosen. It does not host memorial pages, photo collections or donation processing.
Part of Memorials & headstones

Related