Upload and manage your files

Upload your code, unzip it, and browse and edit your files in the built-in code editor.

Everything your server runs lives on its Files tab. It works like a code editor: your folders on the left (the Explorer), and the file you have open on the right.

Find your way around

Click a folder in the Explorer to open it in place. Click it again to close it.
Click a file to open it on the right.
The home button at the top left goes back to the top folder.
Next to it you can see where new files, folders and uploads will go, for example in /commands. Click a folder to change it.
Search (or press Ctrl + K) finds files by name, including inside folders you haven’t opened.
The two view buttons switch between the Explorer with an editor, and the current folder shown as tiles.

The buttons

Button	What it does
Select	Tick several files or folders, then download or delete them together
New file	Makes an empty file where you are
New folder	Makes a folder where you are
Upload files	Uploads files from your computer
Upload folder	Uploads a whole folder, keeping the folders inside it
Download	Downloads the selected file
Delete	Deletes what’s selected
Refresh	Reloads the list

Hover over a button to see its name. You can also drag files from your computer straight onto the file manager to upload them.

Every file and folder also has a ⋯ menu (or right-click it) with Open, Rename, Download, Delete, and for folders New file here, New folder here and Upload here.

Upload a whole project as a zip

Uploading one zip is much quicker than uploading many files:

On your computer, zip your project folder. Leave out node_modules, venv, __pycache__ and .git. See Don’t upload your dependencies.
Upload the zip.
Open the zip’s ⋯ menu and click Extract here. Its contents are unpacked where it sits. The zip is removed afterwards.

Aviso

Check where your main file ends up after extracting. If it lands inside a subfolder (for example my-bot/index.js), either move the files up to the top level or change your run command to match, such as node my-bot/index.js.

Edit a file

Open a file and edit it on the right. The editor shows line numbers, and Tab indents.

A dot next to the file’s name means you have unsaved changes.
Click Save, or press Ctrl + S (Cmd + S on a Mac).
Close the file with the × on its tab. You’ll be asked first if it has unsaved changes.

Files that aren’t text, such as pictures and zips, and files over 5 MB can’t be opened in the editor. Download them instead.

If the file shows Read only, the server has been shared with you with view files access only.

On a phone

The Explorer fills the screen. Opening a file switches to the editor, and the back arrow returns to your files.

Deleting

Perigo

Deleting files can’t be undone from the file manager. Download anything important first. If you delete something by mistake, open a ticket straight away. For a short time we can sometimes get recently deleted files back.

Keep secrets out of your code

Put tokens and passwords in a separate file, such as .env or config.json, and read them from your code. Never paste them straight into a file you might share. If you share your server, only give view files or edit files to people you trust with those secrets.

Planning to publish a template? Keeping secrets in .env makes that much easier.