FileGator

Self-hosted file management, honestly reviewed. No marketing fluff, just what you get when you run it yourself.

TL;DR

• What it is: Free, MIT-licensed, self-hosted web file manager built on PHP + Vue.js — a browser-based interface for shared file storage with proper user access controls [1][2].
• Who it’s for: Small teams, educators, and developers who need to expose a folder or S3 bucket over the web with per-user permissions — without paying for Dropbox Business or building something custom [1].
• Cost savings: Dropbox Business starts at $15/user/month. A 10-person team pays $1,800/year. FileGator on a $6 VPS costs $72/year with unlimited users [2].
• Key strength: The storage adapter system — you can point FileGator at local disk, FTP, Amazon S3, DigitalOcean Spaces, Azure Blob, or Dropbox with a config change, not a code change [1][5].
• Key weakness: 2,924 GitHub stars is a modest community for infrastructure software. Effectively one maintainer. No sync clients, no mobile apps, no audit logs. This is a web UI on top of storage — not a Dropbox replacement with offline access [1].

---

What is FileGator

FileGator is a self-hosted web application that puts a browser-based file manager in front of your storage. You install it on a PHP-capable web server, point it at a storage backend, and your users get a Vue.js interface where they can upload, download, copy, move, rename, zip, and delete files from any browser — no software installation required [1][2].

The core problem it solves is specific: you have files somewhere (a server, an S3 bucket, an FTP server), and you need multiple people to interact with them through a browser with different access levels — without exposing raw filesystem credentials or running an FTP client. FileGator handles that problem directly and nothing else [1].

The architecture is a PHP backend with a Vue.js/Bulma/Buefy frontend. File operations route through Flysystem, a PHP filesystem abstraction library that handles the storage adapter layer [5]. The same FileGator codebase works against local disk, S3, FTP, Dropbox, and others by swapping a configuration value. That flexibility is the architectural win.

No database is required by default. User accounts live in a JSON file. If you need scale, there are auth adapters for database storage and WordPress integration [1].

The project is maintained by interactive32.com, a small Croatian software shop, with Patreon-backed sponsors. At 2,924 GitHub stars it’s a well-maintained niche utility, not a sprawling open-source community [1].

---

Why people choose it

The use cases in the project documentation are unusually specific, and they cluster around one theme: you have files in backend storage and you need non-technical people to interact with them through a browser with access controls [1].

As an FTP replacement. FTP is unencrypted by default, the client UX is hostile to non-technical users, and managing FTP permissions is painful. FileGator gives you a browser interface on top of the same file storage without requiring users to configure Filezilla or manage SFTP keys. The README lists this explicitly as a primary use case [1].

For controlled uploads from the field. The chunked upload system (built on Resumable.js) handles large files reliably regardless of PHP’s upload_max_filesize setting, splitting uploads into chunks and reassembling them server-side [1]. This matters for use cases like field workers submitting high-res photos or students uploading project files — scenarios where you need reliable large-file upload from non-technical users on variable connections.

As a multi-user S3 browser. The AWS S3 console is not usable by non-engineers. FileGator wraps an S3 bucket in a usable interface and layers RBAC on top — so different teams can access different prefixes within the same bucket with different permission levels [1][5].

For CDN management. If you’re serving static assets from a bucket and multiple people need to upload and organize files, FileGator provides the shared management interface that S3 alone doesn’t [1].

As a simple cloud backup target. The README frames it as a “cloud backup” option — you expose a folder to trusted users and let them push files in without giving them server access [1].

If your need doesn’t fit this template — if you need sync clients, mobile apps, file versioning, or collaborative editing — FileGator is the wrong tool. It’s narrow by design.

---

Features

Based on the GitHub README and project documentation [1][4]:

File operations:

• Copy, move, rename, create, delete, edit, and preview files [1]
• Zip and unzip archives [1]
• Bulk download — multiple files and folders at once, if permitted [1]
• Drag-and-drop upload with progress bar, pause, and resume [1]
• Chunked uploads via Resumable.js — large files work regardless of server PHP config [1]

Storage adapters (via Flysystem):

• Local filesystem [1]
• FTP [1]
• Amazon S3 [1]
• Dropbox [1]
• DigitalOcean Spaces [1]
• Azure Blob Storage [1]
• Others available through the Flysystem adapter ecosystem [5]

User management:

• Multi-user with per-user home folders [1]
• Roles and permissions (RBAC) [1]
• Auth adapters: JSON file (default, no database required), database, WordPress [1]
• Guest account support — the live demo at https://demo.filegator.io shows a read-only guest login [3]

Session management:

• Native PHP file sessions (default)
• PDO (database)
• Redis, MongoDB, Memcached via Symfony’s session handlers [1]

Frontend:

• Single-page application — Vue.js + Bulma CSS + Buefy components [1]
• Browser-only — no desktop or mobile native apps [1]

