filebrowser

A no-nonsense look at self-hosted file management. No marketing copy, just what you actually get when you point a Go binary at a folder.

TL;DR

• What it is: A single-binary, web-based file manager you point at a directory on your server. Upload, download, delete, preview, edit — in a browser, no client app needed [README].
• Who it’s for: Self-hosters who want a clean web UI over files on a VPS, NAS, or home server. Not a Dropbox/Google Drive replacement — no sync clients, no mobile apps, no real-time collaboration [README][1].
• Cost savings: Google Workspace Business Starter runs $6/user/month (2TB). filebrowser is free, self-hosted, Apache-2.0 licensed. For a solo founder or small team that just needs “put files on server, access from browser,” the math is stark.
• Key strength: Absurdly simple to deploy. Single binary or one Docker command. No database to configure, no dependencies beyond the binary itself [README].
• Critical caveat: The original project is in maintenance-only mode as of early 2026 — no new features, security fixes only. A community fork called FileBrowser Quantum appears to be where active development has migrated [README][1].

---

What is filebrowser

filebrowser does exactly one thing: it gives you a web interface to browse, manage, and edit files inside a directory you specify on your server. You run the binary, point it at /srv/data or wherever your files live, and you get a clean web UI that lets you upload, download, delete, rename, preview images, and edit text files. The project’s own description calls it “create-your-own-cloud-kind of software” [README] — which is both accurate and slightly overselling it. It’s not a cloud. It’s a web UI for a folder.

That simplicity is the point. There’s no sync daemon, no client app to install, no “vault” or “team space” concept. You log in at a URL, you see files, you manage them. It’s the kind of tool a sysadmin builds in a weekend to stop SSH-ing into a server to copy files — except someone already built it properly and open-sourced it.

As of this writing the project sits at approximately 33,895 GitHub stars [merged profile], which reflects a decade of organic growth from people solving exactly that “I just need a web file manager” problem. The Apache-2.0 license means you can embed it in commercial products without a phone call to a lawyer.

The catch, and it’s important: in March 2026, the lead maintainer @hacdias posted a personal reflection on the project status and the GitHub README now leads with a prominent warning: “This project is on maintenance-only mode.” No new features are planned. Pull requests for features are not guaranteed review. Priority is triaging bugs and security issues [README]. If you’re evaluating filebrowser for a long-term production setup, that sentence belongs in your notes.

---

Why people choose it

The XDA Developers review by Parth Shah [1] lands on a useful framing: filebrowser — specifically FileBrowser Quantum, the community-driven continuation — works as “an ultimate centralized hub for managing files across multiple self-hosted applications.” Not a replacement for your whole cloud storage workflow, but a clean interface sitting on top of data that already lives on your server.

The appeal is repeatability: self-hosters running Jellyfin, Immich, Paperless-NGX, and similar tools accumulate a lot of server-side data spread across paths. SSH + a CLI file manager works, but it’s friction. filebrowser cuts that friction with a browser tab [1].

Shah notes the FileBrowser Quantum fork specifically for its “modern design principles without the dated appearance common to open-source applications” and calls the interface “polished” with “smooth animations and intuitive navigation” [1]. This matters because the original filebrowser UI, while functional, was starting to show its age before development slowed. The fork appears to be where the UI improvements are landing.

In the alternatives comparison space, filebrowser consistently shows up when people want something lighter than Nextcloud, simpler than Seafile, and narrower than a full self-hosted cloud suite [2]. The comparison isn’t really against Google Drive — it’s against the overhead of installing a full Nextcloud stack when you just want to browse a folder.

---

Features

What ships:

• Web login with session management [homepage]
• Upload, download, rename, move, copy, delete files and folders [homepage][README]
• In-browser file editing (text files) [homepage]
• Image preview [README]
• User management — multiple users, per-user scope restrictions [homepage]
• Custom commands — you can configure server-side shell commands that run against files [homepage]
• Branding and customization options [homepage]
• Rules (allowlist/blocklist patterns per user or globally) [README]
• Full CLI for management: filebrowser users add/rm/update, filebrowser config set, etc. [homepage]
• Available as a single binary or Docker image [README]

What it doesn’t have:

• Sync client (no desktop or mobile app)
• Conflict resolution or versioning
• Collaborative editing
• Sharing links with expiry (not in the community feature set)
• S3 or object storage backends — it points at a local filesystem only
• REST API surface for programmatic management (the CLI handles this locally)

The FileBrowser Quantum fork [1] adds a more modern UI and addresses some UX gaps that the original project left open as it wound down. If you care about interface quality, the fork is worth investigating alongside the original.

---

Pricing: SaaS vs self-hosted math

filebrowser: $0 software cost. Apache-2.0. Run it on whatever you already have.

