Lore: Epic's Version Control vs Perforce and Git LFS

Lore: Epic's Version Control vs Perforce and Git LFS

Lore is Epic's version control system, built for game projects with large binary assets and open-sourced so teams can adopt or self-host it. It matters because game version control has long been a choice between Perforce, which handles big binaries well but is heavy to run, and Git with LFS, which developers know but which strains on large .uasset files. Lore aims at that gap: binary-friendly like Perforce, more approachable to adopt.

This post explains what Lore is, how it compares with Perforce and Git LFS, and who should look at it, as of September 2026.

What is Lore?

Lore is a version control system Epic built for the way games are actually made: hundreds of gigabytes of binary assets alongside code, many people touching the same project, and files that do not merge like text. Epic uses it internally on large projects and has opened it up so studios can use it. The design goals are the ones game teams care about: handle large binaries without choking, scale to big teams and repositories, and be less operationally painful than the traditional heavyweight option.

Why game projects need special version control

Because a game project is mostly binary, and binaries break the assumptions Git was built on. A .uasset, a texture or an audio file cannot be line-merged, so two people editing the same asset is a conflict you resolve by choosing a version, not by merging. Projects also run to hundreds of gigabytes, which general-purpose tools handle badly. That is why studios reach for Perforce or Git LFS: both address large binaries, each with its own cost. Lore is Epic's answer shaped specifically for this problem.

Lore vs Perforce vs Git LFS

The short version: Perforce is the entrenched choice with the most tooling and the most operational weight. Git LFS is familiar and light until asset sizes grow. Lore targets the middle: Perforce-style binary handling with a more open, adoptable footprint.

Should your studio switch to Lore?

If Perforce works and you are heavily invested in it, there is no urgency to move. If you are on Git LFS and feeling the strain as assets grow, or you are starting fresh and want a binary-friendly system without Perforce's operational cost, Lore is worth a serious look, especially since it is open-source and self-hostable. As with any version control migration, pilot it on a non-critical project first, because moving history and retraining a team is real work regardless of how good the destination is.

FAQ

What is Lore in Unreal Engine? Lore is Epic's version control system, built for large binary game assets and open-sourced so studios can adopt or self-host it.

Is Lore better than Perforce? It targets the same binary-heavy use case with a lighter, more open footprint. Perforce has more tooling and industry entrenchment. Which is better depends on your team's investment and scale.

Can I use Lore instead of Git LFS? Yes, and it is aimed at teams that find Git LFS strains as asset sizes grow. Pilot it before migrating a live project.

Is Lore open-source? Yes. Epic open-sourced Lore so studios can use and self-host it.

Closing

Lore is Epic solving a problem every game team knows: version control that respects large binaries without the operational weight of the traditional option. It will not displace Perforce overnight, but as an open, binary-friendly system it gives studios a real third choice. Pilot before you migrate. Ludus AI, the most advanced AI assistant for Unreal Engine, works inside the editor on UE 5.4 to 5.8 regardless of the version control underneath, so your choice here does not change how you work with it.

Start building with Ludus AI