Valheim dedicated server Synology: NAS checks
A Valheim NAS checklist for Synology, unRAID, TrueNAS, and Proxmox: confirm model support, persistent world storage, network paths, and backup recovery.
You will need
- Your exact NAS or hypervisor model and installed software release
- Access to the device architecture, runtime and storage settings
- A disposable Valheim world for acceptance checks
- A separate location for a test backup
If you searched “Valheim dedicated server Synology,” start with the exact model and software release: a container feature label cannot establish image architecture, headroom, persistent storage or safe networking. The same checks apply to unRAID, TrueNAS and Proxmox. This guide helps you decide whether a homelab is a sensible place for your world; it does not claim we tested those appliances.
Valheim dedicated server Synology: verify the exact model#
Synology support is model-specific. Check your NAS in Synology’s Package Center compatibility guide, confirm that its installed DSM version supports Container Manager, then compare the NAS CPU architecture with the image you intend to run. A package that installs successfully, or Docker support on a product page, is only one compatibility check.
Record these details before choosing a deployment:
| Check | Where to verify it | Why it matters |
|---|---|---|
| Exact model and DSM release | NAS product page and installed system information | Package availability and device limits differ by model and software version. |
| CPU architecture | The model’s hardware specifications | The dedicated server or container image must provide a compatible build. Do not infer ARM support from the word “Docker.” |
| Memory available to the game | System monitor while household services run | Memory installed in the NAS is shared with the operating system, file services and other apps. No universal Valheim minimum is established for every world. |
| Container runtime and permissions | The model’s current Synology docs | Confirm persistent mounts, network mapping and the way the service stops before moving a campaign. |
For example, Synology lists the DS224+ with an Intel Celeron J4125, four CPU threads and 2 GB of included memory, expandable to 6 GB. Those are device specifications, not a Valheim performance result or a recommendation for your world. Use the published specifications for your exact NAS, not another model’s shopping page.
If Synology does not list the package you need, that does not prove the machine is impossible to use. It means you must separately establish that the supported runtime, CPU image, available resources and storage mapping all fit. Keep the existing shares and services outside the test until that case is clear.
If the selected host supports Docker, check the image’s own architecture and mounts too; the current Valheim Docker image settings reference explains the maintained project’s paths and defaults.
Choose a container or a VM by the boundary you need#
Pick the method you can update and recover on your installed release. Synology and Unraid center on Docker containers; TrueNAS SCALE 25.10 documents Apps and host storage; Proxmox VE lets you run a Linux guest VM or an LXC container. These choices are not four Valheim editions, and none of the vendor docs certifies a particular NAS plus game image as compatible.
| Platform | Starting point to investigate | Verify before you follow a guide |
|---|---|---|
| Synology | Container Manager, if the exact model supports it | Package support, CPU architecture, persistent volume path and required privileges. |
| unRAID | Docker template with app data outside the container | Bridge versus host networking, explicit port mappings, data path and auto-start behavior. |
| TrueNAS SCALE 25.10 | Apps pool and a custom app or Compose setup | Use the stable docs for your installed release; plan the dataset, host path, network and app permissions first. |
| Proxmox VE 9.x | A Linux VM when you want the game process inside a separate guest OS | Guest resources, bridge/firewall path, storage and a tested guest backup. Community LXC recipes are not official Valheim compatibility tests. |
Unraid explains that bridge mode exposes mapped ports while host mode shares the NAS network stack; either way, a port mapping must match the service configuration. Its docs also recommend keeping app data outside the container so replacing an image does not have to remove the data with it. For TrueNAS 25.10 Apps and VM configuration, decide the app pool, host path, IP, DNS and storage layout before beginning. The Proxmox VE 9.x administration guide describes the hypervisor’s VM, container and backup controls, not Valheim’s resource requirements.
Use a VM when the guest operating system gives your operator a boundary they understand and can maintain. Use a container when the supported image and storage/network mapping are clear to them. If you want help with a general container route, see the Valheim Docker setup and restore guide; its instructions describe that image and test setup, not every NAS app catalog.
Keep world data separate from the container and array#
Keep the game’s complete world data on an intentional persistent dataset or volume, separate from the container’s replaceable image. The correct host path depends on the selected image and server setup, so copy it from that project’s documentation instead of guessing a Valheim path from a different platform.
Before installing, write down four mappings: the host dataset or share, its path inside the VM or container, the user that needs write access, and the location of the recovery copy. Expose only the world/configuration directory that the process needs. Avoid mounting the whole NAS or household shares into the game container; an application should not get broad access to family documents just because it can read them.
Then separate availability from recovery. RAID or a mirrored pool can keep storage available after some drive failures; it does not give you an independent copy if a mistaken delete, failed update, account compromise or appliance loss affects the original. A snapshot on the same pool may help roll back a change, but it remains inside that NAS’s storage failure domain. Keep a copy on another device or storage service that your NAS credentials cannot silently overwrite.
Iron Gate’s server manual documents where server saves go for its Windows and Linux setup, but a container can remap that location. Confirm the actual active save directory in the image or guest configuration, then check that the backup job copies it after a clean stop or uses a method documented as consistent while the server runs. The generic dedicated-server routes guide compares who owns each layer; this page focuses on the appliance boundary.
Trace Valheim traffic through every network layer#
Follow a connection from the game server out to a friend, then back through every boundary you added. For the Steam backend, Iron Gate documents the default UDP range as 2456–2457: the configured port and the next port. A container bridge, VM firewall, NAS firewall and router can each add a separate mapping or rule. Write down the selected server port and check each layer against it; do not expose the NAS web console, SMB, or a hypervisor control panel to the public internet to make a game port work.
The crossplay backend uses a relay and does not require router port forwarding, but the official manual says local and loopback IP addresses cannot be used to join a crossplay server. Crossplay is therefore not a reason to rent a server or to open ports automatically. It is still a reason to test the actual route from outside your home network with the crew’s current clients.
For a bridge container, trace: Valheim’s configured port → the container’s internal port → the host-side mapping → NAS or guest firewall → router rule, if using Steam networking. For a VM, replace the container mapping with the guest interface and its firewall. If a network mode shares the host stack, verify that its port is not already in use by another household service. Change one layer at a time and keep the old configuration so you can undo a failed test.
Measure competing NAS workloads before game night#
Decide with readings from your own device, not an online minimum copied from a different world. Iron Gate’s manual explains how to start and administer the server, but it does not publish one CPU, RAM or disk threshold that guarantees smooth play on every NAS. Player count alone will not account for your world, build area, plugins, clients or the other apps running on the appliance. Use the Valheim server requirements worksheet to keep workload and observed resources separate.
Compare a quiet baseline with the workload that competes for the same machine. On a disposable world, capture the NAS’s available memory, CPU use, disk response/free space and network activity while the array performs its planned backup, scrub or other heavy task. Repeat during a session in the crew’s busiest representative area. Record timestamps and the world activity so that a second reading can be compared honestly.
| Observation | Quiet baseline | During array work | During representative session |
|---|---|---|---|
| Available memory and sustained CPU | Record device reading | Record same reading | Record same reading |
| Storage latency, free space and disk activity | Record device reading | Record same reading | Record same reading |
| Network activity and client symptoms | Record observation | Record observation | Test the same remote client route |
There is no pass/fail number in this table. Look for repeatable contention and decide whether the busy job can move to another time. A container that starts only proves that the process launched; it does not prove the NAS can run it alongside media scans, backups and a busy Valheim world.
Test a clean stop, restart and off-device restore#
Run acceptance checks with a throwaway world before you migrate the group’s campaign. A reboot that returns the container to “running” is not enough: check that Valheim opened the intended world, the server logs show a clean start, the correct external client can join, and new progress remains after another clean stop and start.
Use a copy of the test world for recovery. Restore the off-device copy to a separate dataset or disposable instance, make sure the path is not the original, and launch it with the same server version. Load the intended world, inspect a known area and ask another player to join from the actual network route. If the restored instance opens a new or empty world, stop and fix the mapping rather than writing over the source campaign.
Finally, simulate the appliance restart you expect to happen after maintenance. Check the automatic start policy, world path, log location and external access again. Save the steps and name a second person who can follow them. If you cannot explain how you would recover the world without mounting the household array into every application, keep testing on disposable data.
Decide whether the NAS or a managed server owns the work#
Keep Valheim on the NAS when the exact model and runtime are supported, the selected image matches its architecture, the world path is persistent, an off-device restore has been rehearsed, the actual busy workload leaves acceptable headroom, and someone owns updates and recovery. If one of those checks is unknown, the NAS may still be a useful experiment; it is not ready to hold the only copy of a long-running campaign.
If your household NAS should stay focused on storage, we recommend Game Hosting’s Valheim service. Its game panel brings Valheim settings and scheduled restarts together, with three free backup slots that can be scheduled, restored, downloaded or locked. That moves the game process and its routine controls off the household array; it is not a benchmark against your device or a guarantee that every world can be restored.
Choose the path that matches the work your crew wants to own. A compatible homelab can be a sensible low-cost route when someone monitors it and maintains an independent backup. Managed hosting is the alternative when keeping a separate NAS operating procedure no longer feels worthwhile. Renting does not repair an incompatible save, client issue or network problem, so keep those checks tied to the actual cause.
Quick answers
Can every Synology model run the same Valheim container?
No. Container Manager availability and supported packages vary by model, and the selected image must support the NAS CPU architecture.
Is a NAS snapshot an independent Valheim world backup?
No. Keep a separate copy outside the NAS or storage pool, then rehearse restoring a disposable world before trusting the procedure.
Should I host Valheim while the NAS is doing a heavy scrub or backup?
Only after checking your own device during that workload and a representative game session; there is no universal safe threshold for every NAS and world.

