Files and SFTP

You get full access to your server's files on every plan. You can use any server jar and edit any config. You can reach the files two ways: the file manager in the panel, and SFTP. Both only reach your own server's folder.

The file manager

Open Files. The path at the top shows where you are; press any part of it to go back up. Folders come first, then files, A to Z.

• Upload files or Upload a folder, or drop files and whole folders anywhere on the file card. A progress bar shows each upload. With Unzip .zip files after uploading ticked, a zip is unpacked where you drop it.
• New folder and New file.
• The more button on each row: Edit, Rename, Move, Copy, Download, Zip, Unzip here (for a .zip) and Delete. Delete asks first.
• Tick several rows to download, zip, move or delete them together.

The editor colours YAML, JSON and properties files and checks them for mistakes. You can drop files and folders to upload them, zip and unzip in place, search across all your files, and pin the files you use most to the top of the page. Each file keeps a history, so you can restore an earlier version.

Config files can be edited raw here. For the common settings there are friendlier forms in Settings.

The editor

Opening a text file opens the editor below the list, with line numbers and colours for YAML, JSON and .properties files.

• Problems show as you type, with the line: a YAML key used twice, tabs used to indent YAML, JSON that does not parse, a setting written the wrong way, or a server.properties value that is not allowed (for example pvp=yes, which must be true or false).
• Save (or Ctrl+S, Cmd+S on a Mac) saves. The server checks known config files again when you save and says if something is wrong.
• If someone or something else saved the file after you opened it, the panel does not overwrite their change. Copy your edits, reopen the file and save again.
• Changes to a config usually need a restart before the server notices.
• Files up to 5 MB open in the browser. Bigger files are uploaded and downloaded instead.
• If two people edit the same file, the second save is refused with "This file changed since you opened it", so nobody overwrites someone else's work by accident.
• Shortcut files (symbolic links) show in the list but are never opened or followed, by the file manager, SFTP, downloads or backups. You can delete them.
• Your server has a disk limit (about 5 GB on the free plan). We warn you at 80% and 95%. When it is full, saves and uploads are refused with "The server's disk is full" until you free some space.
• Deleting a file in the file manager is permanent. Make a backup first if you are unsure.
• Plugin jars go in through the Plugins page, which checks them first. The file manager will not put a .jar file straight into the plugins folder, by saving, uploading, moving or copying. Everything else in that folder, such as a plugin's config, is yours to edit.
• Your server can only reach the places on our allowed list (for example Discord, GitHub and Modrinth). If a plugin needs another site, ask for it in Settings under Internet access; we review each request. We add one named place at a time (like api.example.com), never a whole domain, a bare number address or a name inside our own network.

While the server sleeps

You can look at, download and back up a sleeping server's files at any time. Once we run more than one machine, a sleeping world is also kept in shared storage. Changing its files (saving a file, uploading, a plugin, a setting, a rollback) still works: the world stays on its machine for the next start and goes back to storage a few minutes after your last change. If that machine cannot be reached, the panel says so: start the server, then try again.

History of a file

Every time a file is saved from the panel, by your AI, by a setup or by a restore, we keep the earlier version. Press History in the editor to see each version with when and who, View it read only, or Restore it. Restoring keeps the version it replaced too, so you can go back again.

Search

The search box finds files by name across the whole server. Tick Also search inside files to find text inside them; results show the line. Press a result to open it.

SFTP

SFTP lets you use a program such as FileZilla or WinSCP.

1. Open Files and press SFTP details. It shows the host, the port and your username.
2. Press Make a password. The password is shown once; copy it. You can always make a new one, which replaces the old one. Or add an SSH public key instead.
3. Connect with your program.

Your login only sees your server's folder: / is the top of it, and .. never goes higher. Every login, failed login, upload, download, rename, new folder and delete is written to the audit log. Removing someone from your team, changing their password, or removing their key cuts that person's open connections at once. Everyone else stays connected, so adding a new team member never disconnects anyone.

One connection can have up to 64 files open at the same time; close some to open more.

What SFTP does not do: run commands, open a shell, forward ports or create shortcut files (links). After many wrong passwords from one place, that place waits a few minutes before it can try again. If someone tries many wrong passwords for your username, password sign-ins for it get slower, never refused, and a key still signs you in at once. Nobody is locked out for good. SFTP programs offer every key you have, one after another; a key that is not on your login is simply skipped and does not count as a wrong attempt.

Keys: add the public key line from your .pub file, for example one that starts with ssh-ed25519.

SFTP is also available to team members, within their role. See Team and roles.

Big uploads

For a whole world, use the world upload instead. It checks the file and unpacks it safely. See Worlds.

Each upload link is for one file of the size the panel saw when you picked it, and works for an hour. If the file changed size in between, pick it again. An upload you started but never finished is cleaned up after a while.

Downloads are made as a zip; the link goes only to the person who asked for it and works for an hour.

A zip you unpack at the top of your server folder, or straight into a world folder, that would replace a world is handled like a world upload: the server must be stopped, and we back up your worlds first. Unpacking somewhere deeper, such as a world's datapacks folder, works any time.

Files you upload by hand

Jar files you drop in by hand (over SFTP, or inside a zip you unpack) are not checked the way plugins installed from the panel are. We look at your plugins folder when the server starts, and we flag known bad files for review. We do not ban for this. Install from the panel's plugin page when you can, or use Upload a jar there, which scans the jar before placing it: see Plugins.