There is no reshoot button.
DDump keeps the first copy local and verifies it before the card is released.
One shoot timeline.
Named before handoff.
684 files. Local copy verified. Card safe.
Copy completeVerification passedBackup queued
Two destinations. One visible handoff.
01 / Dump folderVerified
02 / Backup folderQueued
The handoff
Card urgency first. Cloud urgency second.
A slow network should not hold the card hostage. DDump separates the verified local copy from backup delivery so the next shoot can keep moving.
Insert the card
Trusted camera media can start automatically while unrelated drives stay ignored.
Stage locally
Recent media moves to your chosen Dump Folder before slower backup work begins.
Prove the copy
File-size checks are standard. SHA-256 verification is available when you want it.
Eject and move
The card becomes safe while pending backups remain visible and recoverable.
Built into DDump
More feature. Less mystery.
Not another pretty sync folder. DDump understands cards, shoot boundaries, handoff state, recovery, and the controls photographers need when the day gets weird.
Verified locally before safe eject
The first safety copy is separate from cloud delivery. DDump checks the local result before it treats the card as ready.
LOCAL COPYVERIFIED
Photo-aware card detection
Trusted-card memory, recent-file lookback, manual folder selection, and inventory checks reduce wrong-drive surprises.
Cluster cards from the same job
Capture-time grouping can attach camera, drone, and second-shooter cards to one organized shoot.
Calendar and template naming
Use Apple Calendar, Google Calendar, ICS, dates, cameras, sequences, and Lightroom-style tokens.
Backups that remember unfinished work
Queue pending files, retry with backoff, resume after network reconnect, and use a fallback destination when needed.
BACKUPRETRY SCHEDULED
Automatic, not trapped
Pause, stop after a file, keep a card mounted, run a timed pause, or choose the folder manually.