Epic Games releases Lore, an open-source Git alternative for games

Key Takeaways

• Lore is Epic's open-source, binary-first version control system now available on GitHub
• The system handles massive game assets with 500ms delta-transfers versus minutes with Git LFS
• Originally developed for Unreal Editor for Fortnite, it's designed for million-user scale

Epic Games has released Lore, an open-source version control system designed specifically for handling the enormous binary files that make Git painful for game developers. The tool, now available on Epic's GitHub, originated as the internal backbone for Unreal Editor for Fortnite workflows.

Anyone who has tried to version control a game project knows the friction. Git was built for text. Source code diffs cleanly, merges predictably, and stores efficiently. A 4GB texture file does none of those things. Git LFS helps, but it's a workaround bolted onto a system that fundamentally wasn't designed for the job.

Lore takes a different approach. It's binary-first, using content-addressed storage and intelligent chunking to handle assets the way Git handles code. Epic claims typical delta-transfer latency of 500 milliseconds for massive binary chunks, a task that can take minutes through traditional Git LFS setups.

Why game studios have been stuck with Perforce

For decades, Perforce Helix Core has been the default choice for studios working with large assets. It handles binaries well and scales to enterprise needs. It also costs enterprise money. Smaller studios and indie developers often make do with Git LFS, accepting the trade-offs, or they simply avoid proper version control for their art assets altogether.

Lore's open-source release potentially changes that calculus. Early Hacker News discussions have drawn direct comparisons to Perforce, with developers noting that a capable open-source alternative could significantly lower barriers for high-fidelity game development.

How Lore handles scale differently

The architecture uses a distributed, multi-region design that Epic says can support over one million concurrent users. That's an ambitious target, clearly aimed at the collaborative metaverse-scale projects Tim Sweeney has discussed publicly.

Content-addressed storage means files are identified by their contents rather than their paths. When you modify a 2GB asset, Lore doesn't re-upload the entire file. It chunks the data, identifies what changed, and transfers only the deltas. This is why those 500ms transfer times become possible for assets that would otherwise require full re-uploads.

The chunking strategy also enables better deduplication across a project. Two artists working on similar textures share underlying data automatically, without manual optimization.

Beyond games: where binary-first VCS matters

Game development isn't the only field struggling with version control for non-code assets. VFX studios, architecture firms, hardware design teams, and machine learning researchers all work with large binary files. Any project where the important artifacts aren't plain text runs into the same Git limitations.

Lore's release could find adoption well beyond Epic's immediate ecosystem. The open-source license means teams can evaluate it without licensing negotiations, and the architecture documentation Epic has published gives potential adopters visibility into the design decisions.

What's still unclear

Epic's announcement focuses on capabilities and architecture but leaves some practical questions open. How does migration from existing Git repositories work? What's the learning curve for teams already comfortable with Git workflows? How mature is the tooling around Lore, like IDE integrations and CI/CD compatibility?

The Discord community Epic has set up will likely become the place these questions get answered as early adopters test the system against real-world workflows.

Frequently Asked Questions

Is Lore a complete replacement for Git?

Lore is designed specifically for workflows heavy on binary assets. Teams working primarily with source code may find Git's mature ecosystem more practical. Lore shines when large non-text files are central to the project.

How does Lore compare to Perforce?

Both handle binary files well and scale to enterprise needs. The key difference is licensing: Lore is open-source, while Perforce Helix Core requires commercial licensing for larger teams.

Can Lore work with Unreal Engine projects?

Yes. Lore was originally developed to power Epic's own Unreal Editor for Fortnite workflows, so Unreal Engine integration is a core use case.

What does binary-first version control mean?

Traditional VCS like Git optimize for text files, treating binaries as opaque blobs. Binary-first systems use chunking and content-addressing to handle large assets efficiently, enabling incremental transfers and better deduplication.

Source: Hacker News: Best