In Control panel / Updated October 17, 2026

The file manager is your server's disk in a browser window: create folders, upload files, open and edit text files, and save. Those are the verbs, and this page walks them as numbered steps with the honest limits attached.

Before the steps

Log in at panel.carbonhosting.xyz, open your server's page, and open the Files tab. Two habits before anything moves: check the folder path before an upload lands, because a file lives where you put it; and remember that your server reads many of its files at startup, so some edits apply when the server restarts rather than right away. The steps below walk the loop in the order you use it.

Step 1: create a folder

Use the file manager's folder control and give the new folder its name. The recipe you reach for first is the plugins folder: a fresh install may not have one yet, plugin jars go inside it, and no plugin install works without it. The complete plugin routine around that folder, version fit, upload, restart, and the console check, is linked below and this page leaves the steps entirely to it.

Step 2: upload files

Use the upload control and pick your file. The most common upload is a plugin jar into the plugins folder, and jar uploads carry one standing rule: upload the jar as it is, never unzipped. A config file goes into whatever folder it belongs to, and after a plugin's first run its own files show up in its own folder; most plugins write their config there on first run, and that is the file you edit in the step below.

Step 3: open and edit a text file

Open the file from the file manager and make your edit. The textbook case is server.properties at your server's file root: it is plain text, its lines carry a setting name, an equals sign, and a value, and the edit is changing the value of the setting you came for.

One worked example of that exact edit already exists: the lag article drops the view-distance value a step or two, saves, and restarts: Why is your Minecraft server lagging: causes you can control . The same edit and save shape works for the other settings that file carries.

Step 4: save

Save the file. Saving is the moment an edit becomes the file: until you save, the disk still holds the old version, and the server does not know an edit exists. Small edit or large one: save every time, before you move on to the next step.

Step 5: restart when a change needs it

Changes the server reads at startup apply on the next restart, and the restart control sits on your server's page. Not every file change needs one; the plugin article says when its own loop does. Pair a restart with a console read, so the startup confirms what the saved file actually did.

Archives, in the honest hedge form

One conditional deserves its own shape, because it is conditional on purpose: if your panel's file manager can archive a folder to a zip, archive it and download the archive; otherwise move the folder file by file. The mirror image runs the other way: if the file manager can extract an archive, extract it where it lands; otherwise send the files as they are. These are "can" sentences, not promises, and this page claims nothing stronger than they say.

The honest limits

• No upload size numbers: no measured upload limit exists in the published record, so this page prints no number. An upload that refuses for no visible reason is a ticket question, not a number to guess.
• No transfer method outside the panel: nothing about SFTP or any other transfer route is described here; the file manager is the transfer story tonight.
• The zip verbs stay hedge-shaped: "can archive" and "can extract", in the same form the migration article already uses, and never stated as confirmed behavior.

Related reading: How to install plugins on your Minecraft server , Moving your Minecraft world to a new server without losing data .

If an upload, an edit, or a save behaves in a way this page does not describe: open a ticket from your account, say which file and which step, and a person checks it with you.