Google Drive / Workspace (the merged profile’s listed SaaS competitor):

• Business Starter: $6/user/month (2TB pooled storage)
• Business Standard: $12/user/month (2TB + Meet recording, etc.)
• Business Plus: $18/user/month (5TB)
• Enterprise: custom pricing

For a solo founder or a team of three, Google Workspace Business Starter runs $18–$216/year per user. For a team of 10, that’s $720–$2,160/year just for the Starter tier.

But the comparison is imperfect because Google Drive and filebrowser don’t do the same job. Google Drive includes:

• Desktop sync clients (Windows, Mac, iOS, Android)
• Real-time collaborative editing (Docs, Sheets)
• Mobile access with offline sync
• Google Meet, Gmail, Calendar (on Workspace)
• CDN-grade availability and uptime guarantees

filebrowser gives you none of that. What it gives you instead: a web UI to files on your server, hosted infrastructure you control, and a zero recurring cost.

The honest savings math: If your use case is “my team needs to drop files somewhere and pull them from a browser,” and you don’t need sync clients or collaborative editing, filebrowser on a $5/month VPS saves roughly $700–$2,000/year for a 10-person team compared to Google Workspace. If you need mobile sync and collaborative docs, filebrowser is the wrong tool entirely — Nextcloud is a better comparison point.

---

Deployment reality check

This is where filebrowser genuinely earns its stars. Deployment is the simplest in the self-hosted file management space:

docker run -v /path/to/files:/srv -v /path/to/config:/config \
  -p 8080:80 filebrowser/filebrowser

Or download the binary, run it. Done. No PostgreSQL, no Redis, no message queue. The default config stores its database (SQLite) in a single file alongside the binary [README].

What you need:

• A Linux server or NAS (anything that runs Docker or a Go binary)
• A reverse proxy if you want HTTPS (Caddy, nginx, Traefik)
• A domain or local network access

Realistic time estimate: 15–30 minutes for a technical user. Under an hour following a guide for someone less experienced. This is genuinely one of the easier self-hosted deployments.

Where it can go sideways:

• Maintenance mode risk. The project’s own README flags that it’s maintenance-only and security-focused. For a simple internal file browser this may be fine — the core feature set is stable and complete. But if a breaking change in Docker or a dependency creates a problem, don’t expect a fast fix [README].
• No authentication hardening beyond basic login. If you expose filebrowser to the internet without a VPN or IP restriction, your login page is your only barrier. Use a strong password and consider restricting access by IP or putting it behind a reverse proxy with additional auth.
• FileBrowser Quantum vs original. The XDA review [1] is specifically about the Quantum fork, not the original repo. If you want active maintenance and UI improvements, you may be looking at the fork, not the official project. This creates a documentation gap — the official docs at filebrowser.org don’t reflect the fork.
• No file versioning. If you delete something or overwrite a file, it’s gone. No recycle bin, no version history in the default setup.

---

Pros and Cons

Pros

• Simplest deployment in the category. Single binary, zero external dependencies, works on any Linux box in minutes [README][1].
• Apache-2.0 license. No commercial restrictions. You can embed it in a product, white-label it, ship it to clients [README].
• Multi-user with scoped access. You can create users that can only see specific subdirectories — useful for giving contractors or clients access to their own folder without exposing everything [homepage].
• Custom commands. Trigger shell commands against files from the UI — useful for triggering conversions, processing scripts, or other automation on upload [homepage].
• Genuinely lightweight. Doesn’t eat RAM or CPU at idle. Runs comfortably alongside other services on a small VPS or NAS.
• 33,895 GitHub stars — not a dead project in the traditional sense; the community is large enough that problems and workarounds are well-documented [merged profile][2].
• FileBrowser Quantum fork appears active and addresses UI quality concerns that accumulated as the original wound down [1].

Cons

• Maintenance-only mode. The original project’s lead maintainer explicitly declared it finished. If your use case evolves or you hit a bug in an edge case, don’t count on upstream fixes [README].
• No sync clients. You cannot use filebrowser the way you use Dropbox. Files don’t sync to your laptop or phone automatically. This is a browser-only tool.
• No sharing links. Out of the box you can’t generate a “share this file with an external person” link the way you can with Nextcloud or Google Drive. Everyone who needs access needs a filebrowser account.
• Local filesystem only. No S3, no SFTP backends, no object storage. It sits on top of whatever the server can mount locally.
• No file versioning or recycle bin. Deleted is deleted. Overwritten is overwritten.
• UI ambiguity between original and Quantum fork. If you’re drawn in by screenshots of the modern Quantum UI, make sure you’re deploying the right project. The official filebrowser.org docs and Docker image reflect the original, not the fork.
• Not a Google Drive replacement. The merged profile lists Google Drive as the SaaS competitor, but this comparison sets incorrect expectations. filebrowser replaces “I need to browse files on my server from a browser” — not “I need collaborative docs, sync, and mobile access.”

