Here One Day, Gone the Next: Why Indie Games Are Disappearing and What Developers Can Do About It

You remember that quirky little puzzle-platformer you played back in 2017 — the one with the hand-drawn art style and the banger lo-fi soundtrack? You told yourself you'd go back to it someday. Now you search for it on Steam, on the App Store, on itch.io, and it's just... gone. No trace. No explanation. Not even a forum post with a download link.

This isn't a rare edge case. It's becoming the norm.

The indie game scene has always thrived on scrappiness and passion. Small teams, tight budgets, big ideas. But that same scrappiness has created a preservation crisis that almost nobody is talking about loudly enough. Indie games — the hidden gems that Cazimbo readers dig up and love — are disappearing at a rate that should make every gamer sit up straight.

The Invisible Architecture Holding It All Together (And Falling Apart)

When a major studio releases a game, there's usually a corporate paper trail a mile long — licensing agreements, source code repositories, legal teams, and at least a few redundant backup systems. When a two-person indie team releases their passion project through a mid-tier publisher, the situation is wildly different.

Publishers fold. Contracts expire. Rights get tangled up in bankruptcy proceedings. And when that happens, the developer — the actual human being who spent three years building the thing — can find themselves locked out of their own creation. They can't update it, can't re-release it, and in some cases can't even legally distribute it for free.

This happened in a very public way with the cult hit Fez, which had its own high-profile drama around updates and platform relationships. But for every Fez, there are dozens of smaller titles where the story ends quietly. The game just disappears, and nobody writes an article about it.

When the Server Shuts Down, So Does the Game

Online-dependent indie games face an even grimmer reality. Any indie title that requires a server connection to function — whether for multiplayer, DRM, or even basic save-syncing — is essentially living on borrowed time from the moment it launches.

Small studios can't afford to maintain server infrastructure indefinitely. When the money runs out or the team moves on, those servers go dark. And unlike a cartridge you can blow into and slot back into a console, a dead server means a dead game. No workaround. No emulator. Just nothing.

Preservation advocates like those at the Video Game History Foundation have been sounding this alarm for years, pointing out that an estimated 87% of classic games are already out of print or otherwise inaccessible. Indie titles, with their leaner resources and more fragile institutional backing, are arguably even more vulnerable than the console releases that preservation efforts traditionally focus on.

Developers Racing Against Their Own Timelines

Talk to indie developers who've been through a publisher collapse, and you'll hear the same panic in their voices. One common story: a developer spends years building a game, signs with a small publisher for distribution and marketing support, and then watches that publisher quietly close its doors eighteen months after launch. Suddenly, the game's storefront listings are in limbo, the build files are on servers the developer no longer has access to, and the source code — if it was ever properly backed up — might be sitting on a hard drive somewhere in a former employee's garage.

Some developers have managed to claw things back. There are stories of devs spending months in legal negotiations just to regain the rights to their own work, then scrambling to find source files from old teammates who'd long since moved on to other projects. It's a nightmare scenario, and it's one that the current indie publishing ecosystem makes surprisingly easy to stumble into.

What Preservation Experts Are Saying

People who work in game preservation — archivists, historians, and the volunteer communities that support them — are increasingly turning their attention toward indie titles, but they'll be the first to tell you the challenge is enormous.

Unlike retro cartridges, which can be physically dumped and stored, indie games often exist across fragmented ecosystems: a Steam build here, a DRM-free itch.io version there, a mobile port that's already been delisted. Tracking down every version, every patch, every build variation is a massive undertaking, and most preservation groups are working with limited resources and no official support from the platforms themselves.

The Internet Archive has done heroic work hosting abandonware and older titles, but it operates in a legal gray zone that makes hosting actively delisted commercial games complicated. Without formal cooperation from developers and platforms, preservation is largely reactive — archivists saving things after they've already started to disappear.

What Developers Can Do Right Now

If you're an indie developer reading this, here's the practical reality: no one is coming to save your game for you. The good news is there are concrete steps you can take today to make sure your work survives.

Control your source code. Use a version control system like Git and maintain your own off-platform backups. Don't rely solely on a publisher or a third-party service to store your build files. If your publisher relationship sours, you want to be able to walk away with everything intact.

Read your contracts carefully. Rights reversion clauses are your best friend. Make sure your publishing agreement includes clear language about what happens to distribution rights if the publisher ceases operations. If your current contract doesn't have this, talk to a lawyer.

Release a DRM-free version. Even if your primary distribution is through Steam or the Epic Games Store, consider maintaining a DRM-free build on itch.io. If your storefront listings ever get pulled, that version can survive.

Document everything. Keep records of your assets, your build processes, your dependencies. Future-you — or a preservation archivist — will thank present-you for it.

Consider open-sourcing after a window. Some developers have chosen to release their source code publicly after a set period, effectively handing preservation off to the community. It's not the right move for everyone, but it's worth thinking about.

The Games Worth Saving

Here at Cazimbo, we spend a lot of time digging up the games people never forgot — the ones that left a mark even if they never hit mainstream radar. A huge chunk of those games are indie titles: the weird little experiments, the heartfelt one-person projects, the niche genres that big studios wouldn't touch.

The thought that games like these could vanish not because nobody cared, but because the infrastructure around them crumbled quietly, is genuinely frustrating. These aren't obscure relics of a pre-internet era. These are games released in the last decade, sometimes the last five years, already at risk of becoming inaccessible.

The preservation conversation can't just be about NES cartridges and Dreamcast discs anymore. It has to include the indie games that are shaping what gaming looks like right now — before they're gone and we're left searching for them the same way we search for lost Flash games from 2005.

The clock is already running.