Your audience cannot play the disc anymore
You just mailed an eight-message teaching set on DVDs to a recurring partner, and between the duplication, the printed cases, the padded mailer, and the postage, the package cost more than that month's gift covered. Half of the people who receive it will not play it, because the laptop with a disc drive went in the trash three years ago and the living-room DVD player followed it. A printed card with a QR code costs cents, weighs almost nothing in the envelope, and plays the same eight messages on the phone already in the recipient's hand.
Ministries that built a faithful audience on cassettes, then CDs, then DVDs, are not abandoning the teaching when they drop the disc. They are dropping a delivery format that the audience can no longer play. The card does the same job the disc did: it puts your teaching in someone's hands and asks them to engage. It just does it on the device they actually carry.
The honest truth: most QR vendors will sell you a "media solution" and let you believe the QR holds your audio or video. It does not. A QR code is a pointer. Understanding that one fact is what keeps a teaching-media program cheap, durable, and under your control, so the rest of this guide is built around it.
EZQR links to your media. It does not host it.
Here is what actually matters before you generate a single code: a QR code stores a short web address, not a file. Your eight-hour MP4 teaching set is gigabytes; the QR holds maybe a few hundred characters. So the audio and video have to live somewhere on the web, and the QR sends the phone to that address. EZQR generates and tracks the code. It does not store your files, and there is no per-gigabyte or per-terabyte storage bill from us, because we are not your media host.
That division is a feature, not a limitation. Keep the files on a host you control and the QR is just a pointer you can re-aim. Put the files inside a vendor that also owns the QR, and the day that vendor raises storage prices your library is hostage. Most vendors won't tell you this, because bundling storage is how they lock you in.
Where ministries host the media:
| Host | Best for | Cost shape | Notes |
|---|---|---|---|
| Subsplash | Churches already on a ChMS or app | Plan-based monthly | Sermon hosting, giving, and app in one; QR points to the media page |
| SermonAudio | Teaching ministries with a large archive | Plan-based monthly | Built for sermon libraries; stable URLs per message |
| Vimeo | High-quality MP4 teaching sets | Tiered by storage and bandwidth | Clean player, no ads, password and privacy controls |
| YouTube (unlisted) | Free video hosting at any volume | Free | Unlisted links are not searchable; lowest cost, least control |
| Cloudflare R2 / Bunny / Amazon S3 | Raw MP3/MP4 you fully own | Per-GB stored + delivered | Cheapest at scale for owned files; needs basic technical setup |
Tips
- For a library of several thousand files in both audio and video, object storage (Cloudflare R2 or Bunny) is usually the cheapest path and keeps the files yours. SermonAudio or Subsplash trade a higher monthly fee for not having to manage any of it.
- Whatever you pick, give each teaching a stable URL that will not change. The QR is only as durable as the address it points to.
The durable-card model: one card per partner, re-pointed every month
The structure that makes this cheap is one durable card per recurring partner, not a new card every month. Give each partner a single dynamic code printed on a sturdy card they keep. Each month you re-point every one of those codes to the new teaching, and the same card in their hand now plays this month's message. No reprint, no second mailing of cards, no postage on the card itself after the first send.
This is the opposite of how most ministries imagine the switch. They picture printing and mailing a fresh QR card with every release, which is just the DVD mailing with a cheaper disc. The dynamic code removes the monthly print run entirely. You mail the card once. After that, the only thing that travels each month is the edit you make to the code's destination, and that is free.
A dynamic code is what makes the re-point possible, because the printed pattern stays fixed while the destination behind it changes. The partner who keeps engaging with your teaching is the partner who keeps giving, so a card that follows them for years is a stewardship investment, not a printing expense. The churches QR page covers how this sits alongside giving, volunteer signups, and wayfinding as one program.
How to tell which teachings get watched
Give each partner a unique code and every scan becomes a quiet engagement signal. The dashboard shows you each code's activity: how many times it was opened, on what date, and from which city, and you can export the whole set to a spreadsheet. Print the same teaching link behind a thousand unique codes and you can see which partners opened this month's message and which did not, by card.
What you do not get, and should not promise your board you get, is personal surveillance. EZQR tracks the code, not the person. There is no name, no email, and no precise location attached to a scan; the data is the code's activity, the timestamp, the city, and the device. There is also no instant text alert on a free or mid tier. Real-time scan notifications are a Max-tier feature; below that, you review engagement in the dashboard on your own schedule.
If you only do one thing with the data, watch which teachings get re-opened weeks after you sent them. A message that gets scanned again in month three is the one worth re-mailing to your wider list. That is the kind of read a donations program uses to decide which appeals to repeat, applied to teaching instead of giving.
Mailing at scale: bulk generation and the API
Generating one code is a click. Generating the codes for a full partner list is a Max-tier job, because the features that make volume sane all live on that tier. Bulk generation from a spreadsheet, the REST API, unlimited dynamic codes, and team access are Max ($20/mo) capabilities. Pro at $10/mo stops at 100 dynamic codes, which a partner list in the thousands clears in a week, so Pro is the wrong tier for this specific job.
The operational flow has two moves. First, create the partner codes once: upload a spreadsheet of your partner list and bulk-generate a unique code per row, or call the API to create them in a batch. Second, re-point them every month: a script that walks the list and updates each code's destination to the new teaching URL turns the monthly release into one job instead of thousands of clicks. There is no one-button bulk re-point in the dashboard yet, so this monthly step runs through the API today.
For a ministry sending to several thousand partners with a multi-thousand-file archive, that combination, owned media plus durable codes plus a scripted monthly re-point, is the entire system. Everything else is print and postage, which a commercial mail house handles.
Designing a teaching card that survives the mail
A card that rides through the postal system needs more error tolerance than a code on a screen. Generate at error-correction level H, which rebuilds the code from up to 30% damage, so a bent corner or a coffee ring does not kill the scan. Keep strong contrast between the code and the card, dark pattern on a light field, and give the code quiet margin on all four sides.
Export a vector file, SVG or EPS, for your printer rather than a low-resolution PNG, so the code stays razor-sharp at any card size. Add a short, plain instruction next to it, something a longtime partner reads without hesitation, and print the destination address under the code so anyone who prefers to type can. EZQR produces the code and the branded artwork; the physical card stock, the printing, and the mailing are your print vendor's job, and a mail house will quote those at volume far better than any QR tool could.
Test before the run. Scan the proof on an actual phone, on cellular, with no saved cookies, and confirm the teaching loads in under three seconds. A card you cannot reprint cheaply is a card you test twice.
What it costs, and what survives if you stop paying
The economics favor the card from the first mailing, and they compound after it. A disc set carries duplication, cases, and postage on every single send. A teaching-media program on durable cards pays for printing and postage once per partner, then runs on a flat monthly subscription no matter how many teachings you release.
The tier that fits depends on volume, and the ladder is simple:
| Plan | Dynamic codes | Fits | Key features for media |
|---|---|---|---|
| Free | 3 | Trying the workflow | PNG export, scan counts |
| Lite — $5/mo | 25 | A small class or partner group | 30-day analytics, SVG/PDF export, codes survive cancellation |
| Pro — $10/mo | 100 | A mid-size mailing list | Full analytics, CSV export, EPS export, city-level data |
| Max — $20/mo | Unlimited | A few thousand partners a month | Bulk generation, API access, scan notifications, 5 team seats |
Tips
- One thing to verify in writing before any print run: the codes keep redirecting after you cancel. EZQR codes survive cancellation; some vendors deactivate dynamic codes weeks after a lapsed payment, which would silently kill every card already in partners hands.
- A budget pause during a leadership transition is exactly when cards quietly die on vendors that deactivate. The permanent-code policy matters more for a mailed ministry than the per-month price.
Where teaching media meets giving
A teaching-media program and a giving program reinforce each other, and they run on the same codes. The card that plays this month's message can carry a second code to your giving page, or the teaching page itself can hold a give button. The same per-code analytics that show which teachings get watched also read which giving placements convert, so one QR program serves both the discipleship and the stewardship side of the work.
If your ministry already takes donations by QR, the donations playbook covers the trust-design and tax-receipt mechanics, the nonprofits page covers the broader pattern for registered orgs, and the church giving guide covers offering, tithe, and campaign codes. Host the teaching with video and podcast links where your audience already listens and watches, and let the card be the bridge that costs cents.
The bottom line
Drop the disc, keep the teaching. Host the audio and video on a platform you control, print a durable QR card for each recurring partner, and re-point that card to the new message every month so you never reprint. Give each card a unique code and the dashboard tells you which teachings land, without collecting anything personal about the people who scan.
For a ministry mailing a few thousand cards a month against a library of several thousand files, this is a Max-tier program at $20/mo: owned media, durable codes, bulk generation, and an API for the monthly re-point. The card costs cents, plays on every phone, and outlasts the next format change, which is the one thing a disc could never promise.