---

Who should use this / who shouldn’t

Use filebrowser if:

• You have files on a server and want a browser-based way to manage them without SSH.
• You’re running other self-hosted services (Jellyfin, Home Assistant, etc.) and want a web UI to the data directories those services use.
• You want to give non-technical collaborators scoped read/write access to specific folders on your server without setting up full cloud storage.
• You want something that deploys in 20 minutes and stays out of your way.
• You need an Apache-licensed file browser you can embed or bundle with your own product.

Skip it (use Nextcloud instead) if:

• You need desktop or mobile sync clients.
• You want collaborative document editing.
• You need sharing links that expire, password-protected shares, or external access without creating accounts.
• You want a genuine Google Drive or Dropbox replacement for a team.

Skip it (use Seafile or Syncthing instead) if:

• Your primary need is file synchronization — keeping files in sync between machines rather than browsing server files.

Skip it (use FileBrowser Quantum specifically) if:

• You want filebrowser’s architecture but with active development and a modern UI — in which case look at the fork directly rather than the original [1].

Think twice if:

• You’re putting this in front of non-technical end-users long-term. The maintenance-only status means you’re accepting that what you see today is roughly what you’ll have in two years, bugs and all.

---

Alternatives worth considering

From the related repositories comparison [2] and the self-hosted file management space:

• Nextcloud — the obvious upgrade path. Full cloud suite: sync clients, collaborative editing, calendar, contacts, app ecosystem. Significantly more complex to deploy and operate. Worth it if you need more than a file browser.
• Seafile — focused on file sync and sharing, not just browsing. More robust conflict resolution and versioning than filebrowser. Client apps for desktop and mobile. More moving parts to operate [2].
• Cloudreve — 27,000+ GitHub stars, more actively developed file management and sharing platform, supports multiple storage backends (local, S3, OneDrive, OSS). Closer to a Dropbox alternative than filebrowser [2].
• Filestash — “Universal Data Access Layer.” Connects to SFTP, S3, Git, FTP, and others through a single web interface. More complex but more flexible if you need to manage files across multiple storage backends [2].
• rclone — not a web UI, but a CLI tool with browser-capable serve modes. If your primary use is syncing between storage providers rather than a persistent web UI, rclone covers more ground [2].
• Syncthing — continuous file synchronization between machines, no server required. No web file manager interface; this is pure sync [2].
• FileBrowser Quantum — the community fork of filebrowser itself with active development and a modern UI rewrite [1]. If you like filebrowser’s architecture but want forward momentum, start here.

For a non-technical founder who just needs to manage files on a server: filebrowser (or its Quantum fork) vs Cloudreve is the realistic shortlist. filebrowser is simpler and more focused. Cloudreve adds sharing and multi-storage support if you need it.

---

Bottom line

filebrowser does a narrow job well: web-based file management for a directory on your server, deployed in minutes, with zero external dependencies. The 33,895 GitHub stars represent years of people solving “I need a file manager, not a cloud suite” and landing here. The Apache-2.0 license and single-binary deployment make it easy to recommend for the right use case.

The maintenance-only status is the honest caveat you need to carry into any production decision. The project’s lead maintainer said, in effect, “it’s finished.” For a simple internal tool that changes rarely, that’s arguably fine — stability is a feature. For anything you’re betting on long-term, either track the FileBrowser Quantum fork or accept that you’re running something that won’t evolve with your needs.

What filebrowser is not: a Dropbox replacement, a Google Drive replacement, or a full self-hosted cloud. If someone quotes you $12/user/month for Google Workspace and you’re evaluating filebrowser as the swap — that’s the wrong comparison. The right question is whether you actually need sync clients and collaborative docs, or just a clean browser tab over files that already live on a server you own. If it’s the latter, a $5/month VPS and a 20-minute deploy will outlast that recurring invoice.

---

Sources

1. Parth Shah, XDA Developers — “I self-hosted a free and open-source web-based file browser, and it’s perfect for managing my other tools” (June 25, 2025). https://www.xda-developers.com/self-hosted-free-open-source-web-based-file-browser/
2. RelatedRepos — “haiwen/seafile alternatives and similar packages” (includes filebrowser in comparison list). https://relatedrepos.com/gh/haiwen/seafile

Primary sources:

• GitHub repository and README: https://github.com/filebrowser/filebrowser (33,895 stars, Apache-2.0 license)
• Official website: https://filebrowser.org
• Maintainer reflection on project status: https://hacdias.com/2026/03/11/filebrowser/