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

# Persistent Servers

> Create and manage a server that keeps its worlds, configuration, and plugins.

A persistent server is a Minecraft server or proxy that runs on one serverhost and keeps its files when it restarts or is disabled. Use one for a survival world, build server, or anything else that must keep its local data.

<Info>
  If you want multiple interchangeable servers or automatic scaling, use [Server Groups](/docs/en/manual/setup/server-groups) instead.
</Info>

## Before you start

Connect at least one serverhost and make sure it has enough memory for your server.

<Warning>
  SimpleCloud does not move or back up a persistent server's files. Back up worlds and other important files yourself.
</Warning>

## Create a persistent server

<Steps>
  <Step title="Open Persistent Servers">
    In the dashboard, open **Persistent Servers** and click **Add Server**.
  </Step>

  <Step title="Choose the server">
    Enter a name, choose **Server** or **Proxy**, and select the serverhost that will run it. Names may contain up to 100 ASCII letters, digits, underscores, and hyphens (`[A-Za-z0-9_-]`) and are unique within the network case-insensitively — `Survival-1` and `survival-1` count as the same name.
  </Step>

  <Step title="Choose the software">
    Select the server software, Minecraft version, and Java version.

    If the software is not listed, choose **Custom** and fill in the required fields.
  </Step>

  <Step title="Set resources">
    Choose the memory and maximum player count. Proxies also require a starting port.
  </Step>

  <Step title="Create the server">
    Review the configuration and click **Create Server**. SimpleCloud starts it automatically unless you disabled **Activate on creation**.

    <Check>
      Open the server and follow its first startup in the console.
    </Check>
  </Step>
</Steps>

## Start and manage the server

Open the server in the dashboard to view its status, console, and files. Use its actions menu to enable, disable, or restart it.

* **Enable** tells SimpleCloud to keep the server running. If it stops, SimpleCloud starts it again.
* **Disable** stops the server and leaves it stopped until you enable it again.
* **Restart** stops and starts the server without deleting its files.

You can also enable or disable the server with the **Active** switch in **Settings**. Save any other settings you change. If a change affects how the server starts, restart it to apply the new configuration.

Use the main **Settings** page for resources and the **Blueprint** page for software and startup configuration. The **Deployment** page changes the assigned serverhost; follow the migration steps below before using it.

Use the **Files** tab to manage its world, configuration, and plugins. These files stay in place when you restart or disable the server.

## Move the server to another serverhost

Changing the assigned serverhost does not move the server's files. Back up and copy them before starting the server on the new host.

<Steps>
  <Step title="Disable the server">
    Disable the persistent server and wait for it to stop.
  </Step>

  <Step title="Copy its files">
    Copy the complete `running/persistent/<server-name>` directory from the old serverhost to the same location on the new serverhost.
  </Step>

  <Step title="Change the serverhost">
    Open **Settings** > **Deployment**, select the new serverhost, and confirm the change.
  </Step>

  <Step title="Enable and verify">
    Enable the server, join it, and confirm that its worlds and configuration are present before removing the old copy.
  </Step>
</Steps>

<Warning>
  Starting the server on the new serverhost before copying its files can create a new, empty server directory.
</Warning>

## Delete a persistent server

Open **Settings** > **Danger Zone** and follow the deletion prompts. SimpleCloud stops the server if necessary and removes its configuration and any associated blueprint. The server files remain on the serverhost.

## Troubleshooting

<AccordionGroup>
  <Accordion title="The server does not start">
    Confirm that the server is enabled, its serverhost is connected, and the host has enough free memory. Then check the server's console for the error.
  </Accordion>

  <Accordion title="The world is empty after changing serverhosts">
    Disable the server. Copy its `running/persistent/<server-name>` directory from the old serverhost to the new one, then enable it and check the world again.
  </Accordion>

  <Accordion title="A setting did not take effect">
    Save the change and restart the server. Check its console if the problem continues.
  </Accordion>
</AccordionGroup>