TL;DR: The photography AI prompts worth having are not the ones that make pictures. They handle the work around the shoot: enquiry replies, qualification, briefs, shot lists, permission admin, gallery notes, follow-ups, captions and portfolio copy. Generation earns a place in mood boards and set exploration, and nowhere near a delivered file.
Almost every page ranking for photography AI prompts is written for someone who wants a machine to produce a photograph. If you are a working photographer, that page is describing your job back to you and calling it a shortcut. You do not need help making images. You need help with the eleven hours a week that surround making them.
This page is organised the way a job is organised, from the first enquiry to the review request, with thirty prompts you can adapt. It assumes you know lighting, lenses and composition better than we do, and it does not explain any of them to you.
What do photography AI prompts actually do for a working photographer?
They write the structured, repetitive text that sits either side of a shutter press. That is a narrow claim and a large one.
Look at where a booked job actually goes. An enquiry arrives with half the information missing. You write back. You write back again. You build a brief, then a shot list, then a run of day. You chase a location permission. You deliver a gallery with a note explaining how to select. You chase the selection. You send an invoice, a follow-up, a review request. You write four captions and a portfolio page. Somewhere in there you photographed something.
Every item on that list except the last one is structured writing with a known audience and a known outcome. That is precisely the shape of work a language model is good at, and it is the shape of work that quietly eats a freelance week. A prompt template you have already tuned once turns each of those into a two-minute job.
The prompts below are written with square-bracket placeholders so you can fill them in and reuse them. Fill in the brackets, delete the lines that do not apply to your genre, and keep the version that worked. That is the whole method.
How do you handle an enquiry without writing the same email for the ninth time?
By separating the reply from the qualification. Most enquiry emails fail because they try to be warm, informative and diagnostic in one pass, and end up vague enough that the client answers none of the questions.
The pattern that works: a short human reply, then a small numbered set of questions you genuinely cannot proceed without. Three or four. Not a form.
1. Triage an incoming enquiry
You are helping a working [GENRE] photographer respond to a new enquiry.
Here is the enquiry, with identifying details removed:
"[PASTE ENQUIRY]"
Do three things:
1. Summarise what they have actually told me, in one line.
2. List what is missing that I cannot quote or plan without. Maximum four items.
3. Draft a reply of under 120 words: warm, specific to what they said, ending
with those questions as a short numbered list.
My tone: [e.g. friendly but businesslike, no exclamation marks, British spelling].
Do not invent any detail about my availability, packages or process. Where you
need one, write [PLACEHOLDER] and I will fill it in.
That last instruction matters more than it looks. Left alone, a model will cheerfully hallucinate a two-hour minimum, a turnaround time and a package name you have never offered, and the draft reads well enough that you send it.
2. Qualify scope without naming a number
Draft a reply that establishes the scope of this [GENRE] job without quoting any
price, day rate or package figure. I want to learn: hours needed, number of
locations, number of people to be photographed, where the images will be used
and for how long, and who else needs to approve.
Ask for those conversationally, not as a questionnaire. Under 140 words. Do not
include any numbers. Do not imply what my pricing is.
3. Turn a vague enquiry into a brief they will confirm
This is the highest-value prompt on the page. A client who confirms a written brief cannot later remember a different job.
Turn the notes below into a shoot brief written back to the client for
confirmation.
Notes: "[PASTE YOUR NOTES AND WHAT THEY SAID]"
Structure it as: Purpose · Date and call time · Location(s) · Who is being
photographed · Deliverables and quantity · Where images will be used ·
What is explicitly not included · What I need from you before the day.
Rules: every line must be either something they told me or a line reading
"TO CONFIRM:" followed by the open question. Invent nothing. End with a single
sentence asking them to reply confirming or correcting it.
4. Decline or refer a job that is not yours
Write a short, kind decline for a [GENRE] enquiry I am not the right
photographer for. Reason: [REASON, e.g. genre, date, budget shape, location].
Under 90 words. Do not apologise more than once. Do not explain my reasoning at
length. Offer to point them toward someone who does this work, without naming
anyone. Leave the door open for other work.
What does a good AI-written shoot brief and shot list look like?
Specific enough to argue with. A shot list that reads "candid moments, details, group shots" has told you nothing you did not know on the drive over. A useful one is bound to a clock, a place and a named person who has to be somewhere.
The model is not deciding what to photograph. You are. What it is doing is turning your decisions into a document that a second shooter, an assistant, a coordinator and a nervous client can all read.
5. The shoot brief
Write an internal shoot brief for a [GENRE] job.
Inputs: [DATE], [LOCATION], [DURATION], [SUBJECTS], [CLIENT'S STATED PURPOSE],
[DELIVERABLES], [KNOWN CONSTRAINTS].
Sections: Objective in one sentence · Non-negotiable shots · Nice-to-have shots ·
Constraints and hazards · Who to speak to on site · What "done" looks like.
Keep it to one page. No adjectives about mood or feeling. This is an operational
document, not a treatment.
6. The run of day
Build a run of day for a [DURATION] [GENRE] shoot at [LOCATION], starting
[TIME]. Fixed points: [LIST ANY FIXED TIMES].
Output a table: time block, what is happening, who is needed, where, and my
one-line note to self. Include realistic transitions between locations and a
buffer I can lose without losing a shot. Flag any block where the schedule
depends on something outside my control.
7. The shot list
Turn this brief into a shot list grouped by time block, not by category.
Brief: "[PASTE BRIEF]"
For each shot: a short label, who is in it, where, and a one-line note on why the
client wants it. Mark each as MUST or OPTIONAL. Do not specify lighting,
lenses or settings. Do not exceed [N] must-have shots.
The "do not specify lighting, lenses or settings" line is deliberate. Left to itself the model will pad a shot list with focal lengths pulled from nowhere in particular, and you will spend longer deleting them than you saved.
8. Kit and contingency
I am shooting [GENRE] at [LOCATION TYPE] on [DATE], conditions likely
[CONDITIONS]. Duration [DURATION]. Power available: [YES/NO/UNKNOWN].
Produce two lists: what could go wrong that is specific to this job, and the
question I should ask [WHO] before the day to close each risk. Do not produce a
generic camera-bag checklist. Assume I own and can pack my own equipment.
9. The second shooter sheet
Write a one-page instruction sheet for a second shooter on a [GENRE] job.
Cover: what I am covering versus what they are covering, the moments they own
outright, where to be at each fixed time, how we avoid being in each other's
frames, file naming and handover format [SPECIFY], and who they ask when
something changes.
Direct and readable. No pleasantries. They will read this on a phone at 6am.
Can AI write your model release and location permissions?
It can produce a draft to take to someone qualified, and it can explain a document you already use to someone who is about to sign it. Those are two genuinely useful jobs. Neither of them is "generate a release and use it."
This is not legal advice and these prompts do not produce legal advice. What your release needs to say depends on where you are, what the images are for, how long they will run and who the client is. The document that governs your shoot is your own contract. The people who can tell you whether it is adequate are your own adviser, your insurer, and whichever professional body you belong to. Bodies like the Association of Photographers, the American Society of Media Photographers, Professional Photographers of America and the British Institute of Professional Photography all publish member guidance on exactly this. Ask them, not a chatbot, and not this page.
10. Explain your own release in plain English
Below is the model release I already use. Do not rewrite it, do not improve it,
and do not comment on whether it is adequate.
"[PASTE YOUR RELEASE]"
Write a plain-English summary a subject can read in under a minute, in [N]
short bullets, covering: what they are agreeing to, where the images may appear,
how long that lasts, and what is not covered. End with one line telling them to
ask me anything they are unsure about before signing. Neutral tone. Do not
reassure, persuade or minimise anything.
11. Location and property permission request
Draft an email requesting permission to photograph at [PROPERTY / LOCATION] on
[DATE], for [PURPOSE], with a crew of [N] and equipment [LIST].
Include: what we will do, how long we will be there, what we will not do, what
we will restore, and an offer to supply proof of insurance and a risk assessment
on request. Ask what permissions or fees they require rather than assuming any.
Under 200 words. Polite, specific, easy to say yes to. Leave every detail I have
not given you as [PLACEHOLDER].
12. The pre-shoot information sheet
Write a pre-shoot information sheet for people being photographed at a [GENRE]
shoot.
Cover: what will happen on the day, roughly how long, what to bring or wear
[SPECIFY], what will be photographed, that a release will be provided separately,
and who to contact with questions.
Do not summarise or paraphrase the release itself, and do not state what rights
anyone has. Keep it to what happens on the day. Friendly, under 300 words.
How do you talk about money without sounding like a template?
By writing about scope, not about the number. The figure is yours, it goes in last, and no prompt on this page will suggest one. What generates well is the language around it: what is included, what is not, what happens when the job changes, and what the client is actually licensed to do with the pictures.
13. Scope into quote line items
Turn this scope into quote line items I will price myself.
Scope: "[PASTE SCOPE OR CONFIRMED BRIEF]"
One line per item, each with a short description of what the client receives.
Include a separate section listing what is explicitly excluded. Leave every
amount as [ ]. Do not suggest, estimate, benchmark or imply any figure,
percentage or rate. If you think something is missing from the scope, list it at
the end as a question rather than adding it as a line.
14. The scope-change conversation
The client has asked for [CHANGE] after we agreed [ORIGINAL SCOPE].
Draft a reply that: acknowledges the request without irritation, states plainly
that it is outside what we agreed, describes what it would take to do it well,
and asks whether they want me to send a revised quote. Under 130 words. No
figures. Not passive-aggressive. Not apologetic.
15. Usage and licensing in plain English
Here is the usage clause from my contract:
"[PASTE CLAUSE]"
Rephrase it for a client who is not a lawyer, keeping the meaning exactly. Do not
broaden it, narrow it, or add anything it does not say. Where the clause is
ambiguous, say so in a separate note to me rather than resolving the ambiguity.
Under 150 words.
That last constraint is the useful one. A model asked to simplify a contract clause will happily resolve an ambiguity in whichever direction makes the sentence cleaner. Ask it to flag ambiguity instead of smoothing it.
What should a gallery delivery note say?
More than "here is your gallery." A delivery note that tells the client how to select, by when, and what happens next removes most of the follow-up chasing that otherwise fills the fortnight after a shoot.
16. The gallery delivery note
Write the email that accompanies gallery delivery for a [GENRE] job.
Include: a warm one-line opener referencing [SOMETHING SPECIFIC ABOUT THE DAY],
the link placeholder, how many images, how to select [PROCESS], the deadline
[DATE] and what happens after that, download instructions [SPECIFY], and one
sentence on what they are licensed to do with the files, drawn only from
[PASTE THE RELEVANT CLAUSE].
Under 200 words. Do not describe the images as stunning, gorgeous or magical.
17. Chasing an unmade selection
The client has not made their selection [N] days after delivery and the deadline
was [DATE]. Write a follow-up that is friendly, makes it easy to act, restates
the one thing they need to do, and notes what happens if the gallery expires
[POLICY]. Under 80 words. Second reminder, so no apology for chasing.
18. The RAW files question
A client has asked for the RAW files. My position is [YOUR POSITION].
Draft a reply that states that position clearly, explains it in one short
paragraph in terms of what the client actually wants to achieve, and offers
[ALTERNATIVE, e.g. additional edits, a different crop, a higher-resolution
export] if that is what is behind the request. Under 120 words. Do not lecture
them about file formats. Do not be defensive.
19. Follow-up and review request
Write a follow-up sent [N] weeks after delivery of a [GENRE] job.
Two short paragraphs: one asking how the images have been used and whether
anything else is needed, one asking for a review on [PLATFORM] with a direct
link placeholder. Make the review ask specific: suggest they mention
[WHAT WOULD BE USEFUL TO A FUTURE CLIENT]. Under 110 words. Do not offer an
incentive of any kind.
Which marketing copy is worth generating?
The repetitive kind. Captions, alt text, portfolio page copy and the shoot write-up you keep meaning to publish. Not your about page, and not anything that carries your actual point of view, because that is the one thing on your site a competitor cannot copy.
The failure mode here is voice. Without samples you get warm, breathless, interchangeable copy that reads like every other photographer's feed that week. Give it your own writing to imitate, and if you write a lot of this, keep the voice description somewhere reusable rather than retyping it. That is what a saved context is for, and building a brand-voice context covers how to assemble one.
20. Captions in your voice
Here are four captions I wrote and liked:
"[PASTE 1]" "[PASTE 2]" "[PASTE 3]" "[PASTE 4]"
Describe the voice in those in three lines, then write [N] caption options for
this image: [DESCRIBE THE FRAME AND WHAT WAS HAPPENING].
Match the voice, including sentence length and punctuation habits. No emoji
unless my samples use them. No hashtags. Do not describe the light or the
composition back to me.
21. Portfolio page copy and alt text
For a portfolio gallery titled [TITLE], covering [WHAT IT IS], write:
1. A 40-word intro paragraph for the page.
2. Alt text for each image from these descriptions: [LIST].
Alt text rules: describe what is in the frame for someone who cannot see it,
under 125 characters, no "image of" or "photo of", no keyword stuffing, no
adjectives about quality. Name the location only if I have given it to you.
22. A blog post about a shoot
Write a 600-word post about a [GENRE] shoot for my site.
What happened: "[YOUR NOTES]". What was difficult: "[NOTES]". What I would do
differently: "[NOTES]".
Structure: what the client needed, one specific problem on the day and how it was
solved, and what the images were used for. Write it so another photographer would
find it useful and a prospective client would find it reassuring.
No portfolio-speak. Do not call anything a journey. Leave [IMAGE] markers where
a picture should sit. Use only the details I gave you.
23. Genre and city service page
Draft copy for a service page targeting "[GENRE] photographer in [CITY]".
Sections: who this is for, what a booking includes [FROM MY LIST: LIST],
what happens on the day, what you receive, and how to enquire.
Rules: no superlatives, no claims about experience, awards, client counts or
ratings unless I supply them, no invented testimonials, no "award-winning".
Mention [CITY] naturally where a real sentence needs it and nowhere else.
Can AI document your editing workflow and presets?
Yes, and this is the most underrated item on the list. Your edit is consistent because it lives in your hands. That works until you hire an editor, take a holiday, or come back to a series eight months later and cannot remember why the shadows were lifted that far.
Documentation is writing, and writing is the thing to hand over.
24. The edit recipe
Turn my description of an edit into a repeatable recipe another editor could
follow.
What I do: "[DESCRIBE YOUR PROCESS IN YOUR OWN WORDS, INCLUDING TOOL NAMES AND
ROUGH VALUES]".
Output as numbered steps in the order they are applied, with the intent of each
step in one line, and a note on what to check before moving to the next. Use only
the values and tools I gave you. Where I was vague, write "ASK NAFIUL" rather
than filling in a number.
25. Delivery and export specification
Write a delivery specification from these settings: [PASTE YOUR EXPORT SETTINGS
AND FILE NAMING CONVENTION].
Produce a table: deliverable, format, colour space, dimensions, naming pattern,
and where it goes. Add a short section on what a person checking the export
should verify before it goes out. Do not add deliverables I did not list.
26. The culling rubric
Help me write down how I cull [GENRE] work so it is consistent across jobs and
teachable.
My rough criteria: "[DESCRIBE THEM]".
Turn that into an ordered rubric: what gets cut in the first pass, what survives
to the second, and the tie-breaker when two frames are close. Phrase each rule so
someone else could apply it without asking me. Flag any rule that is really a
matter of taste rather than a rule.
Where does image generation genuinely help a photographer?
In the conversation before the shoot, and nowhere after it. There are three honest uses, and the honesty is in what they have in common: nobody is buying the generated pixels.
Mood boards and concept references. You are pitching a look. A generated frame gets a client to point at something and say "that, but warmer" faster than a Pinterest board of other photographers' work does, and it has the advantage of not being someone else's copyrighted image.
Backdrop and set-dressing exploration. Working out what the wall, the table, the props and the palette should be before you rent any of it.
Lighting previsualisation. Seeing roughly what a setup implies before you carry it up three flights of stairs. Roughly is the operative word.
| Use | Is it a deliverable? | What it is for |
|---|---|---|
| Mood board for a pitch | No | Agreeing a look with a client |
| Backdrop and set exploration | No | Deciding what to build or rent |
| Lighting previsualisation | No | Sanity-checking a setup before load-in |
| Anything in a client gallery | Never | — |
| Anything on a portfolio page presented as photography | Never | — |
You already know what a beauty dish does, what a 35mm does to a room, and what happens at f/1.4. None of that is the problem. The problem is that the model needs those things spelled out in words it responds to, which is a vocabulary question rather than a photography one. Two reference posts handle exactly that: lighting vocabulary for AI image prompts and camera and lens terms that change your AI images. Read them as phrasebooks, not as tutorials. If you shoot products, the product photography prompt generator covers that genre's shot types in detail, and background replacement prompting covers swapping a backdrop behind a real photograph you took.
27. Concept and mood reference
Concept reference for a [GENRE] pitch. Not a deliverable.
Scene: [WHAT IS HAPPENING], set in [PLACE], time [TIME OF DAY].
Light: [SETUP IN YOUR OWN TERMS], quality [HARD/SOFT], direction [DIRECTION],
ratio roughly [RATIO].
Palette: [COLOURS]. Wardrobe and styling: [NOTES].
Framing: [SHOT SIZE], [FOCAL LENGTH] equivalent, [ORIENTATION].
Subject: an unnamed, non-identifiable person, face turned away or out of frame.
Exclude: legible text, brand marks, any recognisable individual.
28. Backdrop and set-dressing exploration
Empty set reference. No people in frame.
Space: [ROOM OR LOCATION TYPE], [DIMENSIONS OR FEEL].
Surfaces: floor [MATERIAL], walls [MATERIAL AND COLOUR], backdrop [DESCRIPTION].
Dressing: [PROPS], arranged [HOW].
Light: [WINDOW/PRACTICAL/STUDIO], direction [DIRECTION], quality [QUALITY].
Camera: [SHOT SIZE] at [FOCAL LENGTH] equivalent, [HEIGHT].
Exclude: people, text, brand marks, visible lighting equipment.
29. Lighting previsualisation
Previsualisation of a lighting setup, for my own reference only.
Subject: a featureless mannequin or plain form, [POSITION], [DISTANCE] from
background.
Key: [MODIFIER] at [ANGLE] and [HEIGHT]. Fill: [MODIFIER OR NONE] at [RATIO].
Rim or hair light: [DESCRIPTION OR NONE]. Background light: [DESCRIPTION OR NONE].
Background: [COLOUR/MATERIAL] at [DISTANCE].
Show me the shadow behaviour and falloff this implies. Neutral colour.
Exclude: any human face, any identifiable person, text.
30. A look pitch for a client
I need three visually distinct directions for a [GENRE] job so the client can
choose one. Brief: "[PASTE BRIEF]".
For each direction give me: a two-word name, one sentence describing the look in
plain language, and a complete image prompt following this shape: scene, light,
palette, styling, framing, exclusions.
Every prompt must specify that people are non-identifiable and must exclude
legible text, brand marks and any real individual. These are pitch references,
not deliverables, and I will label them as such.
What must never come out of a generator?
Two things, and both of them are sharper for you than for most people who use these tools.
A real, identifiable person. Not the client. Not the client's child. Not the celebrity the client keeps mentioning. Not you, in a portrait you plan to pass off as a self-portrait. Every major vendor restricts this in its own terms: Google's Generative AI Prohibited Use Policy lists "Impersonating an individual (living or dead) without explicit disclosure, in order to deceive." alongside conduct that "Violates the rights of others, including privacy and intellectual property rights" (policies.google.com, Generative AI Prohibited Use Policy, last modified December 17, 2024, accessed August 29, 2026). For a photographer that policy line is the least of it. Likeness, releases and portfolio rights are the substance of your business. A generated face has no release behind it and never will.
A generated image presented as a photograph. It is not a photograph. It is a plausible arrangement of pixels that resembles a photograph, and delivering one as your work is a professional problem before it is anything else. The technical position is not even ambiguous any more: Google's Gemini API image generation documentation states that "All generated images include a SynthID watermark" (ai.google.dev, Gemini API image generation, accessed August 29, 2026), so the provenance of a generated file is machine-detectable and getting more so.
How do you keep client information out of a chat tool?
By stripping it before you paste, every time, until it is a reflex.
The material in your inbox is not yours. Names, addresses, venue details, phone numbers, wedding dates, corporate campaign plans and unreleased images are things you are holding on someone else's behalf, usually under a contract that says so. Pasting a client's enquiry into a chat window to get a faster reply is a small act with a real risk attached.
The fix is mechanical. Replace before you paste, restore after you copy:
Sarah and Michael -> [CLIENT_1] and [CLIENT_2]
The Old Barn, Hitchin -> [VENUE]
14 June -> [DATE]
Nova Robotics product launch -> [CLIENT_COMPANY] [EVENT]
+44 7700 900123 -> [PHONE]
Write the prompt against placeholders, get the draft back, then substitute the real values in your own email client where they belong. This has a second benefit: a prompt written against placeholders is reusable, which is the entire point of keeping a library rather than a chat history.
The short version
Nothing on this page will make you a better photographer, and none of it is trying to. The pitch is narrower and more useful than that: the writing around a shoot is a real, unpaid job inside your paid job, and it is the part of your week that a language model handles well.
Take four or five of these, fill in your own brackets, and save the versions that survive contact with a real client. That is a working library, and it compounds. Prompt Architects exists to keep those tuned versions somewhere you can find them across ChatGPT, Claude and Gemini instead of scrolling back through a chat window, and to generate the image prompts for the mood-board work when you need them. It does not take photographs. That was always going to be your job.
Stop rewriting prompts. Start shipping.
Works with ChatGPT, Claude, Gemini, Grok, Midjourney, Ideogram, Veo3 & Kling. 5.0★ on the Chrome Web Store.
Create An Account