How to Join a LAN Server in Minecraft: Everything You Need to Know
Minecraft's LAN (Local Area Network) feature is one of the simplest ways to play with friends — no dedicated server required, no hosting fees, no complicated setup. But "simple" doesn't always mean obvious, especially when network configurations, device differences, and Minecraft editions enter the picture. Here's a clear breakdown of how LAN servers work and what affects whether joining one goes smoothly.
What Is a LAN Server in Minecraft?
A LAN server is a temporary multiplayer session hosted directly from one player's game and shared across a local network — typically a home Wi-Fi network or wired router. The host doesn't run separate server software. Instead, they open their single-player world to the network, and other players on the same network can join.
This is different from a dedicated server, which runs independently and is accessible over the internet. LAN play is local-only by default, meaning everyone needs to be connected to the same router or network switch.
The Basic Process: How to Host and Join
On the Host's Side (Java Edition)
- Open a single-player world in Minecraft: Java Edition
- Press Esc to open the pause menu
- Select "Open to LAN"
- Choose your game mode and whether to allow cheats
- Click "Start LAN World"
Minecraft will display a port number (e.g., Port 25565 or a randomly assigned one). This port matters if players have trouble connecting manually.
On the Joining Player's Side (Java Edition)
- Launch Minecraft and go to Multiplayer
- The LAN world should appear automatically under "LAN Games"
- Click it and select Join Server
If the world doesn't appear automatically, the joining player can select Direct Connection and type the host's local IP address followed by the port number — formatted as 192.168.x.x:port.
Finding the Host's Local IP Address
On Windows: Open Command Prompt and type ipconfig. Look for the IPv4 Address under the active network adapter — usually something like 192.168.1.x.
On macOS: Go to System Settings → Network → select your active connection → the IP address is listed there.
Java Edition vs. Bedrock Edition: A Key Distinction 🖥️
The process differs meaningfully between Minecraft's two main versions.
| Feature | Java Edition | Bedrock Edition |
|---|---|---|
| LAN hosting method | Open to LAN via pause menu | Enabled automatically in multiplayer worlds |
| Auto-discovery | Usually automatic on same network | Usually automatic on same network |
| Cross-platform | Java-to-Java only | Cross-platform (PC, console, mobile) |
| Account required | Microsoft/Mojang account | Microsoft account |
| Manual IP entry | Supported | Supported via "Add Server" |
Bedrock Edition (used on Windows 10/11, consoles, and mobile) handles LAN slightly differently. Worlds with multiplayer enabled are visible to friends on the same network automatically, but the host's multiplayer settings and privacy settings in their Microsoft account can block visibility.
Common Reasons LAN Worlds Don't Appear
This is where most users hit friction. A LAN world failing to show up is almost always a network or software configuration issue, not a Minecraft bug.
Firewall blocking: Windows Firewall or third-party security software may block Minecraft's network traffic. Allowing Minecraft through the firewall — or temporarily disabling it to test — is a standard first diagnostic step.
Different network segments: If one player is on Wi-Fi and another is on a wired connection, they may be on different network subnets depending on router configuration. Both players need to be on the same subnet (same router, same network band in some cases).
VPN interference: If either player is running a VPN, it can route traffic away from the local network entirely. Disabling VPN for LAN play usually resolves this.
Mismatched Minecraft versions: Both players must be running the exact same version of Minecraft. A world opened on version 1.21 won't be visible to a client running 1.20.
Mods and modloaders: If the host is running mods (via Forge, Fabric, etc.), joining players typically need the same mods installed. Some mods also affect networking behavior.
Manual Connection as a Fallback
When auto-discovery fails, manual IP connection is reliable as long as both players are genuinely on the same network. The steps:
- Host confirms their local IPv4 address (not their public/external IP)
- Host notes the port number Minecraft assigned when opening to LAN
- Joining player selects Direct Connection in the Multiplayer menu
- Enters the address in format:
192.168.x.x:XXXXX
The port Minecraft assigns is displayed in chat when the host opens to LAN. If missed, it can sometimes be found by checking the host's router's connected devices or by reopening the world.
What Affects the LAN Experience Beyond Connectivity 🎮
Even after successfully connecting, several variables shape how the session actually plays:
- Host machine performance: The hosting computer runs both the game and the server logic. Slower hardware means more lag for all players.
- Network speed and latency: Even on a local network, wireless interference or an older router can introduce noticeable lag.
- Player count: LAN sessions aren't optimized for large groups. Performance degrades with more simultaneous players compared to a dedicated server.
- World complexity: Large builds, many active mobs, and loaded chunks all add strain to the host's system.
The Variable That Changes Everything
Whether LAN play works seamlessly — or requires manual troubleshooting — depends heavily on the specific combination of Minecraft edition, operating system, network configuration, and installed mods. A setup that works perfectly on one home network may need firewall adjustments on another. A Java Edition host with Fabric mods has a very different process than a Bedrock player on a console.
Understanding the mechanics above puts you in a position to diagnose what's actually happening in your specific environment — because the network sitting between those two machines is what determines the real answer.