Substack Subscribe Form: Native Embed vs Supascribe

The native Substack embed does one thing: it puts a subscribe form on your page. If that's all you need, it works. But it's an unstyled iframe with a hardcoded width that breaks on mobile, no conversion analytics, and no control over where subscribers go after they sign up. Here's how both options compare.

#What the Native Substack Embed Actually Is

Substack provides a subscribe form you can add to any website. You find it under Settings > Growth features > "Embed signup form on other websites". The code they give you is an iframe:

<iframe
  src="https://yourpublication.substack.com/embed"
  width="480"
  height="320"
  style="border:1px solid #EEE; background:white;"
  frameborder="0"
  scrolling="no">
</iframe>

The form is served entirely from Substack's servers. When someone types their email and clicks Subscribe, the interaction happens inside that 480×320 box. The signup flow stays within the iframe; the visitor never leaves your page.

For a quick, no-setup form, it functions. But the iframe structure is also the source of every limitation listed below.

#What the Native Embed Can't Do

There are five specific gaps worth knowing before you choose which option to use.

Styling is locked. The iframe walls off all CSS from your site. The only configuration Substack exposes is a toggle to show or hide your publication logo. You cannot change the button color, the background, the font, or anything else. The form looks like a Substack form wherever you place it.

It breaks on mobile. The iframe has a hardcoded width="480". On screens narrower than 480px (most phones), the form overflows its container or gets cut off. The workaround is to manually edit width="480" to width="100%" in the copied snippet. Substack doesn't do this automatically.

No custom redirect after signup. After someone subscribes, they see a brief confirmation message inside the iframe. You can't send them anywhere: no thank-you page, no lead magnet, no specific post to read first. That immediate moment after someone subscribes is when they're most engaged. The native embed has no way to use it.

No analytics. Substack doesn't track how many times your embed was viewed, how many people submitted the form, or what the conversion rate is. Standard Google Analytics can't see inside the iframe either: it's cross-origin, so GA on your site is blind to form submissions entirely. You have no way to know whether your embed is actually working.

No success message control. The text someone sees inside the iframe after subscribing is fixed. You can't change what it says.

#What Supascribe Adds

Supascribe connects to the same Substack subscriber list as the native embed. When someone submits the form, they go into your Substack list exactly as they would through the native embed. The subscriber experience on Substack's end is identical. The differences are entirely on the website side.

Custom styling. Set your own background color, button color, and font. Change the headline, button label, and placeholder text. Use a single-line or stacked layout. The form looks like it belongs on your page rather than being pasted in from somewhere else.

Mobile-responsive by default. Single-line layout collapses to stacked automatically on small screens. No code edit needed.

Custom redirect after signup. Set a URL to send subscribers to after they complete the form. A thank-you page, a lead magnet download, or a specific post you want them to read first. Welcome emails have an 83% average open rate, the highest of any email type. The immediate post-signup experience sets the tone for everything that follows.

Per-placement analytics. Each embed has its own views, conversions, and conversion rate tracked separately in your dashboard. Average signup form conversion rates across the web sit around 2–3%. Knowing your actual numbers, and comparing your end-of-post embed against your homepage embed, tells you where to focus your attention. Without that data, you're guessing.

Feed widget and popup. The native Substack subscribe embed is only a form. Supascribe also supports a feed widget that shows your latest Substack posts on your site, and an exit popup that fires when visitors are about to leave. You can run all three from the same account and track each independently.

#Side-by-Side Comparison

#When to Use Each

Use the native embed if you need something working in the next five minutes, you don't care whether the form matches your site's design, and you're not running any optimization work. It's functional and it's free with your Substack account. For writers who just want a working form with zero setup, it's a reasonable choice.

Use Supascribe if any of the following matter: you want the form to look like it belongs on your site, you want to know whether the embed is converting, or you want to do something with the subscriber after they sign up. Also if you want a feed widget or popup: the native embed can't do either of those.

Both options add subscribers to the same list. Moving from the native embed to Supascribe doesn't change anything on the Substack side. Subscribers still receive your standard Substack welcome email and all your future issues as normal.

#Set It Up on Your Platform

Supascribe generates an embed snippet you paste into your site's HTML editor. The exact process depends on your platform. See the step-by-step guide for yours: