Model Release Contract: Template, GDPR, and Digital Consent Explained
If you want to publish images of recognizable people, you generally need a sound legal basis for doing so – and the model release contract is the tool you use to document it. It records who is pictured, what the images may be used for, and to what extent. Without that documentation, you have no proof if the use is ever questioned.
This post explains clearly what belongs in a model release contract, how image rights and GDPR interact, which mistakes happen most often – and how to capture consent digitally instead of on paper. Important note: this post is orientation, not legal advice. For a specific case in doubt, you should consult a lawyer.
Model release contract template – free to copy
Don't want to read the whole legal background first? The template is right here on the page. It covers the points that most often go missing in practice: purpose, channels, territory, duration, sharing with third parties, compensation, and data protection.
This template is written for adults and for typical photo and video productions. Image rights are governed nationally, so set the governing law in section 12 and adapt the wording to the country you work in.
1. Parties
Licensee / commissioning party
Person depicted
- I confirm that I am at least 18 years old.
2. Project
This agreement covers the photo, video and audio recordings made as part of the project named above in which the person depicted is recognizable (the “Recordings”).
The template has 12 sections — the first two are shown here. To fill it in, download the PDF or Word version.Show the full templateCollapse the template
3. Permitted use
The person depicted permits the licensee named above to use, reproduce, publish and make the Recordings publicly available to the extent set out below. The Recordings are used solely for the purposes agreed here.
Purpose
- Portfolio / self-promotion
- Company website
- Organic social media posts
- Paid social and online advertising
- Print advertising / brochures / flyers
- Press and public relations
- Presentations / internal communication
- Campaigns and advertising for the following client
- Other purpose
Media and channels
Territory
- Country of the production only
- European Union / EEA
- Worldwide
- Other
Duration
- Until
- For the duration of the project / campaign described above
- Without a time limit, as far as legally permitted
Use for purposes materially different from those agreed here is not covered by this agreement.
4. Editing the Recordings
The Recordings may be edited technically and creatively within the agreed purpose. This includes in particular selection, cropping, resizing, color correction, retouching, audio editing, and placement into layouts, videos or other design elements.
Any use that attributes statements, characteristics or actions to the person depicted that are not factual is not covered by this agreement. Use in degrading, discriminatory or otherwise seriously damaging contexts is not permitted.
Unless separately agreed, the following are not covered:
- training generative AI models on the Recordings,
- generating synthetic or deceptively realistic depictions of the person depicted,
- face swaps or comparable alterations of identity,
- any use beyond the purposes agreed above.
5. Sharing with third parties
The Recordings may be passed to the end client named above and to service providers, as far as this is necessary to produce, edit, publish or carry out the agreed use. Service providers do not thereby receive independent rights of use beyond the agreed purpose.
Any sharing or licensing beyond that — in particular to third parties not named here, or for use with other products, brands or campaigns — is permitted only where expressly agreed below:
6. Credit
- The Recordings may be used without naming me.
- My first name / name may be shown alongside the Recordings.
7. Compensation
For the agreed use:
- The agreement is made without payment.
- The following compensation was agreed
- TFP / time for prints: in return, the person depicted receives
Further claims to compensation exist only where expressly agreed or provided for by law.
8. Use by the person depicted
- The person depicted may use the Recordings provided to them for private purposes.
- The person depicted may also use the Recordings for their own portfolio and social media channels.
- No own use agreed.
Copyright and any other rights of the photographer or other rights holders remain unaffected.
9. Data protection
The person depicted has been informed who is responsible for processing their personal data and for which purposes the data and Recordings are processed.
Where the GDPR applies, the full privacy information under Art. 13 GDPR was provided before this agreement was concluded and is available at:
It sets out in particular the legal bases, recipients, storage period or the criteria for it, data subject rights, and how to get in touch.
Where processing rests on consent under data protection law, the rights provided for by law remain unaffected, in particular the right to withdraw consent with effect for the future.
10. Contact for questions or changes
Questions about the agreed use or the processing of personal data can be directed to:
11. Governing law
Rules on the right to one's own image, and the form requirements that go with them, are set nationally. Name the law that applies to this agreement:
Should individual provisions be or become invalid, the validity of the remaining provisions is unaffected.
12. Consent and signature
I have read and understood the agreement above. The scope of the permitted use was communicated to me before the agreement was concluded.
Person depicted
Licensee
If concluded digitally
The confirmed version of the agreement is made permanently available to both parties.
Download PDF · Download Word template · Have it signed digitally
Who is this template for? Adults, in typical photo and video productions. For minors, employee photos, and unusual productions you need a separate version — see special cases below. Because image rights are national law, section 11 asks you to name the governing law explicitly.
In the PDF and Word versions the note sits on its own clearly marked page: it is not part of the agreement and can be removed before use.
What is a model release contract – and when do you need one?
A model release contract (also called a model agreement or consent form) is the written agreement between you as the photographer and the person pictured about how their images may be used. It's relevant whenever a person in the image is recognizable and the shots are meant to be published or used commercially.
The legal framework rests on two pillars that apply across the EU:
- The right to your own image – as a rule, a person's likeness may only be published with their consent. National law varies across the EU, and most jurisdictions recognize exceptions to that rule (more on those below).
- The GDPR, because a photo of an identifiable person is personal data, and processing it needs a legal basis (overview of personal data and consent under GDPR).
In short: for planned portfolio, social media, or advertising use, a clearly documented model release is the cleanest route in practice – because it records the scope of the permitted use and gives you proof of what was agreed to.
When do I need a model release – and when not?
The blanket rule "recognizable face, therefore always consent" is convenient as a rule of thumb but legally too crude. National image-rights law across the EU generally states the consent principle and then recognizes exceptions to it.
A model release is typically the right route for:
- staged portraits for a website, portfolio, or self-promotion
- advertising campaigns, corporate brochures, and paid ads
- social media posts featuring recognizable people
- shots handed over to an end client
- images submitted to a stock agency
Not automatically the same situation – here an exception may apply, depending on the jurisdiction:
- people who appear only incidentally alongside a location or landscape
- images of public assemblies and processions the subjects took part in
- certain situations involving matters of legitimate public interest
- images serving a higher artistic interest
Two caveats matter. First, these exceptions are not unlimited: they typically fall away where a legitimate interest of the person depicted is harmed. Second, the exception has to genuinely apply in the specific case – "taken at an event" does not mean any individual portrait from it can later be used freely in advertising. The moment an event shot becomes an advertising asset, you leave the ground those exceptions cover.
Because the details are set nationally, the specifics differ between EU member states. In Germany the framework is §§ 22 and 23 KunstUrhG; Spain regulates it in Ley Orgánica 1/1982; other member states have their own rules.
Separately from image rights, the GDPR layer still has to be assessed: even where publication would be permissible, processing the image needs a legal basis.
What belongs in a model release contract? (Checklist)
A solid agreement covers more than just "may be published." These points should be included:
- The parties: name and address of photographer and model; for minors, the legal guardians.
- Scope of use: where may the images appear – print, website, social media, advertising?
- Duration and territory: unlimited or restricted in time and geography?
- Sharing with third parties: may the images be passed to clients or agencies?
- The model's own use: may the model use the images themselves, e.g. for their own portfolio?
- Compensation: fee, TFP (time for prints), or free of charge – what was agreed?
- Data protection notices: information about the processing under GDPR and the pictured person's rights.
- Date and signature from both sides.
As a starting point, you'll find well-founded templates and explanations from specialized sources. But always adapt such a template to your specific use case rather than using it blindly.
Consent or contract: which GDPR legal basis applies?
One point often causes confusion in practice: does the processing rest on consent or on a contract? The difference matters more than it sounds – and it is frequently oversimplified.
- Consent (Art. 6(1)(a) GDPR) is the classic form of agreement. It can be withdrawn with effect for the future; the lawfulness of processing carried out before the withdrawal is not affected.
- Contract (Art. 6(1)(b) GDPR) requires that the processing be necessary for the performance of an actual contract. That necessity is the decisive hurdle.
Here lies a common misconception. The reasoning "I'll just call the document a contract, and the withdrawal problem goes away" does not hold. It is not enough to dress consent up in the outward form of a contract – what gets assessed is whether a contract genuinely exists and whether the specific processing is necessary to perform it. Relabeling the document does not move the legal basis.
A model release can contain both: contractual terms on use and declarations that matter under data protection law. But it does not follow that every act of image processing can rest on (b) simply because the paper says "contract." Which basis actually carries in a given case depends on the shoot, the agreed use, and how the arrangement is set up.
For practice this means: describe the use specifically, make data protection transparent – and don't rely on the document's title to settle the legal basis.
What happens if the model withdraws consent?
Where processing rests on consent, Art. 7(3) GDPR expressly provides that it may be withdrawn at any time, and that withdrawing must be as easy as giving it. Two points matter in practice:
- Withdrawal takes effect going forward. The lawfulness of processing carried out before the withdrawal, on the basis of that consent, is not affected. A brochure already printed does not become unlawful retroactively.
- You need to be organizationally ready for it. When a withdrawal comes in, you have to know which images are affected and where they are in use. That is where this usually breaks down in practice – not because the law is complicated, but because nobody can remember which campaign the shot ended up in.
So a durable model release process is not just the document. It is also a filing system in which the image, the scope of use, and the consent can still be found together later.
Special cases: minors, TFP, and handing images to a client
The template above covers the standard case. These three constellations each need their own treatment:
Minors. Capacity to consent and authority to represent have to be assessed in the specific case — often the legal guardians' declaration is required, depending on the situation from both parents. No blanket age threshold can honestly be given. Don't use a shortened version of the standard template here; use one with its own fields for the guardians. Where images of minors are used commercially, a legal review is advisable.
TFP (time for prints). Here the consideration is not a payment but the delivery of images. That belongs explicitly in the compensation clause — which images the model receives, at what resolution, by when, and what they may do with them. Section 8 of the template ("Use by the person depicted") is not an optional tick box in a TFP deal; it is the core of the agreement.
Handing images to a client. The case templates found online most often miss: photographers are frequently not the end users of the images. So the decisive question is not only "may I publish this photo?" but "may I pass it to my client for the agreed use?". Section 5 of the template covers exactly that — and separates service providers who merely contribute technically from third parties who would receive rights of their own.
Common mistakes with model releases
These mistakes come up again and again in practice – and are easy to avoid:
- Agreed only verbally. Verbal consent can be valid – the problem is not validity but provability. Without documentation you cannot show that consent was given, or how far it went.
- Too vague. A blanket "may be used" without naming the channel, duration, and purpose is open to challenge.
- Overlooking minors. With minors, capacity to consent and authority to represent have to be assessed in the specific case – often the legal guardians' declaration is required. The release should provide separate fields for it.
- Forgetting data protection. Beyond the contract, pictured people must be informed about the data processing and their rights.
- No clean record. A slip of paper somewhere in a folder helps little when, two years later, you have to prove who agreed to what and when.
Capturing a model release digitally: paper vs. attached to the project
The last mistake – the missing clean record – is most elegantly solved by not running the model release on paper at all. The comparison shows why the digital route wins:
| Aspect | Paper form | PDF by email | Digital, on the project |
|---|---|---|---|
| Record findable | Slip in a folder | Search the inbox | Stored right on the project |
| Signing on-site | Only with a printer | Cumbersome | On the phone in seconds |
| Link to the images | Manual | Manual | Automatically connected |
| GDPR notices | Attach separately | Attach separately | Integrated |
Digital means, concretely: on set you show a link or QR code, the model reads the text, agrees, and signs right on their phone. The release then sits cleanly on the right project – not in a filing folder and not scattered across the inbox.
That's exactly what model release at Exportlab provides: consent is captured digitally and connected directly to the corresponding shots and the contract workflow. And if you also want to know how to hand over the finished images professionally, our post on delivering photos to clients helps.
FAQ: Model release contract
When do I need a model release contract?
For staged shots you intend to publish or use commercially – portfolio, website, social media, advertising, stock – a model release is the right route. For purely private shots without publication you generally don't need one. And there are situations in which national image-rights law recognizes an exception to the consent principle, for example people appearing only incidentally alongside a location, or images of public assemblies. Those exceptions do not apply automatically, and they do not cover advertising use.
What is the difference between a model agreement and a model release?
In practice the terms are used more or less interchangeably. "Model agreement" leans toward the arrangement about the shoot itself – date, deliverables, compensation. "Model release" leans toward clearing the images, meaning the permitted scope of use. Often both sit in one document. What matters is not the label but that purpose, channels, duration, territory, and any sharing with third parties are set out concretely.
Is there a model release form as a PDF or printable template?
Yes – a fillable form is genuinely useful on set, because you don't have to draft the wording each time. What matters is that the template does not sweep up "all purposes, worldwide, in perpetuity" by default, but offers selectable fields for purpose, channels, territory, and duration. A form full of free-text boxes nobody fills in ends up documenting less than a template with clear options.
What has to be in a model release contract?
At minimum: the parties, the permitted scope of use (channels, duration, territory), any sharing with third parties, the compensation, data protection notices under GDPR, and the date and signature of both sides. For minors, additionally the consent of the legal guardians.
Is verbal consent enough?
Verbal consent can be legally valid – there is generally no written-form requirement for publishing a likeness. The risk is therefore not in its validity but in the proof: if a dispute arises, you have to be able to show that consent was given and how far it went. Under the GDPR that burden sits with the controller where processing rests on consent. A written or digital agreement protects both sides.
Is a digital model release legally valid?
A model release does not have to happen on paper simply because it concerns rights in images. The GDPR expressly recognizes electronic declarations as a possible form of consent, provided they are freely given, informed, and unambiguous – silence or pre-ticked boxes do not qualify. How well a digital declaration holds up depends on its content, the legal basis, and any applicable form requirements. Where the law demands genuine written form, the electronic substitute has to meet specific requirements (in Germany, § 126a BGB; eIDAS governs signature levels across the EU, and only a qualified electronic signature is treated as equivalent to a handwritten one).
What applies with minors?
With minors, capacity to consent and authority to represent have to be assessed in the specific case. Often the legal guardians' declaration is required, depending on the situation from both parents. No blanket age threshold can honestly be stated here – it depends on the minor's capacity and the intended use. The release should provide separate fields for the guardians and their declaration; for images of minors used commercially, a legal review is advisable.
Conclusion
A model release contract is the foundation for publishing images of recognizable people on a documented basis. It records who agreed and to what extent – and addresses both layers, image rights and the GDPR, when it describes the use specifically and makes data protection transparent. You avoid the most common mistakes – verbal deals, vague wording, missing records – most reliably by capturing consent digitally and documenting it right on the project. That way you always have proof at hand, without digging through a filing folder. This post is not legal advice, but it gives you the structure to approach the topic cleanly.
