The very next thing you do after a green result is erase the card.
Cutvey Offload is built around that one fact. It copies camera cards to every destination at once, proves the copies by content, writes the manifests production will accept, builds the camera report, and only then offers to make the card safe to reuse. One unattended run, on a Mac that does nothing else while it works.
Free with any Cutvey subscription · $19 per Mac per year standalone · macOS 14 or later
SD · 128 GB
CFexpress · 512 GB
SSD · 4 TB
Bucket · us-east-1
Interface illustration, not a screenshot
01 The shape of the day
Three tools, one run, nobody standing over it.
A card comes off camera and three separate things have to happen to it before anyone can reuse it. Most carts run three tools to do that, in three passes, each waiting on a human. Cutvey Offload does all three and joins them end to end.
Get the footage off, and prove it.
Copy to every destination at once, hash inline during the copy pass, and re-read the destination to confirm it. Classic MHL, ASC MHL v2 and checksum lists come out the other side, so the proof survives the shoot.
Replaces a dedicated verified-offload tool
Hand production a camera report.
A contact sheet of everything on the card, first, middle and last frame per clip, with the metadata the camera actually recorded. HTML and PDF, plus ALE and CSV for editorial.
Replaces a dedicated camera-report tool
Make the card safe to reuse.
Once the footage is provably somewhere else, the camera can be made to see the card as unformatted, so it cannot be shot on by mistake. It is a reversible bit-flip, not a format.
Replaces a dedicated card-protection tool
Three tools, not three bills: one of the three is free elsewhere, and we are not going to pretend otherwise. What you are buying is the join.
02 The safety model
The app never treats I could not check this as this is fine.
That is one sentence, and it is the whole design. Every place the engine could quietly round a failure up to a success, it refuses instead, loudly, because of what happens next: the card gets wiped.
- 01 An unreadable folder fails the run A source directory that will not enumerate is a hard error. The app does not copy what it could see and report success, because everything behind that directory is unknown, and unknown is not a pass.
- 02 A skip has to be earned A file already on the destination is skipped only when this run proved by content that the same bytes are there. Name, size and modification time start that check. They never finish it.
- 03 No manifest, no verified copy A manifest the run was asked to write and could not deliver fails the run. A verified copy with no proof of it is not a verified copy.
- 04 Incomplete counts are a floor When a scan could not finish, the totals are reported as a floor rather than a total, in those words, instead of a confident number that happens to be wrong.
- 05 Deleting always needs content proof A Move or an erase requires proof by content, never metadata. Move is refused outright in any mode that cannot prove destination content, rather than quietly downgraded to a copy.
03 What makes a verified copy verified
Cutvey Offload commits withF_FULLFSYNCand re-reads withF_NOCACHE, so verification happens against the device rather than the page cache. No other vendor documents whether their verification reads the device or the cache — ask them. Both are on by default. The cost is roughly 5 ms per file on SSD and materially more on spinning media, and the honest advice is to keep them on. On filesystems that reject the full barrier, notably some network mounts, the app falls back tofsyncand names both error numbers in the diagnostic, because that is the difference between blaming the app and blaming the mount.
04 Camera reports
A document production will accept, built from what the camera actually recorded.
Point it at footage, or let it fire at the end of an offload. You get a dark HTML report and a light PDF, organised by shoot day and reel, with a contact sheet and per-clip thumbnails.
Absent is absent
ISO, white balance, shutter, lens, ND, colour space, bit depth and timecode are captured only where a camera genuinely provides them. A field a clip does not have contributes no row at all, rather than a row that says unknown.
Three ways to render the previews
Manufacturer, generated from each vendor's published curve so previews look like that camera's dailies. ACES 1.3, applied identically to every camera so a mixed-camera shoot is consistent with itself. Or your own .cube, assigned per camera model.
Nothing to install
Cutvey Offload is compatible with Blackmagic RAW, and with RED R3D. Both decode through their own SDKs, and both ship inside the app. ProRes, H.264 and H.265 go through AVFoundation, with a bundled FFmpeg frame-grabber for containers it will not open, notably Sony XAVC MXF.
The check a checksum cannot do
An optional broken-media pass confirms each copied clip still opens and decodes. A clip the camera wrote corrupt copies perfectly and verifies perfectly, so verification will never catch it. That is the case this exists for, and it runs off the copy path, so turning it on can never slow or fail a copy that succeeded.
05 Safe Erase
The card comes back empty. Reversibly.
Once a card is provably backed up, Cutvey Offload can make a camera treat it as unformatted, so nobody shoots over it by mistake. The change is a reversible bit-flip rather than a format: Restore is the identical flip re-applied, and it works right up until the camera does a real format.
How the gates workGATE Nothing is erased without proof
- Every file on the card must be found in a watched backup folder by content, not by name and size.
- A backup folder that overlaps the card is refused, so a card can never verify against itself.
- A card the app could not fully read is a hard failure, not a pass with a warning.
- A card whose identity it cannot pin is refused, and identity is re-checked against a fresh read of the disk immediately before the write.
- Every erase needs an acknowledgement, an explicit confirmation naming the card, and your administrator password.
06 The automated chain
Turn it on and a card runs itself.
This is the piece that turns a set of capabilities into a workflow. Both offers at the end are off by default and independent of each other, and enabling the erase offer shows a plain warning about what it does and does not prove.
Cards that finish together are asked about one at a time, each named by volume, capacity and device node. A prompt is dropped if the card was swapped or unmounted before you answered, and it tells you which of those happened.
Only cards, only ever
Only removable, ejectable volumes that were sources of the copy are ever offered. Never an internal disk, never a network mount, never the boot volume. That rule is absolute and it applies to the eject offer too, because ejecting the wrong volume mid-shoot is not a harmless mistake either.
Silence rather than a greyed-out dialog
A card that qualifies for nothing produces no prompt at all. A dialog with everything disabled trains an operator to dismiss dialogs, and the one that matters is the one they will dismiss.
07 Automation
Drive it from whatever already runs your cart.
A cutvey-offload:// URL scheme, a token-gated loopback HTTP API with a live dashboard, eleven lifecycle events that run a shell command with the whole payload in the environment, saved workspaces, S3 destinations, and a Finder Quick Action.
# A full start-the-offload chain, one request
curl -H "Authorization: Bearer $TOKEN" -X POST --data '[
{"command":"applyPreset","name":"A_FX6"},
{"command":"setSource","paths":["/Volumes/SONY A7S III"]},
{"command":"setDestination","path":"/Volumes/Samsung T7"},
{"command":"addTransfers"}
]' http://127.0.0.1:8765/command/actionsThe HTTP API binds loopback only, is off until you turn it on, and requires a bearer token on every request. It dispatches only the existing command set: no arbitrary shell, no arbitrary file access.
08 Pricing
Free with any Cutvey subscription. Or $19 per Mac per year.
If you already run your production company on Cutvey, Offload is included: one Mac on Solo, two on Team, five on Studio. If you do not, it stands alone at nineteen dollars a Mac a year.
Put it on the cart.
Apple Silicon Mac, macOS 14 or later. Downloading needs a Cutvey account, and a free trial gets you one.