Epic Games Open-Sources Lore: A VCS Built for Binary Files

Epic Games open-sourced Lore, a version control system built for large binary files, at State of Unreal 2026 alongside Unreal Engine 5.8. The MIT-licensed, Rust-based tool uses content-defined chunking and BLAKE3 hashing to address inefficiencies in Git LFS and Perforce for binary-heavy workflows, targeting game development, ML engineering, and media production. The announcement on Hacker News quickly garnered over 620 upvotes and 340 comments.

Epic Games open-sourced Lore today — a new version control system built from scratch for large binary files. Announced at State of Unreal 2026 alongside Unreal Engine 5.8, Lore is MIT-licensed, written in Rust, and designed to make both Perforce and Git LFS irrelevant for binary-heavy workflows. Within hours of the announcement, the Hacker News thread https://news.ycombinator.com/item?id=48571081 hit 620 upvotes and 340 comments. That reaction is earned. The Problem with Binary Files and Version Control Git is a text-native system. Its delta compression, diffing, and merge strategies were designed around line-oriented text files — source code. Binary files — 3D models, textures, audio files, ML model checkpoints — are second-class citizens. Git LFS was the band-aid: pointer files that swap out large binaries for stubs tracked by a separate server. In theory it works. In practice, game studios and media teams have a decade of horror stories: pointer file confusion that non-engineers can’t debug, full-file re-uploads on every small change no chunking , and a reputation for leaving repositories in corrupt states when network operations fail. Perforce fills the gap in professional game development, but it’s not cheap. Helix Core Cloud starts at $39 per user per month. A 100-person studio is looking at $10,000+ annually in licensing, plus $5,000–$20,000 in implementation costs and ongoing infrastructure. And the protocol is proprietary, which means no third-party reimplementation, no audit, and full vendor dependency. The industry has been paying this price because there was no credible alternative. Lore is Epic’s answer. What Lore Actually Does Differently The core design decision is treating all content as opaque byte streams. Text gets no special treatment. Binary files aren’t a special case that needs a bolt-on extension — they’re the primary design target. The practical consequence shows up immediately in storage. Lore uses content-defined chunking FastCDC to split files into variable-size pieces averaging 64 KiB, based on rolling-hash boundaries. When you make a small edit to a 4 GB texture, only the chunks near that change need re-uploading — not the whole file. This is the critical win over Git LFS, which stores and transfers large files whole. Repeated small edits to large binaries, exactly what happens during asset iteration, become vastly cheaper. Sparse checkout is the default, not an afterthought. Clients materialize only the repository subset they request; everything else fetches lazily on demand. In Git, sparse checkout remains experimental. In Lore, it’s the baseline. Multi-tenant partitions use 16-byte identifiers to scope all content access. A session bound to one partition cannot read another’s content, even when they share identical data — deduplication happens below the API without cross-tenant leakage. This is the right model for studios running multiple projects on shared infrastructure. BLAKE3 hashing replaces SHA-1 Git and MD5 Perforce . It’s faster on modern CPUs, supports SIMD parallelism, and is cryptographically stronger than both. MIT license with an open wire protocol. No vendor lock-in. You can audit exactly what Lore does with your data. This Isn’t Just a Game Dev Story The community is framing Lore as a Perforce replacement for game studios, which it is. But the same problem it solves — large binary files that overwhelm text-native VCS assumptions — exists across ML engineering and media production. Teams managing model checkpoints, training datasets, and raw camera footage deal with identical pain. A version control system with first-class binary support, chunked storage, and per-partition access control applies directly to any organization where binary artifacts dwarf source code in size and importance. The Honest Caveats Lore is pre-1.0. Version 0.8.3 was released today alongside the announcement, and the documentation is clear: on-disk formats and APIs may change between releases. This is not for production-critical workflows yet. The ecosystem gap is also real — mature IDE integrations, GUI clients for artists, and CI/CD plugins don’t exist at the scale Git and Perforce offer. The Hacker News thread is full of experienced game developers who appreciate the technical design but are skeptical about Epic’s ability to sustain the tooling investment needed to unseat Perforce in studios that have spent years building workflows around it. Those are fair concerns. But the codebase is public, MIT-licensed, and written in Rust with a full-surface API — the right conditions for third-party ecosystem growth. The GitHub repository https://github.com/EpicGames/lore already has 739 stars on day one. A Discord community is open for early adopters at lore.org https://lore.org/ , and detailed system design documentation https://epicgames.github.io/lore/explanation/system-design/ is available. The architecture is technically sound. The question is execution and sustained investment.