File Browser — Self-Hosted Web File Manager

What it is

File Browser is a lightweight, self-hosted web file manager that lets you manage files on your server through a clean browser interface. It supports file uploads, downloads, sharing via links, user management with permissions, and a built-in text editor. No external dependencies are required -- it runs as a single binary.

File Browser is for sysadmins, homelab operators, and teams who need a simple way to manage server files without SSH access or complex NAS software.

The project is actively maintained with regular releases and a growing user community. Documentation covers common use cases, and the open-source nature means you can inspect the source code, contribute fixes, and adapt the tool to your specific requirements.

How it saves time or tokens

Managing files over SSH requires terminal familiarity and is impractical for non-technical users. FTP is insecure and outdated. File Browser provides a modern web UI that anyone can use, with drag-and-drop uploads, file previews, and shareable download links. Installation takes one command.

How to use

1. Install File Browser with a single curl command or Docker.
2. Configure the root directory and port.
3. Access the web UI from your browser.

Example

# One-line install
curl -fsSL https://raw.githubusercontent.com/filebrowser/get/master/get.sh | bash

# Start File Browser
filebrowser -r /path/to/files -p 8080

# Or via Docker
docker run -d --name filebrowser \
  -v /path/to/files:/srv \
  -p 8080:80 \
  filebrowser/filebrowser

# Default credentials: admin / admin
# Open http://localhost:8080

Related on TokRepo

• AI Tools for Self-Hosted -- Self-hosted file management tools
• Featured Workflows -- Top workflows on TokRepo

Common pitfalls

• The default admin password is 'admin'. Change it immediately after first login, especially if the instance is accessible from the internet.
• File Browser serves files from a root directory. Misconfiguring the root to '/' exposes your entire filesystem. Always set a specific, non-root directory.
• Large file uploads may fail if your reverse proxy (Nginx) has a low client_max_body_size setting. Increase it to match your expected upload sizes.

Before adopting this tool, evaluate whether it fits your team's existing workflow. Read the official documentation thoroughly, and start with a small proof-of-concept rather than a full migration. Community forums, GitHub issues, and Stack Overflow are valuable resources when you encounter edge cases not covered in the documentation.