How to Add Event Registration to Your Squarespace Website

Sarah runs a yoga studio. Her Squarespace site has an events page that lists her weekly classes and the occasional workshop. It looks good. The class schedule is there, the dates are right, the descriptions explain what each class covers.

When someone wants to register, she sends them to a Google Form linked in the navigation. The registration doesn't happen on her website. Someone who finds her site, looks at the schedule, and decides to sign up for Saturday's class has to open a new tab, fill out a form that looks nothing like her brand, and hope they don't close it before hitting submit.

That's not a Squarespace failure — the platform handles event display well. It's a gap in what the native Events block covers. Most Squarespace users find this out after they've already built their events page.

Squarespace's Events block shows your events. It doesn't manage registration. There are three ways to add registration to a Squarespace events page, and they make very different trade-offs.

What Squarespace Events actually does

The native Events block is useful and worth understanding before looking at alternatives.

What it covers:

Displays events in a list or calendar format
Shows event details — title, description, date, time, location, image
Can link each event to a URL (which is where the gap lives)

What it doesn't cover:

Capacity limits — there's no "20 spots available" state, no "sold out," and no automatic waitlist
Confirmation emails to people who register
Reminder emails before the event
A view of who's registered and how many people are coming

If those missing pieces don't matter for your use case — you just want a public-facing calendar with no registration — the native block is fine. If you need any of them, you're looking at one of the three options below.

Three options for adding registration to a Squarespace site

Option 1: Squarespace Form Block

Squarespace includes a Form block that collects submissions. You can add a Form block to the same page as your Events block — someone sees the event listing above, and the registration form below.

What works: Nothing extra to buy or install. Everything stays inside Squarespace. Non-technical to set up — if you can add a block to a page, you can add a Form block.

Where it falls short:

The Form block doesn't know anything about your events. It's a general-purpose form — it collects whatever fields you add and sends you an email notification for each submission. There's no connection between the form and the event.

Practically, this means:

No capacity enforcement. The form accepts submissions indefinitely. You can't set a cap of 20 and have it stop accepting registrations when 20 people have submitted.
No automatic confirmation email to the registrant. The form sends a notification to you (the site owner) but there's nothing built in to confirm to the person who just registered that their spot is held.
No reminder emails. Someone who registered three weeks ago won't receive anything before the event unless you send it manually.
No registrant dashboard. Submissions go to Squarespace's form panel. To get headcount before an event, you're opening that panel, filtering by the right form, and counting rows.

Right for: One-off events where capacity isn't a concern, you know most attendees personally, and you can manage follow-up manually. If you're hosting a small, informal gathering and just want a way for people to submit their name and email, this works.

Option 2: Link to a third-party platform

List your event on Squarespace and link the registration to a separate tool — Eventbrite, Luma, or a Google Form. The Squarespace page serves as the event listing; the registration happens elsewhere.

What works: Eventbrite and Luma both handle capacity limits, waitlists, confirmation emails, and reminder emails. If you already use one of these platforms, connecting to it from Squarespace is straightforward — add the URL to the Events block link field, and visitors follow it to register.

For paid events, Eventbrite's payment processing is built in. For events where marketplace discovery matters — you want people who don't already follow you to find the event — Eventbrite's search and category browsing can bring in registrants you wouldn't have reached otherwise.

Where it falls short:

Every person who clicks to register leaves your Squarespace site. They land on Eventbrite's platform, inside Eventbrite's design, seeing Eventbrite's branding. The confirmation email comes from Eventbrite, not from you.

For some organisers that's fine. For others, it's exactly what they're trying to avoid. If you've built a Squarespace site because you care about your brand experience, sending every registrant to a page inside Eventbrite's design — with Eventbrite's branding and no reference to yours — is a trade-off worth naming before you commit to it.

Google Forms has the same redirect problem as Eventbrite, plus the capacity and notification limitations from Option 1. It gives you neither the discovery benefits of Eventbrite nor the brand continuity of staying on your own site.

Eventbrite's sidebar also suggests other events to your registrants after they've completed registration — including events from other businesses in your category. If you run a yoga studio, someone who just registered for your Saturday class will see other yoga studios' events.

Right for: Organisers who are already using Eventbrite or Luma for discovery reasons, or who run large paid events where Eventbrite's payment infrastructure is worth the redirect. Not ideal if keeping visitors on your website matters to you.

Option 3: Embed a registration widget

Paste one line of code into a Squarespace Code Block. The events calendar and registration form render on your Squarespace page — inside your layout, styled to match your site, without redirecting anywhere.

What works: Registration happens on your website. A visitor finds your events page, sees your upcoming schedule, clicks an event, and fills in a registration form — all without leaving. The confirmation email goes out automatically from your own setup. If an event reaches capacity, the calendar switches to a waitlist form on its own. Reminders go out the day before the event without any action from you.

You see registrations in a dashboard in real time — who's registered, how many spots are left, any custom field responses you've collected.

Where it falls short: There's one technical step: pasting a code snippet into a Squarespace Code Block. Code Blocks require Squarespace's Business plan or above. If you're on a Personal plan, you'd need to upgrade first.

Right for: Squarespace sites where registration should feel like part of the site — same domain, same visual context, no redirect moment. Works well for recurring events (weekly classes, monthly workshops) where the automation — confirmations, reminders, capacity management — saves time across every event.

How to add Turnout to a Squarespace page

Turnout is the embed option described in Option 3. Here's what the setup looks like:

Sign up at getturnout.app and create your calendar
Add your event — title, description, date, time, location, and an optional capacity limit
Add any custom form fields if you need more than name and email (dietary requirements, which session, t-shirt size)
Go to Embed in the Turnout dashboard and copy the script tag
In Squarespace, open the page where you want the calendar to appear
Add a Code Block (under "More" in the block menu — Business plan and above)
Paste the script tag into the Code Block and save

The calendar widget appears on your page. You can adjust colours, fonts, and border radius from the Turnout dashboard — no need to touch the code.

Turnout works on any Squarespace plan that supports Code Blocks — Business plan and above. If you're on a Personal plan, the upgrade is worth considering if you're using Squarespace primarily to display and manage events.

What happens after someone registers

When a visitor registers through the Turnout widget on your Squarespace page:

They receive a confirmation email immediately — event name, date, time, location
24 hours before the event, they receive an automatic reminder
If the event is at capacity, the widget switches to a waitlist form — the visitor can join the waitlist, and you can promote waitlisted registrants from the dashboard if a spot opens
You see the registration in your Turnout dashboard in real time

You can export any event's registrant list as a CSV. You can check headcount from any device without opening a spreadsheet.

Which option is right for you

Use the Squarespace Form Block if you run small, informal events, don't need capacity enforcement, and are comfortable managing follow-up manually.

Link to Eventbrite or Luma if you're already on those platforms, your events are ticketed and you want payment processing built in, or marketplace discovery is a meaningful part of how people find your events.

Embed a registration widget if registration should feel like part of your Squarespace site, you run recurring events and want confirmations and reminders to happen automatically, and you want a real-time view of who's coming without checking a spreadsheet.

Squarespace handles display well. Registration requires a separate decision about where it happens, who manages the confirmation email, and how you'll know who's coming.

The embed option is the only one that keeps all of that on your domain. If you're on Squarespace and want registration that feels native to your site, Turnout has a 14-day free trial — no credit card required.

Related reading: