Squarespace review: still the safest default, still the most opinionated

The question worth asking about a website builder in 2026 is not what it looks like when you finish building it. Every serious platform can produce something clean now — the design gap that used to separate the builders has mostly closed. The question that actually predicts whether a site survives is what happens fourteen months later, when the person who built it is busy with something else and a colleague who has never opened the editor needs to change one sentence on the homepage. Most of what makes Squarespace worth its price shows up exactly there, and almost none of the reviews written about it are testing for it.

We rebuilt a client site on Squarespace as part of a wider comparison of the builders worth paying for this year, then kept using it past the point most reviews stop — past launch, into the part where someone other than the builder has to touch it. That second phase is where this review lives.

Before getting into Squarespace specifically: if the site in question is one person's page rather than a business with a page tree, reach is worth knowing about first, because it solves a different problem than Squarespace does and solves it faster. You upload a CV and a photo, answer a short form, and reach composes a finished one-page site — generated in about twenty seconds, live on a free subdomain in under two minutes. It has no CMS, no e-commerce and no HTML export, so anything with a blog, a shop or more than one page needs Squarespace or something like it instead. But for a freelancer or consultant who needs one page and nothing to maintain, it removes a step Squarespace never tries to remove: the blank canvas.

Fluid Engine, two years on

Squarespace replaced its old grid-and-block editor with Fluid Engine across the whole platform, and the honest verdict after two years of using it on real projects is that it fixed one problem badly needed fixing and introduced a second one nobody asked for.

The fix: free positioning. The old system forced every element into a rigid stacked grid, and getting an image to overlap a text block or sit off-centre required fighting the layout engine or dropping into custom CSS. Fluid Engine lets you place, resize and layer elements the way Wix always has, and for anyone coming from a design background it is a real improvement — you can finally build a hero section that looks like it was designed rather than assembled from stock rows.

The cost is responsiveness, and it is not a small one. Every layout in Fluid Engine has to be set independently for desktop, tablet and mobile. Nothing here inherits automatically from what you built on desktop the way the old grid did by default. Move an image on desktop and the mobile version does not move with it — you go and reposition it a second time, on a second breakpoint, by hand. On a five-section homepage that is not a big deal. On a site with real content — the kind with a dozen pages, each with several free-form sections — it is the single biggest time cost of building on Squarespace now, and it is invisible until you preview on a phone and notice half your sections have drifted.

The net effect: Fluid Engine gave design control to people who know what to do with it, and gave everyone else three layouts to maintain instead of one. That is a fair trade for a design-conscious solo builder. It is a genuine tax on anyone maintaining a larger site alone.

Where the CMS claim is actually true, and where it stops being one

Squarespace calls itself a CMS in its marketing, and for one content type it earns that label without qualification: the blog. Posts have tags, categories, a scheduling system, author attribution and an RSS feed that works without configuration. You can filter a blog page by category, feature specific posts, and the underlying data — title, body, tags, publish date — is genuinely structured rather than a page pretending to be a list. Events work the same way, as a real collection with dates and locations rather than a manually maintained page.

That is where it stops. Squarespace's collections are a fixed set of types — blog, events, products, portfolio — not a schema you define yourself. There is no way to create a custom content type with your own fields: no "case study" collection with a client name, an outcome figure and three images in a defined order, reused consistently across pages. If your site needs that kind of structure — a directory of team members with role and department as separate filterable fields, a resource library tagged by industry and format — you are simulating it with blog posts and tags, and the simulation shows.

This is the actual dividing line for whether Squarespace is a CMS for your purposes, and it is worth being precise about it because "Squarespace has a CMS" gets repeated as if it answers every case. It answers the blog case. It does not answer the custom-data-structure case, and no amount of Fluid Engine positioning changes that, because the constraint sits in the data model, not the layout.

Commerce: fine for a handful of products, wrong above that

