Epic Games Releases Lore: A Version Control System Built for Game Development

Epic Games just released Lore, an open-source version control system specifically designed for repositories that contain massive binary assets alongside code. The project launched under an MIT license and is available immediately.

Last updated: June 17, 2026

What Lore actually is

Lore is a centralized, content-addressed version control system that represents repository state as Merkle trees. Unlike Git, which was designed around source code and treats binary files as an afterthought, Lore was built ground-up for the mix of code and binary assets that game development requires.

The headline features:

• Native binary handling: Chunked storage and deduplication built into the core, not bolted on like Git LFS
• On-demand hydration: Workspaces fetch file data only when needed, so you can work with terabyte-scale repos without cloning everything
• Sparse workspaces: Artists working on textures do not need to download the entire audio folder
• Immutable revision chain: Cryptographically verifiable history using Merkle trees
• File locking: Built-in support for exclusive locks on assets that cannot be merged

The project is centralized by design - two clients communicate through the remote, not directly. This is intentional. Lore is solving a different problem than Git solved.

Why this exists

Git works well for source code. It was not built for game development.

A typical AAA game repository weighs in at hundreds of gigabytes to over a terabyte. The vast majority of that is binary assets - textures, 3D models, audio files, video sequences. Git handles text diffs efficiently but treats binary files as opaque blobs. Every change to a 500MB texture stores another 500MB.

Git LFS patches around this by storing large files outside the repo, but it adds complexity to an already complex tool. LFS bandwidth limits and storage costs on GitHub bite quickly. Sparse checkouts with LFS still have offline limitations.

Perforce has been the de facto standard for large game studios precisely because it handles this scale. From the HN discussion, multiple commenters with game industry experience confirmed that Perforce is everywhere in AAA studios - and that it requires dedicated tools engineers to keep it running smoothly.

One commenter summarized the core problem: "When you have a game that weighs in at 100GB, only a tiny fraction of that is built from code. The rest of it is binary assets that most VCSs struggle with."

What HN is saying

The discussion thread hit 265 comments and surfaced several perspectives from game developers.

The irony of hosting on GitHub was not lost on commenters. The Lore repository itself lives on GitHub, using Git. As one commenter pointed out: "Lore itself is not an example of a program that meaningfully benefits from any of the key features of Lore." The tool is source code - it does not contain gigabytes of binary assets.

Perforce's dominance came up repeatedly. Multiple commenters confirmed that Perforce is the industry standard but noted its pain points. One developer described spending significant time "helping people fix their workspaces when Perforce goes bad." The list of complaints included desync issues requiring hours-long reconciles, poor scripting support, inconsistent line-ending handling across operating systems, and per-user licensing costs.

GUI support matters for non-programmers. Several commenters noted that artists and designers need GUI tools, not CLI. One wrote: "Non-programmers don't want to dabble with CLI. One reason why Perforce is the defacto standard - the GUI covers 99% of daily used operations."

The CLI syntax is Git-like:

echo "Hello, Lore" > hello.txt
lore stage hello.txt
lore status --scan
lore commit "Initial revision"
lore push

Skepticism about Epic's track record appeared in several threads. One commenter raised the Rocket League situation - Epic acquired Psyonix and subsequently removed Linux and macOS client support, leaving those players unable to access a game they had purchased.

Technical details

Lore ships with binaries for Windows, macOS (ARM64), and Linux (x86-64 and ARM64). Language bindings exist for C/C++, Rust, JavaScript, C#, Python, and Go.

For infrastructure, it supports both a local zero-config mode for experimentation and scalable deployment via Docker. The reference implementation uses AWS S3 and DynamoDB.

The architecture is explicitly not decentralized. From the documentation's "Explicit non-goals" section: "Peer-to-peer decentralization. Lore is centralized by design."

This centralization is a feature, not a limitation, for the target use case. Game studios need access control - the ability to restrict certain directories to developers who have signed specific NDAs. Git cannot do this at the repository level; it is all-or-nothing. Perforce handles this with directory-level permissions, and Lore inherits this architectural choice.

Who should care

Game development teams dealing with terabyte-scale repositories where Git LFS is hitting limits. If you are paying Perforce licensing fees and have dedicated engineers managing the infrastructure, Lore offers an MIT-licensed alternative worth evaluating.

Creative teams working with large media files - video production, 3D animation, mixed-media projects. The same binary asset challenges apply.

Enterprise teams with access control requirements - the centralized architecture enables directory-level permissions that Git cannot provide.

Not general software development teams working primarily with source code. Git remains the right tool for that problem space.

The current state

Lore launched as a pre-stable 0.x release. Epic commits that data written now will remain readable in future versions, which matters for production adoption.

The tool is not yet integrated with Unreal Engine's editor workflows - that kind of deep integration is presumably on the roadmap. For now, it is a standalone VCS that handles the storage and versioning layer.

One open question is whether Epic will continue active development or if this becomes an open-source release that the community inherits. The company's history includes both well-maintained projects (Unreal Engine itself) and abandoned ones.

FAQ

What is Epic Games Lore?

Lore is an open-source version control system from Epic Games, released under the MIT license in June 2026. It is designed specifically for repositories that combine code with large binary assets like textures, 3D models, and audio files.

How is Lore different from Git?

Git was designed for source code and treats binary files as opaque blobs. Lore was built ground-up for binary assets with native chunked storage, deduplication, on-demand file hydration, and built-in file locking. It is centralized rather than distributed.

Does Lore replace Perforce?

Lore targets the same use case as Perforce - large binary-heavy repositories in game development. Whether it can replace Perforce depends on the specific features your team relies on. Perforce has decades of tooling and integration; Lore is a new 0.x release.

Is Lore open source?

Yes, Lore is released under the MIT license. The source code is available on GitHub at github.com/EpicGames/lore.

Can I use Lore for regular software development?

You can, but Git is probably a better fit if your repository is primarily source code. Lore's advantages - binary handling, sparse workspaces, large repo scale - do not apply to typical software projects.

What platforms does Lore support?

Lore has pre-built binaries for Windows, macOS (ARM64), and Linux (x86-64 and ARM64). Language bindings are available for C/C++, Rust, JavaScript, C#, Python, and Go.

Sources

• Lore official site - Epic Games, accessed June 17, 2026
• Lore GitHub repository - MIT licensed source
• Hacker News discussion - 265+ comments, accessed June 17, 2026