The debate over RAW file delivery runs the same way in every photography forum: principled refusal on one side ("they're not the finished product"), pragmatic accommodation on the other ("just charge enough and say yes"). I've spoken to photographers on both sides while building ComoSelect. The honest conclusion is that neither position is universally right — the answer depends on who's asking and why, and most of the time, a request for RAW files is a symptom of a different concern entirely.
Here's the reasoning behind the standard professional "no," the cases where yes genuinely makes sense, how to price it if you decide to offer it, and the exact language for handling the conversation without damaging the relationship.
A RAW file is unprocessed sensor data — flat, desaturated, and often deliberately exposed for later recovery rather than for immediate viewing. The camera's JPEG preview embedded in the file looks nothing like the final edited image. Your editing isn't a filter applied at the end; exposure choices, color decisions, and processing style are planned from the moment you frame the shot. Delivering RAWs is delivering half a product and asking the client to finish it without the tools, software, or skills you spent years developing.
The analogy clients understand: a restaurant doesn't send you home with the raw ingredients of the dish you ordered.
When a client — or their cousin with a cracked copy of Lightroom — processes your RAW files badly and posts the results tagged with your name, that's your portfolio in the wild. You have no control over the most public representation of your work. For photographers who build their business through social media and word-of-mouth referrals (which is most photographers), this is a meaningful business risk, not just an aesthetic preference.
In most cases, a RAW request isn't really about the files themselves. After talking to dozens of photographers who've handled this conversation, the underlying concern is almost always one of three things: the client wants more images than the package included, they want insurance against losing the photos long-term, or they're worried the editing won't match their taste. Each of those has a better solution than handing over sensor data — solutions that are better for both parties.
"The RAW files aren't finished images, but if you'd like more edited photos than the package includes, I offer additional images at €X each — you can pick exactly the ones you want from your proof gallery." This converts a friction point into revenue. A clean proofing gallery where clients browse your culled selects and flag the ones they want makes this conversation easy. See our guide on client photo selection for how this workflow operates in practice.
"Your full edited gallery is yours to download in high resolution, and I archive every project — if you ever lose your copies, write me and I'll re-deliver within [X time]." State clearly how long you archive. For delivered finals, keeping them indefinitely costs almost nothing in storage and creates enormous goodwill. This answer addresses the actual concern without any loss of quality control.
This is feedback, and it's more useful before booking than after delivery. If it comes up during the booking process, show more of your portfolio — specifically images from similar shoots in similar lighting — so the client understands exactly what they're getting. If the mismatch comes up after delivery, offer one round of global adjustments: brighter, warmer, less contrast. Style concerns are prevented at booking, not fixed with RAW files.
The "never" position you see in photography forums is too rigid. There are legitimate cases, and they all share one characteristic: the recipient is a professional with their own processing pipeline.
| Situation | RAW delivery appropriate? | Why |
|---|---|---|
| Wedding / portrait end clients | Generally no | No in-house pipeline; edited JPEGs are the product |
| Commercial / advertising clients | Often yes | In-house retouching team with defined pipeline |
| Editorial / magazine work | Sometimes | Art directors retouch for specific print requirements |
| Work-for-hire contracts | Yes, if agreed | Copyright transfers; deliverables defined in contract |
| Second-shooter to lead photographer | Yes | Standard industry practice for studio workflows |
| Archival / legal documentation | Sometimes | Unaltered originals required for evidentiary purposes |
The pattern: RAW delivery belongs in professional-to-professional workflows, not in photographer-to-end-client delivery. Your contract should specify this clearly at booking.
Some photographers offer RAW delivery as a premium add-on for clients who genuinely need it, and that's a legitimate business choice. But the pricing has to reflect what you're actually giving up.
When you deliver RAW files, you're providing: all captured frames (not just edited selects), an unlimited usage license for unprocessed files, ongoing exposure to how those files will be used, and the loss of the quality-control layer that protects your reputation. That's worth real money.
Common pricing structures:
If the number feels uncomfortable to say out loud, that's exactly the point. It should be priced high enough that saying yes compensates you fully — for the files, the license, and the loss of control over your output.
The least expensive way to handle the RAW question is to answer it before anyone asks. One sentence in your contract and pricing materials:
"Deliverables include professionally edited high-resolution JPEG images. RAW and unprocessed files are not included in any package and are not available for separate purchase."
Or, if you're open to selling them for commercial work: "RAW files are available for commercial engagements by prior arrangement at a separate rate." Either way, the client learns the answer at booking, when the stakes are low — not after delivery, when a refusal feels personal.
This is one of the clauses that belongs in every photography contract and gets forgotten until it's needed.
A clear proofing step prevents most of these conversations: the client sees every usable image in a private gallery, flags the ones they care about, and knows exactly what they're getting before final delivery. ComoSelect handles this — free, no client account needed.
A flat "no, I don't do that" reads as defensive and closes the conversation. A better approach is to acknowledge the request, explain briefly, and redirect to what you can offer:
"RAW files are the unprocessed files straight from the camera — they look flat and unfinished without editing software, so they're not really useful as a standalone deliverable. What I can do is [offer additional edited images / share a proof gallery so you can choose which ones to add to your package / re-deliver your gallery if you ever lose your copies]. Would any of those help?"
This response takes fifteen seconds longer than "no" and converts a refusal into a solution. Most clients accept it immediately once they understand what RAW files actually are.
Should photographers give clients RAW files?
Generally no. RAW files are unprocessed sensor data — not a finished product. The editing is part of what clients are paying for. Standard deliverables are fully edited JPEGs. Exceptions include commercial work with in-house retouching pipelines, or work-for-hire arrangements where copyright transfers to the client.
Why do photographers not give RAW files?
Three main reasons: RAW files are unfinished and look nothing like the final edited image; if a client processes them badly and posts them publicly, that reflects on the photographer's reputation; and most RAW requests actually signal a different concern — more images, archive access, or style mismatch — that has a better solution.
How much should photographers charge for RAW files?
If you offer RAW delivery, price it at 1.5–3x the session fee or a substantial flat rate. This reflects the unlimited usage license, loss of quality control, and ongoing liability for how the images are used. If the number feels uncomfortable to say, that's the point — RAW delivery should compensate fully for what you're giving up.
What do clients actually mean when they ask for RAW files?
Usually one of three things: they want more images than the package includes; they want archive insurance against losing files long-term; or they're worried the editing style won't match their taste. Each has a better answer than RAW files: an upsell option, a clear archive policy, or a better style consultation before booking.
Can a client legally demand RAW files?
Not unless the contract specifies RAW delivery. In most jurisdictions photographers own copyright by default, and deliverables are whatever the contract states. If your contract says "high-resolution JPEG images," that is the agreed product. Clients cannot unilaterally demand something not included in the signed contract.
A private proof gallery where clients select exactly the images they want — and you sell additional edits without friction. Free forever.
Try ComoSelect free