Delivery & file transfer · 20 November 2026

How long should a studio keep a project after delivery?

There is no single standard, so set your own and write it down. A workable default for a commercial studio: keep the full project online and ready to reopen for about three months after delivery, then move a reduced set of files to a cold archive for a period you agree with the client, often a few years, and delete working files you will never need again. Put that policy in the quote, so the client knows what they can still ask for a year from now.

This is a practical working policy, not legal advice. Contracts, sector rules and local law can set other periods, and those come first.

Why does a studio need a retention policy at all?

Because clients come back, storage costs money, and memory is not a filing system.

A client returns eight months after delivery and asks for a 6-second cutdown, a new language version, or the same product in a new color. If the project is still intact, that is a day of work and a happy client. If the scene files are gone or nobody remembers which drive they are on, it is a rebuild, or an awkward “we no longer have that”.

At the same time, keeping everything forever is expensive. A CGI job with simulations and full-resolution render passes can fill several terabytes, most of which can be rebuilt or will never be opened again. Without a policy, studios tend to drift between two bad options: keeping all of it on fast storage until the drives are full, or cleaning up in a hurry and losing the one file someone needed.

What does a three-tier policy look like?

Warm for a few months, cold for a few years, then gone, with a clear list of what moves between tiers.

TierWhenWhat is keptWhereSuggested length
WarmFrom deliveryThe whole project, as it was during productionYour working storage or project toolAbout 3 months
ColdAfter the warm periodA reduced set: masters, deliverables, project files, assets, and a manifestOffline or archive storage, in more than one copyAn agreed number of years
DeletedAfter the cold period, or straight away for some filesCaches, temporary renders, duplicate exportsNowhereNot applicable

The lengths are our suggestion, not an industry rule. The three-month warm period lines up with advice from Charles Haine in Frame.io Insider: archive around 90 days after delivery, which leaves time for late client changes plus a buffer for final notes. The cold period depends on the client and the kind of work. A brand that runs the same campaign every season will value a longer archive than a one-off event film.

What exactly goes into the cold archive?

Everything you need to make a new version, and nothing you can rebuild cheaply.

Haine’s list for edited work is a good starting point: the final master, separate audio stems, the edit consolidated with handles so it can be reconstructed, the finishing project files, and related marketing material. Translated to a short commercial or CGI job, a cold archive usually holds:

  • Masters and deliverables: every file that went to the client, exactly as delivered, including the textless master and caption files.
  • Audio: the final mix and the separate stems for dialogue, music and effects.
  • Edit projects: the locked edit, consolidated with handles, plus the grade and finishing projects.
  • CGI scene files and assets: the final scenes, models, textures, rigs and look development, in a state that opens without hunting for missing files.
  • Source material: camera originals or plates if the client may want new edits; licensed music and stock with their license details.
  • A manifest: a plain text or PDF file listing what is in the archive, the software versions used, the deliverables list, and who approved the final version.

What usually goes: render caches, simulation caches, intermediate renders, proxy files and duplicate exports. These are large and can be rebuilt from the scene files. If rebuilding would take days of farm time, keep the final render passes instead of the caches. The manifest is easy to skip and hard to do without later. File names that made sense during the job, as discussed in our guide to shot codes, versions and file names, help, but a manifest tells a future colleague what they are looking at without opening every folder.

How many copies should the archive have, and where?

At least three copies, on at least two kinds of storage, with one kept somewhere else.

This is the 3-2-1 rule, which Backblaze describes as three copies of your data on two different media with one copy off-site. Haine gives similar advice for video archives, recommending at least three copies in at least two storage formats, for example tape plus a cloud archive.

Two practical additions. First, an archive is not a backup of your working storage; it is a deliberate selection, so treat it as its own job with its own checklist. Second, test it. Once a year, pick an archived project at random and try to open it on a clean machine. An archive you cannot restore does not count.

How do you agree the policy with the client?

Write three lines into the quote: what you keep, for how long, and what reopening costs.

Clients rarely ask about this up front, which is exactly why it helps to say it. A short, plain paragraph in the quote is enough:

After delivery, we keep the full project available for three months for changes. After that, we archive the masters, deliverables, project files and assets for three years. Reopening an archived project for new work is quoted separately. Files we deliver should be saved on your own storage.

Also decide whether the client receives working files, and in which form, because that changes what they will expect you to keep. If ownership of files is part of the conversation, involve whoever handles your contracts. This article stays with the practical side.

A delivery link is a hand-over, not an archive, for either side.

Transfer links expire by design, and that is a good thing for storage and security. It does mean the client must save the files on arrival, and you must keep your own copy. Kadrenta, made by the same team behind The Production Brief, makes that split explicit. According to its help pages, every transfer ends, with a month as the longest it can run; afterwards the link stops opening, the files clear themselves, and the download page tells the client the date to save the work by. A review item, on the other hand, is kept as the record of what was agreed, and on the Free plan, archiving a project frees up one of the three active project slots. None of that replaces your cold archive of masters and project files, but it means the agreement and the approved versions stay with the project after the transfer is gone.

For what should be on the deliverables list in the first place, see what belongs in a commercial’s deliverables list, and for how delivery tools differ on link lifetimes and records, see our comparison of WeTransfer alternatives for video teams.

Frequently asked questions

Should we keep the raw footage or render caches?

Keep camera originals if you shot them and the client may want new edits. Render caches, simulation caches and intermediate exports can usually go, because they can be rebuilt from the scene files if ever needed.

Can we charge for reopening an archived project?

Some studios do, as a small fixed fee for restoring and checking the files before any new work starts. Whatever you choose, write it in the quote so the client is not surprised later.

Is a delivery link enough as an archive for the client?

No. Delivery links expire by design. Tell the client to save the files on their own storage, and keep your own archive copy of everything you delivered.

Should the client get the project files too?

That depends on what you agreed. Decide it at the quote: finished files only, or also working files such as edit projects or scene files, and in what form.

Sources