How Long Should You Keep Wedding Files? The Answer Is a Limitation Period, Not a Storage Bill

How long you keep wedding files should be decided by how long you can still be sued over them, not by what storage costs. For breach of a written contract the limitation period is set by state statute and the spread is large: three years in North Carolina, four in California, six in New York, and ten in Illinois. A photographer who clears the archive at two years in a ten year state has destroyed their own evidence while the contract remains enforceable against them. Once the question is framed this way it stops being one question, because the paperwork and the images have very different costs and very different value in a dispute.

Search this topic and you will find storage maths. Terabytes, per-month rates, what to move to cold storage, a recommendation of two or three years that nobody sources. None of it engages with the only clock that carries a consequence, which is a matter of public statute and takes about five minutes to look up for your own state.

Why storage cost is the wrong question

Because it optimises the cheap half of the problem and ignores the expensive half.

The thing you are protecting against is not running out of disk. It is a phone call, years later, in which somebody asserts that you never delivered, or delivered late, or delivered something other than what was agreed. In that conversation, what helps you is evidence. If the answer to "can you show what you sent and when" is that it was deleted eighteen months ago under a policy you set for storage reasons, the storage saving turns out to have been the most expensive decision in the file.

That does not mean keep everything forever, which is the reflexive overcorrection. It means the retention period should be derived from the exposure period, and the exposure period is knowable.

How long can a couple actually sue you?

For a written contract, the outer window is fixed by statute in each state, and the variation between them is much larger than most photographers expect.

• North Carolina: three years. N.C.G.S. 1-52 opens "Within three years an action" and its first subsection covers an action upon a contract, obligation or liability arising out of a contract, express or implied.
• California: four years. Code of Civil Procedure 337 sets four years for an action upon any contract, obligation or liability founded upon an instrument in writing.
• New York: six years. CPLR 213 covers an action upon a contractual obligation or liability, express or implied.
• Illinois: ten years. 735 ILCS 5/13-206 provides that actions on written contracts shall be commenced within 10 years next after the cause of action accrued.

North Carolina to Illinois is a spread of more than three times. Two photographers with identical businesses, identical contracts and identical clients carry materially different exposure windows purely because of where they are. That single fact should be doing more work in this industry's advice than it currently does, and instead the standard recommendation is a flat two or three years offered to everybody.

The distinction that dissolves the question

Here is the move that makes this tractable, and it is the reason a single number was never going to be the right answer.

You are holding two completely different things, and the industry discusses them as one. The records are the signed contract, the payment history, the correspondence, and the evidence of what was delivered and when. The images are the delivered set and, if you keep them, the RAWs. They differ on every axis that matters:

• Cost. The records are text and a few PDFs, measured in megabytes. A single wedding's images run to tens or hundreds of gigabytes. Keeping records for ten years costs approximately nothing. Keeping every RAW for ten years is a real line item.
• Evidentiary value. In a dispute about whether you performed, the records are the argument. They establish what was promised, what was paid, what was sent and when. The images are secondary to that and the RAWs are usually irrelevant to it.
• Replaceability. Neither is recoverable once deleted, but only one of them is cheap to have kept.

So the policy falls out on its own. Keep the records for the full limitation period in your state, because it is nearly free and it is the part that defends you. Then make a separate, purely commercial decision about the images, informed by the same period but not enslaved to it. Keeping the delivered set for the full window is usually affordable and worth it. Keeping every RAW frame for a decade generally is not, and nothing in the analysis above says you must.

Note that this is the opposite of how the decision is usually made. Most photographers set an image retention number first, from storage cost, and never set a records policy at all, because the records were never in one place to have a policy about.

It is a Tuesday in a year you have stopped thinking about that wedding, and an email arrives that opens with a date and a tone. Something about the second album, or a set of photographs from the reception that were supposed to be there. You do not remember. That is not a failure of professionalism, it is four hundred weddings ago. What decides the next fortnight is not your memory and not your goodwill, it is whether the thread that settled it at the time still exists somewhere you can find it in ten minutes. If it does, this is an afternoon. If it does not, you are negotiating from nothing against somebody with a clear and sincere account of events.

What your own contract has already committed you to

Before setting any policy, read what you have already promised, because a contract term overrides your preference.

Two clauses matter. If your agreement promises the gallery will remain available for a stated period, that is an obligation with a date on it, and taking it down early is a breach rather than a housekeeping decision. If it promises archival or re-delivery, you have committed to holding files for whatever term you wrote, possibly indefinitely if you wrote it carelessly. Our piece on what belongs in a wedding photography contract covers the drafting side, and the delivery piece covers setting an availability window couples will accept.

The failure mode to avoid is treating gallery expiry as file deletion. They answer different questions. Expiry governs how long the couple can help themselves. Retention governs how long you can prove what you did. A studio that takes galleries down at ninety days and deletes at the same moment has aligned its evidence policy to a customer-service setting, which is an accident rather than a decision.

One further clock runs alongside these and is worth naming so it does not get conflated: business records kept for tax purposes follow their own requirements, unrelated to contract limitation periods, and are a question for the preparer who handles your returns. Three different clocks, three different lengths, and only one of them is about photographs.

Setting the policy

• Look up the written-contract limitation period for your own state, from the state's own code. It is public and it takes minutes. Do not inherit a number from an article written by somebody in a different jurisdiction, including this one.
• Keep contracts, payment records, key correspondence and proof of delivery for at least that period. This is the cheap half and it is the half that answers a claim.
• Decide the image retention separately, and write it down. Delivered set for the full window is a defensible default. Every RAW for the full window usually is not.
• Do not promise archival you have not costed. An open-ended re-delivery clause is a permanent liability accepted in a sentence.
• Keep the retention copy under the same discipline as everything else, which means it is not one drive in a drawer. The workflow side of that is in our piece on wedding photo backup, and the short version is that an archive you cannot read is the same as an archive you deleted. If the retention copy lives in the cloud, it is also worth knowing what your provider actually commits to, because a lapsed card ends an archive faster than any hardware fault.