Leaving Foxcore and your data

Your files are yours, but the export path is narrow

The terms say files on an instance are yours. There is no export fee and no proprietary world format. The panel does not yet have a way to hand you a whole world.

Files reads one file at a time and refuses anything larger than 256 KB (262,144 bytes). Backups stay on the node and are not downloadable. There is no folder download, no SFTP, no rsync, and no object-storage bucket.

What you can take today

Individual files of 256 KB or less: a config, a whitelist, a small plugin, a player list. Download each one from Files while the node session is ready and check that it opened.

A world directory, a modpack, and a backup tarball cannot be exported. That is the limit of the surface today, not a fee or a permission support can lift for you.

Before you cancel or destroy

Work out what you would lose. If the answer is a world you cannot rebuild, do not cancel and do not destroy the instance yet; there is no path that moves it out for you.

Cancelling Pro stops future renewal. It does not delete the instance or its files. Destroying the instance is a separate action, and node-local files and backups are removed when the destroy job finishes on the node.

1. List the files you need and check each one is 256 KB or less.
2. Download those single files through Files while the session is ready.
3. Open each download and check it is complete.
4. Accept that anything larger stays on the node before you cancel.
5. Cancel the subscription, then destroy the instance separately.

Cancellation and deletion are separate

That separation is deliberate: a billing mistake should not silently erase a world. Do whatever export the surface allows first, then cancel, then destroy.

If a file operation fails, contact support with the instance id. Support can look at the job and the node report; staff cannot hand you a copy of the volume.