World uploads are not available yet

What Files can take

Upload and read on the Files tab take one file at a time, and each file is capped at 256 KB (262,144 bytes). A larger upload is refused, and a larger file cannot be opened or downloaded. mkdir creates an empty folder; it does not accept a folder tree.

There is no multi-select, no SFTP endpoint, no rsync target, and no object-storage bucket on the instance. Nothing in the panel moves a world directory.

Why a world does not fit

A world is region files, level data, player data, and often datapacks. Region files alone are routinely larger than 256 KB, and there are hundreds of them. Unpacking an archive does not help: the archive itself has to reach the node first, and the panel has no unpack step.

World-scale transfer is not available yet. Support cannot import a world either: there is no admin upload, no importer, and no node-side fetch, so the limit is the surface, not a permission you can request.

What still works

A world that already exists on the instance stays on the node volume under the pack’s data path. Switching titles keeps that volume. Backup and restore work on the whole data directory, and Restore latest clears the data directory before unpacking the newest node-local archive.

Small single files still move: a server.properties edit, a whitelist, a short config, a plugin under 256 KB. Stop the guest first so a live process is not writing over the file you replace.

1. Check the size of each file you would need to move. Anything above 256 KB cannot go through Files.
2. Stop the instance from the header and confirm observed power is stopped before editing a config.
3. Create a backup and wait until On-disk archives lists the tarball.
4. Upload one small file at a time, then start the instance and read Console.
5. Keep the only copy of a world on the host that already has it, and do not destroy the instance.

Rolling back instead

If a small edit goes wrong, Restore latest returns the newest listed archive and clears the data directory first, so files added after that archive do not survive. That is the supported rollback for a world, and it is node-local.

When a bulk transfer path ships, this article will name it. Until then no page promises SFTP, rsync, folder upload, or object storage for an instance.