Download
Grab the latest DMG, open it, then double-click Install DDump.command.
Mac photo-card ingest
DDump
SD card to staging, destination, verified done.
DDump is built for photographers who want to insert a card, leave the laptop alone, and still get a safe local copy, organized folders, cloud upload, verification, and phone alerts without babysitting Finder or Google Drive.
DDump
835 GB Importing - EOS_DIGITAL
- Transfer to staging folder
- Eject card
- Upload to destination
- All complete
No babysitting
Insert the card. Let DDump do the dump.
The point is not another file browser. DDump is meant to sit ready on a working Mac, ingest the newest card media automatically, eject only when the staged copy is safe, and keep uploading when the computer is on Wi-Fi.
Unattended ingest Card in, scan, copy, verify, eject.
Cloud when available Upload starts without changing daily folders by hand.
Alerts on your phone ntfy can tell you done, failed, or needs-card status.
Start here
Install once. Then let card inserts trigger the workflow.
Choose your workflow
Pick local-only, Google Drive Desktop, cloud fallback, notifications, and naming rules.
Leave it ready
Keep the Mac awake or in clamshell-ready mode, then insert a card when you get back.
Walk away
DDump imports new media, stages safely, ejects when safe, uploads, verifies, and alerts you.
Download
Use the DMG for normal installs.
The DMG contains the app and installer payload. The release page has version notes, checksums, and any future assets.
Feature set
What DDump does after a card appears.
Closed-laptop workflow
Built for unattended ingest: insert an SD card, let DDump pull new files, and get notified when it is safe.
Whole-card media scan
Finds eligible photo and video files across the card, not only DCIM folders or one chosen folder.
Safe staging first
Copies locally before any cloud upload so the SD card is not your only copy.
Shoot clustering
Groups multiple shoots from one card by capture-time gaps you control.
Smart destinations
Builds date ladders like 2026 / 2026.06 / 2026.06.07 automatically.
Calendar naming
Native Google Calendar OAuth can name folders from scheduled shoots.
Google Drive Desktop first
Uses your existing Google Drive folder for faster local handoff when that workflow is enabled.
rclone fallback
Uses direct cloud upload/retry as the backup path when the desktop sync path fails or needs verification.
Mobile notifications
Send ntfy alerts to your phone for done, needs-card, upload failure, or recovery events you choose.
Verification pass
Checks pending batches and destination state before calling the job done.
Retry recovery
Pending uploads and reconnect retries help finish interrupted transfers without losing the staging copy.
Workflow
Built around the real card-to-cloud day.
1. Card appears
DDump detects the card, scans the full volume for recent media, and starts copying without making you pick folders.
2. Local staging
Files land in a local staging folder first, so the card can be ejected only after the first copy is safe.
3. Destination routing
Smart naming chooses the correct date, cluster, calendar event, or manual shoot name.
4. Cloud upload
If Wi-Fi is available, DDump uploads to the cloud destination you selected and keeps retry state for anything unfinished.
5. Phone alert
macOS and ntfy notifications can tell you when the import is done, stalled, missing a card, or needs attention.
Cloud strategy
Use Google Drive for speed. Keep rclone as the backup path.
Google Drive Desktop can be the fast first route when you already have it installed. DDump can also keep a direct cloud uploader available for retry, fallback, and verification so a flaky Drive sync does not quietly strand a shoot.
Fast local handoff into your existing Google Drive folder when Drive is available.
A separate uploader can retry or finish batches if the desktop sync path fails.
DDump checks counts and pending batches so the screen does not say done while a folder is missing.
Settings
Keep cloud and alerts opt-in.
DDump works as a local card ingest tool first. Cloud uploads, Google Calendar naming, and ntfy alerts are enabled only when someone chooses them in Settings.
General staging folder, cleanup, update checks
Destinations local folders, Google Drive Desktop, direct cloud fallback
Naming smart, calendar, cluster, sequential, custom
Detection lookback window, trust prompts, eject timing
Notifications macOS and mobile ntfy alerts with custom message templates
Cloud Google Drive app launch/quit, rclone retry, verification checks
Google Calendar
Native browser sign-in, read-only scope.
Calendar naming uses Google OAuth from inside DDump. If the OAuth app is still in testing, the Google account must be added as a test user before sign-in will complete.
First real test
Use a small card before paid work.
Confirm the destination folder appears, file counts match, and the app reaches “All complete.” If something stalls, open the Log button and send the newest lines.
Phone alerts
Use ntfy when you will not be watching the Mac.
Send only the alerts you care about: completed import, upload problem, missing staged files, or a card that needs to be reinserted.
Launch readiness
What needs to be true before selling it broadly.
Public Calendar OAuth
Complete Google app verification so users do not need to be manually added as test users.
Subscription checkout
Add a paid plan, license key, and in-app activation flow before broad distribution.
Support loop
Add a clear support email, version number, log-export button, and bug report path.
Trust assets
Publish privacy policy, terms, changelog, checksums, and a simple refund/support policy.
Roadmap
More destinations, same workflow.
DDump starts with local folders, Google Drive Desktop, and direct cloud upload fallback. The next destination work should keep that same setup style: no terminal steps, clear verification, and useful recovery when a provider stalls.
Dropbox Direct destination setup for Dropbox teams and personal accounts.
Box Direct destination setup for Box.com storage and client workspaces.
More calendar sources Apple Calendar, shared ICS feeds, and other schedule sources for shoot naming.
Better cloud proof Post-upload verification reports that compare staged files, remote files, and retry queues.