Palworld Server Ports: Which Ports to Open

To host a Palworld dedicated server that other players can join over the internet, you need to open UDP port 8211 for the main game traffic, plus UDP port 27015 for Steam query responses. This article explains exactly which ports to forward, how to configure them on your router, and what to do when players still can’t connect.

Default Palworld Server Ports

Palworld’s dedicated server software listens on two UDP ports by default:

• UDP 8211 – The main game port. All player connections and gameplay data flow through this port.
• UDP 27015 – The Steam query port. This lets Steam’s server browser and tools like SteamCMD see your server’s name, player count, and status.

Both are UDP only – Palworld does not use TCP for player connections. If you’re hosting on a local network only (LAN), you don’t need to open any ports; players on the same network can join via your local IP address.

How Port Forwarding Works for Palworld

Port forwarding tells your router to send incoming traffic on specific ports to a specific device on your network – in this case, the computer running the Palworld server. Without this rule, the router drops incoming packets, and remote players get a “connection timed out” error.

When you set up port forwarding, you provide:

• External port – The port players use to reach your server (default 8211).
• Internal port – The port your server actually listens on (also 8211 by default).
• Internal IP – The static IP address of your server machine on your local network.
• Protocol – UDP (or both UDP/TCP if your router requires it, but UDP is sufficient).

Most routers also require you to set a static IP for the server computer, otherwise the port forward breaks when the DHCP lease renews and the IP changes.

Step-by-Step: Opening Ports on Your Router

1. Find your router’s gateway IP (on Windows, run ipconfig and look for “Default Gateway”; on macOS, go to System Settings > Network > your connection > Details).
2. Type that IP into a browser and log into the router admin panel (check the router label for default credentials).
3. Locate the port forwarding section – often under “Advanced,” “NAT,” “Virtual Server,” or “Gaming.”
4. Create a new rule: name it “Palworld,” set protocol to UDP, external port 8211, internal port 8211, and internal IP to your server’s static IP.
5. Create a second rule for UDP 27015 with the same internal IP.
6. Save and apply the changes. Some routers require a reboot.
7. Test from a device on a different network (e.g., your phone on cellular data) by trying to join using your public IP and port 8211.

If your router supports UPnP, you can enable it instead of manually forwarding – the server will try to open the ports itself. However, UPnP is less reliable and can be a security risk, so manual forwarding is recommended for a persistent server.

How to Change the Default Ports

You can change the ports in the server configuration file PalWorldSettings.ini, located in the Pal/Saved/Config/WindowsServer folder of your server installation. The relevant settings are:

• PublicPort=8211 – The main game port.
• ServerName – Not a port, but the name shown in the server list.

There is no separate setting for the query port in the ini; the query port is always 27015 and cannot be changed in the standard dedicated server build. If you change the game port, you must update your port forwarding rules accordingly.

If you run multiple Palworld servers on the same machine, each needs its own game port (e.g., 8211, 8212, 8213) and a separate port forward rule for each. The query port 27015 can only be used by one server per IP, so additional servers will not appear in the Steam server browser – players must join them via direct IP:port.

Common Connection Problems and Fixes

Even with ports forwarded, players may still fail to connect. Here are the most frequent causes:

• Windows Firewall blocking – Add inbound rules for UDP 8211 and UDP 27015 in Windows Defender Firewall. The server may prompt you on first launch; if you clicked “Cancel,” the firewall blocks it.
• Wrong internal IP – Double-check that the server machine’s IP hasn’t changed. Set a static IP or DHCP reservation.
• ISP blocking inbound connections – Some internet providers block inbound traffic on common game ports or use carrier-grade NAT (CGNAT), which makes port forwarding impossible. Contact your ISP or use a VPN tunnel like Hamachi or Radmin.
• Router double NAT – If your network has two routers (e.g., a modem-router plus a separate Wi-Fi router), forward ports on both devices, or put the second router in bridge mode.
• Server not running – The server must be fully started and listening before you test. Check the console output for “Successfully started” or similar.

To verify if the port is actually open, use an online port checker tool – but note that these tools test TCP by default, and Palworld uses UDP, so a TCP test will always show closed. Instead, test by having a friend try to join, or use a UDP-specific tool like netcat on Linux.

Dedicated vs. Co-Op Hosting

Palworld offers two ways to play with others:

• Co-op (host player) – You join a world and others join your game session. This uses the same port 8211, but the host must have the game running and be in the world. Port forwarding works the same way, but the host’s game must be open.
• Dedicated server – A separate server process runs 24/7 without anyone playing. This is what most community servers use. It requires the same port forwarding but is more stable and allows more players (up to 32).

For co-op, you can also use the in-game invite system which may use Steam’s peer-to-peer networking, bypassing port forwarding entirely. However, for a persistent server that anyone can join, dedicated hosting with forwarded ports is the standard approach.

Security and Safety Considerations

Opening ports exposes your server to the internet, so take basic precautions:

• Set a strong admin password – In PalWorldSettings.ini, set AdminPassword to something long and unique. This prevents unauthorized console commands.
• Keep the server software updated – Palworld updates frequently; an outdated server may have known vulnerabilities.
• Don’t forward ports you don’t need – Only forward 8211 and 27015. Avoid enabling DMZ or forwarding all ports.
• Use a firewall on the server machine – In addition to Windows Firewall, consider a hardware firewall or a cloud provider’s security group if you rent a VPS.

If you’re renting a dedicated server from a hosting provider, you don’t need to forward ports – the provider gives you the IP and port, and you simply share that with players. Port forwarding is only for self-hosting from your home network.

Frequently Asked Questions

Do I need to open both TCP and UDP ports?

No. Palworld uses UDP exclusively for game and query traffic. Forwarding only UDP is sufficient. Some routers require you to select “Both” or “TCP/UDP” if they don’t allow UDP-only rules, but that won’t cause problems – it just also forwards TCP on those ports, which Palworld ignores.

What is my public IP address to share with friends?

Your public IP is the address of your router on the internet. You can find it by searching “what is my IP” in a browser. Share it in the format your.public.ip:8211 (e.g., 203.0.113.5:8211). Note that many ISPs assign dynamic IPs that change periodically, so you may need to update the address or use a dynamic DNS service.

Why can’t I join my own server using my public IP?

This is a common issue called NAT loopback. Many routers don’t allow connections to your own public IP from inside your network. Test your server from an external network (like a phone on mobile data) or use your local IP when playing on the same LAN. If external players can join, your server is working correctly.

Can I run multiple Palworld servers on one machine?

Yes, but each server needs its own game port (e.g., 8211, 8212, 8213). You must forward each port individually. The Steam query port 27015 can only be used by one server per IP, so only the first server will appear in the Steam server browser; others must be joined via direct IP:port.

What if my ISP uses CGNAT?

Carrier-grade NAT means your public IP is shared among many customers, and you cannot forward ports from the internet to your home network. You can check if you’re behind CGNAT by comparing your router’s WAN IP to your public IP – if they differ, you’re likely behind CGNAT. Solutions include requesting a public IP from your ISP, using a VPN tunnel like Hamachi, or renting a cheap VPS and running the server there.

Related

• JDK vs JRE vs JVM: What to Install
• Schedule Automatic Dark Theme Android 10
• Google One Lite Plan: Price, Features & Launch Details