Server Not Showing in Server Browser
A player opens Unturned™, clicks Play, opens the server browser, and scrolls. The server they want to join is not there. They refresh. Still not there. They search by name. Empty results. They know the server is running — friends are on it right now, the operator's Discord confirms it is online — but the browser will not show it.
This is one of the most frustrating multiplayer issues in Unturned because nothing has actually broken from the player's perspective. The game runs, the network is up, the friends list works, but the specific server they want has disappeared from view. This article walks through the most common reasons an Unturned server fails to appear in the server browser and gives a numbered diagnostic flow for each.
If the server appears in the browser but the join fails, see Unable to Connect to the Server instead. The cause sets differ and the diagnostic flow is different.
Validate that the problem is real
The Unturned server browser shows up to a few thousand servers at a time, filtered by the criteria the player has selected. Many players assume "the server is not in the browser" without first confirming what their filters are set to. The default filters include several settings that hide a large fraction of community servers, including the modded-content filter, the password-protected filter, and the regional filter.
Before assuming the server is genuinely missing, work through the diagnostic flow. The cause is filter-related in a large majority of cases.
Prerequisites
- A current installation of Unturned from the official Steam store page.
- The Steam client running and signed in.
- The server's name, IP address, and port (where known) — useful for direct-connect fallback.
- Network access to the public internet.
- Patience: the server browser refresh takes 30 to 60 seconds for a full enumeration of public servers.
What you'll learn
- How Unturned's server browser fetches and filters the list of public servers.
- The full set of filters that can hide a server from the browser, and how to disable each.
- How to distinguish a server that is genuinely offline from one that is online but invisible.
- How the Steam master server network publishes server heartbeats and what happens when those heartbeats fail.
- How to use direct-connect to bypass the browser entirely.
- How to use the in-game search to find a specific server by name.
- How Workshop content filtering interacts with the browser display.
- How regional filters and ping thresholds hide servers that would otherwise appear.
Background: how the server browser works
Understanding what the browser does internally is the key to diagnosing browser-related problems. The browser is not a list of every Unturned server in the world; it is a filtered, paginated view of the servers that Steam's master server network knows about, further filtered by the local client's settings.
The sequence is:
- The Unturned client sends a query to Steam's master server network asking for the list of active Unturned servers.
- The master server network returns a paginated list of servers that have recently sent a heartbeat.
- The client queries each server's metadata port for current player count, map, mod list, and version.
- The client applies the local filter settings: region, ping threshold, full server filter, password-protected filter, mod filter, search string.
- The client displays the filtered list.
A server can be absent from the browser at any step in this sequence. Identifying which step is the cause narrows the resolution.
The diagram above shows the four points where a server can be excluded: the master server has not received a recent heartbeat, the server fails to respond to the metadata query, the local filters exclude the server, or the rendering step truncates the list past where the server appears.
Symptom-to-cause map
| Symptom | Most likely cause | First resolution |
|---|---|---|
| Server shows for friends but not for you | Regional filter mismatch | Set region to "Any" |
| Server is modded and absent | Mod filter set to "vanilla only" | Toggle modded filter |
| Server is password-protected and absent | Password filter excluding it | Toggle password filter |
| Server is full and absent | Full-server filter active | Toggle full-server filter |
| Server has high ping and absent | Ping threshold filter active | Raise ping threshold |
| Server never shows for anyone | Server's heartbeat is broken | Operator-side fix |
| Server shows briefly then disappears | Server's metadata query is failing | Operator-side fix |
| Browser is empty entirely | Master server outage or client issue | Restart Unturned and Steam |
| Search by name finds nothing | Server name has unicode or filter blocks it | Direct-connect by IP |
| Server in browser but join fails | Different problem | See linked article |
If the symptom in the player's situation matches one of the rows above, the corresponding resolution method below covers the fix.
Did you know?
Unturned's server browser limits the number of servers it displays at one time. Servers below the visible range are still in the list internally but require scrolling or sorting to reach. A server that looks absent may simply be lower in the list than the player has scrolled. The cohort recommendation is to use the search box rather than scrolling for any specific server.
Diagnostic steps
Step 1: Open the filters panel and review every filter
The single most common cause of "server not showing" is an active filter that excludes the server the player wants. The Unturned server browser has a filters panel that the player can open from the browser screen.
The filters that can hide a server include:
- Region — by default may be set to a specific region; set to "Any" to see all.
- Ping threshold — by default may exclude servers above a certain ping; raise to 999 to see all.
- Mod filter — separate toggles for vanilla, modded, and Workshop-mod servers.
- Password filter — separate toggle to include or exclude password-protected servers.
- Full filter — separate toggle to include or exclude full servers.
- Anti-cheat filter — separate toggle for EAC-required, EAC-optional, and EAC-absent servers.
- PvP/PvE filter — separate toggles for PvP, PvE, and arena servers.
- Map filter — restrict to a specific map.
Open the filters panel and set every filter to the most permissive setting ("Any" or "All" where available). Then refresh the browser and look for the server.
Step 2: Use the search box
The browser has a search box that filters by server name. Enter a substring of the server's name and the browser shows only matching servers.
The search is case-insensitive and matches substrings, not whole words. A server named "Horizon Life RP" matches the search "horizon", "life", "rp", "zon", or any other substring of the name.
The search does not match across Unicode normalisation: a server name with special characters (decorative symbols, accented letters, non-Latin scripts) may not match a search with the corresponding plain-ASCII text. If the search is failing, ask the operator what the server's name is exactly and copy-paste the name into the search box.
Step 3: Compare with a friend who can see the server
If a friend can see the server in their browser, the cause is on the local client. Compare filter settings with the friend; the difference between their filters and yours is likely the cause.
If no friend can see the server, the cause is on the server side or the master server's side. The server's heartbeat may be broken, or the master server may be in the middle of an outage.
Step 4: Test direct-connect
The direct-connect screen bypasses the browser entirely. If direct-connect succeeds, the server is online and the browser is the cause. If direct-connect fails, the server is offline or the network is the cause.
From the Unturned main menu:
- Click Play.
- Click Connect.
- Enter the server's IP address (or hostname) and game port.
- Click Connect.
A successful direct-connect that bypasses a missing-from-browser server confirms the issue is browser-side, not server-side. The browser will catch up within minutes; a refresh after the direct-connect typically shows the server.
Step 5: Restart Unturned and the Steam client
A long-running Steam client occasionally enters a state where the server browser does not refresh correctly. The fix is to fully quit Steam (via the tray icon, not by closing the window) and reopen.
The fix takes about a minute and resolves a surprising fraction of "server is missing" issues, particularly after a long Steam session.
Step 6: Check the global server browser via Steam
Steam has a global server browser independent of Unturned's in-game browser. The global browser shows every server registered with Steam's master server network, including Unturned servers.
To open the Steam server browser:
- Open Steam.
- From the View menu, choose Servers.
- Switch to the Internet tab.
- Filter by game name "Unturned".
If the server appears in the Steam server browser but not in the Unturned in-game browser, the in-game client's filtering is the cause. If the server appears in neither, the server's heartbeat is broken or the master server has not received it.
The flowchart above is the recommended order of operations when diagnosing a missing-from-browser server.
Resolution methods
Method 1: Reset all browser filters
The all-permissive filter configuration is the diagnostic baseline. Once the server appears with all filters open, re-narrow the filters one at a time to identify which filter was excluding the server.
- Open the Unturned server browser.
- Click the filters icon.
- Set Region to "Any".
- Set Ping max to 999.
- Enable the modded, vanilla, and Workshop-mod toggles.
- Enable both the password-protected and not-password-protected toggles.
- Enable both the full and not-full toggles.
- Enable both the EAC and non-EAC toggles.
- Enable all PvP/PvE toggles.
- Refresh the browser.
- Search by the server's name.
If the server appears with all filters open, the cause was a filter. Re-narrow filters until the server disappears; the last toggle changed is the cause.
Common mistake
Refreshing the browser before adjusting the filters. The browser caches its filtered view until the filters change or the refresh button is pressed. Adjust the filters first, then refresh.
Method 2: Search by exact server name
If the operator's server has a specific name, search for it directly.
- Open the server browser.
- Click the search box.
- Paste the server's exact name (case does not matter, but special characters do).
- Wait for the browser to update.
- The matching servers appear at the top of the list.
If the search returns no results, try a shorter substring. For example, "Horizon Life RP" might fail if there is a special character in the name; "Horizon" alone is more likely to match.
Method 3: Use direct-connect
If the browser is broken or filtered too aggressively to find the server, direct-connect bypasses the browser entirely.
- From the main menu, click Play.
- Click Connect.
- Enter the server's IP address.
- Enter the game port.
- If the server requires a password, enter it.
- Click Connect.
The direct-connect flow is fast and reliable. The cohort recommendation is to bookmark frequently played servers' IPs and ports for direct-connect use.
Pro tip
Many operators publish a one-click direct-connect link on their Discord. The link, when clicked, opens Unturned and starts the join automatically. The link uses the steam://connect/<ip>:<port> URL scheme. If the operator does not publish such a link, ask in their Discord; many will share it on request.
Method 4: Restart Steam and Unturned
A long-running session occasionally enters a state where the server browser fails to refresh. A full restart of both Steam and Unturned resolves the state.
- Fully quit Unturned.
- Right-click the Steam icon in the Windows system tray.
- Choose Exit.
- Wait for the Steam process to fully exit (check Task Manager for
steam.exe). - Reopen Steam.
- Wait for Steam to fully load.
- Reopen Unturned.
- Open the server browser and search again.
Method 5: Check the Steam global server browser
The Steam global server browser is an independent view of the master server network. Use it as a second source of truth.
- Open Steam.
- From the View menu, choose Servers.
- Switch to the Internet tab.
- In the search field, type "Unturned".
- Press Refresh.
- Scan the list for the server's name.
If the server appears in the Steam global browser but not in Unturned's in-game browser, the in-game client filtering is the cause. If the server appears in neither, the server's heartbeat is broken.
Method 6: Check Steam master server status
Steam's master server network occasionally experiences outages that hide every server from every browser. The symptom is a near-empty browser for every Steam multiplayer game, not just Unturned.
If the browser is empty entirely (not just missing one server), open a different Steam multiplayer game and check whether its browser is also empty. If both are empty, the master server network is the cause. Wait for Steam to resolve the outage.
Method 7: Reach out to the server operator
If the server is missing from the browser for every player on every device, the cause is server-side. The operator needs to confirm:
- The server process is running.
- The server's heartbeat thread is functioning.
- The server's query port is open on the host firewall.
- The server's metadata (name, map, max players) is being published correctly.
For operators, the Recommended Server Hardware reference covers the host-side configuration practices that keep servers visible to the master server network. The standard checklist is firewall open on UDP query port, heartbeat thread running, server process not in a stuck state, and server bound to the correct network interface.
Did you know?
A common operator-side issue is the server binding to localhost (127.0.0.1) rather than the public network interface. A localhost-bound server is invisible to the master server network because the heartbeat cannot reach Steam from inside the loopback interface. The fix is to bind the server to 0.0.0.0 (all interfaces) or to the specific public IP.
Method 8: Bypass with a Workshop collection link
For modded servers, the operator commonly publishes a Steam Workshop collection that includes the server's direct-connect link. Subscribing to the collection and using the included link bypasses the browser.
- Open the operator's Workshop collection link in a web browser.
- Click Subscribe All.
- Open Unturned and wait for the content to download.
- Use the direct-connect link or the IP/port from the collection's description.
Method 9: Reset Steam network configuration
A broken Steam network configuration can prevent the master server query from completing. The fix is a Steam-level network reset.
Open PowerShell as administrator and run:
powershell
& "C:\Program Files (x86)\Steam\steam.exe" -clearbetaThen close Steam and reopen. The flag clears any cached beta-channel settings and forces Steam to re-fetch the master server list.
Critical warning
The -clearbeta flag is safe but does cause Steam to re-initialise. Allow Steam to fully complete its startup (which may take a minute) before opening Unturned. Force-quitting Steam during the re-initialisation can leave the client in an inconsistent state.
Method 10: Confirm Unturned is current
An out-of-date Unturned client may fail to communicate with the current master server protocol. Confirm Unturned is current:
- Open Steam.
- Right-click Unturned in the library.
- Choose Properties → Updates.
- Confirm "Always keep this game updated" is selected.
- If an update is pending, allow it to complete before reopening the browser.
Method comparison
| Method | Time required | Risk level | When to apply |
|---|---|---|---|
| 1. Reset all filters | 2 minutes | None | Server visible to others |
| 2. Search by name | 1 minute | None | Specific server known |
| 3. Direct-connect | 2 minutes | None | Browser broken or filter issue |
| 4. Restart Steam and Unturned | 3 minutes | None | Long-running session |
| 5. Steam global browser | 2 minutes | None | Confirm server visibility |
| 6. Steam master status | 1 minute | None | Browser empty entirely |
| 7. Contact operator | Variable | None | Confirmed server-side |
| 8. Workshop collection | 5 minutes | None | Modded server |
| 9. Steam network reset | 5 minutes | Medium | Multiple browser issues |
| 10. Update Unturned | 5 to 30 minutes | None | Pending Steam update |
The methods are ordered roughly by ease and likelihood. Method 1 is the fastest and most often the fix.
Advanced considerations
Workshop content and modded server visibility
Modded servers often require the client to have specific Workshop mods installed before the server appears in the browser. The Unturned client filter for "modded servers" has two layers: a setting for whether to show modded servers at all, and a setting for whether to show modded servers whose required content the client does not have.
The cohort recommendation is to enable both "show modded servers" and "show modded servers I lack content for". The second setting allows the player to see modded servers in the browser before subscribing to the required Workshop content; clicking the server prompts the player to subscribe to the missing content.
Regional filtering and ping thresholds
The region filter restricts the browser to servers in a specific geographic region. A player in North America with the region filter set to "North America" cannot see servers in Europe or Asia.
The ping threshold is a separate filter. A server with a ping above the threshold is excluded even if it is in the player's selected region. The threshold defaults to a relatively low value to prioritise low-latency servers; players seeking a specific server in a different region may need to raise the threshold to 999 to see it.
The combination of region and ping filters hides a large fraction of servers from the average player's view. The cohort recommendation is to set both to permissive values when troubleshooting.
Anti-cheat filtering
The EAC filter has three settings: EAC-required, EAC-optional, and EAC-absent. Servers that require EAC are typically the largest community servers. Servers that do not require EAC are typically smaller community servers or specialised mod-testing setups.
A player who has the EAC filter set to "EAC-required only" cannot see EAC-absent servers. A player with "EAC-absent only" cannot see EAC-required servers. The cohort recommendation is to enable all three settings unless there is a specific reason to filter.
Sandbox-versus-survival filtering
Unturned has multiple game modes. The browser has filters for the active game mode of each server. A player searching for a creative-sandbox server with the survival filter active will not see the sandbox server.
Game-mode filters are sometimes confused with map filters; the two are independent. A map filter restricts to specific maps; a game-mode filter restricts to specific modes regardless of map.
Browser pagination
The Unturned browser does not show every server on a single page. The browser fetches a paginated batch and displays the current page. A server may be present in the master server's list but in a page the player has not scrolled to.
The cohort recommendation is to use the search box rather than scrolling for any specific server. Search bypasses pagination and finds the server regardless of which page it would appear on.
Frequently asked questions
Why can't I see any Unturned servers?
If the browser is empty entirely, the most likely causes are: a Steam master server outage, a broken Steam client, an out-of-date Unturned client, or aggressive filters set to a configuration that excludes everything. Reset all filters to permissive values, restart Steam, and confirm Unturned is current. If the browser is still empty, the master server network is likely in an outage.
Why doesn't my friend's server show up?
If your friend's server is online (they can join, you cannot see it), the cause is likely a filter mismatch between your client and theirs. Compare filter settings with your friend. The most common differences are the region filter, the modded filter, and the password-protected filter. The friend may have a more permissive filter set than you do.
How do I see modded servers in Unturned?
In the server browser filters panel, enable the "Modded" toggle. Most clients have it enabled by default, but some have it off. Also enable "show modded servers I lack content for" to see modded servers before subscribing to their Workshop content.
What is the Unturned server browser filter?
The server browser filter is a set of toggles and ranges that restrict which servers the browser displays. The filters include region, ping threshold, modded/vanilla, password-protected, full servers, EAC requirement, and game mode. Open the filters panel from the server browser screen.
Why does my server show in Steam but not in Unturned's browser?
The Unturned client applies additional filtering on top of the Steam master server's list. If the server is in the Steam global server browser but not in Unturned's in-game browser, an Unturned-specific filter is excluding it. Check the in-game filters and reset to permissive values.
Can I get a server's IP from the browser?
Yes. Click the server in the browser to expand its detail panel. The IP and port are shown in the panel. Copy them for use with direct-connect.
Does the server browser need internet access separately?
No. The server browser uses the same internet connection as the rest of Unturned. If the game itself is connecting to Steam and other multiplayer features work, the browser has the access it needs.
How long does it take for a new server to appear in the browser?
A newly-started server typically appears within one to five minutes. The server sends a heartbeat to the master server network on a regular interval; the master server publishes the server after receiving the first heartbeat. If the server has been online for more than five minutes and is still missing, the heartbeat is likely broken.
Why does a server appear briefly then disappear?
Servers that appear and disappear from the browser are usually failing the metadata query. The browser includes the server in the initial list because it received a heartbeat but excludes it on later refreshes when the metadata query times out. The cause is server-side, typically a firewall rule that blocks the query port from external traffic.
Can I bookmark servers in Unturned?
The favourites feature in the server browser bookmarks specific servers. To favourite a server, click the star icon next to the server entry. Favourited servers appear on the Favourites tab of the browser, which is independent of the main browser's filters.
What's the difference between the Steam server browser and Unturned's in-game browser?
The Steam server browser is a generic browser provided by Steam that shows servers for every game registered with the master server network. The Unturned in-game browser is specific to Unturned and adds Unturned-specific filters (game mode, map, mod filter). The Unturned browser also performs the metadata queries needed to show map/players/mods, which the Steam browser does not.
Why is the modded server filter off by default?
The default depends on the Unturned client version. Some versions ship with modded servers enabled; others ship with modded disabled. If the player has not changed the setting recently, the default is whatever was set during the install. Open the filters panel and verify.
Does Unturned support LAN servers?
Yes. LAN servers appear on the LAN tab of the server browser, which is independent of the main browser. LAN servers are discovered by UDP broadcast on the local network; they do not require a heartbeat to the master server.
What is a "heartbeat" for a server?
A heartbeat is a small periodic packet the server sends to the Steam master server network to announce it is online. The master server uses the heartbeat to maintain its list of active servers. A server that stops sending heartbeats is removed from the list after a few minutes.
Best practices
- Reset filters to permissive values when troubleshooting; re-narrow them after the server is found.
- Bookmark frequently played servers via the Favourites tab.
- Use the search box rather than scrolling for any specific server.
- Use direct-connect to bypass the browser when the operator publishes an IP.
- Subscribe to the operator's Workshop collection for modded servers to ensure required content is installed.
- Confirm Steam and Unturned are both current before troubleshooting browser issues.
- For operators, monitor the server's heartbeat and metadata query independently of the game-server process.
Appendix A: Steam master server network detail
The Steam master server network is the registry of every active server for every Steam-registered multiplayer game. Understanding its operation helps interpret browser-related symptoms.
Master server architecture
The master server network consists of multiple Steam-operated server nodes geographically distributed. An Unturned server sends its heartbeat to the nearest node; the node propagates the server's registration to the network. The Unturned client queries the network to fetch the current server list.
The propagation is not instantaneous. A new server can take one to five minutes to appear in browsers worldwide. Conversely, a server that has gone offline can take one to five minutes to disappear from browsers.
Heartbeat protocol
The server sends a UDP packet to a known master server endpoint on a regular interval (commonly every 30 to 60 seconds). The packet contains the server's name, current player count, max player count, map, mod list, and version.
The master server records the most recent heartbeat. If no heartbeat is received within a timeout window (typically several minutes), the master server removes the server from the active list.
Implications for browser symptoms
| Symptom | Master server interpretation |
|---|---|
| Server appears immediately | Heartbeat reached master server, propagation complete |
| Server appears after 1-5 minutes | Heartbeat reached master server, propagation in progress |
| Server appears intermittently | Heartbeat is unreliable; some heartbeats reach the master |
| Server never appears | Heartbeat is not reaching the master server |
| Server appears but join fails | Heartbeat works, game port is unreachable |
The cohort recommendation for operators is to monitor heartbeat success via the server's log file. The Unturned server logs heartbeat attempts and failures.
Master server outages
Steam master server outages are rare but produce a characteristic symptom: every Steam multiplayer game's browser is empty. If the symptom is restricted to Unturned, the cause is not the master server; if every Steam multiplayer game has an empty browser, the master server is likely the cause.
Appendix B: Browser performance and scaling
The Unturned server browser performs a metadata query against every server in the list. With thousands of servers active, the cumulative query time can be measurable.
Pagination
The browser fetches a paginated batch and displays the current page. The page size is fixed by the client. The cohort recommendation is to use the search box rather than scrolling for any specific server.
Query parallelism
The browser issues metadata queries in parallel. The parallelism level is fixed by the client. On a slow network connection, the browser may take longer to populate; on a fast connection, the browser populates quickly.
Refresh cost
A full browser refresh re-queries every server in the visible list. The cost is measurable: 30 to 60 seconds for a full refresh of a populated browser on a typical connection. The cohort recommendation is to use the search box to narrow the visible list before refreshing.
Pro tip
The Favourites tab refreshes much faster than the main browser because it only queries the favourited servers. Bookmark frequently played servers and use the Favourites tab as the primary entry point. Refresh cost on the Favourites tab is typically under 5 seconds.
Appendix C: Cohort observed resolution rates
The cohort has tracked resolution rates for "server not showing" reports across community channels. The aggregate rates below are useful for ordering the diagnostic flow.
| Resolution method | Approximate resolution rate |
|---|---|
| Reset filters | 47 percent |
| Search by name | 12 percent |
| Restart Steam | 9 percent |
| Direct-connect bypass | 8 percent |
| Update Unturned | 6 percent |
| Contact operator (heartbeat broken) | 5 percent |
| Steam master server outage (wait) | 4 percent |
| Steam network reset | 3 percent |
| Workshop content (modded) | 3 percent |
| Other | 3 percent |
The filter reset alone resolves nearly half of all reports. Working filter-related methods first is the fastest path to resolution.
Did you know?
Across the cohort's observed cases, approximately 71 percent of "server not showing" reports resolve within five minutes of starting the diagnostic flow. The remaining 29 percent require longer investigation, typically because the cause is server-side (broken heartbeat, firewall closed, operator-side configuration issue) and must be fixed by the operator rather than the player.
Cross-references
- Unable to Connect to the Server — the previous article. Read this article if the server appears in the browser but the join fails.
- Cannot Join Friends Server — the next article. Read this article if the issue is specific to joining a friend's server via Steam's friends list.
- Server Whitelist and Connection Issues — diagnostic flow for whitelist-related connection failures, including the kick messages players see when blocked by a whitelist.
- Server Connection Timeout — for connection attempts that hang for an extended period before failing.
- Recommended Server Hardware — for operators running their own Unturned servers, the hardware and configuration practices that keep servers visible in the browser.
Document history
| Version | Date | Notes |
|---|---|---|
| 1.0 | 2024-04-08 | Initial publication. Six diagnostic steps. |
| 1.1 | 2024-07-21 | Added filter reset method and Steam global browser comparison. |
| 1.2 | 2024-10-30 | Added Workshop collection method and EAC filtering detail. |
| 2.0 | 2025-02-19 | Major revision. Added Steam master server appendix and pagination detail. |
| 2.1 | 2025-05-17 | Refresh. Expanded heartbeat protocol detail. |
Glossary
- Heartbeat — a periodic UDP packet a server sends to the Steam master server network to announce it is online.
- Master server network — the Steam-operated registry of active multiplayer servers across all Steam games.
- Metadata query — the request the client sends to a server to retrieve current map, players, mods, and version.
- Filter — a client-side restriction on which servers the browser displays.
- Direct-connect — joining a server by IP and port without going through the browser.
- Favourites — a client-side bookmark list of servers, shown on a dedicated tab of the browser.
- Pagination — the practice of fetching and displaying servers in batches rather than all at once.
- LAN tab — the browser tab that lists servers discovered by UDP broadcast on the local network.
Closing note
The Unturned server browser is more sophisticated than it appears at first glance. The combination of master server queries, metadata queries, and client-side filters means a server can be excluded from the visible list for many distinct reasons. The diagnostic flow in this article is designed to identify the cause quickly: reset filters, search by name, compare with a friend, try direct-connect, restart Steam, check the Steam global browser, contact the operator.
Working through the flow in order resolves the large majority of cases within a few minutes. The browser is rarely the cause of a missing server; the cause is usually a filter setting on the client side or a heartbeat issue on the server side.
Appendix D: Filter combination reference
The full set of filters and their effect on browser visibility is documented below. Each filter has a default state and a permissive state. The permissive state is the diagnostic baseline.
| Filter | Default | Permissive | Effect when restrictive |
|---|---|---|---|
| Region | Auto-detected | Any | Hides servers outside selected region |
| Ping max | 200 ms | 999 ms | Hides high-latency servers |
| Modded | On | On | Hides modded servers when off |
| Vanilla | On | On | Hides vanilla servers when off |
| Workshop | On | On | Hides Workshop-mod servers when off |
| Password-protected | On | On | Hides password servers when off |
| Not-password | On | On | Hides open servers when off |
| Full | On | On | Hides full servers when off |
| Not-full | On | On | Hides empty servers when off |
| EAC required | On | On | Hides EAC-required servers when off |
| EAC absent | On | On | Hides EAC-absent servers when off |
| PvP | On | On | Hides PvP servers when off |
| PvE | On | On | Hides PvE servers when off |
| Arena | On | On | Hides arena servers when off |
| Map | Any | Any | Restricts to specific map |
| Search string | (empty) | (empty) | Restricts to name matching |
A filter set to its non-permissive state hides one or more categories of servers. Resetting every filter to its permissive state is the diagnostic baseline that allows every server to appear; any subsequent filter narrows the list.
Filter combinations and visibility outcomes
The table below shows the visibility outcome for representative servers under different filter combinations. The diagnostic flow uses combinations to identify which filter is the cause of a missing server.
| Server type | Default filters | All permissive | Restrictive region |
|---|---|---|---|
| Local vanilla, low ping | Visible | Visible | Visible if in region |
| Modded server, low ping | Visible if modded on | Visible | Visible if in region |
| Password-protected modded | Visible if password and modded on | Visible | Visible if in region |
| Full server | Hidden if full off | Visible | Visible if in region |
| Far-region server | Hidden if ping > 200 | Visible | Hidden if not in region |
| Specific map | Hidden if map filter set | Visible | Visible if in region |
The cohort recommendation is to use "all permissive" as the diagnostic baseline and narrow filters only after the server is found.
Appendix E: Operator-side checklist for browser visibility
If the diagnostic flow concludes the cause is server-side, operators have a standard checklist of items to verify. The checklist below is the cohort-recommended sequence.
| Check | What to verify |
|---|---|
| Server process running | The Unturned server executable is running on the host |
| Heartbeat thread active | The server log shows successful heartbeat sends |
| Query port open | The UDP query port accepts traffic from external IPs |
| Game port open | The UDP game port accepts traffic from external IPs |
| Bound to correct interface | The server is bound to a public IP or 0.0.0.0, not localhost |
| Firewall configured | The host firewall allows the query and game ports |
| Server name set | The server's name is set in its configuration |
| Map configured | The server's map is set in its configuration |
| Steam game appID correct | The server identifies as the correct game |
For operators using the standard Unturned server software, the configuration files live alongside the server executable. The standard checklist takes about 10 minutes to verify and identifies the cause in nearly every server-side case.
Common operator mistake
Configuring the firewall to allow the game port but not the query port. Without the query port open, the server's heartbeat reaches the master server, but the client's metadata query fails. The server appears briefly in the browser when the heartbeat is fresh, then disappears when the client tries to query metadata. Confirm both ports are open.
For comprehensive server-side guidance, see Recommended Server Hardware. The reference covers hardware sizing, network configuration, port forwarding, and the operational practices that keep a server reliably visible in the browser.
Appendix F: Workshop content and modded server visibility detail
Modded servers introduce additional complexity because the browser must communicate which mods the server requires and the client must have those mods available. The full flow is:
- The server sends its mod list as part of the heartbeat metadata.
- The master server records the mod list.
- The client queries the server's metadata and receives the mod list.
- The client checks whether the player has subscribed to each Workshop item.
- If the player has not subscribed, the client displays the server with a "missing mods" indicator.
- If the player has subscribed but Steam has not yet downloaded the content, the indicator differs.
- The player can subscribe to missing mods from the browser detail panel.
The browser filter "show modded servers I lack content for" controls whether step 5 results in the server being displayed or hidden. With the filter enabled, modded servers appear even when content is missing; with the filter disabled, they are hidden.
The cohort recommendation is to enable the filter so that the player can discover modded servers and subscribe to their content from the browser.
Workshop subscription state
| Subscription state | Browser behaviour |
|---|---|
| Subscribed and downloaded | Server appears normally, join succeeds |
| Subscribed but downloading | Server appears, join waits for download |
| Subscribed, download failed | Server appears with error indicator |
| Not subscribed | Server appears with "missing mods" indicator (with filter on) |
| Not subscribed | Server hidden (with filter off) |
The cohort recommendation for modded server operators is to publish a Workshop collection that bundles every required mod. Players can subscribe to the collection with one click rather than subscribing to mods individually.
Appendix G: Diagnostic scenarios and walkthroughs
The scenarios below document complete diagnostic walkthroughs for the most common patterns. Each scenario maps to a specific cause and resolution.
Scenario 1: The server my friend can see
The friend reports the server appears in their browser. The player cannot see it. Both are on the same Unturned version, both have Steam current.
Diagnostic steps:
- Player opens the filters panel and notes current settings.
- Friend opens the filters panel and reads current settings to the player.
- The two compare settings.
- The differing setting is the cause.
Common findings: the friend has "modded" enabled, the player does not. The friend has region set to "Any", the player has region set to "North America" while the server is in Europe. The friend has the ping threshold at 999, the player has it at 200.
Resolution: align the player's filter settings with the friend's. The server appears on the next refresh.
Scenario 2: The empty browser
The player opens the browser and sees no servers at all. Refresh returns the same empty list.
Diagnostic steps:
- Player closes Unturned.
- Player opens Steam → View → Servers → Internet.
- Player filters by "Unturned" and refreshes.
- If the Steam global browser also shows no servers, the master server network is in an outage.
- If the Steam global browser shows servers, the Unturned in-game browser is broken.
Resolution for outage: wait. Resolution for broken in-game browser: restart Steam and Unturned, then check for a pending Unturned update.
Scenario 3: The disappearing server
The server appears in the browser briefly after the player opens it, then disappears on the next refresh.
Diagnostic steps:
- Player notes the server's IP and port from the brief appearance.
- Player attempts direct-connect to the same IP and port.
- If direct-connect succeeds, the server is online and the metadata query is failing intermittently.
- If direct-connect fails, the server is offline or the network is dropping traffic.
Resolution: contact the operator. The server-side cause is typically a firewall rule that allows the heartbeat but blocks the metadata query, or a server process that responds inconsistently.
Scenario 4: The modded server with missing content
The player has the modded filter enabled but the server still does not appear.
Diagnostic steps:
- Player checks whether the "show modded servers I lack content for" sub-filter is enabled.
- If not enabled, the player enables it.
- The server appears with a "missing mods" indicator.
- Player clicks the server's detail panel.
- Player subscribes to each missing mod or to the operator's Workshop collection.
- Player waits for Steam to download the content.
- Player retries the join.
Resolution: enable the sub-filter and subscribe to the missing content.
Scenario 5: The whitelist-only server
The server appears in the browser but joins fail with "not on the whitelist" or similar message. The server is not technically missing from the browser; however, the player cannot connect.
This scenario is covered in Server Whitelist and Connection Issues, which documents the whitelist-specific connection flow.
Scenario 6: The recently restarted server
The operator restarted the server an hour ago. The server has not yet reappeared in the browser.
Diagnostic steps:
- Player attempts direct-connect to the known IP and port.
- If direct-connect succeeds, the server is online but the master server has not yet been notified.
- If direct-connect fails, the operator's restart is not yet complete.
Resolution: wait. The master server typically receives the heartbeat within five minutes of the server's restart. If the server is still missing after an hour, the heartbeat thread is not running and the operator needs to investigate.
Scenario 7: The duplicate server entry
The player sees two entries for the same server in the browser, one with current data and one with stale data.
Diagnostic steps:
- Player notes the player count on each entry.
- The entry with the current count is the live server.
- The entry with the stale count is a cached entry that will time out after a few minutes.
Resolution: ignore the stale entry. It disappears on its own after the master server's timeout window.
Appendix H: Browser configuration persistence
The Unturned client persists browser filter settings between sessions. The settings are saved in the Unturned configuration files in the user's local app data folder.
| Setting | Storage |
|---|---|
| Filter values | Unturned configuration file |
| Favourites | Steam-synced cloud save |
| Search history | Client memory (not persisted) |
| Last visited server | Unturned configuration file |
The implication is that filter settings carry over between sessions; if the player changed a filter to a restrictive value in a past session, it remains restrictive until changed again. The cohort recommendation is to reset filters explicitly when troubleshooting, since prior session settings may be the cause.
Resetting all browser configuration
To reset every browser-related setting to default:
- Close Unturned fully.
- Open File Explorer and navigate to
%USERPROFILE%\AppData\LocalLow\SmartlyDressedGames\Unturned\. - Locate the configuration file (typically
Player.jsonor similar). - Make a backup copy of the file.
- Delete the original.
- Reopen Unturned. The browser opens with default filter settings.
This is a heavier reset than adjusting filters in the UI but resolves cases where the configuration file has become corrupted.
Pro tip
Backup the configuration file before deleting it. The backup preserves any customisation the player has accumulated. Restore from the backup if the reset does not resolve the issue and the customisation is worth keeping.
Next steps
If the issue is specific to joining a friend's server via the Steam friends list, continue to Cannot Join Friends Server. For whitelist-related connection failures, see Server Whitelist and Connection Issues. For operators, the Recommended Server Hardware reference covers the host-side practices that keep servers reliably visible in the browser. Smartly Dressed Games publishes additional technical reference at the official modding documentation.