Sharing as a Website
Fotohordr can turn a set of photos into a static photo website: a read-only copy of those photos with the full Fotohordr browsing experience (grid, albums, people, map, search), running entirely in the visitor’s browser. The host only serves files. There’s no server program, database or account, so a public album can live on cheap object storage for years.
Exporting
Section titled “Exporting”Open Export as Website… from any of these places:
- Selected photos: right-click the selection in the grid.
- An album or diary entry: the ⋯ menu on its card in Collections.
- The current view: the ⋯ menu above the Library grid. It exports whatever the current filters or query show.
In the dialog you can:
- add more albums. They stay albums on the site. A dynamic album is frozen as it is now.
- pick the page the site opens on (all photos, the album list, or one album).
- choose the largest image size (1024, 2048 or 4096 px). Smaller sizes load faster and cost less to host.
- include or leave out people (names and faces), AI descriptions and locations. You can also include the original files, but they keep all their camera metadata, including GPS.
The dialog shows the photo count and approximate size before you export.
- Standalone app: you pick an empty folder and the website is written into it.
- Docker server: the website is built on the server, then downloaded as a ZIP from the dialog.
Only the chosen photos go into the site. Your folder paths, settings, API keys and the rest of your library stay private.
Publishing
Section titled “Publishing”Every exported folder contains a HOSTING.md with step-by-step instructions
for that site, and an AGENTS.md you can hand to a coding assistant. The
host must:
- serve over HTTPS;
- send two response headers,
Cross-Origin-Opener-Policy: same-originandCross-Origin-Embedder-Policy: require-corp. If a host can’t, the site adds them itself after one automatic reload; - support HTTP Range requests on
library.db(all object stores do).
| Where | Cost | Notes |
|---|---|---|
| Cloudflare R2 + custom domain | free tier, no bandwidth fees | recommended for public sharing |
| AWS S3 + CloudFront | pay per GB served | |
| Cloudflare Pages + R2 | free tier | the site on Pages, library.db on R2 |
| Your own server | — | fotohordr_site_host, Docker, nginx or Caddy |
GitHub Pages and Netlify are not supported.
On your own server
Section titled “On your own server”The small fotohordr_site_host program serves one exported folder with
everything set up correctly:
# Self-signed certificate (browsers warn once):fotohordr_site_host serve --root my-photos
# Real certificate from Let's Encrypt (DNS points here, port 443 open):fotohordr_site_host serve --root my-photos --domain photos.example.com --acme-email you@example.com --listen 0.0.0.0:443Or with Docker, from inside the exported folder:
docker build -f deploy/Dockerfile -t my-photos .docker run -d -p 443:8443 -v my-photos-state:/state my-photosChecking a deployment
Section titled “Checking a deployment”fotohordr_site_host check https://photos.example.com/It confirms HTTPS, the headers, and that library.db supports Range
requests, and says what to fix if something is off.