Writing an AI clause into your photography contract

Decide what you actually do before you write anything

Most photographers cannot answer the question cleanly because they have never drawn the line for themselves. Do you use AI-assisted masking and noise reduction inside your raw developer? Almost certainly, and so does everyone else. Do you use content-aware removal to take a stray cable off a wall? Probably. Do you use a generative tool to replace a sky, extend a frame, or rebuild a background? That is a different category, and a client who says 'no AI' almost never means the noise reduction.

Write yourself a three-tier description: routine algorithmic processing that is part of every modern raw workflow; subtractive retouching that removes things that were physically present; and generative work that adds or synthesises pixels that were never captured. Almost every useful contract clause is really a statement about where in those three tiers you stop by default, and what happens when a client wants you to go further.

Doing this exercise also makes you honest in sales conversations. 'We use AI-assisted noise reduction and masking as standard, we remove distractions on request, and we add nothing generatively unless you ask in writing' is a sentence you can say without hedging, and hedging is what makes clients suspicious.

Language options for describing your editing

A workable clause has four parts: what standard editing means on your jobs, what falls outside it, who has to approve the outside-it work, and how it gets disclosed. Keep it short enough that a client will read it. Long clauses get skimmed, and a skimmed clause has not really been agreed.

The threshold you set should match your genre rather than a general principle. A commercial product photographer may reasonably use generative work routinely and needs a clause that permits it. A documentary or news photographer should be writing a clause that forbids almost all of it. A wedding photographer sits in between and usually lands on 'removal yes, addition only on request'.

Avoid absolute language you cannot honour. 'No AI is used in our workflow' is now false for almost everyone, because it is embedded in denoise, subject masking and autofocus. Promising it and then being asked to explain your denoiser is worse than describing your practice plainly.

• Standard finish: 'Editing includes exposure, colour, contrast and cropping, plus removal of temporary blemishes and minor distractions.'
• Threshold: 'Tools that generate new image content, including background replacement, sky replacement and object addition, are used only where the client requests them in writing.'
• Approval: 'Any image edited beyond the standard finish will be shown to the client for approval before delivery.'
• Disclosure: 'On request, we will identify which delivered images were edited using generative tools.'
• Opt-out: 'The client may elect a no-generative-editing delivery at no additional cost.'

Client opt-out, and making it real

An opt-out that costs the client money is not an opt-out, it is a tariff. If you offer one, price it the same, because the client choosing it is usually doing so for reasons of principle or professional obligation rather than taste. Editorial clients, NGOs, public bodies and anyone with an internal disclosure policy will take it, and they will remember that you offered it without a fuss.

Make the opt-out operationally real, which means it has to be visible in your workflow and not just your paperwork. Flag it on the job folder, put it in the same place every time, and check it before delivery. An opt-out that only exists in a contract you signed eight weeks ago is an opt-out you will breach on a busy delivery day.

Some clients will opt out of generative editing but still want the distraction removal. That is a coherent position and worth confirming explicitly, because 'no AI' from a client's mouth almost never maps precisely onto any line you have drawn.

The training question, and reading your own tool's terms

Increasingly, clients ask whether their images will be used to train models. This is a fair question, particularly for corporate portraits, medical settings, anything with children in it, and any brand with unreleased product in frame. You need to be able to answer it about every tool your files pass through, not just the one you think of as the AI tool.

That means actually reading the terms of your editor, your cloud storage, your gallery host and your file transfer service. The relevant language is usually in the privacy policy rather than the terms of service, and the phrase to hunt for is what rights you grant over uploaded content and for what purposes. If you cannot find a clear answer, ask the vendor in writing and keep the reply. A vendor who will not answer that question in writing has told you something.

Then write your own commitment to match what you can actually deliver. Promising a client that their images will never be processed by a third party is a promise most workflows break the moment a file touches a cloud service. A more honest clause names the categories of vendor you use and commits you to selecting ones that do not claim training rights over client images, plus a commitment not to upload flagged-confidential material to any external tool at all.

Where AI editing belongs on a professional job, and where it does not

It is worth being blunt about scope, because a contract clause written on a misunderstanding of the tooling will not survive contact with a real job. Per-image AI editors are useful for a small number of standalone frames: a single hero shot that needs a cleaner background, a salvaged frame, a quick visual to show a client the direction you have in mind. They are not gallery tools. There is no batch mode in Flora, no API, no automated pipeline, and running four hundred wedding frames through a per-image tool one at a time would be both slow and visually inconsistent across the set.

So a contract clause about generative editing is, in practice, a clause about a handful of images per job. Writing it that way is more accurate and easier to agree: the client is not being asked to consent to their entire gallery being reprocessed, they are being asked about the exceptions. Flora costs credits per edit, roughly five for an everyday look and around fifteen for a flagship one, which is another reason it belongs in the exceptions column rather than the workflow column.

Say this out loud in the booking conversation. Clients who are nervous about AI are usually imagining wholesale synthetic replacement of their photographs. Explaining that the realistic use is one or two frames and that you will show them those frames before delivery resolves most of the anxiety in a sentence.

Genre-specific traps

Editorial and news work: your client's own standards almost certainly forbid content alteration entirely, and their standards override your contract. Your clause should say you will comply with the commissioning publication's ethics policy and that you will supply originals on request. Do not assume your usual retouching level is acceptable here.

Commercial and advertising: the risk shifts from truthfulness of the photograph to truthfulness of the claim. Advertising regulators in many countries take an interest in imagery that misrepresents a product's appearance or a result the customer can expect, and the specifics differ substantially between jurisdictions. Where the image is doing persuasive work about a product, put approval of the edited version in the client's hands in writing and check the relevant advertising code with someone qualified.

Portrait and wedding: the sensitivity is about the person, not the pixel. A clause that permits generative editing of people should be paired with a practice of asking the subject what they want left alone, and of never altering body shape, skin tone or permanent features without an explicit request from the person depicted. That belongs in your workflow whether or not it is in the contract.

Frequently asked