macOS
brew install filebrowserlocal Homebrew formula metadata
sudo port install filebrowserMacPorts ports tree · net/filebrowser/Portfile · source: api.github.com
brew
Web File Browser. Version 2.63.18 via Homebrew; verified 2026-07-04.
install
brew install filebrowserlocal Homebrew formula metadata
sudo port install filebrowserMacPorts ports tree · net/filebrowser/Portfile · source: api.github.com
sudo apk add filebrowserAlpine Linux edge package indexes · filebrowser · source: dl-cdn.alpinelinux.org
nix profile install nixpkgs#filebrowsernixpkgs package indexes · pkgs/by-name/fi/filebrowser/package.nix · source: api.github.com
overview
Web File Browser
history
File Browser is a self-hosted web file manager that serves a chosen directory through a browser UI for uploading, deleting, previewing, editing, and sharing files.
Its package-manager appeal is that it compresses a useful private-cloud pattern into a single Go binary: install it, point it at a path, and run a small web server.
The upstream repository was created in 2015 and describes the project as a web file browser. The README frames the goal as create-your-own-cloud software: a server-side binary directed at a filesystem path and exposed through a web interface.
Versioned tags show the project reaching v1.0.0 in 2017 and v2.0.0 in 2019, with the v2 series becoming the long-lived packaging target for most users.
The README says File Browser is a finished product and is in maintenance-only mode, with maintainers focusing on bug triage, security issues, and review of bug-fix pull requests rather than planned new features.
File Browser's adoption came from a simple niche: self-hosters, homelab users, and small teams wanted a browser-based file manager without deploying a full groupware or storage platform.
Its availability in Homebrew, Alpine, MacPorts, and Nix reflects that it is useful both as a local developer utility and as a small server component in Unix-like environments.
The maintenance-only status is also part of its adoption story: the project reached a stable product shape, so package managers mostly carry it as dependable infrastructure rather than a fast-moving feature app.
Typical use is to install File Browser, choose the root directory to expose, configure a database and settings, and run the web server behind local authentication or a reverse proxy.
Users choose it when they need a quick file-management UI for a server directory, a small replacement for ad hoc SFTP access, or a browser-accessible drop zone for local infrastructure.
The operational model is intentionally compact: one binary, a database file for persistent state, static web assets in the binary, and command-line/config settings for binding, root path, and users.
File Browser is a neat package-manager specimen because it turns what could be a pile of web-app dependencies into a single installed executable.
It also represents the self-hosted Go-binary pattern common in Homebrew and Nix: portable server, minimal runtime dependencies, easy service wrapping, and a config/database file that package maintainers need to account for.
security posture
No matching local secret-handling manifest was found for filebrowser. Nucleus package metadata is still published here so future coverage has a stable package URL.
Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.
local files
These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.
Config paths the tool may read or write during local use.
./.filebrowser.{json,toml,yaml,yml}~/.filebrowser.{json,toml,yaml,yml}/etc/filebrowser/.filebrowser.{json,toml,yaml,yml}Credential-bearing paths to review before unattended agent runs.
./filebrowser.dbexecutables
| Command | Kind | Exposure | Note |
|---|---|---|---|
filebrowser | cli | global executable |
freshness
These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.
https://github.com/filebrowser/filebrowser
install metadata
| Package key | brew:filebrowser |
|---|---|
| Version | 2.63.18 |
| Package manager | Homebrew |
| Package manager page | https://formulae.brew.sh/formula/filebrowser |
| Homepage | https://filebrowser.org/ |
| Repository | https://github.com/filebrowser/filebrowser |
| Upstream docs | https://filebrowser.org/ |
| License | Apache-2.0 |
| Source archive | https://github.com/filebrowser/filebrowser/archive/refs/tags/v2.63.18.tar.gz |
| Last updated | 2026-07-04T09:46:06Z |
| Pulse | updated |
| Build dependencies | go |
| Bottle | available (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux) |
| Homebrew post-install | not defined |
| Service | none declared |
registry facts
| Source Database | Homebrew formula API |
|---|---|
| Tap | homebrew/core |
| Full Name | filebrowser |
| Version Scheme | 0 |
| Revision | 0 |
| Head Version | HEAD |
| Bottle Stable Root URL | https://ghcr.io/v2/homebrew/core |
| Deprecated | no |
| Disabled | no |
| Keg Only | no |
| URL Keys |
|
source database matches
Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.
filebrowser
nix profile install nixpkgs#filebrowserfilebrowser 2.27.0-r21
Web File Browser
https://github.com/filebrowser/filebrowser
sudo apk add filebrowserfilebrowser-openrc 2.27.0-r21
Web File Browser (OpenRC init scripts)
https://github.com/filebrowser/filebrowser
sudo apk add filebrowser-openrcfilebrowser
sudo port install filebrowsersource trail
This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.
View the package source record on GitHub.