14 NOVEMBER 2026 · UPDATED 18 NOVEMBER 2026 · STORAGE · BUSINESS · CONTRACTS

How Long Should You Actually Keep a Client's RAW File?

Twenty-five weddings a year at 140 GB each (the storage calculator gives the figure for your camera) is 3.5 TB of new files every season. Keep all of it in the cloud forever and by year ten you are paying to store 35 TB, which at Backblaze B2’s $6.95 per TB per month is about $243 a month, or $2,919 a year, for one offsite copy of jobs you delivered and were paid for years ago.

“Keep everything forever” feels like the safe, professional answer. It is the expensive one, and most of what it keeps is a file no client will ever ask for. The cheaper answer is a written policy: finals kept long term, RAWs kept for a fixed window, and the client told which is which before they sign.

What a client actually comes back for

Think about the requests you get a year or more after delivery. A couple lost the USB drive. A parent wants a canvas of one frame for an anniversary. Someone’s laptop died and the download link expired. Every one of those is a request for a finished image, not a RAW file.

The RAW is the negative. It matters while you are culling and editing, and for a while after, in case a client spots a problem with a delivered edit or wants a black-and-white version of a frame you left in colour. Past that window, the honest reasons to keep a RAW are yours, not the client’s: a portfolio re-edit, a future stock sale, or an award entry. Those are real reasons, but they apply to a handful of frames per job, not all 2,500.

That gap is the whole basis of a retention policy. The two kinds of file have different jobs, so they get different lifespans.

The size difference is huge

On a 45 MP body, a 2,500-frame wedding is about 112 GB of RAWs and 130-150 GB all-in once catalog previews and working exports are counted. The delivered gallery is a fraction of that. A typical 700-image wedding gallery exported as full-size fine JPEGs at about 15 MB each is roughly 10 GB.

So of the 140 GB a wedding takes up, around 130 GB is RAW files and working material, and around 10 GB is what the client actually received. Cut the 130 and keep the 10, and the long-term archive for that job shrinks by more than 90%.

Three policies, costed

Same business in all three: 25 weddings a year, 140 GB each, about 10 GB of finals per wedding, one cloud copy on Backblaze B2 at $6.95 per TB per month. The figures are the cloud bill in a given year, using the archive size at the end of that year.

Policy 1: keep everything forever. The archive grows by 3.5 TB a year and never shrinks.

  • Year 1: 3.5 TB, about $292 a year
  • Year 5: 17.5 TB, about $1,460 a year
  • Year 10: 35 TB, about $2,919 a year

Policy 2: RAWs for two years, finals forever. The RAW side levels off at two seasons’ worth, about 6.5 TB, and only the small finals pile keeps growing, by about 0.25 TB a year.

  • Year 5: 7.75 TB, about $646 a year
  • Year 10: 9 TB, about $751 a year

Policy 3: RAWs for one year, finals forever. The RAW side caps at one season, about 3.25 TB.

  • Year 10: 5.75 TB, about $480 a year

By year ten, the two-year policy costs about a quarter of “forever,” and the gap widens every season you keep booking. Switching providers does not fix this: Wasabi raised its pay-as-you-go rate to $7.99 per TB per month from July 1, 2026, which puts the year-ten “forever” archive at about $3,356 a year there.

And that is only the cloud copy. Your local archive has to hold the same terabytes on mirrored drives, so “forever” also means buying a new pair of drives every couple of seasons, which is the slope we costed in what a single wedding costs in storage. A retention policy shrinks both copies at once. Run your own camera, frame count and season through the storage calculator to see how big one year of RAWs is for you; that number, times the years you keep them, is what your policy is really deciding.

How long is long enough for the RAW

There is no industry standard for this. The window is yours to set, and the contract is where you set it. Pick it by what can still go wrong:

  • Until the gallery is accepted plus a few months. The minimum. It covers re-edit requests and a client who downloads late.
  • One year. Covers first-anniversary albums and the “can we get a few more edited” emails that tend to arrive in the first year.
  • Two to three years. Comfortable for most wedding work, and the archive still levels off instead of climbing forever.

Before a job’s RAWs go, pull the frames you want for your own use (portfolio, competition, anything you might license) into a small permanent folder. That costs a few gigabytes per job, not 130.

Put it in the contract

A retention policy only protects you if the client agreed to it. Without one in writing, “you deleted our photos?” is an argument about expectations, held years later, with no document to point to. It belongs next to the usage-rights clause in your contract, which is where we already suggest stating that RAWs are not part of delivery in the five clauses most photography contracts miss.

Plain-English starting wording, to fill in and have someone qualified where you work check:

Unedited RAW files are not delivered and are kept for [two years] after the gallery is delivered, then permanently deleted. Final edited images are archived by the Photographer for [ten years] as a courtesy, but this is not a guaranteed storage service. The Client is responsible for downloading and keeping their own copies of the delivered images.

Three details make that clause work:

  1. A start date. “Two years after delivery,” not “two years,” so there is no doubt which day the clock starts.
  2. “Courtesy,” not “guarantee.” Long-term storage of finals is a favour you do, not a paid service you can be held to. If you do want to sell it, price it as an add-on.
  3. The client keeps their own copy. Say it in the contract, and again in the delivery email, along with when the online gallery link expires. On a rented gallery that date is real: the page goes dark when the plan lapses. A gallery you host yourself, the kind Shutterbench Gallery builds, stays up until you take it down, and the client still keeps their own copy.

Then do the deleting. A policy nobody follows is just a sentence in a PDF. Put one calendar reminder a year to clear the RAWs for every job past its window, from the local archive and the cloud copy alike, and note the deletion date in your job records in case a client asks.

The short version

Keep finals long term, they are small and they are what clients come back for. Keep RAWs for a fixed window that covers the re-edit requests you actually get, one to three years for most working photographers. Write both numbers into the contract before the shoot. The archive stops compounding, and the bill stops climbing every season.

If cost breakdowns like this are useful, they turn up now and then in our field-notes emails.

JOB TICKET · MAILING LIST

Get new instruments first

The first one has the whole bench in it. After that, a short note when a new instrument lands or Gallery gets a real update - nothing else, and one click leaves.