Known limitations (documented in the README):

• Symlinks not supported — Flysystem limitation [1]
• File ownership (chown) not supported [1]
• Too many files in a single directory degrades performance [1]
• No file versioning or trash
• No LDAP, SAML, or SSO
• No audit logging

---

Pricing: SaaS vs self-hosted math

FileGator has no SaaS tier. The software is MIT-licensed and costs $0 [1][2]. The relevant comparison is what it replaces.

Dropbox Business Standard: $15/user/month billed annually. A 10-person team pays $1,800/year. FileGator on a $6 Hetzner VPS costs $72/year for unlimited users and as much storage as the attached volume.

Google Workspace Business Starter: $6/user/month. Same 10 people costs $720/year — still more than a VPS, though the gap shrinks.

Managed FTP hosting: $10–30/month depending on provider. FileGator replaces this entirely with a better interface, user management, and S3 compatibility.

AWS S3 with no UI: If you’re already storing files in S3, FileGator’s software cost is $0. You pay only for the compute to run the PHP server — a $4–6/month instance handles it.

Concrete math for a 10-person team needing file sharing:

Option	Monthly	Annual
Dropbox Business Standard	$150	$1,800
Google Workspace Starter	$60	$720
FileGator on $6 VPS	$6	$72

Savings vs Dropbox: $1,728/year. The savings scale with headcount; the infrastructure cost doesn’t.

The honest qualification: FileGator is not Dropbox. No sync client, no mobile app, no offline access. If your team needs those things, the comparison is unfair. If your team needs controlled file uploads and downloads through a browser, it’s exactly the right comparison.

---

Deployment reality check

FileGator is a PHP application — familiar territory if you’ve run WordPress or Laravel, potential friction if you’ve only dealt with Node.js or Go services.

Minimum requirements:

• PHP 7.2+ with standard extensions (mbstring, fileinfo)
• Apache or nginx with PHP-FPM
• No database, Redis, or queue workers for a standard install [1]
• Docker is supported for containerized deployment [1]

What the manual install looks like:

1. Download the latest release archive
2. Extract to your web server’s document root
3. Configure configuration.php with storage adapter and auth settings
4. Set correct file permissions on the repository folder
5. Visit the web UI

For a PHP-experienced developer, this is under 30 minutes on a pre-configured server. For someone coming from Node.js or Python, the nginx + PHP-FPM configuration step adds an hour.

What can go sideways:

PHP’s open_basedir and disabled functions can silently break file operations if your hosting environment is restrictive. Storage adapter configuration (S3 credentials, FTP settings) requires editing PHP config directly — there’s no web-based storage management UI [1]. Connecting a new backend means touching code files, which is friction for non-technical admins.

The large-directory limitation is real. The README explicitly warns that too many files in a single directory hurts performance [1]. If you’re managing S3 buckets with thousands of objects in one prefix, expect slow listing. This isn’t fixable without changing the underlying Flysystem approach.

The JSON file auth adapter works cleanly for 5–20 users. Past that, you’ll want the database adapter, which means setting up an actual database — adding infrastructure complexity [1].

No LDAP support means any team authenticating against Active Directory or another directory service needs separate credential management for FileGator users [1]. This is a hard blocker for most enterprise environments.

There’s no built-in access log showing who downloaded what and when. If you’re handling files that require access tracking for compliance, you need to add that layer yourself (nginx access logs don’t capture per-file actions cleanly).

Realistic time estimate for a PHP developer on a fresh VPS: 1–2 hours including nginx configuration, PHP setup, and permissions. Using Docker and following the docs at https://docs.filegator.io: 30–60 minutes [4].

---

Pros and cons

Pros

• MIT license. Embed it, white-label it, ship it to clients — no commercial agreement needed [1][2].
• Flysystem storage adapters. Moving from local disk to S3 is a config change. The same UI works across every supported backend [1][5].
• No database required. JSON-file user storage keeps the infrastructure minimal for small installs [1].
• Chunked uploads. Reliable large-file upload regardless of PHP’s upload limits — built on the proven Resumable.js library [1].
• Clean Vue.js frontend. The demo at https://demo.filegator.io shows a modern interface, not an aging PHP admin panel [3].
• Per-user home folders with RBAC. Multiple users can share the same FileGator instance with isolated, permission-controlled storage areas [1].
• Bulk operations. Users can download multiple files and folders as a single zip — the “grab everything” use case works [1].
• WordPress auth integration. If your team already has WordPress accounts, you can use them as the auth backend [1].

Cons

