digital model release
Model releases feel simple — until months later you have to find what was approved for what.
Problem
A Canva PDF, a signed form in Drive, or a WhatsApp “OK” is quick. Later, what’s missing is often clear occasion mapping, overview of versions, and a closure moment that fixes the state.
Solution with LegitForm
LegitForm works per occasion: approvals arrive as 🟡 received. When you finalize, the proof is created (PDF + protocol + timestamp) — only then exportable.
Flow
- Create an occasion (e.g., campaign/shoot).
- Create the release and choose purposes.
- Send link — model confirms/signs (no account).
- 🟡 received for the occasion — collect first.
- Finalize → create and export the proof.
Comparison
- The file exists, but context is often scattered.
- Versions/signatures across folders are hard to oversee.
- No clear closure moment.
- Export often means manual assembling.
- Occasion mapping instead of folder chaos.
- 🟡/🟢 status makes the state immediately clear.
- Finalizing creates the proof; then exportable.
- Bundle export for hand-off/archive.
CTA
Start free — you only create proof when you finalize
You can try for 14 days — up to 10 approvals. After that, you can continue with Standard without limits.
What is a model release?
A model release is approval to use photos/videos — for example on a website, social media, or in advertising.
Can I use a model release as a PDF?
Yes. In practice, the bottleneck is often finding and explaining the approval later — not the file itself.
When is the proof created in LegitForm?
Only when you finalize. Before that it stays 🟡 received (interim state) without export.
Does the model need an account?
No. The model opens the link in the browser and confirms/signs.
Can I try it for free?
Yes. In the Starter plan you can try for 14 days and capture up to 10 approvals. After that you can continue with Standard without limits.