Photographers need files served, not a second career in DevOps

Static website hosting for photographers is about galleries, about pages, contact CTAs, and sometimes PDF rate sheets—delivered as HTML and optimized images. If you already export a site from a static generator, a portfolio template, or hand-built pages, StaticHost is a file host: upload the finished tree, open HTTPS preview, then attach your domain and wait for DNS verification before the custom certificate appears. It does not run npm or Hugo for you. It does not include email, a built-in CDN product, or forever-free hosting after a short trial. Plans: Starter $9, Pro $30, Scale $65, Business $130.

You fit this product when visitors request real paths that map to real files. You do not fit when you need a client proofing portal with server accounts, a WordPress blog plugin stack, or a JavaScript router that expects every deep link to fall back to index.html. Here nginx uses try_files $uri $uri/ =404.

Image weight is your storage story

Starter includes 2 GB; Pro 10 GB; Scale 30 GB; Business 100 GB. That is enough for compressed web galleries if you export responsibly (WebP/JPEG at sensible widths, not RAW dumps). Upload the site folder, not your Lightroom catalog. Self-host short looping hero clips sparingly; long video belongs on a video host with an embed.

Publish path:

  1. Build or export locally into a clean folder.
  2. Ensure index.html is at the folder root you zip.
  3. Upload; inspect HTTPS preview on phone and desktop.
  4. Grep for http:// images that will break the padlock.
  5. Point DNS only when preview looks right; wait for verification and certificate.

More context: landing page static hosting, design portfolios, and HTML portfolio hosting.

Contact without pretending the host is a mail server

Photographers need inquiries. StaticHost will not send mail from forms. Wire the contact form to a form SaaS endpoint or mailto: for minimal pages. Host @you.com mail at a mail provider. Do not block launch waiting for inbox features that are out of scope.

Worked example: bakery one-pager with opening hours

A photographer’s side project: shoot for a bakery and gift a one-pager. The page lists weekday hours in an HTML table, shows three optimized photos, and links to an Instagram profile. They write index.html and styles.css locally, drop images into /images, zip with index.html at root, and upload on Starter ($9).

HTTPS preview reveals a typo in Saturday hours; they fix, redeploy, and only then set DNS for crumb.example. Certificate follows verification. The baker updates hours by asking for a text change; the photographer edits HTML, re-zips, redeploys. No CMS. No remote build. No email on StaticHost—the “Order cakes” button links to the baker’s existing form tool.

Same muscle memory applies to the photographer’s own portfolio: multipage HTML, large but compressed images, preview first, DNS second.

Failure to avoid: zipping the parent folder so index.html is nested

The classic 404-on-homepage mistake: you have a folder portfolio/ containing index.html, you zip portfolio itself, and the archive root becomes portfolio/index.html. The host looks for /index.html at the site root, does not find it, and returns 404. try_files $uri $uri/ =404 will not invent a welcome page for you.

Fix: zip the contents of portfolio/ so index.html sits at the archive root. Verify by unzipping to a temp directory and listing the top level before every important upload. Nested zips waste launch mornings more often than DNS does.

When to pick a different product

Need online sales with server carts? Use commerce platforms. Need passworded client galleries with accounts? Use proofing software. Need WordPress and a blog editor for a second brand voice? Use PHP hosting. Need forever-free student hosting? Use a free host; StaticHost’s trial is short, then paid.

Stay when your site is files: HTML galleries, CSS, JS lightbox code that runs in the browser, fonts, and images. Pro ($30) helps if you keep a staging copy plus a client gift site plus your main portfolio. Higher tiers are for volume, not for unlocking CDN or email myths.

Pre-flight checklist for gallery launches

  • Thumbnails and full-size images both present if your lightbox expects both.
  • Alt text written for meaningful photos.
  • No file:// leftovers from local testing.
  • Favicon present as a real file.
  • 404 behavior accepted for mistyped album URLs—or add real 404.html if you want a branded miss page that still is a file.

Album URLs as real directories

Photographers like pretty URLs: /weddings/jordan-alex/ and /editorial/ss26/. On StaticHost those must be real folders with index.html inside (or real jordan-alex.html files linked explicitly). A JavaScript-only router that pretends every path exists will fail under try_files $uri $uri/ =404. Emit the folders when you publish. If you outgrow hand-maintained folders, run a static generator locally and upload its output—StaticHost still will not run that generator for you.

Mobile review on HTTPS preview matters more than on your desktop with cached fonts. Open the preview on your phone on cellular once before DNS. Catch oversized heroes that thrash storage and patience. Starter’s 2 GB is generous for compressed galleries and hostile to RAW archives uploaded by mistake.

Domain order stays fixed: preview TLS, then DNS, then custom certificate. Do not announce the vanity URL in a client email until verification finishes and the padlock is clean. Mixed http:// thumbnails from an old blog export are a common last-minute embarrassment—grep them out while you still only have preview traffic.

FAQ

Will StaticHost resize my images on upload?

No. Optimize locally. The host serves the bytes you send.

Can I use a JS gallery library?

Yes, as static assets. Client-side code is fine; missing files still 404.

Do I get a CDN for worldwide shoots’ audiences?

No built-in CDN product. Optimize assets; add a CDN vendor if you need that SKU.

Is there a free forever photographer plan?

No. Short trial, then $9/$30/$65/$130. Choose another host for forever $0.