Creating a server on uniz.host takes under a minute — once you know what each step asks and which choices are not free to undo. This guide walks the create page at /dashboard/servers/create from the first card to the final button, weighted toward the two things that catch people out: the change that silently wipes every mod you picked, and the number in the cost box that is misread most.
Four steps, but you probably will not walk all four
The wizard runs "Game" → "Edition" → "Server type" → "Size & confirm", and only Minecraft Java visits every one.
| What you pick | The steps you actually walk |
|---|
| Minecraft → Java | Game → Edition → Server type → Size & confirm |
| Minecraft → Bedrock | Game → Edition → Size & confirm |
| Every other game | Game → Size & confirm |
Bedrock has one server type and takes no mods, and other games ship a single build with no edition, so those steps have nothing to ask.
That is why the trail across the top shows only the path you really walked, rather than a rail advertising steps your game never sees. Each crumb carries the value you picked — the game, the edition, the server type with its version — and clicking one jumps back to that step, as pressing "Back" repeatedly would.
Pick your game on the first step
One card per game currently on sale, read live when the page loads rather than baked in, so a newly opened game appears on its own. At the end of the grid sits a non-clickable "More games soon" card, and admins additionally see games not on sale yet, badged "Testing".
Picking a game advances immediately, with no second confirmation. Minecraft moves to the edition step; every other game jumps to size, with the cheapest size clearing that game's RAM floor pre-selected, so you never land on a locked card with nothing valid to submit.
Choose Java or Bedrock (Minecraft only)
Two cards: "Java", described as "PC — supports mods & plugins", and "Bedrock", "Mobile, console & Windows". Pick by the devices your group plays on — the two clients connect to different kinds of server and are not interchangeable.
Java continues to the server-type step. Bedrock skips straight to size and resets the Minecraft version to latest on the way — a reset that matters more than it looks, because it also clears any mods you had picked. See the trap below.
Choose the server type, version and mods (Java only)
The longest step, in three parts down the page.
First, the server-type cards, in three groups: "Recommended" for what most people should take, "Ready-made" for a modpack you pick and play, and "Advanced" folded behind a "Show advanced options" button. The modpack card behaves differently from its neighbours: clicking it opens a full-screen pack catalogue instead of selecting a type, and you return here once you have chosen a pack.
Second, the version picker, labelled "Minecraft version" — a searchable combobox ("Search version…") listing only versions the selected type actually has a build for, so changing the type reloads the list. The newest entry is marked as {version} (latest), and the default pins a real version number rather than the ambiguous "Latest (LATEST)" tag. With a modpack selected it becomes a plain dropdown, "Minecraft version (from modpack)", holding only that pack's versions.
Third, mods or plugins, shown only for types that can take them; the heading reads "Add mods (optional)" or "Add plugins (optional)" to match. Choose the "Platform" first, then the add button opens the search — or click "Add by project name (slug)" and type the name in. Everything you add is pinned to a build compatible with the current type and version, and anything with no usable build is refused right then with "No compatible version for this server".
The step ends with "Next", disabled if you chose the modpack route without picking a pack.
Name the server and pick a size on the last step
The first field is "Server name", placeholder "My Awesome World", required, 3 to 32 characters. It is not just a dashboard label: the name becomes the server's subdomain, so the address your players type comes out shaped like <name>.uniz.host. It can be changed later from the Settings tab.
Below that is "Size" and six cards, smallest to largest, each with three lines — the spec as {ram}GB · {cpu} vCPU, the disk included, and the price as {hourly}/hr · {cap}/mo cap. The 2 GB card is badged "Recommended". At standard prices when this was written:
| Plan | RAM | vCPU | Disk | Per hour | Monthly cap |
|---|
| Starter | 1GB | 1 | 15GB | ฿0.30 | ฿99 |
| Play | 2GB | 1 | 25GB | ฿0.50 | ฿149 |
| Squad | 4GB | 2 | 40GB | ฿0.90 | ฿279 |
| Community | 8GB | 4 | 60GB | ฿1.70 | ฿529 |
| Pro | 16GB | 8 | 100GB | ฿3.20 | ฿999 |
| Max | 32GB | 16 | 150GB | ฿5.90 | ฿1,890 |
Treat that table as an illustration; the rates in force are on , read fresh on every request.
Sometimes a "Hardware" picker appears above the size cards, offering "Standard" — "Our shared cluster — the prices listed across the site." — plus whichever dedicated machines are on sale; with none on sale it does not render at all. Each machine's rates come from its own live rate card, so read them off the card rather than from any guide, and a machine that cannot sell your size locks it as "Not available on this hardware". Some Java types also offer an "Enable Bedrock crossplay (Geyser)" switch; types that cannot do it show a line saying crossplay is only available for Paper/Spigot server types.
Read the cost box, then hit create
Under the size cards is a cost box that follows the selected size. Four lines:
- The large per-hour price, annotated "only while the server is running" — the unit you are actually billed in.
- The caps line: off or asleep is free, then the daily and monthly ceilings. A game the platform cannot poll for an empty server — Core Keeper — gets wording starting from "stays on = billed as used" instead.
- The worked example, saying this is not a monthly fee, that you can top up any amount, and that ฿50 buys roughly so many hours at this size. That ฿50 is a fixed illustrative figure, not the minimum top-up. The hours change with the size; the ฿50 never does. The real minimum top-up is ฿20.
- The disk line, stating how much storage the plan includes.
Then press "Create"; the button reads "Creating…" while the request is in flight.
The big trap: three changes wipe every mod you picked
If you remember one thing here, remember this. Each of these clears your whole pinned mod list, instantly, with no confirmation:
| What you change | The message you get |
|---|
| The server type (clicking a different card) | Mod list cleared — the server type changed |
| The Minecraft version | Mod list cleared — the Minecraft version changed |
| The mod platform | Mod list cleared — the mod platform changed |
This is compatibility, not the platform being precious. A mod is pinned to one file version chosen to fit the type and version set when you added it; move either axis and that file is wrong, and carrying it along produces a server that fails on its first boot.
Two more routes lose your work without announcing themselves:
- Going back to the edition step and tapping Bedrock. That resets the version to latest, which counts as a version change, so the mods go too — and since Bedrock skips the server-type step, you reach size never having seen the empty list.
- Switching platform while choosing a modpack. This clears no mods; it drops the pack you selected, since a reference on one platform means nothing on the other.
There is exactly one way to avoid all of it: settle the server type, the version and the platform first, and add mods last.
RAM: what is a hard lock and what is only a warning
The size step shows two RAM messages that look similar and are enforced very differently.
A game's RAM floor is a hard lock. Above the size cards the wizard prints that game's minimum — "Palworld needs at least 8 GB RAM", for instance — and every card below it is unclickable, with no override, because the server will genuinely not run. Floors differ by game: Minecraft's is the lowest at 1 GB, so nothing is ever locked for it, while several survival games start at 8 GB and take the first four cards out of play.
A modpack's RAM figure is only a recommendation. Pick a modpack and you get "Modpacks usually run best with 4GB+ RAM (Squad tier and up)" — but the smaller cards stay selectable. Choose one and an amber warning appears saying the size is below what is recommended and the server may crash on start if the pack needs more. Warned, not blocked: plenty of small packs are happy on 2 GB, and nothing can know in advance what yours needs. Unsure? Read .
What happens after you hit create
The first real event comes before any of it — your credit balance is checked before anything is provisioned. A zero or negative balance is rejected with an out-of-credit message and no server is created at all; top up at least ฿20 on and come back. There is also a cap on how many active servers one account may hold at once (3 by default), and hitting it produces a message naming your actual limit.
Past both gates:
- The name you typed becomes the server's subdomain, attached straight away.
- Provisioning starts inside the very same request. You do not have to press Start.
- A "Server created — provisioning has started" toast appears and you land on the new server's page.
- That page sits in "Creating" a while, then moves through starting to online. First boots are slower because the game has to be downloaded; a large modpack takes several minutes.
- The billing window opens only when the platform observes the server actually online. Provisioning and starting are not billed.
One more thing worth knowing on day one: every new server has auto-sleep switched off. Once online it stays online, and keeps billing, until you stop it or run out of credits. To have it stop by itself when nobody is playing, switch it on from that server's Settings tab — the walks through it.
Read next
- — stop paying while nobody is playing
- — top-ups, caps, and reading your charges
- — what the server page tells you
- — picking a size without overpaying