Real benchmarks insideLinux · macOS · Windows · CLI + GUI · Open Source

File transfers
at full speed.

blitcp (formerly fast-copy) is a Python CLI that squeezes every MB/s out of your hardware — block-order I/O, SSH tar-pipe streaming, content-aware deduplication, and sparse-file awareness. An honest, faster alternative to rsync and cp. 3–5× faster than scp / rsync / SFTP for remote transfers.

Download Binary View on GitHub

100% FREE · NO TELEMETRY · APACHE-2.0

2.5×faster than cp -ar · Linux, 12,347 files

LIVE // BLOCK-STREAMDUPLICATES DIVERTED AT GATE — 0 BYTES REWRITTEN

SRC

DST

THROUGHPUT

2,082 files/s

READ ORDER

PHYSICAL (FIEMAP)

POST-COPY VERIFY

xxh128 ✓

Latest releasev4.0.0 · August 2026

What's new

A new name, seven languages, and quality-of-life fixes across the board.

Latest v4.0.0

fast-copy is now blitcp — new name, same tool (“blit” as in bit-block transfer). Old commands, imports, sidecar files and FAST_COPY_* environment variables keep working; dedup state and manifests carry over automatically.
Copy in your language — the CLI and GUI now speak English, Ελληνικά, 中文, Deutsch, Italiano, Español and 日本語 (--lang, BLITCP_LANG or the GUI dropdown).
Passphrase generator — creds encrypt --generate (and a Generate button in the GUI) offers a 6-word diceware passphrase (≈77 bits, EFF wordlist, fully offline).
Progress you can trust — the bar and ETA no longer jump to 100%/0s with thousands of small files still copying, and a failed verification now returns a proper error code.

Also new Since v3.7

Faithful metadata preservation — permissions, directory modes & timestamps, and POSIX ACLs copied exactly on every path, matching cp -a — with up to 3.5× faster --preserve acl.
SMB / UNC network shares — copy straight to \\server\share, with encrypted saved credentials.
Whole-drive dedup (--index-existing) — hash a destination drive once, then reflink new copies against everything already on it.
ReFS block cloning on Windows — copy-on-write clones for instant same-volume copies, alongside a cross-platform desktop GUI with update checks.

Full CHANGELOG →All release notes →

Where the speed comes from

Every feature in blitcp exists because it moves bits faster or wastes fewer of them. No phone-home. No surprises.

Block-Order I/O

Uses FIEMAP on Linux, fcntl on macOS, and FSCTL on Windows to sort files by physical disk offset before reading — eliminating random-seek overhead and maximising sequential throughput.

Content Dedup

Files are fingerprinted with xxHash-128 — the fastest non-cryptographic hash available — before writing. Identical content is skipped, saving bandwidth and write cycles.

SSH Tar-Pipe Streaming

Remote transfers bypass SFTP entirely: blitcp pipes a tar stream over ssh + tar for a true single-hop transfer — nothing to install on the far side, zero temp bytes on either end. Works on Synology & busybox NAS.

Reflink-Based Copy

On btrfs / XFS / APFS / bcachefs, files are cloned via FICLONE / clonefile(2) — metadata-only CoW. A 10 GB copy on the same volume completes in milliseconds.

Sparse-File Aware

VM disks and Longhorn replicas are auto-detected via SEEK_DATA / SEEK_HOLE. Holes never hit the wire or the disk — 2.3 TB logical → 12 GB on disk on real backups.

Sudo + Audit Log

--use-sudo re-execs for root-only paths, then writes a hidden chattr +i JSONL audit log of every elevated run. Even root can't quietly delete a record.

Small-File Bundling

Instead of thousands of individual write calls, small files are bundled into a tar stream and block-written in one pass, then extracted locally. 10,000 tiny files move as fast as one big one.

Post-Copy Verification

After every transfer, blitcp re-hashes the destination and compares against the source manifest. Corrupt or incomplete copies are reported before you delete the source.

Pre-Flight Space Check

Before writing a single byte, blitcp computes exactly how much unique data will land — after dedup and sparse holes — and verifies the target has room. Jobs never fail halfway through a 500 GB copy.

Cross-Platform

First-class Linux, macOS and Windows support — as a CLI and a cross-platform desktop GUI. PyInstaller standalone binaries on every release; no Python runtime required on the target.

Also included

Cloud S3 / Azure / GCS + SMB targets · encrypted AES-256-GCM credentials · a cross-run hash cache (2nd backup is much faster) · and a desktop GUI for Windows, macOS & Linux.

See it in action

The same engine, now with a cross-platform desktop app — compose transfers, manage encrypted connections, browse local, SSH and cloud storage, and manage dependencies & updates.

Transfer — sources to a destination, with a live plan & verified results

blitcp vs the alternatives

A feature-level comparison with the tools you're probably already using.

