It's faster and stronger — but is anyone using it in the real world? More than you'd think.
Already switched
These aren't experiments — they're production systems used by millions of people every day.
The operating system that runs most of the world's servers, Android phones, and cloud infrastructure added BLAKE3 support in 2025. When the Linux kernel adopts something, the rest of the ecosystem follows.
One of the most respected VPN protocols uses BLAKE3 for key derivation. It's built into millions of devices and is the default VPN in many Linux distributions. (This is also why it breaks on government systems — BLAKE3 isn't FIPS-approved.)
Two major filesystems — the ones that actually store your files on disk — use BLAKE3 for data integrity checks. Every time you save a file, BLAKE3 creates a fingerprint to make sure nothing got corrupted. Faster hashing means faster file operations.
The Rust programming language's package manager uses BLAKE3 to verify that downloaded code hasn't been tampered with. When developers install a library, BLAKE3 checks the fingerprint in milliseconds instead of seconds.
Epic Games uses BLAKE3 in Unreal Editor for Fortnite's content pipeline. When game creators upload assets, BLAKE3 verifies everything is intact — fast enough to not slow down the creative process.
One of the internet's biggest infrastructure companies uses BLAKE3 internally. When a company that handles ~20% of the world's web traffic picks your hash function, that's a strong vote of confidence.
Still on SHA-256
These aren't behind — they have real reasons for staying put.
SHA-256 is baked into Bitcoin's core design. Changing it would require every miner, every wallet, and every exchange to upgrade simultaneously. It's not happening — and it doesn't need to. SHA-256 works fine for this.
Every secure website uses SHA-256 in its certificate chain. The entire PKI (public key infrastructure) is built around it. Switching would take a decade of coordination across every browser, server, and certificate authority on Earth.
Git is migrating — but to SHA-256 (from SHA-1), not to BLAKE3. Why? Compatibility. Every git repository in the world uses SHA-1 object IDs. They chose the most widely supported upgrade path.
Regulatory compliance (FIPS, PCI DSS, HIPAA) mandates government-approved algorithms. Even if a bank wanted BLAKE3, their auditors would say no. More on this →
Cloud providers need FIPS compliance to serve government clients. Their cryptographic libraries default to SHA-256 everywhere. BLAKE3 would mean maintaining two code paths — added complexity for unclear benefit.
The pattern
| Category | Uses BLAKE3 | Uses SHA-256 |
|---|---|---|
| New open-source tools | WireGuard, Cargo, rclone | — |
| Filesystems | btrfs, OpenZFS | ext4 (no hashing) |
| OS kernels | Linux (2025) | Windows, macOS |
| Gaming / creative | Unreal Engine | Most game DRM |
| Web infrastructure | Cloudflare (internal) | TLS, certificates |
| Cryptocurrency | — | Bitcoin, Ethereum (Keccak) |
| Regulated industries | — | Banking, healthcare, gov |
Projects that can choose freely — open-source tools, new infrastructure, gaming — are adopting BLAKE3. Projects locked into standards — banking, government, legacy protocols — stay on SHA-256. It's not about which is better. It's about who gets to decide.
What's next
Every year, more projects adopt BLAKE3. The Linux kernel adoption in 2025 was a major tipping point — it signals to the rest of the ecosystem that BLAKE3 is mature, trusted, and production-ready. But the regulated world won't follow until NIST acts.
The two-speed world
We're heading toward a split: the open-source world running BLAKE3, and the regulated world running SHA-256 — not because of technical merit, but because of bureaucratic process. The technology has moved on. The paperwork hasn't.
Want to see how BLAKE3 performs on your device? The benchmark on this site runs both algorithms head-to-head, right in your browser. No downloads, no installs — just real numbers from your actual hardware.