Should Photographers Deliver RAW Files to Clients?

Should Photographers Deliver RAW Files to Clients?

Not by default. Most photographers deliver edited final images and hand over RAW files only when the contract says so, the client has a real reason to need them, and the price and licence reflect that. Handing over a RAW file does not transfer copyright, but it does give up control over how the image looks and where unfinished versions end up.

What a RAW file is and why clients ask for it

A RAW file holds unprocessed or minimally processed data taken directly from the camera sensor. The Library of Congress format description of Adobe’s Digital Negative (DNG) specification explains that, unlike JPEG or TIFF files, camera raw files must be processed before use, typically in software from the camera maker or in a converter such as Adobe Camera Raw.

Clients usually ask for RAW files for one of three reasons (this is editorial analysis, not survey data): they want everything they paid for, they want to select or edit images themselves, or they work with a retoucher or agency that expects source files. The right response differs for each.

The default: deliver finished images

The case for finished-only delivery is well established among working photographers. Photographer James Windsor, as summarised by PictureCorrect, argues that many clients lack software that opens RAW files, that files of roughly 20 to 25 MB each make a full session unwieldy, and that unedited images can misrepresent the photographer’s work. These are third-party opinions based on one professional’s experience, not rules. They do explain why “finished images only” is common, and why it should be written down before the shoot rather than argued about afterwards.

State the deliverable in the contract: the number of edited images or the selection method, the file formats and resolution, and a plain sentence saying unprocessed files are not included unless separately agreed.

When delivering RAW files makes sense

Delivering RAW files is reasonable when most of the following apply:

* The brief says the client or its retoucher will do the post-production, and the fee was set on that basis.

* The client is a commercial or editorial organisation with the software and workflow to handle RAW files.

* A written licence covers what the client may do with the files, and the fee reflects that extra use.

* The project is ending and the client is taking over the archive, as agreed in writing.

* You have kept your own untouched master copy.

If none of these apply, offer one of the alternatives below before agreeing to hand over source files. This checklist is editorial judgement, not an industry standard.

Delivering a RAW file does not deliver the copyright

This is the point many clients, and some photographers, get wrong. The following is legal information for the United States and the United Kingdom, not legal advice, and the rules in your country may differ.

In the United States, copyright vests initially in the author of a work (17 U.S.C. § 201(a)). Section 202 separates ownership of a copyright from ownership of any object in which the work is embodied, and says that transferring the copy in which a work is first fixed does not of itself convey rights in the work. Under section 204(a), a transfer of copyright ownership is not valid unless it is in writing and signed by the owner of the rights conveyed or their authorised agent. Section 201(b) makes the commissioning party the author of a work made for hire, so check how your contract treats that status.

In the United Kingdom, the British Copyright Council’s information sheet (last updated 1 June 2022) says the author is the first owner unless the work is made in the course of employment, and that copyright in freelance or commissioned work belongs to the author unless a contract says otherwise. It adds that a licence can set territory, media, duration and exclusivity, while an assignment must be in writing.

In practice, the licence attached to RAW delivery matters more than the delivery itself. Settle these terms in writing:

* permitted purpose and media;

* whether the client may edit, crop or retouch the files;

* credit and attribution;

* whether unedited files may be published;

* sub-licensing to agencies, printers or other contractors;

* term and territory;

* what happens to the files when the project ends.

For a contract template or a live dispute, consult a lawyer qualified in your jurisdiction.

Alternatives that answer the client’s real need

Match the response to the reason behind the request:

* The client wants more choice. Deliver a larger edited selection, or share a low-resolution proof gallery from which they pick extra frames for you to edit.

* The client wants to edit images themselves. Offer a paid licence for named frames, or full-resolution graded exports.

* A retoucher needs source data. Deliver RAW files for the selected frames only, under the written licence.

* The client wants an archive. Agree retention and handover terms at the start of the project.

A note on DNG: the Library of Congress describes DNG as a publicly documented format that can contain camera raw data. Converting to DNG therefore does not make a file less raw for licensing purposes. As a matter of editorial analysis, treat DNG as RAW in your contract.

Keep records before and after delivery

Whether or not you deliver RAW files, your masters are the source for any later record. A short routine:

1- Preserve the masters. Keep an untouched, read-only copy of the original RAW files. Certelo’s FAQ notes that software which rewrites background metadata can change a file’s bytes, and any change to the bytes changes the fingerprint.

2- Fingerprint before delivery. A SHA-256 hash is a fixed-length value computed from a file’s bytes. NIST’s Secure Hash Standard (FIPS 180-4) describes such digests as a way to detect whether a message has changed since the digest was generated. For a large shoot, you can compress the masters into one archive and fingerprint that, as Certelo’s FAQ describes for folders. Alternatively, you can fingerprint a text manifest listing each file name with its own hash; that second approach is an editorial suggestion.

3- Timestamp the fingerprint. Certelo calculates the SHA-256 fingerprint locally in your browser, does not upload the original file merely to create the proof, and anchors the fingerprint to the Electra Protocol blockchain. Certelo also offers a free demo certificate that is clearly marked as not blockchain proof, so you can try the workflow first.

4- Record the delivery separately. Keep the licence, the delivery message or platform log, and a list of exactly which files were sent. A timestamp does not show that anything was delivered.

5- Verify when needed. Anyone holding the file can recompute its hash and compare it with the recorded value and the blockchain record.

The result is evidence that a file with that exact fingerprint existed at or before the recorded blockchain time. Renaming a file does not change its hash, according to Certelo’s FAQ; re-saving, converting or exporting creates a different file with a different hash.

Hypothetical example (not a real case).

A photographer delivers 40 retouched images and, under a signed licence, 12 RAW frames for an agency’s in-house retoucher. Before delivery, she fingerprints and timestamps an archive of her masters and the RAW subset she is sending. Months later, the agency publishes an unedited frame in a way the licence did not allow. Her licence, delivery message, preserved masters and timestamped fingerprint help reconstruct what was supplied and when. They do not decide whether the use was authorised; the licence terms and the applicable law do.

What this record cannot show

A timestamped fingerprint has clear limits:

> Authorship. It does not identify who took the photograph.

> Copyright ownership. That depends on authorship, contracts and local law.

> Capture date. It shows when a matching file was recorded, not when the shutter was pressed. Embedded metadata can be edited or stripped, so treat it as context rather than proof.

> Delivery or acceptance. Other records show whether the client received the files.

> Future use. It does not stop a client from sharing files.

> Legal outcome or admissibility. Weight depends on the jurisdiction and the full facts.

It also does not replace a contract, copyright registration or legal advice.

A practical rule

Treat finished images as the product and RAW files as a separate, licensed deliverable that you offer deliberately. Put the choice in writing before the shoot, keep your masters untouched, and record exactly what you hand over.