Squarespace Mojave Template: It's Brine, and What That Means

Mojave is a Squarespace version 7.0 template, and it is one of 47 members of the Brine family. We verified it in August 2026: mojave-demo.squarespace.com reports "templateVersion":"7" and template ID 55f0aac0e4b0f0a5b7e0b22e — the Brine family ID. That single fact is the most useful thing anyone can tell a Mojave owner, because it means every Brine tutorial, every Brine CSS snippet and every Brine limitation applies to your site exactly as written.

Should you stay on Mojave, restyle it, or move to 7.1?

Mojave is a Brine template

Squarespace's Brine family guide lists 47 templates, and Mojave is one of them. We confirmed the codebase directly rather than relying on the list: mojave-demo.squarespace.com returned HTTP 200 in August 2026 and reports the Brine family template ID 55f0aac0e4b0f0a5b7e0b22e — the same ID reported by brine-demo and rally-demo.

Brine is the largest family in Squarespace version 7.0 by a wide margin. Forty-seven members. The next biggest, York, has nine. Forty-five of the 47 are still installable; only Lincoln (retired April 2017) and Custom Template (retired December 2019) are discontinued, and Mojave is neither.

Three practical consequences:

1. A Brine CSS snippet works on Mojave, unchanged. .Header-branding, .Index-page, .Intro and every other Brine class name is present on your site. When a page offers "Custom CSS for Mojave", what it is actually offering is Brine CSS.

2. Search "Brine", not "Mojave". You will find an order of magnitude more material and all of it applies.

3. A template detector will report your site as "Brine", and it is not wrong. templateId identifies the family, never the individual template. That is also why no detector can tell Mojave apart from Hyde or Margot.

Switching between Brine members unlocks nothing. Installing Brine instead of Mojave gives you a different starting palette, a different font pairing, different default header layout choices and different placeholder images. Every one of those is a site styles value you can change in a few minutes.

The full 47-name roster is in the Squarespace Brine family templates guide, and the list of Squarespace 7.0 templates covers all 121 templates across the 22 families.

What the Squarespace Mojave template does well

Everything below is Brine family behaviour, so it is true of Mojave and of the other 46.

A two-part header. Brine splits the site header into a top header and a bottom header, and you place branding, main navigation, secondary navigation, cart, search and social icons into either. The bottom header can carry a background image and an intro area. This is the most configurable header in Squarespace version 7.0 and the single reason most 7.0 template shops built on Brine.

The intro area. A block-editable region that sits over the banner, so you can put text blocks, button blocks and forms directly on top of a full-bleed image. No other version 7.0 family has it.

Parallax scrolling. Brine and the discontinued Marquee family are the only two version 7.0 families with parallax. Turn it on at Site styles → Main: overlay → Enable parallax. It is site-wide: every banner on the site gets the effect, and there is no per-page control.

Three navigation menus. Brine and Farro are the only two version 7.0 families with main, secondary and footer navigation.

Stacked index pages that accept gallery pages and layout pages as sub-pages, each section with its own background image and overlay colour.

An Advanced store page — the newest version 7.0 commerce layout, shared only with Farro, Skye, Tremont and York.

Separate mobile style tweaks and a content inset, which most version 7.0 families do not expose at all.

What breaks or feels dated on a Mojave site in 2026

No Fluid Engine. Version 7.0 editing is the classic block editor — a 12-column grid, no overlapping elements without CSS, no drag-anywhere canvas. Fluid Engine is 7.1-only and is not coming to Brine.

No content sidebar. Squarespace's guidance for Brine sites that want sidebar-style content is to add the extra content to the footer. No CSS produces a real sidebar, because the markup is not there.

No header button. Brine has no dedicated header call-to-action button. The documented workarounds are to leave a single link in the secondary navigation and style that menu as a button, or to add a button block to the intro area page by page. Bedford family templates have a native navigation button; Brine does not.

Banners are unsupported in more places than people expect. In Brine, banners do not work on individual blog post, product and event detail pages, on cover pages, or on the main index page itself. On an index you add featured images to the content sections inside the index, not to the index page.

Blog comments are off by default, even when you enable comments on an individual post. Turn them on globally at Blog preferences → Comments settings → Enable comments globally.

Mobile is one inherited layout. Brine gives you mobile-specific style tweaks, which is more than most version 7.0 families, but it is still one layout responding to a narrower viewport. Squarespace 7.1 with Fluid Engine keeps a genuinely separate mobile layout per section at a 767px breakpoint.

Store pages cap at 200 products. That is a version 7.0 limit, not a Brine one. Squarespace 7.1 raises it to 10,000.

Mojave quirks Squarespace documents and is not going to fix

Squarespace maintains a Troubleshooting Brine section, prefaced with its actual position on version 7.0: "Although we still support Squarespace version 7.0, fixing bugs or issues is a lower priority for us while we focus on our current platform, version 7.1."

None of these is a fault in your setup. All are Brine behaving as documented, on all 47 templates.

Is the Squarespace Mojave template still available?

Yes — on an existing version 7.0 site, via Design → Template → Install new template. Mojave is not on Squarespace's discontinued list. Only two Brine members are: Lincoln and Custom Template.

You cannot start a new site on Mojave. The live gallery at squarespace.com/templates returned 198 templates in August 2026, every one of them version 7.1 — we counted them. The old squarespace.com/templates/mojave-demo URL, which still ranks first for this keyword, now serves that generic gallery. Squarespace's own demo, mojave-demo.squarespace.com, is still up and still Mojave.

Watch for the name collision. At least one template shop sells a 7.1 product also called Mojave, and it appears on this SERP. If you are searching for help with your 7.0 Mojave site and land on a page about Fluid Engine sections, you are on the wrong Mojave. Check your own page source: version 7.0 reports "templateVersion":"7" — not "7.0" — and the Brine family ID. Version 7.1 reports the universal ID 5c5a519771c10ba3470d8101.

