Storyflow Logo

Storyflow

HomeBlogGuides

Features

Login

Home

/

Blog

/

Article

How to Back Up Footage on a Shoot (2026 On-Set Data Guide)

Every card is in one of three states, and the whole discipline is never letting them blur. Checksum verification, the card protocol, and what to do when a card fails.

How to Back Up Footage on a Shoot (2026 On-Set Data Guide)

Category

Filmmaking

Author

Justkay - Documentary Filmmaker & Founder at Storyflow

Justkay

Documentary Filmmaker & Founder at Storyflow

Topics

Data managementBackupOn-set workflowPost-productionFilmmakingDocumentary

2026-07-29

12 min read

Filmmaking

Table of Contents

Start from a template
Browse all templates

Templates to check out for this topic

Storyflow Mindmap template showing a central idea node branching into themed idea cards on an infinite canvas
MindmapUse this template →
Story Plan template in Storyflow showing premise, three-act columns, story beats, and character arc blocks on an infinite canvas
Story PlanUse this template →
Marketing campaign plan on the Storyflow canvas with goals, audience, channels, assets, and a timeline laid out together
Marketing CampaignUse this template →
Quick answer
how to back up footage on a shoot3-2-1 backup rule videochecksum verification footagewhen to format a memory carddata wrangler workflowmemory card failed recovery

How do you back up footage on a shoot?

To back up footage on a shoot, treat every memory card as being in exactly one of three states and never let them blur. A card is full when it holds footage that has not been copied, copied when the files exist elsewhere but nothing has confirmed they are intact, and verified when checksum verification has confirmed every file byte for byte. Only a verified card may be formatted. Aim for three copies of every clip on two different physical devices with one leaving the location, use offload software that verifies rather than a drag-and-drop copy, and never format a card in camera to free space in a hurry. Everything else on a shoot is recoverable. A missed shot can be picked up, a bad take can be redone, a broken light can be replaced with a window. Lost footage is the one failure with no version of the day where it is fine. Put simply: a copy is not a backup until something has checked it. Until then it is a hope. I have run data on small documentary crews where the person offloading cards was also the person shooting them, and the protocol below is what survives that situation. It is deliberately mechanical, because it has to work at the end of a long day when everyone is tired and the temptation to skip a step is at its peak.

Quick recommendations
H
Hedge or ShotPut Pro: Verified offload to multiple destinations
S
Silverstack: Full data management on larger productions
F
Free offload tools with checksums: Small productions, if verification is included
T
Two separate drives and a fast reader: The hardware half, which no software replaces

Full disclosure: Storyflow is our own product, so weigh its placement here with the skepticism you would apply to any tool a company recommends on its own blog. We rank it last and it deserves to be: it performs no part of this task. It does not copy files, does not verify checksums, does not talk to card readers or drives, and has no presence at the offload station. Offload software and physical drives do all of the actual work. Storyflow is at most somewhere to record what has already been done, and on the day a printed sheet is more practical.

Quick Comparison

The only requirement that matters is checksum verification. A file browser drag-and-drop reports success without proving the copy is intact, which is why it does not belong in this list as an option.

ToolBest ForAI FeaturesPrice

Hedge / ShotPut Pro

Verified multi-destination offload

None

Licence or subscription

Silverstack

Full on-set data management

None

Subscription tiers

Free offload tools

Small productions

None

Free

File browser drag and drop

Nothing here, it does not verify

None

Free

Storyflow

Noting what has been offloaded

Reads the whole board

Free / $7.99 mo

Key Takeaways

  • Three card states: full, copied, verified. Only verified cards may be formatted.
  • A successful copy is not evidence. Verification means comparing checksums, not watching a progress bar finish.
  • Three copies, two devices, one leaving the location, every day, before anyone goes to sleep.
  • Make the physical protocol visible. Card orientation in a wallet beats memory at eleven at night.
  • Never format in camera to make space. It is the most common way footage is actually lost.
Try it on a board

Keep the card log beside the plan

One line per card with date, camera, state, and destinations, next to the shoot plan it belongs to. The copying and verifying happen elsewhere; this is just the record.

Try the canvas freeBrowse templates
Storyflow Mindmap template showing a central idea node branching into themed idea cards on an infinite canvas
Mindmap template →

The Three Card States

The entire discipline reduces to keeping three states distinct and never acting on the wrong one.

Full. The card holds footage that exists nowhere else. This is the highest-risk object on the production, and there should be as few of them at any moment as the shoot allows. A full card should never leave the person responsible for it, should never go in a pocket with keys, and should never be handed to somebody without saying what it is.

Copied. The files now exist in another location, but nothing has confirmed they arrived intact. This state feels safe and is not. A copy can complete successfully and still contain a truncated file, a corrupted clip, or a silently skipped directory.

