Create a Free Minecraft Server with Friends

To play together, your group needs a compatible Minecraft edition, a reachable server and someone responsible for managing the world. The owner creates the server and shares its game address. Friends join through their own Minecraft accounts. Free server hosting covers the selected hosting plan; it does not provide a copy of Minecraft, a Microsoft account or a console multiplayer subscription.

Before creating anything, agree on five details: Java or Bedrock, the exact game version, a new or existing world, any required extensions and who will look after backups. Also decide whether a server that sleeps when inactive suits your sessions. A world with farms that must run continuously has different operating requirements from a weekly evening with friends.

This guide takes you through planning, creation, joining, private access and the next update. The resource and operating limits shown above and in the configurator are the current plan facts. They are not a promise that every world can support a particular number of players. Start with the simplest setup that meets your group's needs, then add features after you have a working connection.

Java Edition and Bedrock Edition use different protocols. Both displaying the name Minecraft does not make them interchangeable. Windows can run either edition, so ask which one a friend actually launches. Android and iOS use Bedrock; ordinary desktop play on macOS and Linux uses Java. Consoles generally use Bedrock, with additional restrictions on selecting external servers.

Geyser translates supported Bedrock connections into a Java server. Floodgate provides an authentication path for Bedrock accounts without requiring an additional Java licence. Neither supplies the player's Bedrock game access. A native Bedrock server does not offer the reverse arrangement for ordinary Java clients.

Use the Geyser setup documentation when planning crossplay. Substantial Java modpacks with custom client content are a separate compatibility problem: a Bedrock client does not become that modpack's Java client through Geyser. Confirm the edition and displayed version of every participant before choosing the server software.

A LAN world is useful when everyone shares the same local network. The person hosting it normally needs to keep that world open. Friends in another household cannot reach it merely because it appears in your own LAN list. A hosted server runs outside your home network and provides an address that participants can use from their own connections.

Realms is another option for private groups. Its supported features and limitations depend on the Minecraft edition and current offer. It is not a substitute for every independently configurable Java modloader or plugin server. If a named pack matters to your group, compare its requirements before choosing a service.

Separate the price of hosting from other costs. Friends still need game access and any platform requirements for online play. Avoid promising permanent activity if your selected plan sleeps when unused. A sleeping world does not process normal game ticks, so a farm will not continue producing simply because its files remain stored.

Record the edition, game version, mode, world source and administrator. A useful starting plan is: Java, one agreed release, Survival, a new world and no mods initially. For a modpack, add its full name and release identifier. Two packs built for the same Minecraft version can still contain incompatible files.

Keep the first installation small. Importing a world, changing loaders and adding many extensions in one operation makes failures harder to diagnose. A working clean server provides a comparison point. Add one intentional change at a time and check that the original connection still works afterwards.

Choose a location appropriate for the group where the available selection allows it. A location close to the owner does not guarantee the same connection quality for a friend on another continent. Agree on session times and who starts the server if the plan uses an inactivity sleep mode.

The hosting owner needs a management account. Other players normally need their game account and the game address, not the owner's dashboard password. If another person should help administer the server, use the available permissions rather than sharing a primary login in your group chat. Keep responsibility for changes and restores clear from the beginning.

Open the configurator on this page and check the selected edition. The free starting option is selected, but available software and resources follow the actual configuration. Review the current operating information before completing the setup. A heavier modpack is not necessary for a simple Survival session.

1. Select the edition from your world plan.
2. Choose supported software suitable for your extensions.
3. Match the server game version to the clients.
4. Create or sign into the hosting account and finish the setup.
5. Open the resulting server in the dashboard and start it through the provided controls.
6. Watch the console until the game process finishes starting.
7. Copy the connection details shown for this server.

Finishing the setup form and starting the game process are separate checks. A first world may need generation work. Repeatedly pressing start does not make that work faster. If the process exits or the console reports an error, resolve that before sending the address to the group.

Keep the assigned game port. Replacing it with a familiar tutorial default can break connectivity while the server itself appears to run normally. The hosting allocation and the application's listening port must agree. Use the dashboard information as the reference for your actual connection, rather than a number remembered from another server.

Launch Java Edition with the version supported by the server. For a modpack, launch its exact client profile. An ordinary Vanilla profile cannot replace a pack that requires client mods. Open Multiplayer, choose Add Server and enter any display name you want for your own server list.

Copy the game address into the address field. When the supplied Java address includes a port, retain the address:port form. Do not include https://, a dashboard URL or your computer's private Wi-Fi address. A Java hostname may resolve a port through an SRV record; that does not mean every connection can safely omit its provided port.

Connect and inspect the world. Check the expected spawn, game mode and, if relevant, a recognisable imported building. Have a friend try the same details from another internet connection. That second client is a stronger check than the server owner successfully opening the dashboard.

Minecraft explains the basic menus in How to play on a Minecraft server. If the multiplayer menu is unavailable, inspect the affected account's multiplayer permissions. Changing a server port cannot unlock a restricted game account. Compare the exact message and client profile with those of a player who can connect.

On a Bedrock platform that allows external server entry, open Play and the server list, then use the option to add a server. Enter the host and assigned Bedrock port in their separate fields. The display name is just a local label. A Java port is not an interchangeable substitute for the Bedrock listener.

