The File Browser GitHub repository has been archived after nearly a decade as the default “put a web UI on a folder” tool for homelabs. The single binary, the tidy UI, and the good defaults kept it in front of a lot of home NAS shares. Archived means no more security patches and no more issue triage. If it sits on the open internet, that clock is now running against you. These File Browser alternatives for desktop cover the same job on Windows, macOS, and Linux, from single-binary drop-ins that behave almost identically to full sync platforms that quietly outgrew File Browser years ago.
We looked at what people are actually migrating to on r/selfhosted and the homelab forums, then pulled seven that are genuinely maintained in 2026. Every pick runs on Windows, macOS, and Linux, either natively or in Docker.
Quick comparison
| App | Best for | License | Storage backends | Standout feature |
|---|---|---|---|---|
| Filestash | Direct File Browser replacement | AGPL / commercial | S3, SFTP, FTP, WebDAV, Git, Dropbox, Drive | Backend abstraction, no local mount required |
| Nextcloud | Full collaboration suite | AGPL | Local, S3, external storage | Office, calendar, chat in one server |
| Seafile | Fast sync at scale | GPL | Local, S3-backed pro | Block-level dedup sync engine |
| FileRun | Photo and media libraries | Free tier + paid | Local (points at existing filesystem) | Auto-tags photos and previews Office files |
| Pydio Cells | Team file sharing with RBAC | AGPL | Local, S3-compatible | Cells (workspace-scoped shares) and audit log |
| Cloud Commander | Terminal + file manager in one | MIT | Local | Built-in editor, shell, and process list |
| Miniserve | Read-only quick shares | MIT | Local | One command, one folder, HTTPS via reverse proxy |
Why people are leaving File Browser
Archival is the visible reason, but the churn started earlier. The recurring complaints in the r/selfhosted threads that led up to it:
- No native backends. File Browser expects a local mount. Anything remote (S3, SFTP, a NAS share not fstab’d in) needed hacks on the host. Filestash and Pydio Cells treat backends as first-class.
- Sharing is thin. Public links exist, but no time-limited access controls, no per-file password rotation, no download quotas. Enough for a home lab, not enough for anything semi-public.
- No sync client. Web UI only. To keep a folder mirrored between a laptop and the server, you had to layer Syncthing or rsync on top. Nextcloud and Seafile ship desktop clients that just work.
- Search is filename-only. No content indexing, no OCR, no photo tagging. FileRun and Nextcloud have all three.
- Audit and RBAC gaps. A single admin, per-user roots, and permission flags is fine for a family server. Pydio Cells actually logs who did what.
Each alternative below covers at least one of these directly. The order goes closest-drop-in first, biggest-platform last.
Filestash, best direct replacement
Filestash is the app most File Browser refugees end up on. Single binary, same “web UI over a filesystem” model, but the filesystem doesn’t have to be local. It speaks S3, SFTP, FTP, WebDAV, Git, Dropbox, Google Drive, Backblaze, and a stack of others out of the box, so you point it at where the data actually lives instead of mounting things on the host. The UI feels lighter than File Browser’s did in its last releases, with preview panes for images, PDFs, video, audio, and Office documents.
Where it falls short: Two-factor authentication and SSO live behind the enterprise license. The self-hosted community build has basic auth and LDAP but no OIDC.
Pricing:
- Free: AGPL community build, no user cap, community backends
- Paid: Enterprise license from around 25 EUR/user/year for SSO, audit log, priority support
Migrating from File Browser: No importer. Both apps read the same files from the same disk, so pointing Filestash at your existing data/ folder is enough. Users, share links, and permission entries have to be recreated. A 20-user setup takes an hour.
Bottom line: Take this one first if File Browser was doing what you needed and you just want a maintained equivalent with more backends.
Nextcloud, best if you want more than files
Nextcloud is the maximalist answer. Files are one app in a suite that also has a Collabora or OnlyOffice document editor, calendar, contacts, mail, group chat, video calls, and a notes app. If the reason you self-host is to keep a family or a small team off Google Drive plus Google Calendar plus Google Meet, Nextcloud is a single server instead of five.
Where it falls short: PHP + MySQL + Redis + a reverse proxy is a lot compared to Filestash’s one binary. Upgrades occasionally require manual intervention on custom apps. The web UI is heavier and feels slower on a Raspberry Pi.
Pricing:
- Free: AGPL, self-hosted, no user cap
- Paid: Managed hosting from around $6/user/month; enterprise support from around 3,900 EUR/year for a 50-seat pack
Migrating from File Browser: Point Nextcloud’s external storage app at your existing File Browser data root and it appears as a mounted folder. Users get moved by re-inviting; File Browser’s share links do not transfer.
Bottom line: Pick Nextcloud if the file server is really a stalking horse for a wider Google replacement.
Seafile, best for fast sync
Seafile rebuilt the sync engine around block-level chunking, so a 10 GB Lightroom catalog only transfers the changed blocks and skips the rest. On a home fiber link that means a folder rename doesn’t push half a terabyte back to the server. The web UI is deliberately minimal, everything real happens in the desktop client, which is packaged for Windows, macOS, and Linux.
Where it falls short: No document editor built in. Photo previews exist but aren’t a photo library. The free Community Edition is capped at three users unless you pay for the Pro or Enterprise tier.
Pricing:
- Free: Community Edition, three-user cap, no S3 backend
- Paid: Pro from $100/user/year (S3 backend, drive client, full-text search, SAML)
Migrating from File Browser: No importer. Ingest by putting your existing folder into a Seafile library from the desktop client on one machine, then wait for the sync. Public share links have to be recreated.
Bottom line: Take Seafile if what you actually want is faster syncing between machines and File Browser was your fallback because it worked.
FileRun, best for photos and Office files
FileRun looks the closest to Google Drive of anything on this list. It sits on top of your existing folder structure without moving files, auto-generates thumbnails for photos and video, previews Office documents inline via WebDAV integration with OnlyOffice or Collabora, and does full-text search on PDFs. The photo gallery view can face timeline scrubbing without hanging.
Where it falls short: The free tier is capped at 10 users and the “not FOSS” nature bothers some homelab crowds. Docker install works but has more moving parts than Filestash’s single binary.
Pricing:
- Free: Up to 10 users, self-hosted
- Paid: From $99/year for the Enterprise license (unlimited users, migration tools, priority support)
Migrating from File Browser: Zero data migration required, point FileRun at the same root. User accounts are recreated in FileRun’s admin.
Download: Website
Bottom line: Best pick if your NAS is mostly photos and documents rather than raw files.
Pydio Cells, best for team file sharing
Pydio Cells targets the SaaS Dropbox-for-Business use case on your own hardware. The core concept is a “Cell”, which is a workspace with its own members, roles, and audit trail. Public shares can have expiration dates, download limits, upload passwords, and watermarks. The activity log records every file touch.
Where it falls short: Setup is heavier than Filestash. The mobile clients are less polished than Nextcloud’s. The community edition drops SAML and advanced audit exports.
Pricing:
- Free: Home Edition (AGPL), no user cap, community backends
- Paid: Enterprise from around $1,000/year for a 25-user pack (SAML, audit exports, priority patches)
Migrating from File Browser: Point a Cell at your existing data root. User migration is manual. If you were already using File Browser’s public share URLs, budget an afternoon to rebuild them.
Bottom line: Take this one if you were about to outgrow File Browser because share management, audit, and per-workspace permissions became painful.
Cloud Commander, best for admin work over the web
Cloud Commander is a two-panel file manager (think Norton Commander) that runs in the browser. It bundles a code editor, a shell, and a process list, so it doubles as a lightweight web console when you don’t want to open an SSH session. Single Node.js process, tiny footprint.
Where it falls short: Not built for end users. Sharing is basic. Multi-user support is limited to HTTP basic auth. Photos and Office previews are not the goal.
Pricing: Free. MIT license, no paid tier.
Migrating from File Browser: Nothing to migrate. Install, point at the folder, done.
Bottom line: Not a general File Browser replacement, but the right pick if what you actually used File Browser for was one-off admin tasks on a headless server.
Miniserve, best for one-shot public shares
Miniserve is a single Rust binary that turns any folder into a browsable HTTP endpoint in one command. QR code output, optional basic auth, per-file upload, TAR/ZIP download of subtrees. No database, no users, no state. If the File Browser instance you’re archiving was really just “let me hand a URL to someone for the next hour”, Miniserve is what you want instead.
Where it falls short: No accounts, no sync, no previews, no editing. Ephemeral by design.
Pricing: Free. MIT license.
Migrating from File Browser: Not applicable, different use case.
Bottom line: Keep it in the toolbox even if you pick something else for the main server.
How to choose
- Pick Filestash if you want the smallest jump from File Browser and richer storage backends.
- Pick Nextcloud if the file server is going to grow into calendars, chat, and document editing anyway.
- Pick Seafile if fast sync between machines was the reason you cared about the file server at all.
- Pick FileRun if the folders on the server are mostly photos and Office documents.
- Pick Pydio Cells if you need audit trails and permission scoping that File Browser never had.
- Pick Cloud Commander if the “file browser” was really a headless admin panel.
- Pick Miniserve for one-off public downloads, in place of anything with a database.
Stay on File Browser only if the instance is on a private network, behind a VPN, and you can accept “no security patches ever” as a documented risk.
FAQ
Is there a fork of File Browser still being maintained?
A community fork called File Browser Quantum picked up the project after archival and ships regular releases. It patches the security backlog and adds a couple of quality-of-life features. It is a straight drop-in for existing File Browser installs. If you value continuity over new features, that fork is the shortest migration; if you want more backends or richer sharing, one of the seven above is the better move.
Is Filestash really a like-for-like File Browser replacement?
Close, and closer than anything else on the list. Same “web UI in front of files” concept, single binary, similar admin ergonomics. The gains are backends (S3, SFTP, WebDAV, Git, cloud drives) and file previews. The gap is enterprise SSO, which stays in the paid tier.
Which of these is the fastest?
For raw sync, Seafile. Its block-level engine noticeably outperforms Nextcloud and rsync on large binary files. For web UI responsiveness on a modest server, Filestash and Miniserve are the lightest.
Can I run these on a Raspberry Pi?
Filestash, Miniserve, Cloud Commander, and Seafile Community Edition run comfortably on a Raspberry Pi 4 or 5. Nextcloud and Pydio Cells work but feel sluggish on anything below a Pi 5 with 8 GB. FileRun runs fine but you will want an SSD for the previews.
Do any of these have mobile apps?
Nextcloud, Seafile, and Pydio Cells all ship official Android and iOS clients. Filestash has a mobile-friendly web UI. Miniserve and Cloud Commander are web-only. FileRun has a mobile web UI plus WebDAV, which most Android and iOS file apps consume directly.
Is it safe to leave a self-hosted file manager on the public internet?
Only behind a reverse proxy with TLS, rate limiting, and an authentication layer in front of the app itself. Nextcloud and Pydio Cells support 2FA and OIDC in their free editions; Filestash and FileRun add those in paid tiers. Miniserve should be scoped to VPN or private network only.
