HFS trusts localhost by default and lets a query string log you in, which is the same design decision twice
HFS is a web file server for your computer. Share folders or even a single file thanks to the virtual file system.
At a glance
- What is it?
- rejetto/hfs is a web file server you run on your own machine so folders or a single file can be opened in a browser from another device, with accounts, resumable transfers, a virtual file system and plugins on top. Its container image downloads a prebuilt Linux binary rather than installing Node, and its manifest version trails the alpha tags currently shipping.
- Who is it for?
- HFS fits one job well: getting a folder or a single file out of your own disk to a browser on another device, with optional accounts, throttling and a plugin for the rough edges. It does not fit a deployment where the admin panel must be reachable safely from a network you do not control, because the panel takes an unauthenticated request from localhost by default and the readme documents a query string that logs a browser in from a URL.
- Can I use it commercially?
- Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
- Is it still maintained?
- Yes. The repository last received commits 5 days ago.
- What is it written in?
- Mainly TypeScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- rejetto/hfs4,003 ★ · +86
| Repository | 2026-09-24 | 2026-11-15 |
|---|---|---|
| rejetto/hfs | 3.9k | 4k |
86 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The admin panel needs no password from localhost, and you can turn that off
The first thing to know about running this is what it trusts by default. By default HFS does not require a login when you reach the admin panel from localhost, which is convenient on a desk and dangerous the moment something else can make requests from that machine. The readme gives the switch as a console command inside the running program:
config localhost_admin falseThe same console is where you recover an admin account when no browser will open, by typing create-admin followed by a password, with the note that this is the HFS console and not an operating system shell. If you cannot reach that console at all, which is the normal case when running as a service, there is a file route instead: edit the config to add the account, or generate it with a shell command, echoing create-admin with the password into config.yaml. Three different recovery paths, one of which requires no editor and no console.
The container downloads a release zip and never installs Node
The container image is not a build of the source tree. It starts from a slim Debian base, installs certificates, curl and unzip, and then downloads a release archive whose name is assembled from two build arguments: the version and the target architecture. The architecture is mapped explicitly, amd64 becoming x64 and arm64 staying arm64, and any other value ends the build with an unsupported architecture error rather than a confusing download failure. The archive is unzipped in place and the zip is deleted. So the container is a thin wrapper around the same zip you would download by hand, which means a release tag that is missing or renamed breaks the image immediately. The entrypoint script it writes sets the update check off, which is what the DISABLE_UPDATE variable exists for, and it bootstraps a configuration file when one is not already present.
Two environment variables set the container admin password and the older one wins
This is the sharpest edge in the installation documentation. Two variables can create the first admin account in a new container, and they do not behave the same way. The newer one, HFS_INITIAL_ADMIN_PASSWORD, is documented as taking only the password, and it is used only at the moment the configuration file is created; after that you are told to manage the password inside HFS itself and keep the configuration volume persistent. The older one, HFS_CREATE_ADMIN, takes precedence whenever it is non-empty, and by default it reapplies its password at every container start. The entrypoint contains the logic for this, unsetting the legacy variable only when the new one is set and the legacy one is empty. The consequence for a volume that was created before the newer variable existed: changing the new variable does nothing, because the old one is still winning.
A URL fragment can log a browser in, and the readme publishes the syntax
A list of undocumented-in-the-breadth URL features sits under a heading about hidden features, and several of them are authentication or discovery surfaces rather than conveniences. Appending a login parameter with a user and password logs the browser in automatically, which means a URL containing credentials can end up in history, in a shared link, or in a screenshot. A fragment opens the login dialog on demand. A search parameter runs a query at startup, and two more parameters restrict results to files or to folders, so a shared link can probe which of the two exists. A parameter asking for the basic interface returns a stripped page for older browsers, applied automatically when such a browser is detected. Another forces a language code on the URL. On the desktop side, shift-clicking a file plays it in the integrated media player, and right-clicking the update check accepts a URL of a version to install.
The manifest sits at 3.3.4 while the alpha tags publish after it
The published releases and the version in the manifest are not the same thing at any given moment. The three most recent tags are an alpha on 2026-09-26, a stable 3.3.4 on 2026-09-30, and another alpha the next day, so the two lines interleave rather than one following the other. The manifest still reads 3.3.4, which is the stable release, so anyone installing from source gets the stable line while the newest download is an alpha. The readme encourages using beta versions and giving feedback, with the trade stated plainly: more problems, more features. What the build does with the version is worth noting, because the server build step compiles the TypeScript, then copies a fixed set of files into the output directory, including a central configuration file, the readme, the licence and the icon, then removes any leftover .DS_Store or storage directories and runs a post-build script.
Four workspaces, one dev proxy pair, and an end-to-end suite on Playwright
The repository is a monorepo with four workspaces declared in the manifest: admin, frontend, shared and a grid form library. Development runs the server under a watcher with a development flag set, and two variants exist, one where the frontend and admin are proxied through fixed ports, 3005 and 3006, and one that starts both workspaces alongside the proxied server. Testing prepares a working directory by copying a configuration file and a sample text file into it, then launches the compiled server against that directory with debugging on. End-to-end tests are configured through a Playwright config file, and an OpenAPI description sits at the root next to a separate security policy file and a developer guide for plugins. One detail explains more than the rest: the postinstall step runs patch-package, and a patches directory is committed, so dependencies are modified at install time rather than forked.
Five install routes, and a Node fallback only for the platforms with no zip
There is a downloadable zip for each supported operating system, listed as Windows, Linux, macOS, FreeBSD and Android, with Windows 10 or Server 2019 as the stated minimum. The zip is unzipped and the hfs executable launched, and a browser opens itself on localhost. There are four other routes. Homebrew is a single command. Docker and service installation both point at wiki pages rather than being documented inline. And for anything that cannot run the binary, including Linux ARM and other unlisted platforms, there is a fallback: install Node.js between version 18 and 24 and run the package with npx, optionally at the latest version, with a pointer to the node-gyp requirements if it fails. That route stores configuration in a .vfs directory under your home directory, which is a different location from wherever the binary build keeps it.
The virtual file system is the product, not a storage layer
Most of the feature list is not about moving files, it is about deciding what exists and who may see it. The virtual file system is what lets a single file be shared as if it were a folder tree, and it is the same structure accounts and permissions are applied to, so limiting access to files means arranging them. Around that sit the operational features: real-time monitoring of live connections, a speed throttler, a geographic firewall, virtual hosting, reverse-proxy support, and a dynamic DNS updater so the address does not have to be typed. Transfers are resumable in both directions, folders download as a zip archive on demand, and files can be deleted, moved and renamed from the browser. Extensibility is by plugin, with anti-brute-force, thumbnails, LDAP and themes named as examples, and the front-end can be replaced with your own HTML, CSS and JavaScript. Translations ship for some languages and are installable from the admin panel for the rest.
Editorial conclusion
HFS fits one job well: getting a folder or a single file out of your own disk to a browser on another device, with optional accounts, throttling and a plugin for the rough edges. It does not fit a deployment where the admin panel must be reachable safely from a network you do not control, because the panel takes an unauthenticated request from localhost by default and the readme documents a query string that logs a browser in from a URL. Three things to check before you expose it. Whether you have turned off that localhost exemption, with the console command given in the readme, because it is on out of the box. Which of the two Docker admin password variables you set, since the older one silently takes precedence and is reapplied at every container start unless the config volume is managed in the app instead. And which build you are running, since the manifest sits at a stable version while alpha tags publish after it.
Frequently asked questions
what is rejetto hfs
It is a web file server that runs on your own computer and shares folders, or even a single file, through the browser on another device. Files come straight from your disk with no upload step, and the project adds a virtual file system, accounts with per-file limits, resumable transfers, zip downloads of whole folders, a speed throttler, a geographic firewall, plugins and a multi-language front-end. It is licensed GPL-3.0.
How do I install hfs on a machine with no prebuilt binary?
Install Node.js between version 18 and 24 and run npx hfs@latest, where the @latest part is optional and only keeps you current. If that fails, the readme points at the node-gyp installation requirements as the likely cause. Configuration and other files from that route are stored in a .vfs directory under your home directory.
Why does my hfs Docker container ignore the password I set?
Two variables can set the initial admin password and the older one wins. HFS_CREATE_ADMIN takes precedence whenever it is non-empty and by default reapplies its password at every container start, while HFS_INITIAL_ADMIN_PASSWORD is used only when the configuration file is created. If the older variable is still present from an earlier image, changing the newer one has no effect.
Does hfs need a password to open the admin panel?
Not by default when you reach it from localhost. The readme states that HFS does not require a login for admin-panel access from localhost, and gives the console command config localhost_admin false to disable that behaviour. If no browser opens on the machine, you can create an admin account by typing create-admin with a password in the running HFS console, which is not an operating system shell.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/rejetto-hfs)Star history chart for your README
[](https://hysenlabs.com/projects/rejetto-hfs)Was this useful?