Guide

14 min readJul 28, 2026

Palworld Port Forwarding: UDP 8211 Dedicated Server Guide

Forward the correct Palworld server port, create the matching Windows Firewall rule, test from outside your network, and fix CGNAT or Double NAT.

The short answer

For a Palworld dedicated server using its default settings, forward UDP port 8211 on your router to the private IPv4 address of the computer running the server. Allow the same UDP port through the host firewall, keep the server running, and test from a different internet connection. The current official Palworld requirements name UDP 8211 as the default, changeable game port. Do not open RCON port 25575 or Steam ports 27015–27016 unless a specific feature you intentionally use requires them.

See the simpler VPN fallback

Which Palworld ports should you forward?

Start with one precise game rule. The official Palworld 1.0 server requirements identify UDP 8211 as the default listening port and allow it to be changed with the -port argument.

Purpose	Default	Protocol	What to do
Player connections	8211	UDP	Forward this to the server PC. If you launch with a different -port value, forward that UDP port instead.
Community server listing	PublicPort	Advertised value	Usually keep it equal to the external game port. PublicPort tells the listing what to advertise; it does not change the server's listening port.
Remote administration (deprecated)	25575	TCP	Do not forward it for normal play. Palworld marks RCON deprecated and recommends keeping management APIs on the LAN.
Extra Steam ports seen in older guides	27015–27016	Varies	Not part of the current official base network requirement. Do not open them by default.

Opening more ports does not make a wrong rule work. It increases the exposed surface and makes troubleshooting harder. Match the port to the server's actual -port value.

Build your Palworld port forwarding rule

Enter the reserved local IPv4 address of the server computer and its listening port. Everything stays in your browser; nothing is submitted.

Server computer's local IPv4On Windows, run ipconfig and use IPv4 Address under the active adapter—not your public IP.Palworld listening port8211 is the default. Change it only if your PalServer launch command uses another -port value.

Router rule

Name: Palworld Server
External port: 8211
Internal port: 8211
Protocol: UDP
Device / target IP: 192.168.1.50

Windows PowerShell (run as administrator)

New-NetFirewallRule -DisplayName "Palworld Server UDP 8211" -Direction Inbound -Protocol UDP -LocalPort 8211 -Action Allow -Profile Private

Address to give friends

PUBLIC-IP:8211

Before you change the router

Make the server work on your LAN

Start PalServer and connect from another device on the same network using the host's private IPv4 and port. Port forwarding cannot fix a server that is not listening locally.

Reserve the host's local address

Create a DHCP reservation in the router for the server computer. Otherwise, a restart can give the PC a new address and leave the rule pointing at the wrong device.

Find the actual internet router

The Default Gateway shown by ipconfig is usually the router you must configure. If an ISP gateway sits in front of your own router, you may have two routing layers.

Confirm you can receive inbound IPv4

Compare the router's WAN address with your public IPv4. A private, shared, or different WAN address can indicate Double NAT or CGNAT.

How to port forward a Palworld dedicated server

Start the server and test it locally

Launch Palworld Dedicated Server and wait for it to finish starting. From another device on the same LAN, connect to the server computer's private IPv4 address followed by :8211. Fix the server, version, mod, or local firewall first if this test fails.

Reserve the server computer's private IPv4

In the router's LAN or DHCP settings, reserve the current address for the host computer. A reservation is safer than choosing a manual static address that may overlap the router's DHCP pool.

Confirm the Palworld listening port

The default is UDP 8211. If you change it, use the -port argument at server startup and restart the server. The router rule and firewall rule must use that same port.

PalServer.exe -port=8211

Create one UDP rule in the router

Open Port Forwarding, Port Mapping, Virtual Server, or NAT in the router. Send the external game port to the same internal port on the reserved server address. Save or apply the rule.

Rule name	Palworld Server
External / WAN port	8211
Internal / LAN port	8211
Protocol	UDP
Device / target	The server computer's reserved local IPv4

Allow UDP 8211 through the host firewall

On Windows, allow PalServer.exe or create a narrow inbound UDP rule for the selected local port. Run the example in an elevated PowerShell window. Do not disable the whole firewall.

New-NetFirewallRule -DisplayName "Palworld Server UDP 8211" \
+  -Direction Inbound -Protocol UDP -LocalPort 8211 \
+  -Action Allow -Profile Private

Test from outside your Wi-Fi

Keep the server running and ask a friend to join PUBLIC-IP:8211, or test from a second internet connection. A TCP-only port checker cannot reliably prove that a UDP game service is open, and a same-Wi-Fi test may fail when the router lacks NAT loopback.

Check the path before opening more ports

Run the NAT test on the same home connection as the server. It can reveal restrictive or symmetric behavior, but the final proof is a Palworld connection attempt from another network while PalServer is online.

Run the NAT test

Dedicated server vs community server for crossplay

Palworld 1.0 dedicated and community servers support Steam, Xbox Series, Microsoft Store PC, macOS, and PS5 crossplay. Xbox and PS5 players must join a community server, so a working port rule alone is not enough; the server also needs to be launched and advertised as a community server.

PublicPort does not change the listening port

For community servers, PublicPort or -publicport tells the public listing which outside port to advertise. The official documentation states that it does not change the port PalServer listens on. Use -port to change the listener, and keep the public listing, router mapping, and actual listener consistent.

Palworld port forwarding not working? Follow this order

Work from the server outward. Each answer removes an entire category of causes before you touch the next layer.

Can another device on your LAN connect to LOCAL-IP:8211?

No: fix PalServer startup, the listening port, game version, mods, or the host firewall. Yes: the server works locally; continue to the router path.

Does the router WAN IPv4 match your public IPv4?

