Why online games stop working when their servers shut down

A game can remain installed on a computer or console and still become impossible to play when its operator shuts down the servers. That happens because the program stored on the device is often only the client: the part that receives input, displays images and communicates with remote services. If sign-in, entitlement checks, a persistent world or essential rules depend on those services, keeping the client is not enough to recreate the experience.

Anthem provides a direct example. Electronic Arts said its servers would close on January 12, 2026, and explained that the game would stop working because it had been designed as an online-only title. That announcement is a company decision and a description of this particular product, not a rule for every multiplayer game. Other games divide responsibilities differently and can survive the end of official support.

What a server does beyond connecting players

In a simple match, a server may appear to be only a meeting point. In practice, it can authenticate accounts, confirm that a user has access to the product, organize matchmaking and assign a machine to run the session. Services such as Microsoft’s PlayFab provide infrastructure that can start instances according to demand and distribute them across regions to reduce latency.

The server can also be authoritative. Instead of treating everything sent by each device as true, it calculates or validates positions, damage, items and results. This centralized authority helps keep participants in the same state and makes some forms of cheating more difficult. In persistent games, the same layer may store characters, inventories, currencies, quests and changes to the world.

When that infrastructure is retired, different dependencies break in sequence. The client may fail at the login screen, be unable to find a session or return an error when requesting a profile. Even if a community redirects the connection address, it would still need to reproduce the expected protocol and, in many cases, rebuild rules and databases that were never publicly distributed.

Online games do not share one failure point

Different architectures produce different outcomes. In peer-hosted connections, one player can act as the host, although discovery and authentication services may still be necessary. A dedicated server separates the match from the clients. Steam’s documentation supports both developer-hosted servers and binaries that can be distributed for community hosting, demonstrating that dependence on a single operator is not a technical requirement in every design.

A service fully controlled by the publisher, by contrast, concentrates logic, data and operations in infrastructure the public does not possess. Hybrid models sit between those extremes: they may support local matches while keeping progression or social features online. As a result, “the servers closed” can mean losing only matchmaking in one game and losing the entire product in another.

Why an offline mode requires planning

Converting an online service is not simply a matter of removing an internet check. Developers may need to move server rules into the client, create local saves, decide what happens to inventories and adapt content tied to scheduled events. Security, privacy, third-party licensing and internal components that cannot be released without review add further constraints.

End-of-life plans can reduce the problem before it occurs. Options include a limited offline mode, local-network matches, distributable dedicated server software or enough documentation for authorized operators to maintain sessions. None of these choices automatically preserves stores, seasons and communities exactly as they existed. A more realistic goal is to retain a functional form of the work and clearly disclose its limitations.

Preserving the client does not preserve the service

The issue gained political weight through the European Stop Destroying Videogames initiative, which collected 1,294,188 verified statements of support. In June 2026, the European Commission said it would not, at that stage, propose a legal obligation to keep games playable after commercial withdrawal, but announced discussions toward a voluntary industry code for managing their end of life. That is the current regulatory position, not a guarantee that future games will remain accessible.

The challenge also differs from traditional emulation. The MAME case study shows how software can document old machines, but preserving an online game also requires the behavior of its servers and the relationships among multiple systems. Archiving the executable remains important, yet the work stays playable only when every indispensable dependency has a viable replacement.