Minecraft Port Explained: Port 25565, Forwarding, and Where to Actually Open It

• 30 June 2026
• by: Theo Vandenberg
• in: Web hosting
• Tags: minecraft port, port 25565, port forwarding
• note: no comments

You typed “minecraft port” into a search bar, and I have good news and slightly inconvenient news. The good news: the answer to “what port does Minecraft use?” is short, memorable, and the same number it’s been for years. The inconvenient news: the *useful* version of that question — “how do I open my Minecraft port so my friends can join?” — has two halves, and most tutorials only tell you about the easy one.

Let’s do both halves honestly. By the end you’ll know exactly what port 25565 is, how to change it, how to forward it through your router, and — the part people skip — what you’ve actually exposed when you do.

Key Takeaways
• The default Minecraft port is 25565 (TCP) for Java Edition; Bedrock Edition uses 19132 (UDP).
• The port is the “door” clients connect through. If you keep the default, players can connect with just your address and omit the port entirely.
• You change it in `server.properties` with the `server-port=` line — mainly to run multiple servers or dodge conflicts.
• Port forwarding maps an external port on your router to your PC’s local IP so the public internet can reach your server.
• Forwarding 25565 from home works, but it exposes your real home IP to scanning and DDoS risk — which is exactly why hosted game servers exist.

What is the default Minecraft port (and what does it actually do)?

The default Minecraft server port is 25565, using the TCP protocol. When a Java Edition client connects to a server, it’s really saying: “I want to reach this IP address, specifically through door number 25565.” The IP address gets the connection to the right building; the port number gets it to the right *room*.

A port is just a numbered channel on a machine. Your computer runs lots of services at once — web traffic, email, game servers — and ports keep them from talking over each other. When you launch a Minecraft server, it binds to port 25565 and starts *listening*: it sits there waiting for incoming connection attempts on that specific door.

Here’s the thing nobody frames clearly. The Minecraft port (25565) is where the friendly world of “just play with friends” collides with real networking, and the moment you port-forward it, you’ve quietly done something significant: you’ve opened a permanent, public door on your home network that anyone on the internet can knock on. That’s why “how do I open my Minecraft port” is really two questions wearing one hat — the easy half (set `server-port` and forward 25565 on your router) and the half people skip (you’ve now *exposed* your home IP and a listening service to the entire internet, which invites connection attempts, scanning, and DDoS risk aimed at your home connection). The port number itself is trivial. The consequence of forwarding it is not. So the honest framing is: forwarding the Minecraft port works and is fine for a quick LAN-plus-friends session, but it turns your home router into a public game-server gateway with your real IP attached — and the reason hosted game servers exist is precisely to give you that open port on infrastructure built to be public (DDoS-protected, isolated from your home network, on a stable IP) instead of on the same connection your family uses. Opening the port is easy; deciding where to open it is the real decision.

Hold that thought. First, the mechanics.

How do I change the Minecraft port in server.properties?

Every Java Edition server ships with a `server.properties` file in its root folder. Open it in any plain-text editor and you’ll find a line like this:

“`properties

server-port=25565 server-ip= max-players=20 online-mode=true “`

To change the port, edit the number and save:

“`properties server-port=25566 “`

Restart the server, and it now listens on 25566 instead. That’s the entire change — one line.

Why would you bother? A few legitimate reasons:

• Running multiple servers on one machine. Two servers cannot both listen on 25565 at the same time — only one process can bind a given port. Give each its own number (25565, 25566, 25567…).
• Avoiding a port conflict. If another program already grabbed 25565, your server will fail to start with an “address already in use” error. Moving to a free port fixes it.
• A little obscurity. Running on a non-default port means automated scanners hunting for “anything on 25565” won’t trip over you quite as fast. It’s not security — it’s mild inconvenience for bots.

Leave `server-ip` blank unless you have a specific reason to bind to one network interface; an empty value tells the server to listen on all of them, which is what you usually want.

How do I port forward Minecraft on my router?

Inside your home, your PC has a local IP (something like `192.168.1.50`) that only exists on your network. The outside internet can’t see it. Your router holds a single public IP, and by default it doesn’t know which internal machine should receive an incoming Minecraft connection. Port forwarding is how you tell it: “anything arriving on port 25565, send it to this internal PC.”

Here’s the process. Specifics vary by router brand, but the steps are universal:

1. Find your PC’s local IP. On Windows, open Command Prompt and run `ipconfig`; look for the IPv4 address. On macOS or Linux, run `ifconfig` or `ip addr`. Note it down (e.g., `192.168.1.50`).
2. Reserve that IP (recommended). In your router’s DHCP settings, assign a static/reserved IP to your PC so it doesn’t change after a reboot and break the forward.
3. Log into your router. Type its gateway address (often `192.168.0.1` or `192.168.1.1`) into a browser and sign in.
4. Find the Port Forwarding section. It may live under “NAT,” “Virtual Server,” “Gaming,” or “Advanced.”
5. Create the rule. Enter the values below.

Field	Value
Service / rule name	`Minecraft`
External port	`25565`
Internal port	`25565`
Internal IP	your PC’s local IP (e.g., `192.168.1.50`)
Protocol	`TCP` (Java)

1. Save and apply. Some routers require a reboot for the rule to take effect.

For Bedrock Edition, forward port 19132 using UDP instead.

Don’t forget the firewall

Your router now forwards the traffic, but your PC’s own firewall might still block it. On Windows, you’ll need an inbound (and ideally outbound) rule allowing the port:

“`powershell

New-NetFirewallRule -DisplayName “Minecraft Java” -Direction Inbound -Protocol TCP -LocalPort 25565 -Action Allow “`

A blocked firewall is the single most common reason a “correctly” forwarded port still refuses connections. Allow the port in and out before you start blaming your router.