Squarespace's commerce tools handle what they were built for cleanly: a boutique with a few dozen products, each with a handful of variants, shipped through standard carriers with tax handled by their built-in calculator. Product pages look considered without extra work, checkout is unremarkable in the way checkout should be, and inventory tracking at that scale needs no workaround.

Push past that — real variant combinations across size, colour and material; inventory synced from an external warehouse system; subscription products with more logic than a flat recurring charge — and you are fighting the platform rather than using it. This is not a defect so much as a scope decision Squarespace made deliberately: it is commerce for a storefront, not commerce for an operation. The moment a business needs the second thing, moving to a dedicated commerce platform costs less in the long run than the workarounds cost in the short one.

What editing it actually feels like, eighteen months in

Here is the test that matters more than anything above: hand the published site to a colleague who has never used Squarespace and ask them to fix a typo, swap a photo and update one price. This is where Squarespace's whole design philosophy pays off, and it is the part most reviews skip because it requires actually living with the thing rather than building it once and writing up the first impression.

The editing surface is the same one used to build the site — there is no separate "editor mode" with a smaller, safer feature set, which means nothing is hidden but also means nothing is simplified. A first-time user opens a section, sees the same block-and-panel structure a professional would use, and the constraints that shaped the design during building are still there protecting them: type scale is locked to the site's system, spacing snaps to a grid, colour choices come from the assigned palette. A colleague who has never touched Squarespace before can swap a hero image and change a headline without breaking the layout, because the platform will not let the layout break in the ways that matter. That is the actual case for Squarespace's price: not that it is easy to learn in an afternoon, but that the site still looks considered after a year of edits made by whoever happened to be free that week.

The place it stops being pleasant is anything structural — reordering sections that were built pre-Fluid Engine and behave differently across breakpoints, or touching a page that leans on custom CSS injected by whoever built it originally, which requires Core or above and a comfort with code most colleagues asked to "just fix a typo" do not have. Below that threshold, though, Squarespace is genuinely the calmest editing experience in this category, calmer than Wix's freeform canvas and far calmer than Webflow's box model.

The price, and the line that catches people

Squarespace has no free plan — the company says so outright, and the 14-day trial that replaces it keeps the site private and marks the content for permanent deletion once the trial expires, so a delayed decision costs you the build. Basic runs $19 a month billed annually or $25 monthly, and gets you a free domain for the first year, unmetered bandwidth, up to 1,000 pages, 30 minutes of video storage and two contributors. Core is $29 annual or $39 monthly, Plus is $49 annual or $65 monthly, Advanced is $99 annual or $139 monthly. Prices checked August 2026.

The line that catches people, and it caught us building the comparison site: code injection — the ability to add a line of custom CSS or JavaScript — starts at Core, not Basic. If the only thing wrong with your Basic site is one spacing rule, there is no route to fixing it short of a $10-a-month upgrade. We cover this and the rest of the tier breakdown in more detail in the Squarespace pricing breakdown, and set it directly against Wix's own pricing traps in Squarespace versus Wix.

Tool	Entry price	Billing	Free tier
reach	$4.99/month or $49/year (Premium; free subdomain has no cost)	monthly or annual	yes, permanent, 40 credits
Squarespace	$19/month	billed annually ($25 monthly)	none — 14-day trial only

Who should actually use it

Squarespace is the right tool for someone who wants their site to look like it was designed and is willing to trade some control for that outcome — a studio, a small hospitality business, a photographer, anyone whose blog is genuinely a blog rather than a disguised database. It is also, underrated in most comparisons, the right tool for a site more than one person will edit, because the constraints that frustrate an expert are the same constraints that protect a beginner from breaking the layout.

It is the wrong tool the moment the site needs a content model Squarespace did not anticipate — a directory with custom fields, a catalogue with real inventory logic, anything that needs its own schema rather than a blog post wearing a costume. At that point the fix is not a higher tier. It is a different platform, and no amount of Fluid Engine flexibility changes what sits underneath it.