Should couples pay for wedding gallery hosting?

The math nobody runs at booking

When you price a wedding, you price camera time, editing, travel, gear amortization. Hosting never makes the spreadsheet, because on the day you quote it, it rounds to zero. The problem is that hosting isn’t a per-wedding cost — it’s a cumulative one, and it’s the only line in your business that never goes down.

Run the number honestly. Say you deliver 25 weddings a year. After your first season you’re hosting 25 galleries. After four seasons, 100. After ten, 250 — and only this season’s couples are paying you anything. Whatever one hosted wedding costs you per month across storage, streaming, and platform fees, multiply it by every wedding you have ever delivered. That’s not a bill, it’s a ratchet: it clicks up every season and it never clicks back.

Now put the viewing data next to it. Almost every gallery follows the same curve: heavy traffic in the first weeks — the premiere, the parents, the group-chat shares, the rewatch wave — then near-silence, punctuated by an anniversary spike if you’re lucky. So the cost is flat and forever, while the value is front-loaded. Worse, the value that does exist in year three flows entirely to the couple, and the cost flows entirely to you. That mismatch is the whole problem, and every delivery model is really just a different answer to it.

The three models studios actually use

There is no secret fourth option. Every studio delivering online is running one of these, whether they chose it deliberately or not.

• Lifetime hosting, baked in. The promise is clean at booking and couples love hearing it. It’s legitimate — if you actually price it in as a real line item rather than a shrug. The risks are structural: you’re underwriting an open-ended liability at today’s prices, you can’t un-promise it later, and the promise follows you through every platform migration for the rest of your career.
• Expiring links. The cheapest option, and honest enough if you disclose it clearly. But the failure mode is brutal: the couple who clicks their gallery on their first anniversary and finds a dead link doesn’t remember the disclosure. In their memory, you deleted their wedding. That one email costs more goodwill than years of hosting fees ever saved.
• An included window plus couple-paid extensions. The studio covers the delivery window — the part that is genuinely your product — and couples who want the gallery open in year two, three, five pay to keep it open. This maps cost to value more fairly than either extreme. The catch has always been execution: someone has to track the dates, send the bill, and have the conversation. That execution problem is why most studios who like this model in theory end up silently running model one.

The fairness argument: charge for the years, not the delivery

Be clear about what should never be charged for. The delivery window — the premiere, the family shares, the rewatch wave in the first couple of months — is part of what the couple already paid you for. Charging inside that window is nickel-and-diming, and couples can smell it. Whatever model you run, the delivery moment is included, full stop.

Year three is a different product. At that point the gallery isn’t a delivery anymore, it’s an archive service: always-on streaming of a large 4K file, available to anyone the couple sends the link to. The value flows entirely to them, and they are the only ones positioned to know whether it’s worth keeping open. Asking them to fund it isn’t a fee — it’s letting the person who gets the value make the call. Couples already understand this model; they pay monthly for cloud photo storage and streaming services without blinking. The discomfort around charging for hosting lives almost entirely on the filmmaker’s side of the table.

And remember what “free forever hosting” actually is: hosting silently priced into every package. The couple who never opens their gallery after the thank-you cards is subsidizing the couple who watches every anniversary — and both of them are really being subsidized by you, at whatever margin you forgot to protect. There’s no version of this where nobody pays. The only question is whether the payer is the person getting the value.

The 50/50 flip: how hosting becomes a revenue line

This is the part we built Knotflix to fix, because we hit the ratchet ourselves. We run Red Bank Studio and deliver our own weddings on Knotflix every week — the hosting model below is the one our own couples are on.

Every gallery includes 90 days of hosting. When a couple wants more time, they extend it themselves, right from their private gallery link — no account to create, no invoice from you, no conversation at all. And half of every extension a couple pays is paid out to your studio through Stripe. The execution problem that kills model three — who sends the bill, who has the awkward conversation — simply doesn’t exist, because nobody sends anything. The gallery is upfront about its window, and extending is something couples do for themselves.

Two guarantees make the model safe to run. First, nothing is deleted while a gallery is hosted; if the window lapses, streaming pauses until the couple extends — the gallery goes dormant, not destroyed. Second, your original master files stay downloadable to you regardless. Hosting is about the couple’s streaming page, never about your archive, so the film is never hostage to anyone’s payment.

Look at what this does to the ten-year math. The cost ratchet stops scaling with your history: your subscription covers the tool and your active work, and the long tail funds itself — with half of it coming back to you. The couples who love their film most become a small, steady revenue line instead of your largest silent expense. Delivery flips from a cost center to something that trickles money back for years.

How to phrase it to couples without souring anything

The relationship never dies because of the charge. It dies in the surprise — the invoice they didn’t expect, the link that quietly died. Get three moments right and this is a non-issue.

• At booking, one plain sentence in the package or contract: “Your online gallery is included for 90 days after delivery, and you can extend it yourselves anytime after that, for as long as you like.” Frame it as their control, not your limitation. Said at booking, it’s a feature; discovered at month four, it’s a fee.
• At delivery, say nothing about hosting. The delivery email is about the film — the thing they’ve waited months for. Don’t relitigate terms in your best marketing moment. The gallery itself shows the window; that’s enough.
• When the window nears its end, let the gallery do the talking. The extension should be self-serve, on the page they already have open, at the moment they’re feeling something about the film. The instant you personally send a bill, you’ve converted a product feature into an awkward conversation — self-serve or nothing.
• What not to say: don’t apologize, and don’t explain your storage costs. Couples don’t care about your infrastructure bill and explaining it makes the charge feel like your problem being handed to them. The frame is always “keeping your gallery open,” never “covering my hosting.”

When charging couples is the wrong call

If your average package sits at the top of the market, absorbing hosting forever is a rounding error, and “online forever, included” can genuinely belong in luxury positioning. Sell it deliberately as a line item and it’s a fine choice — the model above exists for studios where the ratchet actually bites.

If you’ve already promised lifetime hosting to booked couples, honor it. Switch models for future contracts only; a retroactive clock on a promise you sold is exactly the surprise that sours relationships. And if you’d honestly rather pay one flat bill and never think about gallery lifetimes again, platforms with unlimited hosting baked into the subscription exist and that trade is legitimate — just make it knowing you are the one hosting every gallery you’ve ever delivered, forever, including the ones nobody has opened in years.

Common questions