• Small community, effectively one maintainer. At 2,924 stars, if the maintainer steps back, the project stalls [1].
• No LDAP/SAML/SSO. Enterprise auth not supported — hard blocker for Active Directory environments [1].
• No audit logging. No built-in record of who accessed or downloaded what. Not suitable for compliance-sensitive use cases without custom work [1].
• No sync client. Browser-only. Files don’t sync to local machines. Not a Dropbox replacement if offline access matters [1].
• No file versioning. Overwriting is permanent. No version history, no trash or recovery [1].
• PHP dependency. Requires a PHP-capable server. Docker helps, but it’s additional mental model overhead compared to single-binary Go tools like FileBrowser.
• Large directory performance. Explicitly documented as degrading with too many files in one directory [1].
• Storage config requires file edits. No UI for managing storage backends — adding a new S3 bucket means editing PHP files [1].
• No file preview beyond basics. Text and images work; PDF and office documents typically won’t render in the browser UI [1].

---

Who should use this / who shouldn’t

Use FileGator if:

• You need a browser-based file manager for a small team (2–50 users) and don’t want the operational overhead of Nextcloud.
• You’re wrapping an S3 bucket or FTP server in a usable UI for non-technical collaborators.
• You’re replacing FTP for file uploads from field workers, clients, or students.
• You need per-user home folders with different permission levels on shared storage.
• You’re comfortable with PHP + nginx, or willing to use Docker.
• You want an MIT-licensed tool you can embed or white-label in a product.

Skip it (pick FileBrowser instead) if:

• You want a simpler single-binary deployment without PHP. FileBrowser is written in Go, ships as one binary, has a similar feature set, and is easier to deploy.
• You’re running a personal instance where RBAC and multi-user support is unnecessary overhead.

Skip it (pick Nextcloud instead) if:

• You need desktop and mobile sync clients.
• You need collaborative document editing, CalDAV, or CardDAV.
• Your team requires LDAP/SAML authentication.
• You have the server resources (Nextcloud wants 4GB+ RAM in practice).

Skip it (pick Seafile instead) if:

• File synchronization and version history are the primary requirement.
• You need a full audit trail for compliance.

Stay on Dropbox/Drive if:

• Your team needs mobile apps and offline sync.
• You don’t have anyone to manage a Linux server.
• File sharing volume is low enough that the SaaS cost doesn’t hurt.

---

Alternatives worth considering

• FileBrowser — The closest direct competitor. Go binary, no PHP, similar feature set. Simpler to deploy and maintain; slightly less flexible on storage adapters. Compare these two directly before committing to either.
• Nextcloud — The full-featured option. Sync clients, mobile apps, CalDAV, collaborative document editing, LDAP. Significantly heavier to run and maintain. Right tool if you need a complete Dropbox replacement.
• Seafile — Focused on file sync and versioning with good desktop clients. Less useful as a “shared folder browser”; better when sync is the priority.
• Pydio Cells — Enterprise-positioned, supports LDAP and SSO, written in Go. Overkill for small teams; worth evaluating for 50+ users with governance requirements.
• MinIO Console — If the specific use case is managing S3-compatible object storage, MinIO with its console is purpose-built and more capable for that narrow job than a general file manager.
• Samba + web client — For purely internal network access without the web exposure requirement, a Samba share is simpler. FileGator makes sense when external access or a clean multi-user UI matters.

For a non-technical team that needs to share files without Dropbox costs, the realistic shortlist is FileGator vs FileBrowser vs Nextcloud. FileGator wins if S3 adapter support or multi-user home folders are the deciding factors. FileBrowser wins if deployment simplicity matters most. Nextcloud wins if sync clients are non-negotiable.

---

Bottom line

FileGator does one thing well: it puts a clean, multi-user browser interface in front of your storage. If you have files in S3, on an FTP server, or on local disk, and you need non-technical people to interact with them through a browser with proper access controls, FileGator is a direct $0-software solution. The MIT license means no commercial restrictions. The Flysystem adapter layer means switching storage backends is a config edit. The chunked upload system handles large files reliably. The trade-offs are equally clear — no sync client, no LDAP, no audit logs, no file versioning, and a smaller community than comparable tools. But for the specific problem it solves, it solves it with minimal infrastructure overhead. If your team is paying $100+ per month for Dropbox Business primarily to share files through a browser and nobody actually needs the sync client, a $6 VPS and a FileGator install is the obvious math.

---

Sources

1. FileGator GitHub Repository — README, feature list, limitations, use cases, and license. https://github.com/filegator/filegator (2,924 stars, MIT license)
2. FileGator Official Website — Project overview and download. https://filegator.io
3. FileGator Live Demo — Read-only demo instance showing the UI and guest account functionality. https://demo.filegator.io
4. FileGator Documentation — Installation guides, configuration reference, Docker deployment. https://docs.filegator.io/
5. Flysystem — PHP File Storage Library — The underlying storage adapter library powering FileGator’s multi-backend support. https://github.com/thephpleague/flysystem

Independent third-party reviews of FileGator were not available during research for this article. All feature claims, limitations, and use-case framing are drawn from the project’s own documentation, README, and primary website.