How to Make a Copy of an Aternos Server (Full Backup & Transfer Guide)

If you've spent hours building a Minecraft world on Aternos, protecting that work matters. Whether you're switching to a new server, creating a test environment, or just want a safety net before a major update, knowing how to copy your Aternos server correctly saves you from losing everything. Here's exactly how it works — and what to watch for depending on your setup.

What "Copying" an Aternos Server Actually Means

When people talk about copying an Aternos server, they usually mean one of two things:

• Duplicating the server within Aternos — creating a second server with the same world, settings, and plugins
• Downloading the server files locally — exporting your world data to your own computer for backup or migration

Aternos doesn't have a one-click "duplicate server" button like some paid hosting platforms do. Instead, the process involves downloading your server's files and then either uploading them to a new Aternos server or transferring them to another hosting provider entirely.

Step-by-Step: How to Back Up Your Aternos Server

1. Access Your Server Files

Log in to your Aternos account and navigate to your server dashboard. From there, go to the Files section — this is where Aternos gives you access to the directory structure of your server.

Inside the file manager, you'll find folders like:

• world — your main overworld data
• world_nether — Nether dimension data
• world_the_end — End dimension data
• plugins or mods — depending on your server type
• server.properties — your core configuration file

2. Download the World Folder(s)

Select the world folders you want to copy. Aternos allows you to download individual files or folders directly from the file manager. For a full copy, you'll want all three world folders plus your configuration files.

⬇️ Download these at minimum:

• world
• world_nether
• world_the_end
• server.properties
• Any plugins or config folders relevant to your setup

The download will come as a .zip file. Keep it somewhere safe — this is your backup.

3. Create a New Aternos Server

If your goal is to duplicate the server within Aternos, create a fresh server from your Aternos dashboard. Make sure you select the same game version and server type (Vanilla, Paper, Spigot, Forge, Fabric, etc.) as your original. Mismatching versions is the most common reason copied worlds fail to load correctly.

4. Upload the Files to the New Server

Once the new server is created, go to its Files section and upload your downloaded world folders. Aternos supports file uploads through the file manager interface. Replace the default empty world folders with your copied ones.

After uploading:

• Make sure folder names match exactly (world, not World or world_copy)
• Re-upload your server.properties if you want identical settings
• Reinstall any plugins manually — plugin configuration files can be uploaded, but the plugins themselves need to be added through the Aternos plugin installer

Key Variables That Affect How Well the Copy Works

Not every copy goes smoothly, and the outcome depends heavily on a few factors:

Copying to a Different Hosting Provider

If you're moving your Aternos world to a paid host like Apex, Bisect, or a self-hosted setup, the same downloaded .zip files apply. Most Minecraft hosting panels (Multicraft, Pterodactyl, etc.) have their own file managers where you can upload the extracted world folders directly.

The main difference is that paid hosts often give you SFTP access, which is faster and more reliable than browser-based uploads for large worlds. If your world is several gigabytes, this matters.

🖥️ For self-hosted servers, you'd drop the world folders into the same directory as your server.jar file.

What Can Go Wrong (And How to Avoid It)

World corruption on upload — Usually caused by uploading while the server is running. Always make sure your Aternos server is fully stopped before uploading files.

Blank world loads instead of your copy — Typically a naming mismatch. Check server.properties for the level-name setting and make sure it matches your uploaded folder name exactly.

Plugins not working after copy — Plugin .jar files aren't included in world downloads. You need to reinstall them through Aternos's plugin manager and then upload your saved configuration files separately.

Missing chunks or biome errors — This usually points to a version mismatch between the original and new server. Double-check both servers run the same Minecraft version and build.

The Part That Depends on Your Situation

The technical process is consistent — download, create, upload, configure. But how straightforward that is in practice depends on your world's size, how many plugins you're running, whether you're staying on Aternos or switching platforms, and how comfortable you are navigating server file structures. A small vanilla survival world copies in minutes. A heavily modded server with custom data packs and a large map is a different project entirely. Your specific setup is what determines which edge cases apply to you.