No: check for an ISP gateway, Double NAT, or CGNAT. A rule on only the inner router cannot control an upstream NAT owned by another device or the ISP.

Does an outside player time out while PalServer is running?

Recheck UDP—not TCP—the external and internal port, the reserved target address, the active Windows network profile, and any third-party security software.

Can direct IP connect, but the community server is missing?

The network path works. Check -publiclobby, PublicIP, PublicPort, server version, and the community listing configuration instead of changing the router again.

Common symptoms and the most likely fix

What you see	Most useful check	What to do
Friends see a connection timeout	Wrong protocol, target IP, firewall profile, upstream NAT, or server not listening	Confirm LAN access first, then compare every rule with the live server port and test from outside.
It worked until the PC or router restarted	The server computer received a different local IPv4	Update the target address and create a DHCP reservation.
A website says UDP 8211 is closed	Many web checkers only perform a TCP handshake; UDP gives no equivalent reply	Keep PalServer running and use a real Palworld connection attempt from another network.
Public IP fails only from inside the home Wi-Fi	The router may not support NAT loopback	Test from mobile data or ask a friend outside the LAN. Use the private IP while at home.
PC players connect, but Xbox or PS5 players cannot find it	Console players require a community server	Launch with -publiclobby and verify PublicPort and listing settings.
Connections fail only while a VPN is active	Most VPNs do not pass unsolicited inbound UDP to your device	Disconnect it for router forwarding, or use a service that explicitly assigns an inbound UDP port and configure PalServer to match.

Router and ISP-specific help

Router menus use different names, but the rule remains the same: one external UDP port, the same internal UDP port, and the reserved address of the Palworld server computer.

Port forwarding on any router Check whether your ISP uses CGNAT Check for Double NAT Xfinity port forwarding Spectrum port forwarding AT&T BGW320 and BGW210 port forwarding

When port forwarding is unavailable—or not worth the hassle

Use a VPN as a fallback if your ISP uses CGNAT, you cannot access the active router, inbound traffic is filtered upstream, or you would simply rather not keep wrestling with network settings. A VPN with real port-forwarding support can give PalServer a public path: install the app, choose a location that supports port forwarding, and run PalServer on the UDP port the VPN opens or assigns. A normal VPN without inbound port forwarding will not make the server reachable.

Match PalServer to the VPN port

Keep the VPN connected, use a location that supports port forwarding, launch PalServer with -port set to the opened or assigned port, and allow that same UDP port through Windows Firewall. If the VPN assigns a different port after reconnecting, update PalServer and the firewall rule before players join.

PureVPNRecommended

The most direct fit when you want to open a chosen Palworld port instead of rebuilding the server around a random one. Its port-forwarding add-on supports specific ports in selected locations, including the US, Canada, UK, Germany, Japan, Hong Kong, and Singapore.

Proton VPN

A strong privacy-focused option on paid P2P servers. Proton assigns an active incoming port and supports UDP mappings, but the number usually changes after reconnecting, so PalServer must be launched on the current assigned port.

Private Internet Access

A practical option if a nearby PIA region supports port forwarding. Request the assigned port in the desktop app or supported setup, then use that number for PalServer and the inbound firewall rule.

Keep the public server safer

Forward only the UDP game port PalServer actually uses. Do not add TCP or unrelated ranges as a guess.
Do not place the entire server PC in the router's DMZ just to bypass troubleshooting; that exposes far more than one game port.
Do not expose RCON or the REST API directly to the internet. Palworld recommends keeping management APIs on the LAN.
Keep Palworld Dedicated Server, the operating system, and any mods current. Use a strong server password and maintain world backups.
Remove the router and firewall rules when you stop hosting, and review the rule after any port or host-address change.

Palworld port forwarding FAQ

What port does a Palworld dedicated server use?

The current official Palworld server requirements list UDP port 8211 as the default, changeable game port. If the server launches with -port=xxxx, forward that chosen UDP port instead.

Is Palworld port 8211 TCP or UDP?

UDP. Create the game rule as UDP on both the router and host firewall. Choosing TCP or assuming a TCP web checker can verify the service is a common cause of false failures.

Do I need to port forward for a Palworld dedicated server?

Usually yes when you host at home and internet players connect directly over IPv4. You do not need a home-router rule for LAN-only play or when a hosting provider, relay, tunnel, or VPN supplies the public inbound path.

Do I need to forward 27015, 27016, or 25575?

Not for the normal game connection documented by Palworld. The current base requirement is UDP 8211. Port 25575 is the deprecated RCON service, which the official guide recommends keeping on the LAN. Do not open extra Steam ranges without a specific documented need.

Why is Palworld port forwarding not working?

The usual causes are a server that does not work on the LAN, the wrong UDP port, a forwarding rule targeting an old local IP, a Windows Firewall block, Double NAT, CGNAT, or a misleading TCP-only port test.

Can Xbox and PS5 players join a home-hosted Palworld server?

Yes in Palworld 1.0, but the official guide says Xbox and PS5 players must join a community server. Configure the server for public listing as well as making UDP 8211 reachable.

Can I host Palworld without port forwarding?

Yes. Use a hosted dedicated server or an inbound tunnel or VPN that explicitly supports UDP. This can help behind CGNAT, but the assigned public port must match the server setup and may add cost, latency, or third-party dependence.

Will a normal VPN fix Palworld port forwarding?

Usually not. Most consumer VPN connections block unsolicited inbound traffic. You need a provider or tunnel that explicitly offers an inbound UDP port, then run PalServer on the assigned port or map it correctly.

Official and public-interest references

Port defaults, server behavior, firewall steps, and NAT troubleshooting are based on first-party documentation and nonprofit internet-operations guidance.

Share this article