File Browser, one of the most widely deployed self-hosted file management web apps, is shutting down. Henrique Dias, known on GitHub as hacdias, and the project’s maintainer for most of its history, has confirmed that the filebrowser/filebrowser repository will be archived on September 1, 2026. After that date, the project will receive no further releases, no bug fixes, and no security fixes.
For years, File Browser has been a go-to option for anyone who wanted a lightweight, self-hosted alternative to poking around a server over SSH or relying on a NAS’s stock web interface. A single binary or Docker container gives you a clean browser-based file manager, with upload, download, rename, share links, and basic in-browser editing, pointed at any folder you choose. That’s what makes the shutdown worth paying attention to, rather than shrugging it off as one more abandoned repository.
The shutdown announcement
The news arrived attached to release v2.63.22, published on July 27, 2026 at 15:44 UTC and signed by hacdias. The release notes are direct: “File Browser is winding down. The repository will archived on 2026-09-01. After that date there will be no further releases, bug fixes, or security fixes. Existing releases and Docker images stay online and will not be withdrawn.”
A second, smaller release followed just hours later the same day: v2.63.23, published at 20:03 UTC and also signed by hacdias. It’s a housekeeping update, mostly swapping documentation links to point directly at the GitHub repository instead of the filebrowser.org website, and it’s now the final release the original File Browser project will ever ship.
What changes on September 1, and what doesn’t
Archiving a GitHub repository makes it read-only. For File Browser users, that breaks down like this:
- No further releases, bug fixes, or security fixes will be issued after the archive date.
- No new GitHub issues or pull requests can be opened once the repository goes read-only.
- Existing releases and Docker images stay published and will not be pulled or withdrawn.
- Instances already running File Browser keep functioning exactly as they do today.
So nothing breaks on September 1 itself. What ends is the safety net. Any bug found after that date, security-related or not, has no path to an official fix. For a tool whose entire purpose is serving your files to a web browser, sometimes from outside your home network, running indefinitely on a codebase with no future security patches is a standing risk, not a one-time inconvenience.
The wind-down has already reached the wider self-hosting press. Linuxiac covered the news under the headline “Popular Self-Hosted File Manager File Browser Is Shutting Down,” and the community newsletter Self-Host Weekly featured it in its July 31, 2026 edition, treating it as current news several days after the original announcement.
Filebrowser Quantum: the fork already filling the gap
Anyone looking for a next step doesn’t have to search far. Filebrowser Quantum, maintained by Graham Steffaniak (gtsteffaniak) under the same Apache-2.0 license, is a confirmed fork of the original File Browser codebase, and it exists for almost exactly the reason the original project is now winding down. Steffaniak started the fork because issues and pull requests on the upstream repository had been sitting unaddressed for months or years at a time. Rather than keep waiting on a slow contribution process, he built out his own branch with faster, ongoing development instead.
That decision looks well-timed in hindsight. Filebrowser Quantum has kept shipping updates at a pace the original project had already stopped matching well before this shutdown was announced, and it covers the same core use case: a web-based file manager you run yourself, on your own server. We cover the fork’s setup, features, and how it diverges from the original in our Filebrowser Quantum guide.
If you’re currently running the original File Browser, September 1, 2026 is a deadline worth planning around, not because your instance stops working that day, but because every day after it runs is a day without a path to a security fix. Moving to Filebrowser Quantum, or another actively maintained file-management tool, before the archive date is the more comfortable way to make that change. The full release notes for both the shutdown announcement and the final housekeeping release are available directly on GitHub, linked above.