Should Photographers Send RAW Photos to Clients?

Sooner or later a client asks for the RAW files. Sometimes they say RAW and mean it. Sometimes they say RAW and mean everything you shot. Those are two different requests, and answering the wrong one is how the conversation goes badly.

What a RAW file is, in client terms

A RAW file is the unprocessed data straight off the sensor. It is not really an image yet. It has no baked-in colour treatment, no contrast curve, no sharpening. Software has to interpret it before a human sees anything, and different software interprets it differently.

Practically, that means a RAW file is large, needs specific software to open properly, looks flat and lifeless without processing, and will render differently depending on who opens it and where. It is a working file, in the same way a layered project file is a working file for a designer.

Why most photographers do not deliver RAW files

They are not finished work

The edit is not a filter on top of the photograph. Colour, contrast, exposure balance and retouching are how the image becomes what you intended. Handing over the RAW is handing over the ingredients and calling it dinner.

They will be processed by someone else, badly

Once the file leaves, someone will open it in whatever they have, push a slider, export it, and put it online with your name attached. That is a real reputational cost.

They are impractical to send and to open

A single frame can be 25 to 80 megabytes. A full shoot is tens of gigabytes. Most clients cannot open the files once they arrive, then ask you to convert them anyway.

Rights and pricing

In most jurisdictions the photographer owns the copyright unless a contract says otherwise, and what the client buys is a licence to use the finished images. Original files are usually outside that. This varies by country and by contract, so treat it as a reason to check your own agreement rather than as legal advice.

Support you did not price for

The file goes out and the questions come back. Why does this look grey, why will it not open, can you make it a JPEG. That work is unbilled.

When sending RAW files is reasonable

It is not always the wrong answer:

• The contract says so. Some commercial and agency work is bought that way, and the fee reflects it.
• Work-for-hire arrangements. Where the client owns the output outright and both sides agreed at the start.
• There is a retoucher on the other side. If the client has their own post team, they want the data, not your interpretation, and they know how to handle it.
• Archival or documentation work. Museums, heritage and scientific projects often need the originals as the record.
• You are paid for it. A licensed RAW handover priced as its own deliverable is a legitimate product.

The request behind the request

Most of the time the client is not asking for sensor data. They are asking for one of these things:

• They want to see everything you shot, because the gallery felt small.
• They want more images than the package included.
• They want to choose which photos get edited.
• They want a different crop or a different look.
• They are worried something good got left out.

None of those require original files. All of them are solved by letting the client look at low-resolution proofs of the usable set. That distinction between seeing everything and receiving everything is the entire subject of what to do when a client wants to review photos before you edit.

Better answers than yes or no

Offer a proofing gallery

Show web-sized previews of everything usable and let them mark what they want. They see the full range, you keep the originals and the final edit. How that workflow runs is covered in photo proofing for photographers.

Offer additional edited images

If the real request is more photos, price extra finished images. Everybody understands that transaction, and the client ends up with something usable.

Offer lightly processed JPEGs

A neutral batch export of the wider set gives volume without pretending to be your finished work, and without handing over the negatives.

Explain the edit

A short, non-defensive explanation goes a long way: the RAW file is closer to an undeveloped negative, and the editing is where the photograph actually gets made.

Handle it in the contract, not after the shoot

Every argument about RAW files is easier before the shoot than after it. Say in the agreement what the client receives, how many finished images, in what format, what happens to the originals, and what additional images cost. If you do offer RAW as a paid extra, put the price in writing there too.

Giving clients choice without giving up files

For Lightroom Classic photographers, the reason the proofing answer often loses to the just send the RAWs answer is friction. Exporting proofs, hosting them, collecting a list of picks and matching them back to the catalog is real work.

Clientpik removes that middle section. You publish a selection gallery from a Lightroom Classic collection, the client marks the frames they want, and those picks come back into your Lightroom Classic workflow ready to edit. The client gets to see and choose from everything usable, and you never hand over an original file. The mechanics are in how to let clients select photos from Lightroom Classic, and the delivery-method options are compared in the best way to send photos to clients for selection.

Saying no to RAW files is much easier when you have something better to say yes to.