The programs were printed the night before. Two hundred of them, folded by hand at a kitchen table by a daughter who could not sleep, because doing something with her hands was better than the alternative. On the back, below the order of service and the poem her father had asked for, a funeral director had suggested adding a small QR code: scan it to watch the livestream if you could not travel, to see the photo slideshow again, to read the full obituary, to give to the hospice in his name. It seemed like a kind, modern thing to do. The codes went out with the programs, and most of the family tucked their copy into a drawer or a Bible or a memory box, the way people do.
Two years later, a grandson who had been too young to really understand the day found the program again. He scanned the code, hoping to hear his grandfather’s voice in the slideshow one more time. It went nowhere. The livestream’s host had kept the recording for only ninety days. The slideshow had lived on a free photo-sharing site that had since changed its sharing rules. The obituary link redirected to a paywalled newspaper page. The donation button pointed at a fundraiser that had long since closed. The paper had lasted perfectly. Everything it pointed to was gone.
This is the quiet, specific way a funeral-program QR code fails, and almost nobody warns families about it before they print. The program itself is a keepsake people hold onto for decades; the things it links to are built to last weeks or months. This article is about closing that gap: what to link, how each of those links tends to die, and how to make the printed code still resolve when a grandchild scans it years from now.
A note before we go further: Heldqr is our product, and we will explain where it fits near the end. We have tried to make the rest honest enough to be useful even if you never use it. The underlying mechanics of why printed QR codes outlive the things they point to live in our guide to QR codes that don’t expire; this piece applies that thinking to the one piece of paper a grieving family is most likely to keep.
The funeral program is the headstone’s paper cousin — and they have different jobs
We have written separately about memorial QR codes on headstones and markers, and it is worth being clear about how that object differs from this one, because they look similar and fail differently. A headstone code is etched into stone meant to stand for a century: permanent, singular, fixed in one place, with the durability problem stretched out over extreme time horizons.
A funeral program is paper. It is printed once, in a hurry, in a quantity matched to the guest list, and then it scatters: into drawers, scrapbooks, wallets, and the back pages of well-thumbed books, held by dozens of people in different houses and eventually different countries. You cannot recall it or reprint the copies already given away. Whatever code went out on that paper is now out in the world, unchangeable, in more hands than you can count.
That changes the design problem. With a headstone you control the one object forever. With a program you control nothing after the service ends — except, if you set it up correctly, the one thing the printed code points through. That single point of control is the whole game. First, what families link.
What a funeral-program QR code should link to
In practice, four destinations come up again and again, and a good program code leads to one simple landing page offering all four rather than four separate codes nobody can tell apart.
The obituary. The full written notice — longer than the program had room for, often in the family’s own words rather than the newspaper’s template. This is the anchor, what most people scan for first.
The livestream, and then its replay. Many services are now streamed for relatives who cannot travel. During the service the code should reach the live broadcast; after it, the same code should reach the recording. This is the destination that changes within hours of the funeral, and the one that breaks most often.
The photo slideshow or memory gallery. The images shown during the service, plus space for more that relatives add later. Families return to this one for years.
The donation or tribute page. “In lieu of flowers” — a hospice, a research charity, a cause the person cared about. These pages frequently have a campaign window and then close.
Notice something about that list: every destination is expected to change. The livestream becomes a replay, the slideshow gains photos, the donation drive opens and then closes, the obituary gets corrected or moved. A funeral program is, almost by definition, a printed object pointing at a set of moving targets — exactly the situation a fixed printed code handles worst, unless it is built to let the target move underneath it.
The four ways a funeral-program code dies
Before the fix, the failure modes — because once you understand how these links rot, the fix is obvious rather than a sales pitch.
One: livestream link rot. The most common failure, and the most painful, because the replay is the destination relatives most want later. Funeral livestreams usually run through a platform the funeral home subscribes to, and many of those platforms retain recordings only for a limited window — often around ninety days — before deleting them or moving them behind a separate paid archive. Even when the recording survives, the live-broadcast URL frequently differs from the replay URL. A code printed to reach the live stream lands on a dead “this broadcast has ended” page a week later, and on nothing at all a few months after that.
Two: vendor shutdown or rebrand. If the program code was generated by a QR vendor — or the landing page hosted by a small memorial-tribute startup — that company is now a dependency. When a QR vendor rebrands and migrates its short-code domain, every code issued under the old domain can stop resolving; this is the pattern that affected a large vendor’s customers after a 2023 rebrand. A memorial-page host that goes out of business takes every page it served with it. The paper survives; the company behind the link does not.
Three: subscription lapse. Many dynamic QR codes and hosted tribute pages run on an ongoing subscription, and the person paying is usually the next of kin — often elderly and grieving. When the card on file expires, or the payer themselves passes away, the renewal emails go to an inbox nobody checks, and the code is deactivated for non-payment. Nobody finds out until they scan and get an error, which is exactly the moment it hurts most. This mode is unique to memorial use: the subscriber and the subject are sometimes the same household.
Four: the free destination quietly changes its rules. The slideshow on a free photo-sharing site, the fundraiser on a donation platform — these are not hostile, but they are not built to be permanent public links either. “Anyone with the link” becomes “sign in to view”; campaigns close and their pages get repurposed. The link does not 404; it just stops doing what it did, which is harder to notice and harder to explain.
All four share one root cause: the program code points directly at something fragile and changeable, with no layer in between that the family can update. Fix that one thing and all four become survivable.
The fix: point the code at something you can redirect
The durable pattern is the same one that works for every long-lived printed QR code, and it is genuinely simple. Do not print a code that points directly at the livestream, or the slideshow, or any single destination. Print a code that points at a stable redirect you control — a short link whose final destination you can change at any time, without reprinting anything. On the program it looks identical: a small square of dots. Underneath, it resolves through one layer you own.
Now the moving targets stop being a problem. During the service, the redirect points at the live broadcast; the week after, you change it — in under a minute, from your phone — to the recording. When the recording moves to a permanent archive, or the donation campaign closes, you repoint it again. The programs in all those drawers never change, but what they reach stays current for as long as you keep one destination alive.
This is the whole reason “dynamic” QR codes exist: the printed pattern is fixed, the destination is editable. The catch — the one this article exists to warn about — is that most dynamic codes make you depend on the vendor’s redirect layer continuing to exist and to be paid for. So the durability question is not “static or dynamic?” It is: who controls the redirect, and what happens to it when they stop?
That question is the one almost no funeral-program QR provider answers. The sites that rank for this query — CherishedKeepsakes, FuneralProgramSite, and similar template-and-print shops — sell the program design and the code generation, but offer no guidance on what happens to the link in year five, no published continuity plan, and in several cases no clear statement of whether the code is even editable after printing. The paper is beautiful; the durability of what it points to is left entirely unaddressed.
A short checklist before you print
Fifteen minutes with this list, before the copies go to the printer, can spare a grandchild a dead link a decade from now.
-
Is the code editable after printing? If the vendor cannot say plainly that you can change the destination later, assume you cannot. For a funeral program, where the livestream will change to a replay, a frozen link is close to a guarantee of failure.
-
Who owns the redirect layer? If it is the QR vendor’s domain, your code depends on that vendor existing and being paid. If it is a domain you control, it survives the vendor.
-
Is there a published continuity plan? Ask directly: if you shut down, what happens to the codes already printed on our programs? “We’ve been around for years” is not an answer; a documented wind-down is.
-
Is anything on a subscription that can lapse silently? If yes, who pays it, and what happens when that person can no longer pay? Note it down now, while someone is paying attention.
-
Where does the livestream recording actually live, and for how long? Get this in writing before the service. If retention is ninety days, plan now to move the recording somewhere permanent and repoint the code to it.
-
Does the destination page log or sell anything? A memory page that serves ads or tracks visitors is not what a grieving family signed up for. Read the privacy policy; if unclear, assume the worst.
Pass most of these and the program will still work when it matters; fail more than a couple and the paper will outlive everything it was meant to carry.
How to do this with Heldqr
Heldqr is a general-purpose QR-code resolver: you print one code, it points at a destination you can change at any time, and it keeps resolving for as long as we operate. It is not a funeral product, but for the specific job a funeral-program code needs to do it fits cleanly, and for one program the free tier is genuinely enough — full details on the pricing page.
Here is how it maps to the four destinations. You create one Heldqr code, point it at a single simple landing page, and print that code on the program. During the service it leads to the livestream. The week after, you edit the destination to the recording; the change propagates in under sixty seconds and the printed code never changes. When the slideshow moves or the donation campaign closes, you repoint it again. None of it requires reprinting a single program, because the program only ever pointed at your redirect, and the redirect is the one thing that moves.
The free tier carries no expiry, no trial clock, and no deactivation: a funeral-program code is exactly the kind that should keep working for decades, and on Heldqr it does, free, for as long as we operate. It does show a small branded caption beneath the code in the SVG export, and analytics are limited to lifetime scan totals — neither of which matters for one program in a drawer. If a family wanted the printed code to keep resolving even past a hypothetical future shutdown of Heldqr, the Pro tier (€9/mo) adds a custom domain, so the code points at a domain the family controls rather than heldqr.io — but for a single program that is optional, and we would not push a grieving family toward it.
Two commitments matter more than any tier. First, every Heldqr code is backed by the same published continuity plan: if we ever stop operating, there is a documented wind-down — twelve months’ notice, the resolver source code released at month six, per-account exports plus an opt-in public dump at month nine. Second, our analytics are cookieless and record only country and device class, never IPs — a memorial code should not be quietly surveilling the people who scan it, and ours does not.
If you only take one thing from this section: make one editable code, point it at one page, and keep that page alive. Everything else is detail.
What Heldqr is not the right answer for here
Heldqr forwards a scan; it does not build the thing the scan arrives at. If what a family wants is a full hosted tribute experience — a designed memorial page, a video guestbook visitors can sign, a moderated wall of condolences, a permanent hosted home for the slideshow — Heldqr does not provide any of that. It only points at it.
For that fuller product, specialised memorial and tribute vendors are the right call, the same ones we point to in our memorial QR code guide. They build and host the experience and handle the moderation. The honest tradeoff is the one we always name: a specialised vendor gives you a richer page and a dependency on that vendor staying in business. The wrong move is to pay one of them and assume the link on your program is now permanent — it is not, any more than any other vendor link is.
The configuration that gets you both: build the rich tribute page with a specialised vendor if you want one, then print a Heldqr code that points at it. If the vendor thrives, the experience is rich and the code works. If the vendor shuts down, you repoint the same code at a family-controlled archive, and the programs in all those drawers never become dead paper. The keepsake and the durability are two separate purchases; treat them that way and you can have both.
In closing
A funeral program is one of the few things people keep without deciding to. It ends up in the same drawer as a birth certificate and a wedding photo, and gets pulled out years later by someone who needs, for a moment, to feel close to a person who is gone. A QR code on that paper makes a promise to that future person: scan this, and something of him is still here. It is a small promise, but it is made to a grandchild, and it should not be broken by a streaming platform’s retention policy or a lapsed credit card.
If you are a family member arranging a service: link the obituary, the replay, the slideshow, and the donation page through one code you can edit, and make sure the recording is moved somewhere permanent before the streaming platform deletes it. If you are a funeral director: tell families plainly that the link will need to change after the service, and steer them toward a code that lets it — not one frozen at the printer. If you want to use Heldqr, the free tier is enough for one program, and we have built the rest so that the answer, when that grandchild scans, is not silence.
The paper will keep its promise on its own. The link is the part that needs help. Set it up so it still resolves the day someone really needs it to.
Written in June 2026. This piece sits inside the broader guide to QR codes that don’t expire. If you are arranging a service and have a question this article did not cover, or a story of a program code that failed and is worth adding to the public record, email us at hello@heldqr.com.