Epic Games Open-Sources Lore: A Rust-Built VCS That Finally Handles Large Game Files

by Geth Author

Game studios have had exactly two real options for large-file version control for decades: pay Perforce licensing fees, or suffer through Git LFS workarounds that were never designed for binary-heavy pipelines. On June 17, 2026, Epic Games open-sourced Lore, a version control system built specifically for the problem Git was never meant to solve.

The actual problem with Git for game dev

Git is brilliant for text. It's miserable for the assets that make up the bulk of a real game project — multi-gigabyte textures, audio banks, 3D models, video cutscenes. Git LFS alleviates the worst of this by storing large files externally, but it's a retrofit, not a design. Locking, conflict resolution, and branching behavior all become friction points as project size grows.

Perforce has filled the gap, but it's expensive, closed-source, and carries the operational weight of a centralized server product from the pre-cloud era. Most indie and mid-size studios use it anyway because the alternatives are worse.

What Lore is

Lore is written in Rust and licensed under MIT — meaning it's genuinely free and open, not "open core" with the important bits paywalled. The full source is on GitHub at version 0.8.3, currently pre-1.0 and not yet recommended for production use.

Architecturally, Lore combines several ideas into a coherent whole:

  • Content-addressed storage with fragment-level deduplication — only unique file chunks get stored, keeping repository size manageable as assets evolve.
  • Sparse, lazy working copies — artists and developers check out only the subset of assets they actually need, not the entire repository.
  • Free branching — unlike Perforce's stream model, branches are cheap and don't require server-side configuration.
  • Centralized server of record — for access control, conflict resolution, and durability. Not purely distributed like Git.

The design is also meant to be approachable for non-programmers. 3D artists shouldn't need to learn command-line VCS concepts to commit a texture update, and Lore's intended UX reflects that priority.

Why this matters beyond Epic

Epic ships Unreal Engine to hundreds of thousands of developers. If Lore matures into a reliable production tool, it could become the default VCS for Unreal-based projects the way Git became default for web development. The MIT license means studios can self-host, fork, or integrate without license negotiation.

The Phoronix writeup and the It's FOSS analysis both note the cautious framing: this is a 0.8 release, not a Perforce replacement you should migrate to next week. But the direction is clear, and the backing of a company with Epic's infrastructure scale gives it credibility smaller projects couldn't provide.

If you run a game studio still paying Perforce invoices, Lore is worth watching closely.