Epic Games Built Its Own Git — Because Game Dev Broke the One We Have

Say “version control” and almost everyone reflexively thinks Git. So it raised eyebrows when Epic Games announced its own system, arguing that Git simply isn’t built for game development. The tool is called Lore. And coming from the company behind Fortnite and Unreal Engine, it’s worth paying attention to.

One honest note up front: this topic generated almost no community chatter over the past 30 days. So rather than chase real-time reactions, this piece digs into the structural questions — why a tool like this was needed, and how it differs from what we already use.

Why Game Developers Have Always Resented Git

Git is brilliant at handling text. It tracks changes line by line, recording only what moved. The problem is that game development doesn’t run on code alone.

A game is a mountain of large binary files — 3D models, textures, audio, video. When one of these changes even slightly, Git can’t analyze what actually moved. It just stores a whole new copy. Edit a few-hundred-megabyte texture ten times, and your repository balloons into gigabytes.

Then there’s how studios actually collaborate. Dozens of artists touch the same assets, and Git’s freewheeling merge model falls apart in front of binary files. Text conflicts can be merged automatically. A character model file cannot.

The Workarounds Everyone Tolerated

The industry hasn’t been sitting on its hands. The best-known patch is Git LFS (Large File Storage), which stores big files on a separate server and leaves only a lightweight pointer in Git. It puts out the immediate fire, but few call it a real fix. Setup is fiddly, and performance degrades again as projects scale.

The other heavyweight is Perforce. In reality, AAA studios have leaned on Perforce, not Git, for years — it’s strong at large files and centralized file locking. The catch: licenses are expensive, and to a Git-native generation of developers, the experience feels dated.

So game developers have been stuck in a familiar bind: Git is familiar but bloated, Perforce is powerful but pricey and old-school. That gap is exactly where Epic is wedging itself in.

What Lore Is Actually Aiming For

Lore’s core pitch is clear: treat large files as first-class citizens. Instead of designing for text and bolting binaries on afterward — Git’s original sin — Lore is built from the ground up to assume giant assets are the norm.

The other thing to watch is workflow. Epic isn’t pitching a bare repository tool. It’s sketching an integrated collaboration environment where artists and programmers work in the same flow, managing code and assets together. And here Epic holds a serious weapon: it already owns the sprawling Unreal Engine ecosystem.

If one company delivers the engine, the editor, and version control as a single package, that’s less plumbing for developers to wire up. No more bolting on Perforce here and configuring LFS there. That’s the bet.

So Is It a Real Alternative?

Be honest, and the variables pile up fast.

First, switching cost. A studio with a pipeline already built on Perforce or Git won’t rip it out lightly. However good Lore is, “what we have works well enough” keeps people put.

Second, lock-in. Plenty of teams will be wary of binding themselves deeper into Epic’s world. Engine from Epic, version control from Epic — that’s a lot of dependency pointed in one direction.

Third, generality. Git’s real power is that it’s the de facto standard for nearly all software, not just games. Whether Lore intends to step outside gaming or stay a game-only tool changes its stature entirely.

That said, the Epic name carries weight you can’t dismiss. Deep pockets, a huge user base, and a battle-tested proving ground in Fortnite. “A tool we built and refined by using it ourselves” is a genuinely strong sell.

The Takeaway

Lore is less a shiny new tool than a revival of an old question: can one general-purpose Git satisfy every domain? Git was born in the age of text. Whether it still holds up in an era of ever-heavier content is genuinely up for debate.

If you work with games, video, or large assets, you’ll eventually face the choice yourself. Are you willing to give up the familiar for a tool that fits better — or would you rather stay with the safety of the standard, friction and all? Lore’s fate comes down to how developers answer that.