If you play on more than one private server, you will eventually hit a problem that has nothing to do with the game: the clients overwrite each other. Two Wrath realms can ship different patch files, and a patch that a realm requires can break another realm's client. The scene's answer is almost always the same, and it is worth knowing before you lose an evening to a black screen.
What a project's own setup guide says
This is not folklore. When we read lordaeron.eu for its October 16 opening, its own installation guide stated the rule plainly: keep one client folder per realm. It tells players to copy their WoW folder (for example, naming one "WoW Rimeheart") and to put that realm's patch file into that copy only, warning that the other realm's patch must not be present. It also names the cache folders to delete between realms.
That is the pattern across the scene. A private server client is a base game plus that project's patch archives, and the patch is where the conflicts live. Letting two realms share one folder is the most common way to break a working install.
The launcher era changes some of this
Alternatively, some networks sidestep it with a launcher. Whitemane ships a launcher across Windows, Mac, Linux, and Steam Deck for its realms, which manages the client for you. Where a project offers one, use it: a launcher is the maintainer doing this folder management on your behalf, and it is the single biggest quality-of-life feature on a multi-realm network.
Planning the space
Each client copy is a separate install, so the arithmetic is simple: one folder per realm, per era. The sizes differ enormously by era, and we deliberately do not print precise gigabytes, because they move with locale files, patches, and what a project ships. The ordering is the useful part:
- A Vanilla (1.12) client is the smallest by a wide margin.
- Wrath (3.3.5a) is comfortably larger but still modest by modern standards, and it is the era 117 of our tracked entries run.
- Cataclysm, Mists, Legion and later clients grow sharply, and a modern client plus a second realm is where a small drive runs out.
If you plan to run three or four realms, buy storage for four installs, not one. That is the single most useful planning rule on this page.
- A roomy internal SSD if you are building or upgrading (A).
- A budget SATA SSD for an older desktop, which is the one upgrade with a visible effect on zone load times (A).
- A portable SSD if you want the same client copies on a laptop and a desktop (A).
- A large microSD card if you are on a handheld, where per-realm folders eat capacity fast (A).
Two habits that save real time
- Keep one untouched base client. Instead of copying a folder that is already patched and messy, keep a clean, unpatched copy and duplicate from that. It is the difference between a five-minute setup and an afternoon of troubleshooting.
- Name folders for the realm, not the expansion. "WoW Rimeheart" beats "WoW 3", because in six months you will not remember which one had the working addons.
If a realm ever refuses to launch after another install, the fix is almost always the same: restore the untouched copy, add only that realm's patch, and clear the cache folder. The project's own guide will name the exact files.
Where this fits with hardware
Storage is the one place where private servers reward spending, and almost nothing else does. Our hardware floor guide makes the case that this workload needs no new CPU, GPU, or RAM, and our Steam Deck and handheld guide applies the same logic to portable play. This page is the piece those two assume: the reason a shelf of clients is normal, and how to plan for it.
Current client versions for every realm are on the tracker. Related: the hardware floor, Steam Deck and handhelds, and the budget laptop and mini PC roundup.