Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

BitMatch

github.com

  • Free plan
  • macOS
  • iPhone and iPad
7.2 Club score Visit github.com

What BitMatch is

BitMatch copies camera-card footage to multiple drives and verifies the copies, helping users decide when a card can be erased. The free, open-source software is available for macOS, iPhone, and iPad. Verification has three modes: Standard checks destination copies with SHA-256, Thorough rereads the source and adds MD5, and Paranoid compares every byte using SHA-256. Camera detection includes Sony, Canon, ARRI, RED, Blackmagic, Panasonic, Fujifilm, GoPro, DJI, Insta360, and generic DCIM folders. Transfer reports can be exported as PDF, CSV, or JSON, and verified copies receive an ASC MHL inventory by default; this can be disabled in Advanced settings. On Mac, users can optionally upload a verified local copy over SFTP, but the server needs SFTP and SSH shell access; S3 and WebDAV are unavailable. BitMatch reads the source without writing to it, uses temporary files, and does not overwrite conflicting destination files. It is beta software from a one-person project, and not every camera, drive, filesystem, hub, or OS combination has been tested. No physical-device test reports are recorded in its hardware validation matrix.

Who it suits

BitMatch is aimed at indie filmmakers, YouTubers, photographers, and small productions that need verified copies of camera-card footage. It also suits users who want local-drive backups and optional Mac SFTP uploads.

Good to know, and what to watch

  • Free and open-source
  • Three verification modes, including byte-by-byte comparison
  • Exports PDF, CSV, and JSON reports
  • Reads source media without writing to it
  • Supports optional Mac SFTP backup
  • The project is beta software
  • Not every camera and storage setup has been tested
  • S3 and WebDAV are unavailable
  • No physical-device test reports are recorded

Free

Free

Free plan

The verdict

BitMatch provides several ways to verify copies and a careful source-file workflow. Its beta status and untested hardware combinations matter for production use; consult the diagnostics guide and provide relevant error, app, OS, drive, and filesystem details if a problem occurs.

What the maker publishes

ASC MHL
ASC MHL inventory creation is enabled by default for verified copies and can be turned off in Advanced settings. source
Camera support
Camera detection covers Sony, Canon, ARRI, RED, Blackmagic, Panasonic, Fujifilm, GoPro, DJI, Insta360, and generic DCIM. source
File safety
BitMatch reads the source without writing to it, uses temporary files, and does not overwrite conflicting destination files. source
Hardware validation
The hardware validation page says no physical-device test reports are recorded in its matrix yet. source
Intended users
The project is aimed at indie filmmakers, YouTubers, photographers, and small productions. source
Limitations
The project describes itself as beta software from a one-person project and says it has not tested every camera, drive, filesystem, hub, or OS combination. source
Platforms
The repository offers a signed and notarized Mac build for Apple Silicon and Intel, requires macOS 15.5 or newer, and says iPhone and iPad builds must currently be built from source. source
Privacy
The guide says the app does not upload analytics and that selected data goes to the server chosen for remote backup. source
Purpose
BitMatch copies camera-card footage to multiple drives and verifies the copies so users can tell when a card is safe to erase. source
Remote backup
Mac supports optional SFTP uploads after a local copy is verified; the server needs SFTP and SSH shell access, and S3 and WebDAV are unavailable. source
Reports
Transfer results can be exported as PDF, CSV, and JSON on Mac, iPad, and iPhone. source
Support
The guide directs users who find a problem to follow its diagnostics guide and provide the exact error and relevant app, OS, drive, and filesystem details. source
Transfer verification
Standard mode checks each destination with SHA-256; Thorough adds a source reread and MD5, while Paranoid compares every byte and uses SHA-256. source

Checked against the maker's pages on 8 Oct 2026.