Disclosure: SquareLocator earns a commission if you buy an Elfsight plan through some of the links on this page (marked as sponsored), at no extra cost to you. It does not change what I recommend, and in this guide the free native option wins for most sites. I am a web designer, not a lawyer, so treat this as practical setup advice rather than legal advice.

Almost every Squarespace site I hand over to a client in the UK or EU needs a cookie banner, and almost every client asks the same question: is the built-in one good enough, or do I need a plugin? The answer matters more than it looks, because a cookie banner is not just a design element. A banner that only shows a message, while analytics and marketing scripts carry on loading in the background, does not do the job most privacy rules expect it to do.
This guide covers the native Squarespace cookie banner, the Elfsight Cookie Consent widget, Common Ninja's free banner, a full consent platform such as Cookiebot, and the small CSS plugins that restyle the native banner. I will be honest about where each one fits, including where a paid widget is not worth it.
Quick answer
For most Squarespace sites, switch on the native cookie banner in the Cookies and Data Privacy panel and keep non-essential cookies restricted. It is free and built in, it is the only option here that Squarespace documents as stopping its own non-essential cookies and some third-party integrations until visitors accept, and it supports accept, decline and manage preferences. Use Elfsight Cookie Consent when you want a more designed notice (a box or bar layout, a cookie icon, your own fonts and colours) and you are not relying on the banner to block scripts. If your site runs several third-party trackers added with custom code and you need visitors to opt in to each category, look at a dedicated consent platform instead.
Elfsight Cookie Consent
Bar or box cookie banner with accept and decline buttons. Free plan available; paid plans from $5 a month billed yearly.
Why a cookie banner is more than a message
Squarespace itself points out that certain laws may require you to tell visitors about cookies and ask for their consent before you use them. In practice, that splits cookie banners into two very different kinds of tool:
- A notice. It tells visitors the site uses cookies and gives them a button to acknowledge it. Nothing changes behind the scenes whichever button they press.
- A consent tool. It holds back non-essential cookies (analytics, marketing, some embeds) until a visitor agrees, and respects them if they decline.
If your visitors are in the UK or EU and you use analytics or advertising cookies, a notice on its own is unlikely to be enough. Common Ninja says this plainly on its own widget page: its banner displays a notice and records that a visitor acknowledged it, and if you need real consent you need a tool that actually blocks scripts. I respect that honesty, and it is the single most useful thing to understand before you choose.
Option 1: the native Squarespace cookie banner (free)
Squarespace has a built-in cookie banner and, on a typical site, it is where I start. Squarespace's help centre describes it as restricting non-essential cookies so that Squarespace and some third-party integrations cannot place them on visitors' browsers until they accept. It will not restrict necessary cookies, which Squarespace notes includes some placed by integrations such as Weglot and Acuity.
How to switch it on
- Open the Cookies and Data Privacy panel in your site settings.
- Switch on the toggle beside Cookie banner.
- Keep non-essential cookies restricted. Squarespace recommends this because some regions require consent before non-essential cookies are placed.
- Choose what visitors can do: accept only, accept or manage preferences, or accept, decline all, or manage.
- Set the position, a dark or light theme, your button labels and your banner text, and choose a layout (Subfooter, Pill or Hidden) that controls whether visitors can change their preferences later.
- Add a link to your privacy or cookie policy page in the banner text.
- Adjust colours and text size in the Cookie Banner panel under site styles. Button and toggle colours follow your Buttons and Colors settings.
If a visitor accepts with the accept-only setup, Squarespace says the banner does not reappear for 30 days.
Pros and cons
- Pro: free, built in, and no extra script to load.
- Pro: the only option in this guide that Squarespace documents as holding back its own non-essential cookies until consent.
- Pro: accept, decline all and manage preferences are all available.
- Con: limited styling. You get position, theme, colours and text, not a fully custom design.
- Con: custom code is your responsibility. Squarespace notes that code you add yourself which places non-essential cookies may need extra work to respect the banner, and it falls outside Squarespace's support.
Verdict: the right default for nearly every Squarespace site, especially if your trackers are Squarespace's own or built-in integrations.
Restyling the native banner with CSS plugins
If the only thing stopping you using the native banner is how it looks, you do not need a different banner. Ghost Plugins has a set of free CSS snippets for the Squarespace 7.1 banner, pasted into Custom CSS: Custom Cookie Title adds a heading, Stacked Buttons stacks accept, deny and manage, and Rounded Corners Style softens the box. There is also a Cookie Icon plugin. Because these only change the styling, you keep the native consent behaviour. If you are new to Custom CSS, my guide to custom CSS in Squarespace shows where the code goes.
Option 2: Elfsight Cookie Consent
Elfsight Cookie Consent is a hosted widget you build in Elfsight's editor and embed on your site. It is one of Elfsight's simpler widgets, and its strength is design control.
What it does
- Two layouts: a Bar that sits at the top or bottom of the page, or a Box aligned left, right or centre.
- Two modes: a simple notification, or a two-button banner with Accept and Decline.
- Custom text, font size and weight, colours and a cookie icon.
- A dedicated field for your privacy or cookie policy URL.
- Prebuilt GDPR message templates. Elfsight's Squarespace page says it helps you meet GDPR and CCPA standards.
- The visitor's choice is stored in their browser, so the banner does not keep reappearing on return visits.
What Elfsight does not describe on either of its cookie consent pages is blocking scripts or cookies before consent, cookie categories, or region targeting. So I treat it as a well-designed notice with an accept or decline choice, not a full consent manager. If you need visitors to opt in before your analytics run, test that behaviour yourself, or pair it with the native banner's restrictions rather than replacing them. Do not run both banners at once, though: two banners on one page is confusing and looks broken.
How to add it to Squarespace
- Open the Elfsight Cookie Consent editor, choose a template, and set your layout, text, policy link and colours.
- Click Add to website for free and copy the embed code.
- In Squarespace, paste it into Code Injection in the footer area, so it loads on every page.
- Save, then open your site in a private browser window to check it appears and that your choice is remembered.
Code injection is included on the Core, Plus and Advanced plans and not on Basic. Elfsight says that on Basic the banner can be added with a Markdown block instead, but I would not rely on that: Squarespace is changing how Markdown blocks handle custom code, and some plugin makers report that scripts placed in them no longer run (see what is changing on Squarespace 7.1). A site-wide banner belongs in code injection, so on Basic the native banner is the safer choice. My beginner's guide to adding plugins to Squarespace walks through both methods. Elfsight says the widget works with Squarespace 7.0 and 7.1, including Fluid Engine.
Elfsight pricing
Prices from Elfsight's pricing page today, single app, US dollars per month billed yearly (monthly billing costs a little more):
| Plan | Price | Views a month | Widgets |
|---|---|---|---|
| Free | $0 | 200 | 1 |
| Basic | $5 ($6 monthly) | 5,000 | 3 |
| Pro | $10 ($12 monthly) | 50,000 | 9 |
| Premium | $20 ($24 monthly) | 150,000 | 21 |
The free plan shows Elfsight branding, and the view limit is the catch for a cookie banner. A site-wide banner loads on every page view, so 200 views a month will run out within days on almost any real site, and Elfsight deactivates a widget when it goes over its limit. Budget for at least Basic. If you already pay for the All Apps Pack for reviews or an Instagram feed, the cookie banner costs you nothing extra, which is where it makes the most sense. My Elfsight pricing guide explains how views are counted.
Pros and cons
- Pro: far more design control than the native banner, with box and bar layouts and a cookie icon.
- Pro: fast to set up, and included if you already have an Elfsight All Apps Pack.
- Con: no documented script blocking or cookie categories.
- Con: every page view counts towards your plan, so the free tier is only good for testing.
Verdict: a good-looking banner for sites that mainly need a clear notice and an accept or decline choice, or for owners already on an Elfsight plan. Not a replacement for real consent blocking.
Option 3: Common Ninja Cookie Banner
Common Ninja's Cookie Banner widget is a free, no-code notice added with one line of embed code. It has a single acknowledgement button, a policy link in the text, ready-made skins, custom colours and fonts, and room for custom CSS. Common Ninja suggests adding it to a footer area or site-wide template with a custom HTML block.
Its own FAQ is clear that, on its own, it displays a notice and records an acknowledgement rather than blocking scripts. Paid plans for a single widget are $33.60, $45.60 or $76.80 a year, mainly for branding removal and higher limits.
Verdict: fine for a simple notice on a site with no tracking that needs consent. For anything more, use the native banner.
Option 4: a full consent platform such as Cookiebot
If your Squarespace site runs a lot of third-party scripts you added yourself (advertising pixels, heatmaps, embedded tools) and you need visitors to opt in to categories such as statistics and marketing, you are into consent management platform territory. Cookiebot is the best-known example. Its pricing page lists a free tier for one domain with up to 50 subpages, and paid Premium plans per domain by page count, with automatic or manual blocking of cookies and trackers, 47+ languages and geotargeting.
The caveat for Squarespace owners: Cookiebot's pricing page lists Wix, WordPress and Shopify integrations, not Squarespace, so you would be installing it with custom code and testing it carefully on a trial site first. For most small Squarespace sites, that is more machinery than they need.
Verdict: worth it for larger sites with heavy third-party tracking. Overkill for a typical portfolio, service or small shop site.
Which cookie banner should you use?
| Your situation | My pick |
|---|---|
| Standard Squarespace site using Squarespace Analytics and built-in integrations | Native cookie banner, non-essential cookies restricted |
| Native banner is fine but looks off-brand | Native banner plus Ghost Plugins CSS tweaks |
| You want a designed notice with accept or decline and already use Elfsight | Elfsight Cookie Consent |
| A simple notice on a site with no tracking to block | Common Ninja or Elfsight free plan (low traffic only) |
| Lots of custom third-party trackers, opt-in by category | A consent platform such as Cookiebot, tested on a trial site |
Things people get wrong
- Running two banners. If you add a widget, switch the native banner off, and make sure the restriction you rely on still makes sense.
- Forgetting other widgets. Chat tools, embedded maps, video and social feeds can set cookies too. If you have added an AI chatbot or a live chat widget, check what it places before consent.
- No policy page. Every option here expects a link to a privacy or cookie policy. Squarespace notes it cannot advise on what that page should say, and you should not assume the banner alone meets your legal requirements.
- Not testing in a private window. Your own browser remembers your choice, so you will not see what new visitors see unless you test in a fresh window.
If you serve visitors in several languages, remember the banner text needs translating too; my guide to multilingual Squarespace sites with Weglot covers how translation works across a site. And if you are still choosing a plan, Squarespace pricing explained shows which plans include code injection. For more widgets worth adding, see my Elfsight for Squarespace review and the best free Squarespace plugins.
Elfsight Cookie Consent
A designed cookie banner for Squarespace 7.0 and 7.1, set up in minutes.
FAQ
Does Squarespace have a built-in cookie banner?
Yes. Switch it on in the Cookies and Data Privacy panel. It can offer accept only, accept or manage preferences, or accept, decline all and manage, and with non-essential cookies restricted it stops Squarespace and some third-party integrations placing non-essential cookies until visitors accept.
Is the Squarespace cookie banner GDPR compliant?
Squarespace says you should not assume the banner satisfies your particular legal requirements. It gives you the tools, such as restricting non-essential cookies and offering decline and manage options, but compliance also depends on your other scripts and your policy. Take legal advice if you are unsure.
Does the Squarespace cookie banner block code I added myself?
Not automatically in every case. Squarespace notes that custom code which places non-essential cookies may need extra work to respect the banner, and that custom code is outside its support. Check any scripts you added through code injection or code blocks.
Does Elfsight Cookie Consent block cookies?
Elfsight's pages describe a notice or an Accept and Decline banner that remembers each visitor's choice, but they do not describe blocking scripts or cookie categories. Treat it as a designed notice and test the behaviour you need before relying on it.
Which Squarespace plan do I need for a cookie banner widget?
The native banner is built into Squarespace's settings and needs no code. For a third-party widget, code injection is included on Core, Plus and Advanced. Elfsight mentions a Markdown block on Basic, but Squarespace is changing how Markdown blocks handle scripts, so on Basic use the native banner.
Is Elfsight Cookie Consent free?
There is a free plan with 200 views a month and Elfsight branding. Because a site-wide banner loads on every page, most live sites need a paid plan, which starts at $5 a month billed yearly for 5,000 views.
Disclosure: some links in this article are affiliate links, which means SquareLocator may earn a commission if you buy through them, at no extra cost to you. Features and prices were checked on Squarespace's help centre and pricing page and on Elfsight, Common Ninja and Cookiebot's official pages on 12 November 2026 and may change. This is not legal advice.
Early access to the good stuff
Plugin drops, template picks and creator codes. Free in your inbox.
- New plugin drops
- Template picks
- Creator discount codes