Server Browser
A server browser lets players see a list of running game servers and choose one, rather than being assigned automatically by a matchmaker. Players filter by region, capacity, mode or custom rules. It suits persistent-world and community-hosted games, where who you play with matters as much as skill balance.
Also called
game server browser, server list
,
How Does a Server Browser Work?
A server browser is a directory of running game servers, with a way to claim a seat on one. Many games build the same pattern as a lobby list, where a platform service lists player-hosted lobbies rather than dedicated servers. To the player, both look the same: a list to pick from.
Most server browsers follow six steps:
A server registers. It publishes its address and metadata, such as map, mode, location, free seats and any custom rules.
It keeps checking in. The server sends a heartbeat on a schedule and updates its seat count as players come and go.
A player filters the list, by mode, map, ping or free seats.
The player reserves a seat. The reservation holds a slot, so two players can't take the last one at the same moment.
The player connects, and the server confirms the reservation. Unconfirmed reservations expire after a short time, so a player who never arrives frees the seat.
A server that stops checking in is removed, so the list doesn't offer servers that are gone.
The last two steps matter more than they look. A list goes stale in three ways: servers that are full, servers that are gone, and seats held by players who never arrived. Players searching for an "empty" or "not working" server browser may be seeing one of them.
How Does a Server Browser Show Each Server's Ping?
Ping is often the column players sort by, and getting it is harder than it looks.
The classic approach, used by Steam's master server, splits the work. The master server returns only a list of addresses, and the player's client then queries each server directly for its name, map, player count and ping (Valve Developer Community). Every row on the list is a separate query from the player's connection.
With thousands of servers, that adds up. Steam caps it with a pings-per-minute setting, and some players report their home router dropping the connection while a browser loads (FiveM forum, 2018). A lower cap is gentler on the router but fills the list more slowly, which can hide servers.
A newer approach measures latency once, to a few fixed points per city or region, and tags each server with its location. The list then sorts servers by the player's measured latency to their city, without pinging every server. That's the job of a ping beacon. It trades some precision for a list that loads quickly and doesn't flood the player's network.
Why Do Some Games Ship Without a Server Browser?
A server browser asks players to choose, and choice spreads them out.
Players split across servers. Each server needs enough players to feel alive. With a small or quiet player base, a browser can show many half-empty servers, and players often pass them over for the fullest ones. Fill drops, and with it session fill rate.
The list is a service of its own. It runs around the clock, answers every player who opens it, and has to hold up at launch, when every player refreshes at once.
Choosing takes longer than being placed. Browsing, filtering and retrying a full server add time before the first match.
Players notice when a browser is missing, though. Battlefield 6 players asked for a full server browser after launch, and one is scheduled for 8 December 2026 (Digital Citizen, 11 October 2026). The right answer often differs from one mode to the next.
Do Server Browser Games Need Servers Running All the Time?
Not necessarily. A browser lists whatever is running, and what runs can be persistent, started on demand, or both.
Persistent servers suit worlds that keep their state, community servers with their own admins, and long-running social spaces. They run whether anyone is playing or not.
On-demand servers start when players need a seat and stop when the session ends. A rule keeps a minimum number of joinable servers per mode or location, and starts another as they fill.
Edgegap's Server Browser does both through scaling policies: a fixed number of servers for QA, tournaments or persistent worlds, or prewarmed standby servers ahead of demand. When a player asks for a seat and none is free, the service tells the client to retry while capacity scales up. A new server takes a 2 second median to deploy (rolling 30 days, as of 18 September 2026), plus the game's own load time. For persistent servers, a common setup is a reserved fleet for a cost-effective share of overall traffic, and on-demand capacity for everything above it. Both are priced on the pricing page.
A word from our sponsor (ourselves!)
Most studios find their scaling ceiling at launch, in front of players. Edgegap reached 14 million concurrent sessions in a one-hour benchmark on real game server containers, so the limit you plan around is your game's, not your host's.
Edgegap's Take (just our opinion, take it with a grain of salt!)
Decide How Players Should Group Up in Each Mode, Then Pick a Matchmaker, a Server Browser, or Both
Choosing between a server browser and a matchmaker is a question about players before it's a question about tools: what kind of grouping experience should each mode create? The answer depends on the game type and the mode.
A place to start: for each mode, write one line on who plays with whom, how quickly they get in, and how long they stay together.
Matchmaking is often the better fit when that line says "fast" and "fair". It gets players into games and playing, which helps the player experience, and with well-tuned expansions and backfill it can keep the player base from splitting.
A server browser is often the better fit when the line says "the same server" or "the same people". It suits players looking for an established server: a community they know, with its admins and rules, the same group over weeks, the map, mode or mods they choose, and progress tied to that server.
Many games use both, such as matchmaking for quick and ranked play and a browser for community and custom servers. Edgegap runs both on one platform: matchmaking with expansions, backfill and SDKs for Unity and Unreal Engine, and a Server Browser with seat reservations and scaling policies.
,
