LiveChat 
Support 
Arma 3 Dedicated Server Steam App ID: SteamCMD Setup Guide
Standing up an Arma 3 dedicated server starts with one deceptively simple question: which Steam app ID do you actually install? The answer trips up many first-time admins because Arma 3 ships under two different identifiers — one for the game client you play, and a separate, lighter one for the server software you run on a machine with no graphics card.
This guide explains the Arma 3 dedicated server Steam app ID, walks through a clean SteamCMD installation, covers the essential `server.cfg` and networking setup, and digs into the single most misunderstood part of Arma 3 hosting: why clock speed beats core count.
Key Takeaways
• The Arma 3 dedicated server app ID is `233780` — this is what you install via SteamCMD on your host.
• The Arma 3 game client app ID is `107410` — that is the playable game, not the server.
• Install the server anonymously with `login anonymous` followed by `app_update 233780 validate`.
• The default game port is `2302/UDP`, with a small range above it used for queries and Steam reporting.
• Arma 3 server performance is CPU single-thread bound — a high-clock CPU matters far more than a high core count.
What is the Arma 3 dedicated server Steam app ID?
The Arma 3 dedicated server Steam app ID is `233780`. This is the headless server package: it contains the server binaries and required data but none of the client-only rendering assets, so it can run on a Linux or Windows machine with no GPU.
It is easy to confuse this with the Arma 3 game (client) app ID, which is `107410`. That app ID is the game you launch from your Steam library to actually play. You do not install `107410` on a hosting box — installing the wrong ID is the classic reason a “server” install balloons in size or refuses to boot headless.
Both IDs are commonly referenced in community guides and tooling, so it is worth committing them to memory before you touch SteamCMD.
Why two separate app IDs exist
Bohemia Interactive splits the client and server so administrators can deploy the server independently of a paid game license, using SteamCMD anonymous login. The dedicated server package is free to download anonymously, which is what makes automated, scriptable deployments possible on rented infrastructure.
How do you install the Arma 3 server with SteamCMD?
SteamCMD is Valve’s command-line client for downloading dedicated server files. The workflow is the same on Linux and Windows once SteamCMD is installed.
- Download and extract SteamCMD for your operating system into a dedicated directory.
- Launch SteamCMD and wait for it to self-update on first run.
- Set your install directory with `force_install_dir ./arma3server`.
- Authenticate anonymously with `login anonymous`.
- Download and validate the server with `app_update 233780 validate`.
- Quit SteamCMD with `quit` once the download completes.
A minimal session looks like this:
“` force_install_dir ./arma3server login anonymous app_update 233780 validate quit “`
The `validate` flag re-checks every file against Steam’s manifest. Always include it after an update or a crash to catch corrupted downloads before they become mysterious boot failures.
SteamCMD app ID reference and install steps
The table below summarizes the two app IDs and the core commands so you can keep them side by side.
| Item | Value / Command | Notes |
|---|---|---|
| Arma 3 dedicated server app ID | `233780` | Install this on your host via SteamCMD |
| Arma 3 game (client) app ID | `107410` | The playable game — not for headless servers |
| Authenticate | `login anonymous` | Server files download without a license |
| Set install path | `force_install_dir ./arma3server` | Run before `app_update` |
| Install / update | `app_update 233780 validate` | `validate` re-verifies all files |
| Exit | `quit` | Closes SteamCMD cleanly |
How do you configure the Arma 3 server?
Once the files are on disk, the server is driven by a few configuration files and command-line parameters.
The server.cfg file
`server.cfg` defines the server’s public identity and rules. A basic example:
“` hostname = “My Arma 3 Server”; password = “”; passwordAdmin = “changeme”; maxPlayers = 32; persistent = 1; verifySignatures = 2; motd[] = {“Welcome to the server”}; “`
Key fields to understand:
- `hostname` — the name shown in the server browser.
- `passwordAdmin` — the admin login used with the in-game `#login` command. Always set a strong value.
- `maxPlayers` — the player cap; keep it realistic for your hardware.
- `verifySignatures` — set to `2` to enforce signed mods and reduce cheating.
You then launch the server pointing at this file, for example with a `-config=server.cfg` parameter alongside your chosen mission and difficulty parameters.
Which ports does Arma 3 use?
Arma 3 networking runs over UDP. The default game port is `2302/UDP`, and the server uses a short range immediately above it for Steam query and reporting traffic. In practice you should open `2302`–`2306/UDP` to be safe.
If you run multiple instances on one host, give each instance its own base port (for example `2302`, `2402`, `2502`) to avoid collisions, and forward the matching range for each.
How do you add mods and Steam Workshop content?
Mods are loaded with the `-mod=` launch parameter, which takes a semicolon-separated list of mod folder paths. To deploy Steam Workshop content on a headless server, download the workshop items through SteamCMD (using the game app ID `107410` with `workshop_download_item`), then point `-mod=` at the resulting folders.
For signature enforcement, place the mods’ `.bikey` files in the server’s `keys` directory so they pass the `verifySignatures` check defined in `server.cfg`. Mismatched or missing keys are a frequent cause of clients being unable to join a modded server.
Why is single-thread CPU performance the deciding factor?
Here is the detail that reshapes every hardware decision for Arma 3: the server’s simulation runs primarily on a single thread. The main game loop — AI pathfinding, scripting, and the physics that hold a mission together — is bottlenecked by how fast one core can churn, not by how many cores you have.
The practical consequence is counterintuitive. A modern CPU with a high single-thread clock speed and strong per-core performance will sustain a healthier server frame rate (server FPS) than a server-grade chip that has many slow cores. When a 60-player mission with heavy AI starts to stutter, the culprit is almost always a saturated single thread, not exhausted RAM or a lack of cores.
This is why seasoned admins prioritize clock speed over core count when choosing a host, and why a well-chosen consumer-class high-frequency CPU often outperforms a sprawling multi-socket machine for this specific workload. Extra cores still help — they offload networking, the dedicated headless-client trick for AI, and the operating system — but the ceiling on your mission’s responsiveness is set by that one fast thread.
Linux or Windows for the Arma 3 server?
Both platforms are officially supported and both install via the same app ID `233780`.
- Linux servers are popular for their lower overhead, easy automation, and headless operation. They are a natural fit for scripted, repeatable deployments.
- Windows servers can be simpler for admins already comfortable with the OS and for certain mods that historically targeted Windows builds first.
Either way, the performance ceiling comes back to the CPU. The operating system choice is about your comfort and tooling, while the single-thread clock speed decides how many players and how much AI your mission can carry.
What are the system requirements?
There is no single official number — requirements scale with your mission. As a planning guide:
- CPU: Prioritize the highest single-thread performance and clock speed you can get. This is the number one factor.
- RAM: A few gigabytes for a vanilla server; budget more for large modlists and high player counts.
- Storage: An SSD noticeably improves mod loading and mission start times.
- Network: A stable, low-latency connection with enough upstream bandwidth for your player count.
Choosing infrastructure that respects these realities is where hosting quality shows. DarazHost VPS and dedicated servers are well suited to demanding game servers like Arma 3: we offer strong single-thread CPU performance so your server FPS holds up under heavy AI, full root access to install SteamCMD and run game-server binaries however you like, SSD storage for fast mod and mission loading, and a reliable low-latency network so players in your region stay connected. With 24/7 support backing every deployment, you can focus on your mission rotation instead of fighting your host. Explore our or a to get started.
Frequently asked questions
What is the Arma 3 dedicated server Steam app ID? The Arma 3 dedicated server app ID is `233780`. You install it on your host with SteamCMD using `app_update 233780 validate`. The separate game client app ID is `107410`, which is the playable game and not what you run on a server.
Can I install the Arma 3 server without owning the game? Yes. The dedicated server package downloads through SteamCMD with `login anonymous`, so no game license is required on the host. You only need the game on the machines that will actually play.
Why is my Arma 3 server lagging even with plenty of RAM and cores? Because Arma 3’s server simulation is single-thread bound. If one core is maxed out, adding RAM or more cores will not help. Look for a host with a higher single-thread clock speed, and consider reducing AI count or mission complexity.
Which ports do I need to open for Arma 3? The default game port is `2302/UDP`. Open the range `2302`–`2306/UDP` to cover the game, Steam query, and reporting traffic. Use a separate base port per instance if you run more than one server on a host.
Should I run my Arma 3 server on Linux or Windows? Both work and use the same app ID `233780`. Linux is favored for lightweight, scriptable headless hosting; Windows can be easier if you already know the OS. Performance depends on CPU clock speed, not the operating system.