Verified. Offload software has compared checksums between the source and the destination and confirmed every file matches byte for byte. Only now is the card genuinely redundant, and only now may it be formatted.

The failure mode is always the same: somebody treats a copied card as a verified one, because the copy said it worked. The card gets formatted, and three days later a clip will not open.

Make the states physical rather than remembered. The standard technique is a card wallet where full cards sit label-up and empty cards sit label-down, or vice versa, chosen once and never varied. Then the state of every card in the production is legible at a glance, by anyone, without a conversation.

Verification: Why "It Copied Fine" Is Not Enough

Dragging files in a file browser copies data and reports success based on whether the operation completed, not on whether the result is identical to the source. Bit errors, interrupted writes, and faulty cables produce copies that look complete and are not.

Checksum verification computes a mathematical fingerprint of each source file and the copied file and compares them. If they match, the copy is provably identical. If they do not, you find out while the card is still in your hand rather than three weeks later.

This is what dedicated offload software does, and it is the entire reason to use it instead of a file browser. Tools in this category also copy to multiple destinations at once, generate a report you can keep, and preserve the camera's folder structure and metadata sidecars.

Keep the verification reports. They are the evidence that a card was safe to format, and on a professional production they are part of the paperwork.

Verification takes time. Budget for it. On a large card it can take as long as the copy itself, and a shoot that has not allowed for it is a shoot that will skip it.

The Rule, Applied to a Shoot Day

Three copies, on two different physical devices, with one copy off the location.

Copy one: the working drive. What the editor will actually use.

Copy two: a separate physical drive. Not a second partition, not a second folder, a different device that can be dropped without taking the first with it.

Copy three: off-site. Cloud upload where bandwidth allows, or a drive that physically leaves with a different person. On a location shoot the simplest version is that two crew members carry one drive each and do not travel in the same vehicle.

The camera card counts as a copy only until it is formatted, which is why cards are the cheapest insurance in production. Buy enough that you can leave a day's material on them until the material has been verified in three places.

Do it before sleeping, not in the morning. The morning version is how a whole day gets lost to an overnight theft or a hotel fire, which sounds dramatic until it happens to someone you know.

The Offload Station

One person owns it, by name. On a small crew this is often the person with the laptop, and the important thing is that it is not ambiguous.

Set it up somewhere it will not be moved, with power, and away from where people are packing.

Use a card reader, not the camera. Cameras are slow, drain batteries, and put wear on a port you need.

One card at a time, start to finish. Copy, verify, mark the state, then move to the next. Overlapping cards is how one gets missed.

Never rename or reorganise during offload. Copy the card structure exactly as it is. Renaming happens later, during ingest, and renaming during offload is a good way to break the relationship between a clip and its metadata.

Label the destination folders by date and card, so the structure is legible without opening anything.

Do not do anything else while offloading. Editing, browsing, or unmounting the wrong drive mid-write are all avoidable and all common.

A Worked Example: The End of a Shoot Day

The protocol as an actual sequence, because a principle that is not a sequence gets skipped when people are tired.

StepActionCard state afterRoughly how long

1

Collect every card into the wallet, all full cards oriented label-up

Full

2 minutes

2

Set up the offload station: power, reader, both drives mounted

Full

5 minutes

3

Copy card one to drive A and drive B simultaneously, with verification on

Copied

Varies by card size

4

Wait for the verification report and read it

Verified if it passes

Similar to the copy

5

Flip that card label-down in the wallet

Verified

Seconds

6

Repeat for every card, one at a time, start to finish

7

Start the off-site copy: cloud upload, or hand drive B to the second person

Overnight if uploading

8

Note the day in the card log: date, cards, camera, destinations

2 minutes

9

Only now, format cards for tomorrow, and only the label-down ones

Empty

1 minute

Two things about this sequence matter more than they look.

Step five is the whole system. Flipping the card the moment verification passes is what makes the state physical rather than remembered, and remembering is what fails at the end of a long day.

Step nine happens last, deliberately. Formatting is the only irreversible action in the list, so it sits after everything that could tell you not to do it. A production that formats at step three to get ahead has removed its own safety net for no gain.

If you are shooting again tomorrow and the copies are still running, you sleep with the cards unformatted and you use fresh ones. That is what having enough cards is for.

Multi-Day and Remote Shoots

The off-site copy is the hard part when you are travelling, and it is also when you most need it. Cloud upload over a hotel connection may not be feasible for high-bitrate material, in which case physical separation is the answer: two drives, two people, two bags.

Never let both copies travel in the same bag. This is the single most common way a well-run production still loses everything.

Check drive health before you leave, not after. A drive that fails on day one of a remote shoot is a problem with no local solution.

