Digital model release for photographers
Collect consent, close it deliberately, and prove it later when needed.
Important: it’s not “another form”, but a shared approval (Living Consent) — one shared state with history.
A shoot with several people, approvals via WhatsApp or verbally — and somewhere there’s still a PDF on a phone. On the computer there are folders named like “release_final_v3.pdf”. That’s what everyday “photography consent” looks like — without anyone wanting it to be complicated.
Digital model release vs PDF: what’s the difference?
Many photographers already have consent as PDF or paper. That works — as long as everything stays calm. The problem isn’t the signature, it’s later: when someone asks which version applies, which shoot it belongs to, and whether it was deliberately approved in that context.
PDFs are documents. LegitForm models the closure of a process. If you need to prove photo consent, it’s not only the file that helps — it’s a traceable closure.
You work per shoot as one occasion. Approvals come in via link or QR — first as an interim state, then (if needed) as a closed record. The difference isn’t the document — it’s the moment you say: this approval is closed.
- Create an occasion per shoot.
- Share consent via link or QR code.
- Approvals arrive (interim state).
- Finalize the relevant approvals deliberately.
- Proof is created: PDF + protocol (timestamped).
That’s how a digital model release becomes more than “just a form” — it becomes a clean closure for the occasion.
- Overview per shoot — everything per occasion instead of loose paper/PDFs.
- No collecting versions and folders — you work in context.
- Proof only when needed: finalizing = closure.
- No subscription, no pressure — pay only when you finalize.
This flow isn’t only for photographers, but also for TFP shoots and video productions — and anywhere consent from people needs to be collected and later documented clearly (e.g. social media, agencies, studios).
Watch the demo — prepare approvals digitally
What is a model release for photographers?
A model release is an approval to use photos/videos — e.g. for website/portfolio, social media or advertising. In practice it helps most when it remains clear later what was approved, and in which context. That’s what gets documented cleanly per occasion.
Is a signed PDF enough?
A signed PDF can work as a document. The bottleneck often comes later: which shoot does it belong to, which version applies, and is the scope unambiguous? LegitForm reflects the flow per occasion — and creates exportable proof only when you finalize (PDF + protocol).
When is proof created in LegitForm?
Only when you finalize. Before that, an approval is stored only as 🟡 received for the occasion and is not exportable yet. When you finalize, PDF + protocol with timestamp are created and proof becomes exportable.
Do I need to finalize every approval?
No. You collect approvals for the occasion and finalize only the relevant ones — when you actually need closure and exportable proof. That keeps the process calm and you pay only when needed.
Can I use LegitForm for other occasions too?
Yes. The principle “occasion → received → finalize → proof” fits anywhere approvals should remain traceable later — e.g. video, social media, agencies or studios. You can use the system independent of the use case.