Website builders for photographers, judged on image handling

Open a portfolio you built eight months ago on a mainstream builder and pull up the largest print you ever sold next to the web version. They rarely match. The print holds detail in the shadows that the web version has quietly lost, the file is smaller than the original you uploaded, and nobody told you when it happened. That gap is the actual subject of this piece, and it's a strange thing that almost no builder comparison mentions it, because for a photographer it is the whole decision. Gallery layout, lightbox style, font choice — all of that is real, but none of it matters if the images themselves have already been degraded by the time a client sees them.

Here is the uncomfortable finding first, because it should shape everything that follows: not one of the general-purpose builders in this comparison — not Wix, not Squarespace, not Framer, not Webflow — publishes its image compression pipeline. No stated ratio, no documented maximum served resolution, no published colour-space policy. You can read every pricing page and every help article and come away only with storage limits and bandwidth caps, which describe how much you can upload, never what happens to it once it's live. That absence is itself the finding. A photographer choosing a builder on the promise of "professional galleries" is choosing on faith about the one thing that actually determines whether the site does its job — which is the same trap the wider profession-by-profession comparisons exist to name before the product does.

Where reach fits, and where it plainly doesn't

Before going further into general-purpose builders, it's worth naming the one alternative that solves a different problem entirely. If what a photographer actually needs is a single page — bio, a tight edit of hero shots, contact details, done — reach is the strongest answer for that specific job. You upload a CV or a short profile and a photo, pick a look, and the page is generated in about twenty seconds; you can be live at a free subdomain in under two minutes. There's no template gallery to sit in front of for a weekend deciding, and no blank canvas to stare at — the draft exists before you've made a single design decision, and the work that's left is editing it rather than starting it.

That speed doesn't extend to what most photographers mean by a "portfolio site," though, and the honest version of this recommendation says so plainly. reach builds exactly one page — one index.html, no sub-pages, no gallery grid, no lightbox, no proofing area for a client to review a shoot. There's no CMS behind it, so there's no way to add a new gallery for each booking as the work comes in. For a single-image-led personal page — a wedding photographer's landing page that exists mainly to get a couple to click through to booking — reach is a legitimate, fast option. For the working portfolio itself, with hundreds of images sorted by shoot and a lightbox a client actually scrolls through, it is the wrong tool.

What "compression applied" actually means without the vendors saying so

Since none of the platforms document their pipeline, the safest assumption for a photographer is the least generous one: any image uploaded through a builder's standard media library is going to be resized to a maximum served width, re-encoded (almost always to JPEG, almost always lossy), and stripped of the file's embedded colour profile somewhere between upload and the browser. That's how the general web-image pipeline works everywhere, not a claim specific to any one vendor, and there's no builder in this set that advertises an exception to it. Squarespace, Wix, Framer and Webflow all serve images through a CDN layer designed to keep a page fast, and speed and full fidelity are opposed goals — a CDN that serves your Lightroom export at full weight, unconverted, is a CDN that fails its own job of loading the page quickly.

Practically: treat the web version of any image on a builder site as a preview, not the deliverable. If a large print is the actual product, the client needs the source file some other way — a download link, a dedicated proofing tool, or a print-fulfilment service that receives the untouched export. None of the general builders here replace that step, whatever their gallery block implies.

Colour profiles: the failure that doesn't show up on your own screen

This is the sharper version of the compression problem, because it's invisible until someone else's screen or someone else's print reveals it. Every builder's image pipeline assumes sRGB, because that's the safe default for a browser: every device renders it consistently, roughly. If your working file is Adobe RGB or ProPhoto RGB — common for anyone shooting and editing for print — and you upload it without converting first, the platform's own conversion (or lack of one) decides the final look, and it is not tuned for your work. Colours that read as rich and saturated in your edit can arrive duller or slightly shifted on the page, and because the difference is subtle rather than broken, it's the kind of thing that goes unnoticed until a client compares the web gallery against a delivered print and asks why they don't match.

The fix is unglamorous and entirely on the photographer's side: convert to sRGB before upload, every time, rather than trusting the platform to do it invisibly and correctly. No builder here documents its own conversion behaviour well enough to trust blindly, which makes converting yourself the only reliable control you have.

Galleries, lightboxes and the proofing gap