Feature	blitcp	rsync	cp (Unix)	robocopy (Win)	TeraCopy (Win)	scp / SFTP
Block-order I/O (physical offset sort)	✓	✗	✗	✗	✗	✗
Content deduplication (xxHash-128)	✓	checksum only	✗	✗	✗	✗
SSH tar pipe (single hop)	✓	✗	✗	✗	✗	✗
Cloud storage (S3 / Azure / GCS)	✓	✗	✗	✗	✗	✗
Zero temp files on remote transfer	✓	partial	✗	✗	✗	✗
Reflink / CoW clones (btrfs/XFS/APFS)	✓	✗	✗	✗	✗	✗
Sparse-file awareness (SEEK_DATA)	✓	partial	✗	✗	✗	✗
Tamper-resistant audit log under sudo	✓	✗	✗	✗	✗	✗
Post-copy hash verification	✓	--checksum	✗	✗	optional	✗
Pre-flight space check (before writing)	✓	✗	✗	✗	✗	✗
Small-file bundling	✓	✗	✗	✗	✗	✗
Standalone binary (no runtime needed)	✓	system pkg	system pkg	✓	installer	system pkg
Platform support	Linux/macOS/Win	Linux/macOS	Linux/macOS	Windows only	Windows only	Linux/macOS/Win

Deep dives with benchmarks: vs rsync · vs cp · vs scp · vs Robocopy · vs FastCopy · vs TeraCopy — or see them all

How a copy actually runs

blitcp runs a pipeline optimised for maximum I/O efficiency on every transfer — scan in disk order, fingerprint as it streams, decide, then verify.

01 // SCAN

Walk in disk order

The source tree is walked in physical extent order, not alphabetical — so the disk head only ever moves forward. A pre-flight space check refuses a copy that can't finish.

02 // HASH

Fingerprint as it streams

Every file is fingerprinted with xxHash-128 while it’s being read — no separate pass — and cross-referenced against the destination manifest.

03 // DECIDE

Seen this content before?

Match found → a reflink or hardlink is written, zero new bytes. No match → the file is written once, in block-sorted order, small files bundled.

04 // VERIFY

Confirm & log

Post-copy verification runs by default — the destination is re-hashed and diffed against the source — plus a tamper-resistant sudo audit log for elevated runs.

Install in seconds

Run directly with Python 3.8+, or grab a standalone binary from GitHub Releases — no runtime required on the target machine.

🐍 Python (all platforms)

# requires Python 3.8+
python blitcp.py <source> <destination>

# SSH support
pip install paramiko

# Optional: ~10x faster hashing
pip install xxhash

# Cloud copy (S3 / Azure / GCS)
pip install boto3 azure-storage-blob google-cloud-storage

# Encrypted credentials
pip install cryptography

# Desktop GUI
pip install PySide6

📦 Download binary

Detected: …

💻Your platform

Download CLI Download GUI

Windows may show a SmartScreen warning — the binaries are open source but not yet code-signed (choose “More info → Run anyway”). See why, and how to verify your download against the official SHA-256 hashes. Only download from the official GitHub release, where every build is published.

Other platforms & checksums

Windows	CLI	GUI
macOS (Apple Silicon)	CLI	GUI
macOS (Intel)	CLI	GUI
Linux	CLI	GUI
Python source	blitcp.py

Questions, answered

The things people usually want to know before trying blitcp.

How much faster is it than scp, rsync or SFTP?

For remote transfers, typically 3–5× faster than scp/rsync/SFTP. SFTP often tops out at 1–2 MB/s because of its chunked protocol; blitcp streams a raw SSH tar pipe instead. Locally, the win comes from reading files in physical disk order and skipping duplicate and sparse data — on the same volume with a reflink-capable filesystem, copies can finish in milliseconds.

Do I have to install it on both machines for SSH transfers?

No. blitcp runs on your side and drives the remote over a normal SSH connection using the tar and ssh that are already there — no daemon, agent, or matching install required on the remote. It even works against busybox-based systems like Synology NAS.

Will it ever modify or delete my source files?

No. The source is only ever read. blitcp never writes to, renames, or deletes anything in the source tree — it builds the copy at the destination and verifies it.

Do I need Python installed?

Not necessarily. You can grab the standalone binary from the releases page (no runtime needed), or run it as python blitcp.py if you already have Python 3. Both behave identically.

What does deduplication actually do to my files?

Identical files are stored once and the duplicates become reflinks (copy-on-write clones) or hard links on filesystems that support them — the files still appear normally, they just share underlying data. On link-incapable drives like FAT32 or exFAT, nothing is linked; blitcp simply reports the bandwidth it saved by not re-reading the duplicate.

Is it safe to run under sudo?

Yes. The --use-sudo flow is security-hardened: it uses O_NOFOLLOW to resist symlink attacks, runs a script-permission preflight, refuses self-update while elevated, and writes a tamper-resistant (chattr +i) JSONL audit log recording who copied what.

Which platforms are supported?

Linux, macOS and Windows — each with native I/O optimizations (FIEMAP on Linux, fcntl on macOS, FSCTL on Windows). Windows long paths over 260 characters are handled too.

Windows says “Windows protected your PC” (SmartScreen) — is blitcp safe?

Yes — the warning appears because the binaries are open source but not code-signed (certificates cost hundreds of euros per year for a free tool), not because anything is wrong with them. Click More info → Run anyway, and better yet verify the download: run Get-FileHash in PowerShell and compare against the official SHA-256 digests computed by GitHub for every release asset. Full walkthrough at blitcp.dev/install/windows/.

Does it phone home or collect any data?

No. There is no telemetry, no analytics, and no network calls beyond the SSH connection you explicitly ask for. It's open source under Apache 2.0 — you can read every line.

Do I have to pay to use blitcp?

No. blitcp is completely free and open source under the Apache 2.0 license. There's no paid tier, no license fee, and nothing locked behind a paywall — every feature you see is the whole tool.

Stop waiting on cp.

100% FREE · NO TELEMETRY · APACHE-2.0 · SINGLE BINARY