Raft Dedicated Server 2026: RDS Setup, Hosting, Requirements, and Limits
Learn how Raft dedicated servers work in 2026, including RDS setup, official limits, hosting requirements, firewall rules, saves, cross-play, and fixes.

A Raft world is easy to start with friends, but it becomes frustrating when everyone depends on one host to stay online. If the host leaves, sleeps, loses internet, or cannot play, the whole group loses access to the world.
Raft still has no official vanilla dedicated server in 2026. Standard multiplayer is host-based online co-op.
For persistent 24/7 hosting, most players use RDS, an unofficial RaftModding community server tool that can run a world outside a normal player-hosted session.
This guide explains what RDS can and cannot do, including setup paths, hosting requirements, firewall rules, save migration, cross-play limits, networking modes, update risks, and common troubleshooting issues.
Raft Dedicated Server Quick Facts
| Item | Detail |
|---|---|
| Game | Raft |
| Steam App ID | 648800 |
| Official dedicated server | Not available |
| Official SteamCMD server app | Not available; App ID 648800 is the main Raft game app, not a separate official dedicated server app |
| Standard multiplayer model | Player-hosted online co-op |
| Community server option | RaftDedicatedServer (RDS) |
| RDS status | Unofficial community solution from the RaftModding ecosystem |
| Main RDS files | RaftDedicatedServer.exe and RDS_Data/config |
| RDS hosting type | Windows easiest, Linux advanced, Docker/Pterodactyl community-based |
| Cross-play status | Official Raft cross-play moved to the default branch in 2026; RDS cross-play depends on the current RDS networking layer and host implementation. |
Raft RDS Server Requirements
The following are practical RDS hosting estimates, not official Raft dedicated server requirements.
The RDS project lists an Intel Xeon E5-2670, 4 GB RAM, and 20 GB storage as the minimum, and a Ryzen 7 3800X, 8 GB RAM, and 40 GB storage as the recommended baseline. The table below translates those specs into practical hosting guidance.
| Component | Minimum Requirement | Recommended Requirement |
|---|---|---|
| CPU | 2 cores, 2.6+ GHz | 4+ cores, 3.5+ GHz (high clock speed) |
| RAM | 4 GB | 8 GB |
| Storage | SSD, 20 GB free | NVMe SSD, 40+ GB free |
| Bandwidth | Stable upstream connection | Practical estimate: stable low-latency bandwidth with enough upstream capacity for your player count |
- Minimum: Suitable for small private tests, depending on raft size, mods, RDS version, and host performance.
- Recommended: Better for larger worlds, modded servers, and groups above a few players, but performance depends on raft complexity and RDS compatibility.
- Storage: SSD/NVMe storage is strongly recommended for faster world saves, backups, and recovery.
- Bandwidth: Stable low-latency bandwidth helps reduce lag and disconnects, but CPU load, routing, packet loss, and server health also matter.
- For larger groups, dedicated servers offer more predictable CPU, storage, and network resources than a home PC.
How to Set Up a Raft Dedicated Server with RDS
Windows
Step #1: Understand SteamCMD’s Role
- Download SteamCMD only if your chosen RDS workflow or hosting panel uses it to manage Raft game files.
- Extract to a dedicated folder like C:\steamcmd and run:
steamcmd.exe
- This initializes SteamCMD.
Note: SteamCMD cannot install an official Raft dedicated server app. Some panel-based or community workflows may use SteamCMD, but the RDS Windows guide tells users to copy the Steam-installed Raft files into the server folder. Raft App ID 648800 is the game app, not a dedicated server app.
Step #2: Copy Raft Game Files
- Install Raft via Steam.
- Copy all files from the Steam Raft directory to a new server folder such as C:\RaftServer. This requires a valid Raft license because no official standalone dedicated server binaries exist. If you prefer a Windows-based workflow, Windows dedicated server hosting can make file management, updates, and service setup easier.
Step #3: Deploy RaftModding RDS Binaries
- Obtain an RDS Private Key (required for self-hosting).
- Download RaftDedicatedServer.exe from the RaftModding RDS project or a trusted RDS host. Do not describe it as official Raft server software.
- Place it in your server folder alongside the Raft game files.
Step #4: Configure RDS INI and JSON Files
- Generate the RDS config files.
RaftDedicatedServer.exe
- Edit rds_config.ini for server settings and ranks_config.json for permissions in RDS_Data\config. Leave anticheat_config.ini at defaults unless you know what you are changing.
- Add your RDS Private Key and Steam Web API Key as required.
Step #5: Open Only Required Ports
- Allow RaftDedicatedServer.exe through Windows Firewall only for the network profiles and ports required by your RDS setup.
- Follow the port and networking guidance for your exact RDS build or hosting panel. Do not expose internal console or admin ports, and only open additional Steam or UDP ranges when the current RDS documentation specifically requires them.
Note: Self-hosting may require an RDS Private Key and Steam Web API Key before launching the server.
Step #6: Launch and Verify Logs
- Start RaftDedicatedServer.exe.
- Check the console and log files for successful startup messages, version mismatch warnings, missing keys, and networking errors.
Note: Always back up configuration files before changes and verify server compatibility after Raft updates.
Linux Advanced Setup
The Linux steps below are example commands for advanced users. Confirm the current RDS Linux guide, distro version, Wine requirements, and hosting panel instructions before using them in production.
A Linux dedicated server is useful when you want full control over Wine, services, backups, firewall rules, and long-running RDS maintenance.
Step #1: Create a Dedicated User
- Create a secure non-root user with:
# sudo useradd -m -s /bin/bash steam
# sudo mkdir -p /home/steam/raftserver
# sudo chown -R steam:steam /home/steam/raftserver
Step #2: Install Dependencies
- Install the Wine and Linux dependencies required by the current RDS Linux guide or your hosting panel. Do not assume one dependency list works for every RDS build.
Ubuntu/Debian example only:
sudo apt update && sudo apt upgrade -y
sudo dpkg --add-architecture i386
sudo apt install -y wget software-properties-common winetricks xvfb lib32gcc-s1 steamcmd
Step #3: Configure Wine Environment
- For Wine-based Linux setups, install the dependencies required by your chosen RDS guide and test the launch before creating a service.
# sudo -u steam bash -c "cd /home/steam/raftserver && wget https://dl.winehq.org/wine/wine-mono/latest/wine-mono-latest.msi"
# sudo -u steam bash -c "cd /home/steam/raftserver && winetricks sound=disabled dotnet48"
# sudo -u steam bash -c "cd /home/steam/raftserver && wine msiexec /i wine-mono-latest.msi /quiet"
Step #4: Copy Raft Game Files
- Install Raft via Steam. Raft App ID 648800 is the game app, not an official dedicated server app ID.
- Copy the entire Raft folder to /home/steam/raftserver
- Fix ownership
# sudo chown -R steam:steam /home/steam/raftserver
Step #5: Download the RaftModding RDS Binary
- Download the RaftModding RDS executable.
# sudo -u steam wget -O /home/steam/raftserver/RaftDedicatedServer.exe https://master.raftmodding.com/download/RaftDedicatedServer.exe
Step #6: Test Launch
- Manually test the launch
# sudo -u steam bash -c 'cd /home/steam/raftserver && /usr/bin/xvfb-run -a -s "-screen 0 1024x768x24:99" env WINEDLLOVERRIDES="winhttp=n,b" WINEDEBUG="-all" wine64 RaftDedicatedServer.exe'
- This generates the RDS_Data/config folder.
- Press Ctrl+C after the configs appear.
Step #7: Configure Server
- Open the configuration file with any text editor like Nano:
# sudo -u steam nano /home/steam/raftserver/RDS_Data/config/rds_config.ini
- Edit these values:
- Server name
- Max players
- RDS Private Key
- Steam Web API Key
Step #8: Create systemd Service Example
Test the launch command manually before creating a persistent service.
- Open the file with any text editor:
# sudo nano /etc/systemd/system/raftds.service
- Add the following to the file:
[Unit]
Description=Raft RDS Server
After=network.target
[Service]
User=steam
Group=steam
WorkingDirectory=/home/steam/raftserver
ExecStart=/usr/bin/xvfb-run -a -s "-screen 0 1024x768x24:99" env WINEDLLOVERRIDES="winhttp=n,b" WINEDEBUG="-all" wine64 RaftDedicatedServer.exe
Restart=always
RestartSec=5
KillMode=process
[Install]
WantedBy=multi-user.target
- Execute the following:
# sudo systemctl daemon-reload
# sudo systemctl enable raftds
# sudo systemctl start raftds
Step #9: Open Firewall Ports Required by Your RDS Build
- Use firewall rules only for the ports required by your current RDS networking mode or provider panel.
Step #10: Verify and Monitor
- Check the RDS service status.
# sudo systemctl status raftds
# sudo journalctl -u raftds -f
How RDS Changes Multiplayer
(Note: Official Raft cross-play moved to the default Steam branch in 2026. RDS cross-play depends on the active RDS networking layer and hosting implementation.)
- RDS replaces host-based sessions with a standalone community server process.
- The server runs outside a normal player-hosted session, but it still depends on the machine, network, and RDS build running it.
- Many RDS join flows use Raft Mod Loader, then join by a provider-supported join code, server browser, or host-specific method, depending on server configuration.
- Clients join through the networking layer supported by the RDS build, mainly RTCP or Steam mode, according to RDS documentation.
- RTCP mode generally requires Raft Mod Loader and is not suitable for vanilla clients. Steam mode may support vanilla users, but setup requirements can differ and may require another Raft copy or provider-specific configuration.
- Some older or community RDS setups may require manual firewall or router configuration, but admins should follow the current RDS documentation or provider panel.
- World state is saved on the server, allowing 24/7 access when the host, RDS build, and network remain stable.
- RDS and Raft save behavior should be verified in the current build. Always configure regular external backups.
Limitations of RDS
- Partial Feature Coverage: Some vanilla multiplayer behaviors, mods, or features may behave differently on RDS. Verify required features before moving an active world.
- Slower Updates: Because RDS is community-driven, admins should verify compatibility after major Raft patches before updating production servers.
- Manual Intervention: Server admins may need to update binaries, configs, mods, and sometimes migrate saves after significant game changes.
- Windows Binary Focus: RDS is distributed as a Windows executable; Linux setups are more advanced and may rely on compatibility layers or community workflows.
RDS Firewall Safety Checklist
RDS firewall requirements depend on the networking layer, build, and hosting method. Use the table below as a general safety checklist, not as official or version-specific port documentation:
| Purpose | Protocol | Port / Rule |
|---|---|---|
| RDS Networking Mode | TCP/UDP | Varies by RDS build, networking mode, or hosting panel |
| Optional Steam Extras (Only If Required) | TCP/UDP | Only open these if the current RDS documentation or provider panel requires them |
| RDS Console/Admin Port | TCP | Do not expose console or admin ports publicly |
Note: Most users should follow their RDS panel or current RDS config. Avoid opening extra ports unless required, and never expose internal console or admin ports publicly. For public communities, DDoS protected dedicated servers can help reduce downtime risk when game traffic or unwanted network activity increases.
Firewall Rules
For Windows:
- Allow RaftDedicatedServer.exe through Windows Firewall only for the network profiles and ports required by your RDS setup.
- Add inbound/outbound rules only for ports required by your exact RDS build or hosting panel.
For Linux:
- Use firewalld or iptables only for ports required by your exact RDS networking mode. Do not run firewall commands until you confirm the correct ports from your RDS build or hosting panel.
Router Forwarding Checklist
- Forward only the ports required by your current RDS build or provider panel to the server’s static local IP.
- Reboot the router if necessary.
- Disable VPNs during testing or ensure they support inbound port forwarding.
Note: Only open/forward necessary ports and use program-based firewall rules for added protection.
How to Join a Raft Dedicated Server
Depending on the RDS build and host, you may join RDS servers through:
- Server browser behavior
- World code or provider-supported join method
- Steam friends fallback
Server Browser Behavior
- Open Raft through the required RDS or Mod Loader flow, then check the available server browser or join-code option.
- Filter by server name, world code, or community RDS listings if your build supports them.
- Steam-mode or browser-listed servers may appear publicly if the RDS build and configuration support that behavior.
- Refresh list (F5) or search server name
World Code or Provider-Supported Join Method
- Obtain the world code, server listing details, or provider-supported connection details from the administrator.
- Use the RDS join code, server browser, or provider-supported join method instead of assuming a universal IP:port connection.
Steam Friends Fallback
- Vanilla Multiplayer: Join friends via Steam overlay
- Right-click friend
- Join Game
- Joins their client session directly
- RDS Servers: Steam friends behavior depends on the RDS networking mode. Use the server browser, provider-supported join code, or host instructions when available.
- For vanilla Steam co-op, Steam overlay and friends-list joining may work as expected. For RDS, follow the host or provider instructions for the current networking mode.
Raft RDS on PS5 and Xbox
- Raft has no official PS5 or Xbox dedicated server app. Do not assume console access to RDS unless the current RDS build or hosting provider explicitly confirms console-compatible support.
- RDS cross-play depends on the current networking layer, RDS build, and hosting provider. Admins should verify support before buying or migrating.
- Official Raft multiplayer is session-based and host-dependent. RDS behavior may differ depending on the provider, platform, and networking layer.
- Raft cross-play moved to the default Steam branch in 2026 after previously being available through a beta branch.
| Feature/Capability | PS5/Xbox Status (2026) |
|---|---|
| Official Raft Dedicated Server Support | Not available |
| Unofficial/Modded RDS | Depends on the current RDS networking layer and provider support |
| Cross-Platform RDS Hosting | Verify with the current RDS build or host before purchase |
| Official Online Co-op | Supported |
| Official Dedicated/Persistent Server Hosting | Not available |
Self-Hosting vs Paid Raft Server Hosting
Self-hosting is where you run RDS on your own system or server. The setup depends on your hardware, network, operating system, and RDS build.
Paid Raft server hosting is where you run RDS on infrastructure managed by a hosting provider.
Before you decide which to choose, you must weigh the trade-offs between self-hosting and paid managed solutions.
| Feature/Aspect | Self-Hosting | Paid Hosting / Managed RDS Hosting |
|---|---|---|
| Uptime | Dependent on local hardware, power, and ISP. 24/7 uptime requires a robust infrastructure. | Usually hosted in data centers with stronger power and network redundancy than home setups, depending on the provider. Uptime depends on the provider’s infrastructure, SLA, and support quality. |
| Control | Full root/admin access Unrestricted mod/plugin installation. | High, but some restrictions (panel-based access, limited OS-level control). |
| Cost | Hardware, electricity, and bandwidth cost | Subscription-based No hardware/electricity costs Predictable expense. |
| Maintenance | User is responsible for OS/game updates, backups, security, and troubleshooting. | Many providers offer panels, support, and optional backup or security features, but exact coverage varies by plan |
| Risk Exposure | Hardware failure, data loss, security breaches, ISP outages, and time investment. | Different risk profile: fewer home-network and hardware risks, but more provider, plan-limit, and support dependency. Users still need to understand backups, updates, mod compatibility, and provider limits. |
Which to Choose: Self-Hosting vs Paid Raft Server Hosting
Choose self-hosting:
- Small private groups
- Short play sessions
- Full technical control
Choose paid hosting:
- Always-online worlds
- Groups in different time zones
- Players who want an easier setup and less local admin work.
RDS vs Traditional Game Dedicated Servers
- Update Lag Risk:
- Because RDS is community-driven, admins should verify compatibility after major Raft patches before updating production servers.
- After major game updates, servers may become temporarily incompatible until RDS, mods, configs, or hosting panels are updated.
- Feature Parity Issues:
- RDS is community-driven and not fully server-authoritative.
- Some multiplayer features, mods, or behaviors may be missing or behave differently compared to official dedicated server tools in other games.
- Long-Session Stability:
- RDS can offer persistent, always-on worlds when the host, network, and RDS build remain stable.
- Stability can be affected by update lag, client-authoritative design, and performance bottlenecks with large rafts or high player counts.
- Official dedicated server tools often have clearer update paths and documentation than RDS, but automation and backups depend on the game and host.
| Feature | RDS (Raft) | Traditional Game Dedicated Servers |
|---|---|---|
| Authority Model | Client-authoritative with persistent server state | Often server-authoritative (e.g., shooters, MMOs) |
| Update Automation | Manual or semi-manual | Often easier to automate |
| Modding Support | Community-driven | Varies by game |
| Scalability | Depends on hardware, raft size, mods, and RDS build | Depends on game, server software, and hosting setup |
| Security | Depends on RDS build, exposed ports, permissions, host firewall, and update discipline | Depends on server software, host hardening, admin controls, and patching |
Who Should Use RDS for Raft
- Long-Running Co-op Groups: Communities looking for persistent worlds for collaborative projects and flexible play schedules.
- Mod Testers: Developers and enthusiasts needing a stable environment for testing plugins, mods, and custom scenarios.
- Always-Online Communities: Streamers and groups that need 24/7 access and are comfortable with RDS limits, updates, and maintenance.
Who Should Avoid It
- Casual Weekend Players: Individuals or small groups playing occasionally usually do not need self-hosted RDS unless they specifically want an always-online world.
- Console-Only Groups: PS5/Xbox players should verify current RDS console compatibility before choosing RDS and should use official multiplayer where available instead of assuming RDS support.
- Zero-Maintenance Expectations: Users unwilling to perform regular updates, backups, compatibility checks, or troubleshooting should avoid self-hosted RDS and use official online co-op or managed hosting instead.
Common RDS Issues and Fixes
The following table discusses common issues and fixes you may face during RDS setup.
| Issue | Symptoms/Impact | Workaround/Best Practice |
|---|---|---|
| Game update breaks the server | Server fails to start, version mismatch | Delay updates until RDS and mods are confirmed compatible; back up before patching. |
| Save corruption | World fails to load, missing raft/progress | Implement daily automated backups and test restore steps before major updates. |
| Desync | Disappearing islands/players, item issues | Restart the server if needed, have players rejoin, verify version compatibility, and check connection stability. |
| Connection failures | Black screen, timeout, "Issues Connecting" | Check firewall rules, networking mode, Mod Loader status, server version, password, world code, and client compatibility. |
| Performance bottlenecks | Low FPS, lag on large rafts/player counts | Limit raft complexity, use strong single-core CPU performance and NVMe storage, monitor resource use, and restart during maintenance windows. |
Host Your Raft RDS Server on RedSwitches Dedicated Infrastructure
RDS is not an official Raft dedicated server, but it can help PC players keep a Raft world online when the setup is managed correctly. For serious co-op groups, modded communities, and always-online worlds, dedicated server hosting offers more control than a home PC or unstable local network.
A reliable Raft RDS setup needs strong single-core CPU performance, fast SSD or NVMe storage, stable bandwidth, regular backups, and proper firewall rules. With RedSwitches bare metal servers, you get full root access, predictable resources, and more control over updates, mods, save files, and monitoring.
Before moving an active world, plan your server location, backup process, update schedule, and security settings. The right game server hosting setup can make RDS easier to manage and keep your Raft world available across time zones.
Frequently Asked Questions
Common questions about raft dedicated server 2026: rds setup, hosting, requirements, and limits.
Does Raft Have An Official Dedicated Server In 2026?
How many players can a Raft dedicated server handle?
Can you run a Raft server 24/7?
Is Raft cross-platform multiplayer supported?
Can you migrate a Raft world to a dedicated server?
Does Raft support official dedicated servers?
Hafsa Qadeer
Technical Writer
Hafsa Qadeer is a Technical Content Writer at RedSwitches and a journalist with a background in molecular biology and oncology. She brings research precision to technical writing and SEO strategy, turning complex topics in infrastructure, biotech, and AI into content that informs and engages.
Power Your Next Project With Bare Metal
10 min delivery, zero setup fees, and 24/7/365 human engineers across 20+ global locations.


