Static Web Server

Static Web Server is a fast, cross-platform, single-binary web server for serving static websites and files.

  • Tools & Utilities
  • Web & Publishing
Static Web Server is a fast, cross-platform, single-binary web server for serving static websites and files. Written in Rust with no runtime dependencies, it gives homelab users a lightweight, reliable way to publish landing pages, documentation sites, or static assets from any computer.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server

Other devices

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

76/100 Good

Maintained
100last commit 0 days ago
Popular
682,415 GitHub stars
Easy to install
352 install platforms, install notes
Light to run
502 GB minimum RAM
Security check
100no serious findings, CI, tests

Availability: platform listings confirmed today

GitHub stars
2,415
Open issues
40
Last commit
2026-11-22
Latest release
v2.44.3
License
Apache-2.0
Activity
rising

Checked today - source: GitHub (static-web-server/static-web-server)

Resources & Compatibility

Minimum requirements: 2 GB RAM.

Checked today - source: Docker Hub image tags and published docs

First-install notes

  • Point it at the full public folder path Pass the full path on disk to the folder containing your site files, such as /path/to/project/public, instead of just 'public'. If the static handler does not receive a valid string path, it can throw an error at startup. source
  • Let unmatched requests keep going By default, if no file matches, the request passes on to the rest of your app instead of immediately returning a file error. That matters if your app also has dynamic pages or a single-page app, because those URLs are not files on disk. source
  • Use only allowed dotFiles values If you set dotFiles, choose only allow, deny, or ignore, because other values can trigger a startup error. Dotfiles are hidden files or folders, such as .well-known files, and this option decides whether they are served. source
  • Download Download the prebuilt static-web-server binary from the GitHub Releases page; it is a single file (~4 MB) with no outside dependencies. source

Fetched today - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Should I use v3 for a production instance?

No; the README says v3 is upcoming and in development, while v2 LTS should be used for production.

Is a config file required to run SWS?

No. You can point it at a folder with zero configuration, or customize it through CLI flags, environment variables, or a TOML config file.

Does it support compression for client delivery?

Yes. It can compress text-based files on the fly using Gzip, Deflate, Brotli, or Zstandard, and it can also serve pre-compressed .br, .gz, and .zst files directly.

Can I get structured logs to a file?

Yes. It supports structured JSON logging via --log-format and file-based log output via --log-file.

Does directory listing include download access?

Yes. Optional directory listing can output HTML and JSON, and it also includes a .tar.gz download.

Does it have built-in authentication?

Yes. Basic Authentication is included in the v3 feature list.

Answers sourced from github.com, static-web-server.net

Community

Collected today - public community threads