Take more cards than you think you need so material can stay on them longer when the offload situation is unreliable.

On long shoots, verify the working drive periodically, because drives degrade and a corrupted file discovered in week three is recoverable from the other copies only if you notice.

When a Card Fails

Rare, and this is what to do.

Stop using it immediately. Do not shoot more to it, do not format it, do not run repair utilities. Every write reduces what can be recovered.

Do not let the camera reformat it, even when prompted. That prompt appears at exactly the wrong moment.

Copy the raw card image first if you can, so recovery attempts happen on a copy rather than on the only remaining original.

Try recovery software on the copy. Many cases are a corrupted file table rather than lost data, and the clips are still physically present.

For genuinely critical material, stop and use a professional recovery service. They are expensive and they are far cheaper than a reshoot, and amateur attempts frequently make professional recovery harder.

Then retire the card. A card that has failed once is not trustworthy, and the cost of a new card is not a real consideration next to the cost of finding out again.

After the Project

Archive is not the same as backup. Backup protects work in progress. Archive is the long-term copy you keep after delivery.

Keep camera originals, not just the export. A finished file cannot be re-graded, reframed, or recut.

Two archive copies in different places, because a single archive copy is a single point of failure with a very long exposure window.

Include the project files, the log, and the licence documentation, not only the media. A project you cannot reopen is only partially archived.

Check archive drives periodically. Drives left unpowered for years fail silently, and discovering that during a reissue request is too late.

Common Mistakes

Treating a completed copy as a verified one. The root cause of most real losses.

Formatting in camera to free space. Fast, tempting, and irreversible.

Both copies in the same bag. Defeats the entire point of having two.

Offloading in the morning. Leaves a night of exposure for no reason.

Nobody specifically responsible. Shared responsibility for cards means intermittent responsibility.

Renaming during offload. Breaks the link between clips and their metadata.

Reusing a card that has already failed once. Saving the cost of a card against the cost of a shoot day.

No verification reports kept. No evidence a card was safe to format.

Quick Picks: Tools for On-Set Backup

Best for verified offload: dedicated offload software. Hedge, ShotPut Pro, and Silverstack all copy to multiple destinations simultaneously with checksum verification and generate reports. Silverstack goes furthest into full data-management workflows for larger productions. Pricing varies by product and tier (verify current pricing).

Best free option: free offload tools with checksum support. Several exist and are genuinely adequate for small productions. The requirement is checksum verification, not the brand.

Best hardware approach: two physically separate drives plus a fast card reader. The reader is the bottleneck on a long shoot day and is worth spending on.

Best for the off-site copy: cloud sync where bandwidth allows, otherwise physical separation with two people carrying two drives.

For tracking what has been offloaded: a written card log, or Storyflow if the shoot plan already lives there. One line per card with date, camera, state, and destinations. Storyflow's Free plan is $0; Plus is $7.99/month billed annually. The honest limit: it copies nothing, verifies nothing, and a printed sheet on the offload station works better on the day.

ToolVerifies with checksumsMultiple destinationsFree tierTypical model

Hedge / ShotPut Pro

Yes

Yes

Trials vary

Licence or subscription

Silverstack

Yes, plus full data management

Yes

No

Subscription tiers

Free offload tools

Varies, check first

Often

Yes

Free

File browser drag and drop

No

No

Yes

Do not use for this

Storyflow

No

No

Yes

$7.99/mo annual

Pricing checked July 2026. Competitor pricing changes often and varies by product and tier, so verify on each vendor's page before quoting it.

The Bottom Line

Data management is the least interesting part of a shoot and the only part where a mistake cannot be undone. Everything else has a version of the day where you recover. This does not.

Three states: full, copied, verified. Only verified cards get formatted, and verification means a checksum comparison rather than a progress bar reaching the end. Three copies on two devices with one leaving the building, completed before anyone sleeps. One named person who owns it. Cards physically oriented so their state is visible without a conversation.

None of it is clever, and that is deliberate, because it has to work at the end of a fourteen-hour day when everyone wants to go home. A copy is not a backup until something has checked it. Until then it is a hope.

Author

Justkay is a documentary filmmaker and the founder of Storyflow. He has run data on small documentary crews where the person offloading the cards was also the person who shot them, which is where a mechanical protocol earns its keep.

FAQ: Backing Up Footage on a Shoot

How do you back up footage on a shoot?

Copy every card to at least two physically separate drives using offload software that verifies with checksums, get a third copy off the location the same day, and only format a card once verification has confirmed the files are intact. Track each card's state, full, copied, or verified, in a way that is physically visible rather than remembered.

What is the 3-2-1 backup rule?

Three copies of the data, on two different devices or media types, with one copy stored off-site. On a shoot this typically means the working drive, a second physical drive, and either a cloud upload or a drive that physically leaves with a different person, completed before anyone sleeps.