Version 7.0 has no announced end-of-life, and Squarespace states the move is optional: "Updating your site from version 7.0 to 7.1 is optional." Whether old Squarespace templates are still supported covers the support position in full.

Moving a Squarespace Mojave site to version 7.1

The tool is at Design → Update to Version 7.1. Before you touch it:

1. It is permanent. "After you click Publish update, your site will update to version 7.1 permanently."

2. It caps at 150 pages and errors above 200 products on a store page.

3. Developer mode must be off, and Developer Platform code disappears when you disable it.

4. Custom CSS survives commented out. Remove the comment tags in the CSS editor and save. Selectors written against Brine class names will mostly not match 7.1 markup — and on a Brine-family site that is usually a lot of CSS, because Brine sites tend to be the heavily customised ones.

5. Move index sub-pages out first if you want to keep their SEO titles and descriptions.

What happens to the parts a Mojave site is built from:

Brine sites are among the harder version 7.0 migrations, for two structural reasons. The stacked index flattens rather than converting to a portfolio page, so every sub-page URL is orphaned — compare York and Tremont, whose grid and slideshow indexes become portfolio pages with automatic redirects. And the intro area has no 7.1 counterpart, so every banner with text or a button on it has to be rebuilt as a section.

Audit before you press the button. Export every index sub-page's navigation title, SEO title and description to a spreadsheet — that is the data the tool discards. Enable every disabled sub-page. Screenshot the Site: header, Main: overlay and Site: border tweaks. Count pages and products, and export the Custom CSS.

And the expensive one: changing a page slug on Squarespace creates no automatic 301 redirect, ever. Add the orphaned index sub-page URLs by hand in Settings → Advanced → URL Mappings using the /old -> /new 301 format.

The screen-by-screen version is in the Squarespace 7.0 to 7.1 guide, and the Squarespace 7.0 template comparison chart shows how Brine's feature set compares with the other 21 families. The Squarespace Brine template guide works through this same decision for the family as a whole.

So: stay on Mojave, or move?

Stay if the Mojave site does its job and nothing on your list requires 7.1. Mojave is not discontinued, Brine is the best-supported family in version 7.0, and the update tool will still be there next year.

Restyle if the objection is aesthetic. Fonts, colours, header arrangement, banner heights, overlay opacity and index section backgrounds are all site styles values. Switching to another of the 46 Brine templates unlocks nothing at all.

Move if you need Fluid Engine, courses, video pages, a store past 200 products per page, or an independently editable mobile layout — and go in knowing that the intro area and the stacked index are the two things you will rebuild by hand.

For scale: across 54 Squareko-built client sites measured in August 2026 (Playwright/Chromium lab test, cloud datacenter, unthrottled, single run per site), 53 of 54 run Squarespace 7.1. Version 7.0 is the minority case now, but a working Mojave site is not an emergency.

Most Mojave sites we are sent migrate cleanly on the page content and then need one to two weeks on the structure — rebuilding intro areas as sections, splitting the flattened index back into real pages, and adding URL Mappings for every orphaned sub-page. The exception is the Brine site carrying several hundred lines of family-specific Custom CSS, where you are rewriting the stylesheet as well as the structure: there, starting from a premium Squarespace template built for 7.1 and Fluid Engine is usually the shorter path. The table at the top of this page settles it for most people without spending anything.

FAQ

• What family is the Squarespace Mojave template in?

  The Brine family. We fetched mojave-demo.squarespace.com in August 2026 and it reports "templateVersion":"7" and template ID 55f0aac0e4b0f0a5b7e0b22e, which is the Brine family ID shared by all 47 members. Because templateId identifies the family, a detector tool will report a Mojave site as Brine.

• Is Mojave the same as Brine in Squarespace?

  In code, yes. All 47 Brine family templates run the same codebase, the same class names and the same feature set, differing only in default fonts, colours, header layout choices and demo content — all of them site styles values. Installing Brine instead of Mojave unlocks no features whatsoever.

• Is the Squarespace Mojave template still available?

  Yes, on an existing version 7.0 site via Design → Template → Install new template. Only two Brine members are discontinued: Lincoln, retired April 2017, and Custom Template, retired December 2019. You cannot start a new site on Mojave — the live template gallery returned 198 templates in August 2026, all version 7.1.

• Does the Mojave template have parallax?

  Yes. Brine and the discontinued Marquee family are the only two Squarespace 7.0 families with parallax scrolling. Enable it at Site styles → Main: overlay → Enable parallax. It applies site-wide to every banner with no per-page control. Squarespace 7.1 has no site-wide parallax, only a per-section background image effect.

• Why is my Mojave banner not showing?

  Usually one of two site styles values rather than a missing image. Increase Main → Intro padding (with background image), then check that Main: overlay → Overlay color is not fully opaque — an opaque overlay renders a banner invisible while leaving it technically present. Brine also does not support banners on blog post, product, event or cover pages.

• What happens to a Brine index page in Squarespace 7.1?

  It flattens. All content from enabled sub-pages displays on a single layout page, sub-page SEO titles and descriptions are lost, and links to former sub-pages break with no automatic redirect. Disabled sub-pages do not appear at all, so enable or move everything out before you run the update tool.

Author Bio

I'm Walid Hasan, a Certified Squarespace Expert and Squarespace Circle Platinum Partner with over 12 years of hands-on experience designing and optimizing high-performing websites. Over the years, I've had the privilege of building more than 2,000 Squarespace websites for clients around the world, always focusing on clean design, strong user experience, and conversion-driven results.