Raw footage or virgin file: what it is and how to manage it
What raw footage or a virgin file is in video and photography, how to organize it, back it up, and decide whether or not to deliver it to the end client.
The team behind Polimake. We explore the intersection of technology, creativity, and automation.
Raw footage or a virgin file is the original material captured during a shoot or session, before editing, color correction, sound mixing, or exporting a final version. In video it includes repeated takes, mistakes, silences, support shots, and separate audio. In photography it usually refers to RAW or the unprocessed image.
Raw footage is the most valuable—and most fragile—asset of a production. It lets you go back when you have to change the edit months later. And it gets lost with alarming ease when there's no clear system to manage it.
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.
Without raw footage, every new version means producing it all over again. It's the difference between owning an asset and owning only the result.
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, at maximum quality, ready for archiving.
- Proxy. A lightweight version of the raw footage for smooth editing without overloading the machine. It does not replace the raw footage.
In the final archive you should keep raw footage and masters. Proxies are for working, not for archiving.
Best practices with raw footage
- Organize by date, camera, and scene. Not by an arbitrary name. A clear convention from day 1 saves you weeks of searching months later.
- Back up in at least two locations. A local copy + a remote one (cloud or LTO). Three if the production is critical.
- Don't delete takes without reviewing them. What looks like a reject today may be gold tomorrow.
- Keep raw footage, projects, and exports separate. Three separate folders, not mixed together. Confusing them is the number 1 cause of losing material.
- Agree with the client on whether the raw footage is delivered or not. It's a contractual negotiation, not a last-minute technical decision.
The most common mistake: deleting to free up space
Sooner or later the "we need space on the server, what do we delete?" moment shows up. The temptation is to delete old raw footage. It's almost always a bad decision, because:
- It takes up a lot of space but is worth more than the cost of storage.
- Once deleted, it's unrecoverable.
- The "we haven't needed it in 2 years" math doesn't hold up in year 3 when you do need it.
The practical rule: before deleting raw footage, multiply the storage cost by 10 and ask yourself whether re-producing that piece would cost more. The answer is almost always yes.
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.
At Polimake, raw footage is part of Media, with exact, semantic, and reasoning-based search. It's tagged automatically on upload and connected to the brief in Studio and to the edit in Studio.
Related concepts
This piece is part of the Polimake glossary and the cluster on creative operations. If you manage audiovisual archives at scale, also read the guide on content production.