Photographers feel hosting limits first because images are heavy. A beautiful gallery that feels snappy on your laptop can crawl on a phone using cellular data — and a 2 GB plan fills faster than a text-heavy brochure ever would. This guide talks about image weight, gallery patterns, and where SiteHost’s Starter storage fits, without pretending a marketing site is the same as a client proofing portal.

Two different products photographers confuse

Public photography website. Your style, selected work, about page, contact form (usually third-party), maybe a blog of finished stories. This is a great fit for file hosting: HTML/CSS/JS plus optimized images.

Client proofing. Logins, watermarks, selection tools, download limits, expiration dates. That workflow usually needs a specialized proofing product. You can link to it from your public site. Do not expect SiteHost to become proofing software. More: website hosting for photographers.

If you only need the public face online, continue here. A wedding shooter who tries to turn a marketing host into a delivery portal ends up fighting permissions, passwords, and support tickets that never belonged in this aisle.

Image weight — the real hosting constraint

Before you pick a host, pick a maximum dimension and compression strategy:

  • Hero images: often 1600–2400px on the long edge is plenty
  • Grid thumbs: hundreds of pixels wide, not thousands
  • Prefer modern formats when your export chain supports them (WebP/AVIF) or well-compressed JPEG
  • Do not upload RAW or full-resolution TIFF to your public gallery folder

Open your gallery folder’s properties. If you are staring at 4 GB before optimization, Starter’s 2 GB ceiling ($9/mo, 1 site) will not fit — and should not, because visitors should not download 4 GB of vanity resolution either. Optimize down; then measure again.

Pro ($30, 3 sites, 10 GB, staging), Scale ($65, 10 sites, 30 GB), and Business ($130, 30 sites, 100 GB, teams) expand storage when you truly need it. Still: performance loves smaller files regardless of plan. A Pro plan full of unoptimized eight-megabyte heroes will still feel slow on a train.

SiteHost has no built-in CDN. For many photography marketing sites, solid compression matters more than a CDN. Optional Cloudflare in front is available if you want caching at the edge later. Skip miracle speed claims; measure your own images. Fast-loading website hosting.

Gallery patterns that behave on static hosting

  • Simple HTML pages with curated images and lightbox JavaScript you already have
  • Separate pages per story rather than one endless megapage
  • Lazy loading if your templates support it — fewer bytes on first paint
  • Contact via Formspree-like tools or mailto with a real address you monitor

Avoid dumping every shutter click into a public folder. Editing is part of hosting success. A portfolio that shows twelve excellent frames beats a folder that shows two hundred “almosts.”

Workflow: export → local check → zip → preview

  1. Export web galleries from Lightroom/Bridge/your tool with a web preset.
  2. Place them in your site structure with relative paths.
  3. Open locally; click through; watch load time on your phone via local network if you can.
  4. Zip with index.html at the root of the archive contents.
  5. Publish on SiteHost; use HTTPS preview (immediate).
  6. Roll back if a gallery path breaks.
  7. Point DNS for yourname.photo when happy; certificate follows DNS verification.

Trial ~1 day, then paid — no forever-free plan. No cPanel, no email included. Keep business mail elsewhere. SiteHost is not a VPS: you do not patch the OS or babysit a certificate cron.

Storage math example

A wedding photographer’s marketing site: 40 hero-quality JPEGs averaging 250 KB after discipline = ~10 MB. Plus HTML/CSS. Trivial on 2 GB. The same photographer’s “full dump” at 8 MB each × 200 images = 1.6 GB for one gallery — will feel slow and leave little room for the rest of the site. Curation is a hosting strategy.

Another common trap: exporting “for print” dimensions into a web folder because the export preset was wrong. Fix the preset once. Name it something obvious like Web-2400-q80 so future you does not guess.

Domain and branding

Use a domain you own. Social profiles supplement; they should not be the only portfolio. Where to host a portfolio website overlaps for design-heavy layouts; photographers should still obsess over byte size more than typographers might.

After DNS verifies and the custom-domain certificate is issued, update Instagram, Google Business Profile, and your email signature with the real URL. Until then, share the HTTPS preview with trusted reviewers only when you must — any public URL can be forwarded.

Choosing a gallery structure before you host

Before you create a SiteHost account, decide how visitors will move through images. A single endless page of fifty full-width photos feels dramatic in a desktop design review and miserable on a phone using cellular data. Story-based pages — “Weddings,” “Portraits,” “Personal work” — let people sample without downloading your entire decade.

Within each story, prefer a grid of compressed thumbnails that open a larger view only on demand if your JavaScript supports it. If you do not have a lightbox script, fewer larger images with thoughtful cropping still beat a dump of everything. Hosting will not invent curation for you; it will only serve what you zip.

If a designer builds the site, ask them to deliver a performance budget: maximum weight for the homepage and for a typical gallery page. Put that number in the brief. It prevents the awkward launch-week conversation where everyone blames “the host” for an 8 MB hero.

Migrating off a social-only presence

Many photographers “host” their reputation on Instagram. That is distribution, not ownership. When you move to a real site, do not attempt a full mirror of every post. Pick twenty images that define your current style. Write an about section that sounds like you. Add a contact path that does not require a direct message algorithm to surface you.

Keep social profiles, but point them at your domain once HTTPS on the custom name works. Until DNS verifies, share the SiteHost HTTPS preview with clients who need to review the new site privately enough for practical purposes — remembering that any public URL can be forwarded.

Backup discipline photographers forget

Your Lightroom catalog and RAW drives are backups of masters. Your web export folder needs a backup too. Keep dated zips of what you published (studio-site-2026-04.zip). If you ever leave a host, you should not have to reconstruct the public site from memory. SiteHost rollback helps with recent publishes; it is not a substitute for your own archive of intentional releases.

Also keep a note of which third-party form endpoint receives inquiries. When you republish a redesign, forms break quietly if the embed snippet was omitted from the new HTML.

Example: portrait photographer launching for busy season

Lina shoots family portraits. Her designer delivers a four-page site with a twelve-image homepage grid. Locally it looks fine on Wi‑Fi. On cellular, the homepage takes eight seconds because each “thumbnail” is still a 3 MB export. She re-exports at 400px wide for the grid and 1800px for lightbox targets, republishes, and the same page feels instant. She stays on Starter ($9/mo) with room to spare. When she later adds a second seasonal campaign site, she moves to Pro ($30) for the extra site slot and staging — not because her images magically needed a CDN.

What SiteHost is not for photographers

  • No built-in client galleries with passwords and downloads
  • No email inboxes for [email protected]
  • No WordPress tutorial or one-click theme stack (that is a different kind of hosting)
  • No VPS shell access

Those exclusions are features for people who want a calm marketing site. Pair SiteHost with a proofing tool and a mail provider and you have a professional stack without renting a server.

Questions people actually ask

Is 2 GB enough for a photography site?

For a curated marketing site with optimized images, usually yes. For archiving original files, no — use backup drives or photo cloud storage, not your public web host.

Can clients select favorites on SiteHost?

Not as a full proofing app. Link out to a proofing service; keep the public site lean.

Should I use a builder that hosts for me?

You can. If you already exported HTML, SiteHost fits. SiteHost is not itself a builder.

Do I need WordPress for galleries?

Only if you want WordPress galleries and plugins. That is a different kind of hosting. Static galleries are valid.

Will a CDN fix huge images?

It can help delivery; it will not shrink a 10 MB hero into a 200 KB one. Optimize first.