![Day[Z] Titan Launcher logo](/assets/img/logo2.webp?v=1781090027){kind=logo}
Day[Z] Titan Launcher
The Titan DayZ Server Launcher is a Windows app that turns running a DayZ server into a single control room: create instances, install and auto-update Workshop mods, sync .bikey keys, send RCON restart warnings, back up your world, and watch FPS, players, CPU and network in real time. This guide walks every panel in the order you actually use them.
Download — Titan Server LauncherWork top to bottom the first time you set up a server. Each panel does one job; together they cover the whole life cycle, from creating a server to keeping it healthy.
The left rail lists your server instances, so you can jump between your HU, EU or test servers in one click. The top bar shows the live numbers that matter: CPU, RAM, Net I/O, Disk I/O, player count, map, Server FPS, game version, IP and run state.
The Overview panel also carries the backend side - publish status, heartbeat, external probe and quick actions - so you can confirm at a glance whether the server is online and listed.
Click New Server to create an instance with a guided form: name, map (ChernarusPlus, Livonia, Sakhal, or Namalsk Regular/Hardcore), max players and the Game/Query/RCON ports. The launcher suggests free ports and checks they do not clash with another instance.
Behind the scenes it verifies SteamCMD, installs or updates the DayZ Dedicated Server files, creates the instance folder and base config, opens the firewall rules, and - for Namalsk - adds the required Workshop mods and syncs their keys. When it finishes it selects the new server and drops you on its Configuration page.
Add mods by Workshop ID or URL, or search the Workshop by name. Mark each one as a client mod (players need it too - it goes into -mod=) or a server-side only mod (it goes into -serverMod=). Install, publish the mod list, check for updates or purge a mod from here.
After adding or updating any mod, run Sync keys so the mod's .bikey public keys land in the server keys folder - without them players are rejected with a signature error. The launcher copies public keys only; it never generates private keys or signs PBOs.
The Configuration panel edits the server's own settings without opening serverDZ.cfg by hand: name, map, max players, ports, RCON, CPU affinity, process priority and the launch/runtime options, plus direct JSON editing.
Save Config writes your changes; Reload re-reads the current config. Remember that most server-side changes only take effect after a restart.
A dedicated screen reads your mission's db/globals.xml and shows the values grouped by category - Population, Cleanup, Loot Economy and the animal/infected/event globals - so you never edit raw XML. Blocks collapse and expand to keep the screen readable.
A backup is taken before saving, and the values take effect after the next restart. Change small amounts at a time and watch the Metrics panel afterwards, because the economy does not always settle instantly.
The Editor groups several mission tools: a Loot Editor that loads types.xml and mod loot sources for searching and editing category/usage/value; Starting Gear for the spawn loadout; Spawnable Types for cfgspawnabletypes.xml attachments and cargo; and a visual Mission Map Editor for player spawns, event spawns, zombie territories and effect areas.
There is also an XML/JSON validator and formatter, and a File Knowledge Base that explains which server file controls what. Every edit is backed up, and changes need a restart to apply.
Settings is the control center. Steam holds your SteamCMD login (needed for mod and server downloads); Account links the backend and the alert email. Server Operations is where the automation lives: auto mod-update, DayZ server validation, restart running servers after updates, the check interval and log rotation.
Notifications defines the RCON global-chat countdowns for shutdowns, updates and scheduled restarts, with placeholders like {{countdown}}, {{mod}} and {{server}}. On this machine auto Workshop updates run every 60 minutes with restart-after-update enabled; the restart countdown is 300 s and the mod-update countdown is 120 s.
The Maintenance panel gives one-click operations when you need to fix something fast without digging through settings: Update Server (DayZ base files), Update Mods (Workshop), Repair Keys (re-sync .bikey files) and Clear Logs (free disk space from old runtime logs).
This is the page to reach for first when a mod, key or update problem appears.
Metrics charts the selected server and instance state: player count, Server FPS, CPU, RAM, Disk I/O, Net I/O, process ID, run status and history graphs. Net I/O uses a Windows pktmon counters-only measurement filtered to the server's game, query and RCON ports.
When FPS drops, start here rather than changing config blindly: read FPS, CPU, RAM and the RPT log first, then adjust one thing at a time.
Backups handles manual and automatic local saves: instant backup, an automatic interval, retention days, the storage folder plus any extra files and folders, and a browsable list with size and contents. On this machine auto-backup runs every 60 minutes with 30-day retention.
Restore shows a preview, stops the server if it is running, writes the selected files back and reports what was overwritten or created. Always take a backup before a big mod update, a mission XML change or a wipe.
The Files manager exposes the instance folder so you do not have to hunt through Windows Explorer: serverDZ.cfg, mpmissions, profiles, logs, config, the mod list, the backup index and the RCON logs. The typical DayZ mission files - types.xml, events.xml, globals.xml, cfgspawnabletypes.xml, cfgeconomycore.xml, init.c and the spawn-point files - all live here.
The goal is that you rarely edit these by hand; where the launcher offers a UI it backs the file up before saving.
The Events/log view is your first stop in troubleshooting. The important log types are the launcher app log, the operation log, the SteamCMD Workshop log, the DayZ install log, the server RPT, the script log, crash dumps, the RCON log and the backup/restore log.
Search for markers like Error, Exception, Cannot compile, Missing addon, Bad version, Signature, Steam Guard and Workshop. When the UI says an operation failed, the matching operation log usually shows the concrete reason.
Free Windows installer. Your instances, configs and backups live in a separate data root, so updating the launcher never touches them.
Download — Titan Server LauncherInstall the Titan DayZ Server Launcher on a Windows PC, click New Server, pick a map and a name, and let the wizard download the DayZ server files and set everything up. A few clicks later you press Start and your server is live - no command line or manual config needed.
Download it from the official download page on this site. It is a normal Windows installer: run it, open the launcher and you are ready to create your first server. The download button at the top of this guide takes you straight there.
Yes, the launcher is free to use. You only need a Steam account so it can download the DayZ Dedicated Server and any Workshop mods for you.
Yes. The launcher runs several server instances side by side, each with its own map, mods, ports and settings, and you switch between them from the left rail. It even suggests free ports so they never clash.
Open the Mods panel, paste a Steam Workshop link or ID (or search by name) and install it, then run Sync keys. The launcher downloads the mod, adds it to the start options and copies its keys so players can join - after that just restart the server.
No. The launcher gives you a visual panel for everything that normally means editing files by hand - server settings, mods, loot, backups and restarts - so you can run a server without the command line. Take a backup before big changes and you are free to experiment.