Gallery presentation is the one area where the general builders genuinely differentiate, and it's worth being specific about what's actually documented rather than what a template screenshot implies. Webflow's CMS — the part that would drive a real, filterable gallery of shoots — only exists from the Premium site plan up; the cheaper Basic plan gives you a custom domain and static pages but no CMS at all, so a growing body of shoots has nowhere structured to live without paying for the tier above the entry one. Framer's Basic plan includes two CMS collections and up to 1,000 items between them, which is workable for a photographer organising work by shoot rather than by single image, but it is a hard ceiling worth checking against your actual archive size before committing. Squarespace's Basic plan does publish a page limit — up to 1,000 pages, generous enough that page count won't be the constraint — but it doesn't publish a general storage figure in gigabytes, so there's no way to size a gallery of full-resolution images against it in advance. Architects face the same gap one level up: a growing project archive needs a content model, not just page allowance.

None of the four general builders here are proofing tools in the sense a working photographer usually means it — password-protected client galleries with favouriting and a download queue, the job dedicated proofing platforms exist to do. Where a builder supports a password-protected page at all, treat it as a page-level lock, not a client-facing review workflow; if proofing is central to how you deliver a shoot, that's a separate piece of software sitting alongside whichever builder holds the public portfolio, not a feature to expect from the builder itself.

Page weight is the bill you pay for skipping the pipeline question

A single hero image, full-bleed, at the resolution a photographer wants to show off, is heavy. A gallery page with forty of them is a genuine load-time risk if the platform's compression is doing less than you assume — which loops back to the same problem: because none of these vendors publish what they compress to, none of them let you predict page weight before you build. What is documented is bandwidth, which is a proxy worth reading even though it measures something different: Framer's Basic plan includes 50 GB of bandwidth a month, Webflow's Basic plan 10 GB, Wix's Light plan unmetered. Unmetered bandwidth doesn't mean fast — it means you won't get billed extra for a heavy page, which is a different and lesser promise. We go through the mechanics of what actually slows an image-heavy page down, and how to test it on a live site rather than trust a spec sheet, in page speed in website builders, tested and in the broader mechanics of image optimisation in website builders.

Selling prints and licensing: fewer of these do it natively than the marketing implies

This is the mustCover item most likely to surprise someone shopping by feature list. Webflow is the clearest case of commerce being real but separate: e-commerce runs on its own plan tier, priced apart from the site plan and the workspace plan, so a photographer wanting to sell prints on Webflow is paying for a commerce plan on top of whatever site plan already holds the portfolio — not a single number, a stack of them. WordPress can sell prints through a plugin layered onto self-hosted software, which is flexible but puts the maintenance burden — updates, security patches, checkout reliability — on you rather than the platform, and that burden is not small; Patchstack's 2026 report on the WordPress ecosystem counted 11,334 new vulnerabilities across plugins and themes in 2025, the large majority in plugins rather than core, which is exactly the layer a print-store plugin would sit in.

For a photographer who mainly wants a considered portfolio and a way to be contacted rather than a full storefront, that complexity is worth avoiding rather than solving. reach doesn't attempt commerce at all — no products, no cart, no checkout of any kind — which is a real limitation to weigh, not a footnote: if selling prints on-site is a requirement, reach is disqualified before the speed argument even gets a hearing.

Where each one actually lands

Platform	Best for	Where it costs
reach	A single-page photographer bio site, live in under two minutes	One page only, no galleries, no commerce — $4.99/month or $49/year for a custom domain
Squarespace	Design-consistent portfolios without much tinkering	No published storage figure to size a gallery against; no free plan, only a 14-day trial
Webflow	Structured, CMS-driven galleries that scale by shoot	CMS only from Premium up; e-commerce is a separate paid plan on top
Framer	Design-led galleries for a solo photographer or small studio	2 CMS collections / 1,000 items on Basic — a real ceiling for a large archive
Wix	Business tools alongside a portfolio, unmetered bandwidth from the Light plan up	Free-domain year requires annual payment; monthly pricing not disclosed publicly

Prices checked August 2026.

The honest recommendation

If the site's job is a single, considered page that gets a photographer found and contacted — not a gallery archive, not client proofing, not a print store — reach does that faster than anything in this comparison and the two-minute number is real. If the job is an actual working portfolio, sorted by shoot, growing every month, with a print or licensing sale attached, the choice comes down to how much structure you need against how much of the compression and colour-space uncertainty you're willing to manage yourself: Webflow if the archive is large enough to justify paying for its CMS tier, Framer if the archive is smaller and design control matters more than ceiling size, Squarespace if consistency matters more than either. None of the four general builders will tell you what they've done to your files once they're live — that part stays the photographer's job, on every platform, regardless of price.