How to Get Your Hytale Server Into the In-Game Server Discovery List (2026 Guide)

Hytale's in-game Server Discovery is live, and getting into it is not one step but five. You create a server profile in Account Manager, fill in a small set of required fields, prove you control the domain with a DNS TXT record, wait in a moderation queue, and then keep a heartbeat running for as long as you want to stay visible. Miss any one of those and your server simply is not there — no error, no notification, just absence. We covered Discovery twice in April, when it was first announced as an in-game server browser with friend lists and again when applications opened. Those pieces were written about a feature that had not shipped. This one is about the mechanics as they were actually published, and about the failure modes, which is the part nobody documents until it happens to them. Every mechanic below is sourced to Hytale's own "Official Server Lists" post of April 28, 2026, or to the Server Operator Policies. Where a number is not published — and one important one is not — we say so instead of supplying one. One honest note on sourcing: the Hytale Server Manual on the support site would be the other primary reference here, and it returned a 403 to us on August 19, 2026, so nothing below is drawn from it. If the manual contradicts anything here, the manual wins. What Hytale Server Discovery Actually Is Discovery is a catalogue built into the game client. A player opens the server list from the menu and browses servers that operators have opted into listing. That is the whole of it, and the "opted into" is the important half: your server does not appear because it exists. It appears because you submitted a listing, a human approved it, and your server is currently telling the discovery service that it is up. Two design decisions shape everything that follows. It is pull-based on your side, not scan-based on theirs. Hytale is not port-scanning the internet for servers. Your server pushes a heartbeat to the discovery service, authenticated with a token. No heartbeat, no listing. This is the opposite of how most people assume a first-party server browser works, and it is the single biggest source of "my server is online but not listed" confusion. It is version-aware. The announcement is explicit that the token is "used for sending information like server version/patchline and a general availability check", so players see servers they can actually join. If you run a pre-release build and a player is on stable, or the reverse, that is a legitimate reason your server is not in their list even though everything on your side is correct. Our guide to running and testing pre-release builds covers keeping a test server on a different patchline from your public one. What You Need Before You Start Gather these first. Every one of them is a place people get stuck halfway through. A Hytale account with Account Manager access, and — this matters more than it sounds — a clear idea of which game profile the server belongs to. See the multiple-servers section below. A domain you control the DNS for. Verification is done with a TXT record, so you need the ability to add records at your registrar or DNS host. If your server is reachable only by a bare IP address handed to you by a host, sort out a domain before you start. OP access to the server console or in-game chat. Token generation is "a simple command you run in either the console or chat as an OP to complete the link". If you are on a managed host with no console and no OP, you cannot finish the process. Our self-hosted vs managed hosting comparison goes through which host types actually give you that. A server description you are willing to have reviewed by a person, and a working knowledge of the Server Operator Policies. Most denials, per Hytale, "come down to small policy mismatches that are easy to fix". Somewhere public to point at for your website or store, privacy policy, refunds policy and support contact. The policies require listed servers to publish those links. How to Add Your Server to the Hytale Server List, Step by Step Step 1: Open Server Profiles in Account Manager Sign in to Account Manager and open the Server Profiles page. This is the home for every listing you own — the card you see here is the same card that later shows your moderation status, your denial reason if you get one, and your discovery token. Bookmark it. You will come back to it more than you expect. Step 2: Click "Create server" and fill in the listing The published field set is short, and each field does real work in the browser's filters, so treat them as ranking inputs rather than paperwork: Name and description. These are what a stranger reads in a list of strangers. Say what the server is in the first clause, not what it aspires to be. Server type, chosen from nine options: Survival, Adventure/RPG, Creative, PvP, Minigames, Roleplay, Social, Sandbox or Other. Pick the one a player filtering for your server would tick, not the one that flatters your feature list. Other is a filter almost nobody uses on purpose. Audience tag: Everyone, Teen or Mature. Worth a flag: the Server Operator Policies describe the age groups as All Ages, Teen and Mature, while the Discovery announcement calls the first one Everyone. We read those as the same three tiers under two labels, but we cannot verify that from a single source, so if the form shows you a fourth option, trust the form. Region, chosen from ten options spanning North America, South America, the EU, the Middle East, Asia and Oceania. The individual region names are not enumerated in the announcement, so we are not going to list ten guesses. Pick the one your hardware actually sits in — a mislabelled region produces players with 200 ms ping who leave and never come back. Domain verification, covered next. Step 3: Verify your domain with a TXT record Domain verification exists "to prove you control the host you've listed". The mechanism is a DNS TXT record that Hytale provides during the flow. The exact record name and value format are not published in the announcement, so we will not invent one — copy what the Account Manager gives you, character for character, and paste it rather than retyping it. Three practical notes that apply to TXT verification everywhere and cost operators the most time here: Add the record at the right level. A record for play.example.com is not a record for example.com. If your listed host is a subdomain, verify the host you listed. Wait for propagation before you resubmit. Your TTL is the floor, not the ceiling. Check with dig TXT play.example.com +short (or nslookup -type=TXT play.example.com on Windows) from a machine that is not the one that just made the change, and only click verify once you can see the value yourself. Do not delete the record afterwards. Treat it as permanent infrastructure. Verification records get pruned during "DNS tidy-up" months later, and the resulting delisting is baffling if you have forgotten the record existed. Step 4: Wait for moderation Submissions are "reviewed in the order they arrive", and "the status on your listing card will update as it moves through review". There is no email to watch; the card is the status. How long does it take? Hytale has not published a number. The announcement says only that "most listings should clear the queue quickly". You will find third-party guides quoting specific windows — one to seven days is a figure in circulation — and we have not found a primary source for any of them, so we are not repeating them as fact. Plan for "days, unknown", not "by tonight", and do not schedule a launch event around an approval you cannot predict. Discovery is the canopy gap: it is where new players first see daylight through the trees. Getting into it is a queue and a DNS record, not a growth strategy. A general official Hytale screenshot. Step 5: Generate the discovery token and start heartbeating Once accepted, you "configure your server to send heartbeats using the discovery token". The token is described plainly as "the secret your server uses to authenticate its heartbeat with the discovery service", and it is generated by a command run in the console or in chat as an OP, with the token shown on your listing card. Two consequences of that word "secret". First, the token is a credential. Anyone holding it can speak to the discovery service as your server. Keep it out of screenshots, out of public config repos and out of the support ticket you paste your whole config into. If you ever suspect it leaked, regenerate it. Second, the OP requirement is a gate, not a formality — it is how Hytale ties the listing to somebody with real authority over the machine, which is exactly why a managed host that will not give you console access is a genuine blocker rather than an inconvenience. The Two-Minute Rule Is the One That Bites Here is the mechanic worth putting on a sticky note: "If your server stops sending heartbeats for more than two minutes, it is hidden from listings until it comes back online." The server pings every two minutes, and the tolerance for a missed ping is also about two minutes. That is a tight window, and it means your Discovery visibility is only as reliable as your uptime and your outbound network path. Some things that will drop you out of the browser without anything looking wrong on your dashboard: A restart schedule. A nightly restart takes you off the list for its duration. That is fine and correct. A restart loop caused by a bad plugin takes you off the list intermittently, which is worse than being off it entirely, because you never notice. An outbound firewall. Heartbeats go out from your machine. Operators who lock down egress on a hardened box can end up with a server that is perfectly reachable inbound and completely invisible in Discovery. A crash the process supervisor quietly restarts. If your server is flapping, your listing is flapping. Our crash recovery and config guide is the place to start if your uptime is the real problem. A host-side network blip. Nothing you can do about it, but it explains sightings of "my server vanished for ten minutes yesterday". The upside of the tight window is that recovery is automatic. There is no resubmission, no re-verification, no queue. The server comes back, the heartbeat resumes, the listing returns. Why Your Hytale Server Is Not Showing in Server Discovery Four distinct failures, four different fixes. Work down the list in order, because each one rules out the ones below it. 1. The listing says "Pending verification" — and there is a 30-day timer on it This status means the domain side is not finished. Almost always it is DNS: the record is on the wrong host, has a typo, was added as the wrong record type, or has not propagated. Verify the record resolves publicly before you touch anything else. Do not let it sit. Hytale is explicit: "Listings stuck in 'Pending verification' for more than 30 days are removed." That is a hard published number and the harshest rule in the system, because it punishes inattention rather than error. If you submitted a listing, half-finished the DNS, and got distracted by an update cycle, set a calendar reminder today. 2. The listing was denied The remedy is spelled out: "Review the reason in your listing card alongside the Server Operator Policies. Update the listing and resubmit; most denials come down to small policy mismatches that are easy to fix." Read that as good news. A denial is a correction, not a ban, and the reason is on the card. The common shapes are an audience tag that does not match the actual content, a description that advertises something the monetization rules do not allow, or missing required links. See the compliance section below. 3. Accepted, heartbeating, still not visible to a specific player This is the version-mismatch case, and it is the one that sends operators chasing imaginary bugs. Because the heartbeat carries "server version/patchline", a player on a different build will not see you. Before assuming Discovery is broken, ask the player what build they are on and compare it to yours. If your server tracks pre-release and your community does not, you have found it. Rule out the ordinary causes too — a server that will not accept connections is not a Discovery problem, and our failed-to-connect troubleshooting guide covers the connection layer underneath all of this. 4. You have more than one server and only one shows up This one is a rule, not a bug: "One listing per game profile. If you would like multiple servers listed you'll need to add them each under their own game profile." If you run a network — a survival server, a minigames server, a creative build server — each one needs its own game profile. There is no multi-listing view under a single profile. Plan that structure before you create the first listing rather than after, because retrofitting it means redoing the profile, the domain verification and the token for every server after the first. Listing Compliance: What Moderation Is Reading Against Since denials are measured against the Server Operator Policies — effective January 13, 2026 — it is worth knowing what is in them before you submit rather than after. The obligations most likely to catch a listing: Accurate operator identity and contact details, plus moderation able to respond to urgent safety issues within 24 hours "where reasonably practicable". Public links to your website or store, privacy policy, refunds policy and support contact. An honest age group and content descriptors covering violence, language, user chat and monetization types. Under-rating a server to widen its audience is the fastest way to a denial. Monetization limits. Sexual content, NFTs, speculative crypto tokens and real-money gambling are prohibited outright. All Ages servers cannot offer paid random items. Loot boxes require odds displayed numerically, disclosure of expected spend, and twelve months of records — and chained randomization, where a purchase yields random currency that feeds another random draw, is banned. Our breakdown of the monetization policy goes through this in detail. Cosmetics compatibility. A listed server cannot block official player cosmetics or sell confusingly similar ones to force purchases. Enforcement escalates through warnings, delisting, token suspension and account-level action. Note the middle two: losing your token is a listed penalty, which makes compliance an availability concern and not only a legal one. What Discovery V1 Does Not Do Yet The announcement is refreshingly direct about its own limits: "No custom icons, banners, or rich media yet" and "No live player count or ratings yet", with "richer listings, better browsing tools, deeper customization" named as future work. So a V1 Discovery entry is a name, a description, a type, an audience tag and a region. That is enough to be found and not much more, and it means the things players usually decide on — is anyone actually playing right now, what does this place look like, do people rate it — are not answerable from the listing. Which is the honest place to say where lists like this one fit. Discovery is where players who are already in the game go looking; third-party lists are where the icons, banners, live player counts, reviews and screenshots live until Discovery grows them. They answer different questions and the sensible move is to be in both, which is the argument we made at length in Server Discovery vs. server lists. If you want to see what a richer listing looks like in practice, browse the server list — and if the goal is players rather than listings, our growth guide is about the part no browser does for you. FAQ How do I add my server to the Hytale server list? Sign in to Account Manager, open the Server Profiles page and click "Create server". Fill in the name, description, server type, audience tag and region, then complete domain verification with the TXT record provided. Wait for the listing to clear moderation — the status updates on the listing card — and once accepted, generate your discovery token with the OP console or chat command and configure your server to send heartbeats with it. Why is my Hytale server not showing in server discovery? Four common causes, in the order worth checking. The listing is still in "Pending verification" because the TXT record is missing, wrong or not yet propagated. The listing was denied and the reason is on the listing card. The heartbeat has not been received for more than two minutes, which hides the listing until the server returns. Or the player looking is on a different version or patchline from your server, since the heartbeat carries that information and Discovery shows players servers they can actually join. How long does Hytale server list approval take? Hytale has not published a timeframe. The official announcement says only that submissions are "reviewed in the order they arrive" and that "most listings should clear the queue quickly". Specific figures circulating on third-party sites do not trace back to a primary source, so treat them with caution. The one hard number that is published is on the other side: a listing left in "Pending verification" for more than 30 days is removed. What is the Hytale discovery token? It is the secret your server uses to authenticate its heartbeat with the discovery service, and it also carries information such as your server version and patchline plus a general availability check. You generate it with a simple command run in the console or in chat as an OP, and it is shown on your listing card. Treat it as a credential and keep it out of screenshots and public configs. Can I list multiple Hytale servers on one account? Not under one game profile. The rule is one listing per game profile, and Hytale states that to list multiple servers you need to add each one under its own game profile. Plan that structure before creating your first listing, because each additional server needs its own profile, its own domain verification and its own token. What are the requirements for Hytale server discovery? A server profile in Account Manager with a name, description, server type, audience tag and region; a domain you control, verified with a TXT record; approval through the moderation queue; OP access to generate the discovery token; a heartbeat running from your server; and compliance with the Server Operator Policies, including accurate content ratings, published website, privacy, refunds and support links, and the monetization restrictions. Does my server get removed if it goes offline? It gets hidden, not removed. A server that stops heartbeating for more than two minutes is hidden from listings until it comes back online, and recovery is automatic — no resubmission or re-verification. Removal is a different rule and applies to listings stuck in "Pending verification" for more than 30 days. Does Server Discovery show live player counts? Not in this version. The announcement states there is no live player count or ratings yet, and no custom icons, banners or rich media, with richer listings and better browsing tools named as future work. What This Means If You Run a Hytale Server Four things to do, in order. Decide your profile structure first — one listing per game profile is a rule you cannot work around later without redoing verification and tokens for every server past the first. Get the domain right before you submit, verify the TXT record resolves publicly from a machine that is not yours, and then never delete it. Put a reminder against the 30-day pending-verification timer the day you submit, because that is the one rule that removes a listing for inattention rather than for anything you did wrong. And monitor your heartbeat like you monitor your uptime, since a flapping server is an intermittently invisible one and nothing on your own dashboard will tell you. Then set expectations accordingly. Discovery V1 gets you found by people already in the game, with a name, a description and three filter fields to work with. It does not tell them who is online, what your world looks like, or whether anyone liked it. Those answers still live elsewhere for now — and on the approval timeline, the honest position is the one Hytale itself takes: reviewed in order, usually quick, no promised number. We would rather tell you that than make one up.