Skip to content

Managing raw footage and original files: organization, backup, and archiving at scale

How to organize, back up, and archive raw footage and original files at scale: a folder convention, backups in multiple locations, raw vs. master vs. proxy, and the client-delivery decision.

Editorial teamUpdated
Managing raw footage and original files: organization, backup, and archiving at scale

When a team produces at scale, raw footage or original files —the material captured during a shoot or session, before editing, color correction, sound mixing, or exporting— pile up fast and get lost with alarming ease when there's no clear system to manage them. Organizing, backing up, and archiving them well is what lets you reuse them months later instead of producing from scratch again.

Raw footage can include repeated takes, mistakes, silences, support shots, and separate audio. Here, “raw” means unedited footage; it does not mean RAW encoding. A camera original can be compressed video, JPEG, or RAW. Keeping it lets you return to captured material when editing requirements change.

Why raw footage matters so much

  • Later re-editing. If the piece has to be updated in six months, without raw footage you can only tweak the existing master.
  • Versions for new channels. A new format comes out, and you crop from the raw footage.
  • Alternative selection. The shot you discarded today might be the right one for another piece tomorrow.
  • Team learning. Reviewing raw footage teaches you which takes worked and why.

You can produce some versions from a master, but it cannot recover discarded takes or separate elements baked into the export. Re-editing may also require the project and its assets.

Raw footage vs. master vs. proxy

Three different files that people confuse:

  • Raw footage / virgin file. Straight out of camera, untouched.
  • Master. The final approved version, with the quality and format agreed for archiving and derivatives.
  • Proxy. A lightweight version of the raw footage for smooth editing without overloading the machine. It does not replace the raw footage.

Keep raw footage, masters, and, if re-editing is needed, the project and its dependencies. Proxies do not replace originals; whether to retain them depends on the workflow and whether they can be regenerated.

Best practices with raw footage

  • Organize by date, camera, and scene. Use a shared convention that helps identify and retrieve material.
  • Plan independent backups. CISA’s 3-2-1 rule proposes three copies—the original and two backups—on two types of media, with one offsite. LTO is a storage medium, not a location. Regularly check that files can be restored.
  • Don't delete takes without reviewing them. What looks like a reject today may be gold tomorrow.
  • Keep raw footage, projects, and exports distinct. Identify each type so a compressed delivery is not mistaken for the material needed to re-edit.
  • Agree with the client on whether the raw footage is delivered or not. It's a contractual negotiation, not a last-minute technical decision.

Before deleting to free up space

When storage is running out, review the value and retention requirements of raw footage before deciding what to delete:

  • Compare storage cost with the feasibility and cost of repeating production.
  • Deleting every recoverable copy loses the material. Verify backups before removing a copy.
  • Lack of recent use does not establish that material will be useless for a future adaptation.

Set retention according to the project, client agreements, and expected reuse. There is no universal storage-cost multiplier that determines what to keep.

Raw footage in creative operations

In teams that produce at volume, raw footage lives in a library with hierarchy and permissions: each member accesses their own, everyone accesses the common pool, and every asset has consistent metadata. Without that structure, raw footage piles up on personal drives, shared drives, and forgotten servers, and resurfaces as a problem when someone needs it and can't find it.

In the Polimake cloud library, you can view, analyze, and search camera RAW files by their visual content. The library supports asset retrieval through the interface, API, or MCP, and searching external sources without uploading the originals. Preserve project files and the settings needed to edit again in your production tool.

Related concepts

Frequently asked questions

Are raw footage and a RAW file the same thing?

No. Raw footage means unedited material, straight out of the camera or recorder. RAW is a capture format that stores unprocessed sensor data. Raw footage can be RAW, but it can just as well be a compressed MP4 or a JPEG: the term describes the state of the material, not the format.

Do you have to hand over raw footage to the client?

Only if it was agreed. Delivering raw footage is a term of the quote or contract, not a default obligation. If it is included, put in writing the format, the storage medium, the deadline, whether it costs extra and what usage rights the client has over that material.

How long should you keep a project's raw footage?

There is no single rule. It is decided per project based on what was agreed with the client, how likely the piece is to be re-edited or adapted, and what it would cost to reshoot. Footage of interviews, events or places that can't be filmed again justifies keeping it longer than a shoot that is easy to repeat.

How do you offload a camera card without losing footage?

Copy the entire card with its folder structure, not just the clips, because some cameras store metadata there that the editing software needs. Use a tool that verifies the copy with a checksum, make two copies on different drives and don't format the card until you've confirmed both open.