Docs/ Operations/ File Manager

File Manager

Browse and manage files inside your containers with a visual file explorer. View, edit, upload, and download files without opening a terminal.

Browsing Container Files

The file manager provides a visual interface to the filesystem inside any running container. Access it from the service detail page by clicking the Files tab.

  1. Navigate to your service within its stack.
  2. Click the Files tab.
  3. The file browser opens at the container's root directory (/).
File manager main view -- showing a directory listing with file names, sizes, modification dates, and permission indicators

The file list displays the following information for each entry:

  • Name -- File or directory name, with icons distinguishing files from folders.
  • Size -- File size in human-readable format (KB, MB, GB).
  • Modified -- Last modification timestamp.
  • Permissions -- Unix permissions displayed as a string (e.g., rwxr-xr-x).
  • Owner -- File owner and group.

Click any directory name to enter it. The breadcrumb path at the top shows your current location and lets you jump back to any parent directory.

Breadcrumb navigation -- showing path segments / > app > src > routes with each segment clickable

You can also type a path directly into the path bar to jump to a specific directory. Press Enter to navigate.

Tip
Common paths to check: /app (application code), /var/log (logs), /etc (configuration), and /tmp (temporary files).

Viewing File Contents

Click on any file to open it in the built-in viewer. The viewer supports syntax highlighting for common file types:

  • Source code files (JavaScript, Python, Ruby, Go, Rust, PHP, etc.)
  • Configuration files (JSON, YAML, TOML, INI, XML)
  • Plain text and log files
  • Shell scripts
  • Dockerfiles and docker-compose files
File viewer -- showing a package.json file with syntax highlighting and line numbers
Note
Binary files (images, compiled binaries, archives) cannot be displayed in the viewer. You can download them instead.

Editing Files

The file manager includes a built-in editor for making quick changes to files. Click the Edit button when viewing a file to switch to edit mode.

  1. Open a file in the viewer.
  2. Click Edit in the top-right corner.
  3. Make your changes in the editor.
  4. Click Save to write the changes to the container.
File editor -- showing an editable text area with syntax highlighting, a Save button, and a Discard button
Warning
File edits are written directly to the container filesystem. If the file is not in a mounted volume, changes will be lost when the container restarts or redeploys. For permanent changes, update your source code and redeploy.

Uploading Files

Upload files from your local machine to the container. This is useful for transferring configuration files, certificates, data files, or assets.

  1. Navigate to the target directory in the file manager.
  2. Click the Upload button.
  3. Select one or more files from your machine (or drag and drop them onto the file list).
  4. The files are uploaded and appear in the directory.
File upload dialog -- showing a drag-and-drop zone and a file picker button with upload progress indicators
Note
Maximum upload file size is 100 MB per file. For larger files, use the Terminal with wget or curl to download files directly into the container.

Downloading Files

Download files from the container to your local machine. Right-click a file (or use the action menu) and select Download.

You can also download entire directories as a .tar.gz archive. This is useful for pulling log directories, backup files, or application data.

File context menu -- showing options for Download, Rename, Copy path, and Delete

File Permissions

The file manager displays Unix file permissions for each file and directory. You can modify permissions through the properties panel:

  1. Right-click a file and select Properties.
  2. View or modify the permission mode (e.g., 644, 755).
  3. Click Apply to update the permissions.
Common permission patterns
644  - Owner read/write, group/others read-only (files)
755  - Owner full, group/others read+execute (directories, scripts)
600  - Owner read/write only (private keys, secrets)
777  - Full access for everyone (avoid this in production)

Persistent vs. Ephemeral Files

Understanding which files persist across container restarts is critical:

TypeSurvives Restart?Examples
Mounted volumesYesDatabase data, uploaded files, persistent config
Container filesystemNoApplication code, temp files, logs (unless volume-mounted)
Tip
In the file manager, directories that are backed by a volume are marked with a volume icon. This makes it easy to tell which paths will persist across restarts.