Digging Their Own Games Back Up: How Indie Devs Are Becoming Their Own Archivists

There's a particular kind of grief that comes with watching something you made vanish from the internet. Not dramatically — no explosion, no announcement. Just a storefront delisting, a server shutdown, a domain that quietly stops renewing. For a lot of indie developers who built games in the Flash era, the early mobile boom, or the first wave of Steam Greenlight, that grief is extremely familiar.

But something has shifted. More and more of those same developers are coming back around, dusting off old project files, and figuring out how to bring their forgotten work into 2024. Not because there's money in it — usually there isn't — but because the alternative is letting something they poured themselves into simply cease to exist. And that, it turns out, is a hard thing to accept.

The Problem Nobody Talks About

Game preservation gets a lot of attention when it involves big publishers and beloved franchises. But the quiet crisis lives further down the food chain. Thousands of indie games — genuinely interesting, sometimes brilliant ones — exist only as faded memories in the minds of the people who played them once on a now-defunct platform.

The challenge for indie developers trying to rescue their own work is that they're doing it without a team of engineers, without a legal department, and often without the original source code. That last part is more common than you'd think. Hard drives fail. Cloud services shut down. Version control wasn't always a habit. Some developers are essentially reconstructing their own games from scratch, using old screenshots, player recordings, and whatever fragments survived.

And yet they're doing it anyway.

What Resurrection Actually Looks Like

For some developers, bringing a game back means a straightforward port — taking something that ran on an obsolete runtime and rebuilding it in a modern engine like Unity or Godot. It sounds simple. It rarely is. Old code carries the fingerprints of whoever wrote it years ago, often under pressure, often with workarounds that made sense at the time and make no sense now. Untangling that is part archaeology, part therapy.

Others take a different approach: the spiritual successor. Rather than fight with decade-old spaghetti code, they use their original game as a blueprint and build something new that captures the same feeling. This path comes with its own emotional weight. At what point does a remake stop being a preservation effort and start being a new game? Developers wrestle with that question more than you'd expect.

Then there's the remaster route — keeping the bones of the original intact while updating the presentation enough that modern players can actually access it without fighting their operating system. This tends to be the path that resonates most with existing fans, who want the thing they remember, not a reimagining of it.

The Emotional Math

Here's the part that doesn't show up in patch notes: bringing back an old game means spending a lot of time with a version of yourself you may have complicated feelings about. The code reflects who you were. The design decisions you made when you were younger, less experienced, and probably working a day job on top of all of it.

Developers who've gone through this process often describe it as unexpectedly personal. One common thread is the moment of reconnecting with why they made the game in the first place — the specific itch it was scratching, the thing they wanted to exist in the world. That clarity can be motivating. It can also be painful when the execution doesn't match the memory.

There's also the question of the community. Some of these games built small but devoted followings before they disappeared. Those players have been waiting, sometimes for years. The pressure to deliver something worthy of that loyalty is real, even when the developer is working alone in their spare time with no budget.

What This Means for Preservation Broadly

The mainstream conversation about game preservation tends to center on corporate actors — what Nintendo is or isn't doing, whether major publishers will open up their back catalogs, whether streaming services will keep older titles available. Those are important conversations. But they leave out the long tail of indie work that doesn't have a corporation behind it.

What's happening right now, with individual developers taking preservation into their own hands, is genuinely significant. It's messy and inconsistent and depends entirely on whether the original creator has the time, energy, and source files to make it happen. But it's producing results that no institutional effort would prioritize.

The games that get rescued this way aren't always the most commercially significant ones. They're the ones that meant something to someone — to the developer, to a small community of players, to a specific moment in gaming history that would otherwise go unrecorded.

Why It Matters to Players Like Us

If you grew up playing games on platforms that no longer exist — Newgrounds, early iOS, GameJolt in its early days, or any number of Flash portals — there's a decent chance something you loved is gone. Maybe permanently. But there's also a chance the person who made it is out there, thinking about bringing it back.

The best thing the community can do is make noise. Leave reviews. Post about old games on forums. Tag developers. Let them know their work is still remembered. More than one resurrection project has started because a developer stumbled across a thread where people were still talking about their game years after it disappeared.

Game preservation isn't just a job for archivists and corporations. Sometimes it starts with a comment section. Sometimes it starts with someone who made a game ten years ago, reading that people still care, and deciding that's enough reason to start digging.

At Cazimbo, we've always believed that the best games aren't always the most visible ones. The ones worth finding are often buried — and the people who made them are sometimes the best ones to do the digging.