For a mixed Java and Bedrock setup, give Bedrock players the Geyser connection details. Test this path separately from Java. A successful Java login does not prove that the Bedrock UDP listener is reachable. If a private access list is enabled, confirm the identity used by the Bedrock authentication path.

Xbox, PlayStation and Switch may not provide ordinary arbitrary server entry. Check the actual external connection method on those devices before building your plan around them. Community helpers depend on platform, network and software version; they are not an extra guaranteed hosting feature. See the Geyser console documentation for the documented limitations.

After connecting, test gameplay that matters to your group, including inventories and extension menus. A Java world remains a Java world when Bedrock users enter through Geyser. Treat custom client mods as a separate requirement and avoid promising that every Java feature will behave identically on every device.

An address is not a password. Anyone who learns it can attempt a connection. For a private Java group, add the intended accounts to a whitelist and keep normal account authentication enabled. Add your own account before switching the list on so you do not accidentally exclude yourself.

The basic Java console commands look like this. Replace PlayerName with the real account name. In the server console the leading slash is normally omitted; an in-game command requires appropriate permission.

whitelist add PlayerName
whitelist on
whitelist list

Test with an allowed friend and, where available, a separate account that should not enter. A configuration display saying the whitelist is active does not replace a real join test. Native Bedrock and Floodgate setups use their own identity and access-management details. Follow the method for the software actually running.

Do not give everyone operator status just to play Survival. Operator permissions allow significant changes. Remove temporary privileges after setup and use more specific permissions where supported. Keep hosting management, in-game permissions and Microsoft account access separate: an in-game administrator does not need to know the hosting owner's password.

Agree on difficulty, game mode and a few practical rules before the first long session. Decide whether PvP is allowed, who may use Creative and how the group handles damage or lost items. Unannounced changes can affect players who are offline, so tell the group when rules change.

Back up an existing world before uploading it and stop the destination server before replacing files. Check the edition and supported version. Renaming a Java archive does not convert it into a native Bedrock world. Opening a newer world with older software is not a reliable downgrade procedure.

Inspect the actual world directory and selected world setting. If a new landscape appears after importing, check whether the imported world is inactive or nested one directory too deeply. Do not immediately delete the original copy. The files may be intact but outside the path the server uses.

After import, inspect spawn, a known building, player inventory and relevant dimensions. Give backups names that identify the world, date and reason. Keep a copy outside the active installation. A backup that cannot be associated with a particular software and world state is much harder to restore when something goes wrong.

Player capacity is not determined by RAM alone. World generation, view distance, simulation distance, entities, loaded areas and extensions all influence demand. A promise that one small free server always supports a fixed number of friends would ignore those differences.

Start with moderate distances and observe your normal activity. Delayed block interactions, mobs pausing and several players being moved back together can indicate server-side trouble. Check the console and resource display at the same time. If only one player's picture stutters, their graphics, device or connection may be responsible.

Memory pressure and slow tick processing are different problems. Adding memory does not automatically fix a large Redstone machine or excessive chunk activity. Change one setting, reproduce the same situation and compare. Avoid buying resources based on a symptom you have not yet distinguished from a client problem.

If the free server sleeps while inactive, ordinary world processing stops during that time. Choose an operating option appropriate for a project that needs continuous activity. Artificial idle connections do not replace that decision. Check current plan conditions and available resources before expanding a small shared world into a much more demanding project.

Ask for edition, exact version, copied address and the complete error message. Note the time of the attempt and compare the matching console entry. If nobody can connect, begin with the server. If one player is affected, compare that player's profile and connection with a working client.

Do not enable general offline mode as a quick solution to authentication problems. That changes account verification and may affect how player data is associated with identities. Resolve the actual profile, account or configured authentication issue instead. Keep one known working client available while investigating so each change can be compared.

Back up before changing Minecraft versions, loaders or important extensions. Include player data, dimensions and required configuration, not only the buildings. A modded world's recoverable state also needs the matching mods and versions. Retain that information alongside the saved files.

Coordinate updates with the group. One client moving to a new release while the server remains on the old one may prevent joining. First confirm that the server software and extensions support the new version. Then update deliberately and test one client before asking everyone to change.

For rollback, use the backup from before the update and the previous compatible software. Do not simply launch an already converted world with the old version. Restore the known complete state, verify the world and check a player login. A backup is useful evidence only when it can produce a functioning server again.

Before the next session, share the agreed version, saved game address and whether an update or restore is underway. Name the person who will start the server if needed. Clear operating information prevents friends from joining the wrong profile or beginning a replacement world while the intended world is being restored.

Your setup is ready when every required device path has been tested, the intended players can join, private access works and a recoverable backup exists. Restart once and confirm the same world loads again. A first login alone does not establish that the world selection will survive the next start.

• Minecraft multiplayer server basics explains joining from the game.
• Geyser setup describes a supported Java and Bedrock arrangement.
• Floodgate setup explains the Bedrock authentication path.
• Console connection limitations covers external server access on consoles.

Use the related topics below for device and network questions. When configuring the server, choose the edition and software you have already checked with your friends. The useful result is a shared world your group can join, protect and restore again next week.