How do players connect to my Minecraft server?

Players connect using the format `host:port` — your public address, a colon, and the port number. For example:

“` 203.0.113.45:25565 “`

But here’s a small convenience: Minecraft assumes 25565 by default. So if you kept the default port, players can simply enter:

“` 203.0.113.45 “`

…and the client fills in `:25565` automatically. If you changed the port to 25566, players must include it: `203.0.113.45:25566`. No `:port`, no connection.

A quick reference for who needs what:

Connection method	What players type
Same LAN, default port	`192.168.1.50`
Over internet, default port	`your-public-ip`
Over internet, custom port	`your-public-ip:25566`
Java vs Bedrock	Bedrock often asks for IP and port in separate fields

If you’ve got a domain name pointed at your server, players use that instead of the raw IP — but the port rules are identical.

How do I run multiple Minecraft servers on one machine?

This is the most common reason people touch the port at all. You want a survival world *and* a creative world running side by side. The rule is simple: each server needs its own unique port.

Server	`server-port=`	Players connect to
Survival	`25565`	`your-ip` (default, port optional)
Creative	`25566`	`your-ip:25566`
Modded	`25567`	`your-ip:25567`

For each one, you’ll need to:

1. Set a unique `server-port=` in that server’s `server.properties`.
2. Add a matching port forward rule on your router (25566 → your PC, 25567 → your PC, and so on).
3. Open each port in your firewall.

Three servers, three doors. Forget to forward one, and that world simply won’t be reachable from outside even though it’s running perfectly fine locally.

Is port forwarding for Minecraft safe? The security angle nobody mentions

Now the half people skip. When you port-forward 25565 from your home router, you have done two things at once:

1. Exposed your real home IP address to everyone who connects — and to everyone who scans. Your friends now see it. So do automated bots that constantly sweep the internet looking for open ports and listening services.
2. Put a listening service on the public internet running on the same connection your household uses for everything else.

The practical risks:

• Scanning and probing. Open ports get found fast. A listening Minecraft server will start logging connection attempts from addresses you’ve never heard of within hours.
• DDoS targeting. Once someone knows your home IP, a grudge from an in-game dispute can become a flood of junk traffic aimed at your connection — knocking not just the server offline, but your entire household’s internet.
• Surface area. Any listening service is a potential target. Keeping software patched matters more once it’s exposed.

None of this means port forwarding is *wrong*. For a quick LAN-plus-friends weekend session, it’s perfectly reasonable. But it’s worth saying plainly: you’ve turned your home router into a public game-server gateway with your real IP attached. That’s a meaningful change to your home network’s exposure, and it deserves a moment of thought before you do it.

The cleaner alternative is to open the port somewhere built to be public in the first place.

---

Open 25565 where it belongs — with DarazHost

DarazHost game-ready VPS and dedicated servers give your Minecraft server its port on infrastructure built to be public. The port is open and reachable without exposing your home IP, with DDoS protection, a stable address, and always-on uptime. It’s the right place to open 25565 — full control over `server.properties`, your own isolated environment separate from your family’s connection, and 24/7 support when something needs a second pair of eyes. The friends-connect experience stays identical; what changes is that the door opens on hardware designed to have doors knocked on, not on the same router your household depends on.

---

Bedrock vs Java: which Minecraft port do I use?

The two editions use different ports *and* different protocols, which is the most common source of “I forwarded the port and it still doesn’t work” confusion.

Edition	Default port	Protocol	Notes
Java	`25565`	TCP	Port can be omitted by clients if default
Bedrock (Win/console/mobile)	`19132`	UDP	Also commonly forwards `19133` for IPv6

If you forward 25565/TCP but you’re running a Bedrock server, nothing will connect — you’ve opened the wrong door with the wrong key. Match the edition to the port to the protocol, all three, every time.

Frequently asked questions

What is the default port for a Minecraft server? The default Minecraft port is 25565 using TCP for Java Edition. Bedrock Edition uses 19132 over UDP. If you keep the Java default, players can connect using just your IP or domain without typing the port.

Do I have to port forward to play Minecraft with friends? Only if friends are joining over the internet to a server you host at home. On the same local network, no forwarding is needed — players use your PC’s local IP. For internet play without forwarding, options include LAN-tunneling tools or a hosted server that has the port open by default.

Why is my Minecraft port not working after I forwarded it? The usual culprits, in order: a firewall on the server PC blocking the port, the forward rule pointing at a local IP that changed after a reboot, the wrong protocol (UDP vs TCP), or the server not actually running. Confirm the server is listening, reserve a static local IP, and allow the port in your firewall.

Can I run two Minecraft servers on the same computer? Yes. Each server needs a unique `server-port=` value in its `server.properties` (for example 25565 and 25566), a matching port-forward rule, and a firewall exception. Players reach the non-default server by appending `:port` to your address.

Is it dangerous to forward port 25565 from my home network? It carries real trade-offs. Forwarding exposes your home IP and puts a listening service on the public internet, which invites scanning and creates DDoS risk to your whole connection. It’s fine for casual sessions, but a hosted server keeps the public-facing port off your home network entirely.

Connecting it all back

The Minecraft port question turns out to be two questions. The first — *what port and how do I open it* — is genuinely easy: 25565 for Java, 19132 for Bedrock, `server-port=` to change it, forward it on the router, allow it in the firewall. The second — *where should I open it* — is the one that actually matters. Opening the port is trivial; deciding whether to open it on your home connection or on infrastructure built to be public is the real decision.

If you want the bigger picture of how ports, IPs, and DNS work together to get a player from “click join” to “spawned in your world,” start with our pillar guide: Networking & DNS for Hosting: The Complete Guide to How Visitors Reach Your Server.