Why is checksum verification necessary?

Because a copy that completes successfully is not necessarily identical to the source. Bit errors, interrupted writes, and faulty cables produce files that appear present and are corrupt. Checksum verification computes a fingerprint of each source and destination file and compares them, which is the only way to know a copy is genuinely safe before formatting the card.

When is it safe to format a memory card?

Only after checksum verification has confirmed every file copied intact to at least two destinations. Never format in camera to free up space during a shoot, and never format a card whose state you are not certain of. If you are formatting cards mid-day to keep shooting, you need more cards.

Who is responsible for backing up footage on set?

On a larger production, a data wrangler or digital imaging technician. On a small crew it must still be one named person, because shared responsibility for cards reliably becomes nobody's responsibility. That person owns the offload station and the card wallet, and nothing gets formatted without them.

What should you do if a memory card fails?

Stop using it immediately and do not format it, shoot to it, or let the camera repair it. If possible, make a raw image of the card and attempt recovery on the copy rather than the original. For critical material, use a professional recovery service, since amateur attempts can make professional recovery harder. Retire the card afterwards regardless.

How many memory cards do you need for a shoot?

Enough that you never need to format a card during the shooting day to keep going. Cards are inexpensive relative to a shoot day, and having enough is what allows material to stay on a card until it has been verified elsewhere, which is the entire safety margin.

Can you use a laptop to back up footage on set?

Yes, and that is the usual arrangement on small productions, provided you use offload software with checksum verification rather than dragging files in a file browser. Use a dedicated card reader rather than the camera, and do only the offload on that machine while it is running.

What is the difference between backup and archive?

Backup protects work in progress and exists so that a failure during production does not lose anything. Archive is the long-term copy kept after delivery, and it should include camera originals, project files, logs, and licence documentation rather than only the finished export. Both need more than one copy.

Should you back up footage to the cloud?

As the off-site copy, yes, where bandwidth allows. High-bitrate material over a hotel connection often makes this impractical, in which case physical separation achieves the same goal: two drives carried by two people who do not travel together.

Can Storyflow help with footage backup?

Only for tracking. A line or card per memory card with date, camera, state, and destinations, kept beside the shoot plan. It copies nothing and verifies nothing, and on the day a printed sheet at the offload station is more practical.

Where does Storyflow lose for on-set backup?

Comprehensively, and it should be said plainly. It performs no part of this task: it does not copy files, does not verify checksums, does not talk to card readers or drives, and has no presence at the offload station. Offload software and physical drives do the work. Storyflow is at most a place to note what has been done.

Templates you can use in Storyflow

Every Storyflow board starts from real structure and an AI that reads the whole canvas. Open one of these templates and make it yours.

Storyflow Mindmap template showing a central idea node branching into themed idea cards on an infinite canvas

Mindmap

Use this template →

Story Plan template in Storyflow showing premise, three-act columns, story beats, and character arc blocks on an infinite canvas

Story Plan

Use this template →

Marketing campaign plan on the Storyflow canvas with goals, audience, channels, assets, and a timeline laid out together

Marketing Campaign

Use this template →

Brand Strategy template in Storyflow showing mission, positioning, audience, voice, and visual direction sections on an infinite canvas

Brand Strategy

Use this template →

Storyboard template on the Storyflow canvas showing a grid of shot frames with image areas, action captions, and shot detail notes

Storyboard

Use this template →

Second Brain template in Storyflow showing notes, saved links, and idea clusters connected on an infinite canvas

Second Brain

Use this template →

Browse all templates

See Storyflow in Action

A visual AI workspace where every feature lives inside one canvas. No tab-switching, no context lost.

Build your entire board from a single message

Type what you need in the AI chat at the bottom of your canvas. The AI adds cards, headings, and structure directly onto your board.

Use expert frameworks as AI context

Type @ in the AI chat and choose any Tactic. The AI tailors every response to that framework instead of giving generic advice.

Turn your board into a mind map in seconds

Ask the AI to restructure your canvas as a mindmap. It connects your ideas into a visual hierarchy so you can see how everything relates.

Why Storyflow Exists

Storyflow actually began as a personal tool while working on creative and research projects.

We kept running into the same problem: ideas were scattered everywhere: notes, documents, and whiteboards.

Nothing helped us see how everything connected.

So we started building a workspace designed around how ideas actually grow.

→ Read how Storyflow was created
Justkay - Documentary Filmmaker & Founder at Storyflow

Justkay

Documentary Filmmaker & Founder at Storyflow

Published: 2026-07-29

Start creating with AI and become more productive

Transform your creative workflow with AI-powered tools. Generate ideas, create content, and boost your productivity in minutes instead of hours.

Ask Storyflow to