Tov Studio Photo's 2026 guide names the pattern exactly: couples who refuse portfolio use are rare. Couples who feel they were never asked are not, and theirs is the complaint that ends up in a Facebook group with your name attached. The fix isn't collecting more signatures. It's a layered consent model that most 2026 guides now converge on.
Mistake 1: treating the couple's signature as consent for everyone in the frame
A wedding has 120 people in it. Your contract is signed by two.
The layered model (Tov Studio Photo): the couple's contract is the primary consent — it licenses your portfolio, social, editorial submissions and teaching use, including images depicting guests, and it puts one duty on the couple: "the couple is responsible for informing guests that the wedding will be photographed and that images may be used as described."
Guest consent through the couple carries the right weight, per Tov's and YourLaunchKit's guides. Guest relationships belong to the couple; the guest-communication burden belongs there too. What you add on top is cheap and strengthens your position: a signage notice at the ceremony entrance. A working example from the same guide:
"This wedding is being photographed. Images may be used for the couple's personal records, the photographer's portfolio and marketing, the vendors' portfolios, and editorial submissions. If you do not wish to be photographed or featured, please speak with the photographer or the wedding coordinator before the ceremony."
Signage isn't a legal substitute for consent. Tov's argument, which we find persuasive: it sets the guest's reasonable expectation, and that expectation is central to how right-of-publicity and GDPR "legitimate interests" questions get argued (and note: California, New York and Illinois have stricter right-of-publicity laws than most states, so if you shoot NY/CA weddings, the layered model stops being optional).
Mistake 2: no opt-out, or one buried in the signature stack
YourLaunchKit's 2026 guide is blunt about the standard that works: default portfolio provision with an explicit opt-out, both documented. Not a release shoved into the signature stack. Not silence.
The opt-out needs a process, not a vibe. What happens if the couple says no after the fact — email? Is there a deadline? Do you charge for it? A refusal path that exists on paper is what keeps the relationship intact when someone eventually uses it.
Mistake 3: portfolio use and commercial use treated as the same thing
They're not, and the line matters most in the frames you'd never suspect. Tov Studio Photo draws it cleanly:
- Portfolio use — your website, your Instagram, your blog, editorial submissions, teaching examples — is often treated as expressive/editorial use, though self-promotion can be judged commercial in some states, so the line isn't the same everywhere. Broad latitude in practice. A guest crying during the ceremony on your grid: fine.
- Commercial use — paid advertising, stock sales, third-party licensing, brand partnerships — narrower latitude, and identifiable people prominently featured often need explicit releases. A central image of a guest, in a paid ad, is the gray zone that a release settles.
The practical rule: if a frame's destination is an ad buy, that frame gets its own release, whatever the couple's contract says. Stanford's fair-use overview adds the two requirements that make any release valid: informed consent (the signer understood it) and authority (they could actually grant it) — which is why a wedding party's blanket release is weaker than it looks.
Mistake 4: no withdrawal process when a guest objects
Someone emails three weeks after the wedding: remove the shot of them from your Instagram. The right answer is almost always yes, quickly, without argument — and then document it.
Tov's procedure is worth copying verbatim into your workflow: log the request (date, image reference, action taken), remove everywhere you control, and if the image was syndicated to a publication, email the publication too — most oblige. Under GDPR (relevant for UK/EU weddings), YourLaunchKit's guide treats the photographer as a data controller with response deadlines and record-keeping duties; in the US it's less formalized, but the reputation math is identical: the cost of a small portfolio edit is trivial, the cost of a public complaint is not.
Mistake 5: overcomplicated releases nobody signs
When you do need a real release — styled shoots, editorial-commissioned weddings, any ad-campaign image — keep it short. YourLaunchKit's term list is complete: parties, shoot description, scope of consent (be specific: "use in advertising for beauty brands" beats "commercial purposes"), limits, duration, territory, consideration, signature. Two or three clauses for wedding contexts. Overcomplicated releases "feel threatening and discourage signing" (same source).
Minors: parent or guardian signs, relationship recorded, date of birth noted so minor status is unambiguous (YourLaunchKit).
Mistake 6: the AI-training gap in pre-2024 contracts
New in 2026 guides and missing from many templates bought before then: explicit non-authorization for AI training datasets. Tov's model clause now names what the license is not for: third-party commercial use without further consent, AI training datasets, stock photography sales. If your license text predates the AI era, it's silent on scraping — nothing in it stops a dataset crawler, and nothing in it gives you a written argument either. One sentence fixes it.
The clause that does all of this, compressed
A working portfolio clause (adapted from the guides above):
The couple grants the photographer a non-exclusive, royalty-free, perpetual license to use wedding images for the photographer's own portfolio, marketing, publication submission, and educational purposes, including images depicting guests; the couple is responsible for informing guests that the wedding will be photographed and that images may be used as described. The license does not extend to third-party commercial use, AI training datasets, or stock sales without further written consent. The couple may opt out of portfolio use in writing before or within [30] days after gallery delivery; the photographer will honor any guest removal request promptly.
Three sentences. Covers consent, scope, the AI gap, the opt-out, and the withdrawal promise. Replace the 30-day opt-out window with whatever term you actually honor. The wedding photography contract template has a portfolio line with a blank opt-out and a personal-use license; add the guest-notice and AI-training sentences above yourself — your state, your market, and your boundaries aren't ours to fix in stone.