> ## Documentation Index
> Fetch the complete documentation index at: https://help.freakhosting.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How to Upload a Custom Minecraft World

> Upload custom worlds to your Minecraft server by transferring singleplayer saves or community maps. Follow the workflow for activating uploaded world files.

## Migration: Bringing Your World to the Cloud

Whether you have architected a masterpiece within a singleplayer environment or downloaded a complex adventure map from a community repository, migrating your world to a dedicated server is the most effective way to share your progress. This procedure involves more than a simple file transfer; you must correctly synchronize the metadata, dimension directories, and configuration variables to ensure a stable deployment. This guide walk you through the professional technical workflow for world migration on the FREAKHOSTING platform.

<CardGroup cols={2}>
  <Card title="Difficulty" icon="gauge-low">
    Intermediate
  </Card>

  <Card title="Time" icon="clock">
    8 Minutes
  </Card>
</CardGroup>

***

## Technical Preparation: The ZIP Protocol

Minecraft worlds are composed of thousands of minute files situated within the `region` and `playerdata` subdirectories. Attempting to upload these individually via a standard browser or SFTP will lead to significant latency and an increased probability of data corruption.

* **Mandatory Step:** You **must** compress your world folder into a standardized **.ZIP** archive before initiating the transfer.
* **Verification:** Ensure that the internal directory structure starts immediately with files like `level.dat` and the `region/` folder, rather than being nested within redundant subdirectories.

***

## Migration Workflow

Follow these steps to deploy your custom world to your FREAKHOSTING instance.

<Steps>
  <Step title="Initialize Maintenance">
    Log in to the [Game Panel](https://games.freakhosting.com) and **Stop** your server. World files are actively locked by the Java process and cannot be modified while the engine is initialized.
  </Step>

  <Step title="Purge Legacy Data">
    Navigate to the **Files** tab. Delete the existing `world`, `world_nether`, and `world_the_end` directories. (We recommend generating a [Full Backup](/portals/game-panel/how-to-create-and-restore-backups) before this destructive action).
  </Step>

  <Step title="Upload and Extract">
    Upload your compressed ZIP archive directly into the server's root directory. Once the transfer concludes, right-click the archive and select **Unarchive**.
  </Step>

  <Step title="Standardize Naming">
    Rename the extracted folder to **`world`** or update the `level-name` variable in your `server.properties` to match your folder name precisely.
  </Step>
</Steps>

***

## Dimension Mapping: Paper & Spigot

If you are migrating a singleplayer world to a professional server build (e.g., Paper or Purpur), you will notice a technical discrepancy in how dimensions are stored.

<Tabs>
  <Tab title="Singleplayer (Vanilla)">
    All three dimensions (Overworld, Nether, and End) are stored within a single parent directory. The Nether resides in `DIM-1` and the End in `DIM1`.
  </Tab>

  <Tab title="Multiplayer (Paper/Spigot)">
    The engine automatically detects the `DIM` folders upon the first boot and splits them into distinct top-level directories: `world_nether` and `world_the_end`. This is standard behavior and is required for multi-threaded performance optimizations.
  </Tab>
</Tabs>

***

## Troubleshooting Connectivity

<AccordionGroup>
  <Accordion title="Positioning & Spawn Glitches">
    If you materialize within the ocean or a void upon joining, it is likely that your player coordinate metadata was not correctly synchronized. use the server console to execute:
    `/tp @a 0 100 0`
    This will teleport all active players to the map's origin, allowing you to manually navigate to your builds.
  </Accordion>

  <Accordion title="Version Mismatch Errors">
    Ensure that the Minecraft version used to create the world matches the version running on your server. While newer engines can often "Upgrade" older world formats, attempting to load a 1.21 world on a 1.12.2 server will lead to immediate world corruption and crashes.
  </Accordion>
</AccordionGroup>

***

<Note>
  ### Need Extra Help?

  If you encounter any issues, our support team is ready to assist:

  * **Live Chat:** Quick assistance via our website.
  * **Support Ticket:** [Open a Ticket](https://freakhosting.com/clientarea/submitticket.php)
  * **Discord:** [Join our Community](https://discord.gg/freakhosting)
  * **Email:** [support@freakhosting.com](mailto:support@freakhosting.com)
</Note>

<Tip>
  ### Save on Your Hosting

  Ready to get a new server? Use code **KB20** at checkout for **20% off** your first month!
</Tip>

***

<div align="center">
  **Last Updated:** January 2026 | **Minecraft:** World successfully migrated.
</div>