
Shopify Script Tags Stop Running March 1, 2027: Is Your Form App Ready?
If a form, popup, or email-capture app on your store still injects JavaScript the old way — through Shopify's ScriptTag API — that code has a hard stop. Shopify will stop injecting script tags into storefronts on March 1, 2027. After that date, anything that depended on those tags simply does not load.
The create-and-update window is already closed. As of October 1, 2026, apps can no longer create or update script tags on any API version. Existing tags keep running until March. This post is a merchant-facing checklist: what script tags are, what actually breaks, how to tell if your form app is already on a theme app extension, and what to do about forms and popups specifically.
What a script tag is (in plain English)
A script tag is a Shopify API object that lets an installed app inject a JavaScript file onto your storefront without touching your theme files. The app calls the Admin API, Shopify stores a URL, and Shopify inserts that script on pages for you.
That convenience is why so many older form builders, popups, announcement bars, and review widgets used them. The merchant installed the app, the script appeared on every page, and the widget rendered itself.
The catch: those scripts do not show up in the theme editor. You cannot toggle them off next to your sections and blocks. You often cannot tell which app owns which file just by looking at the storefront.
Shopify's replacement is a theme app extension:
- App embed blocks load JavaScript on some or all storefront pages — the direct replacement for most script tags. They appear under App embeds in the theme editor, where you can turn them on or off. They work on vintage themes and Online Store 2.0 themes.
- App blocks let you place the app's UI in a section, the same way you place a heading or image. They need a theme that supports JSON templates.
- Web pixels replace scripts that only collect analytics or conversion data. They run in a sandbox and respect customer privacy permissions.
If your form app listing mentions "theme app extension," "app embed," or "app block," it is already on this model.
Photo: Jiří Navrátil on Unsplash
Why Shopify is blocking them
Shopify is explicit about the reasons, and they are merchant-facing, not just developer hygiene.
You cannot see or control them. Shopify's changelog says script tags run JavaScript directly on a storefront without appearing in the theme editor, which makes them difficult for merchants to find and control. App embeds show up in the editor. You can see the app is running and turn it off.
They are a security surface. Shopify's storefront security guidance is blunt: a script tag loads code from a URL you cannot see or disable in the theme editor. If an attacker controls that URL, their code runs on every page that loads it. Theme app extension assets are versioned and shipped with the app, so a fix goes out through a normal release.
Analytics replacements are safer for customers. Web pixels — the replacement when a script only tracks behavior — run in a sandbox and respect customer privacy permissions.
A side effect merchants already feel: ungoverned scripts add page weight and compete with your theme for the main thread. Shopify's deprecation docs do not list performance as an official reason, but the new model also gives you a single place to see what is loading.
What breaks, and when
Shopify split this into two tracks: the Order status page, and everything else on the storefront.
Order status page — already done. Script tags with a display scope of order_status or all stopped running on the Order status page for remaining stores on August 26, 2026. Plus stores lost them earlier, on August 28, 2025. If a form, survey, or pixel on that page went quiet last summer and nobody migrated it to a customer account UI extension or a web pixel, that is why.
Creating and updating tags — already done. Since October 1, 2026, the scriptTagCreate and scriptTagUpdate mutations return an error on every API version, and REST POST / PUT requests to the ScriptTag resource fail the same way. Pinning an older API version does not help. Existing tags still run.
Storefront injection — March 1, 2027. On that date Shopify stops injecting script tags into storefront pages. The leftover records do nothing. Any form, popup, banner, or widget that still depends on a script tag will not load.
In short:
- August 26, 2026 — Order status page script tags stopped for remaining stores.
- October 1, 2026 — Apps can no longer create or update script tags.
- March 1, 2027 — Storefront script tags stop running.
Until March, running a script tag and its replacement at the same time loads the script twice. That can render a form twice or double-count analytics. After March, leftover records have no effect, so you do not need to delete them for Shopify's sake — you need to make sure the replacement is actually on.
One more caveat: admin-created custom apps cannot use app extensions at all — no theme app extensions, no web pixels. Those are apps created directly in the Shopify admin, not in the Dev Dashboard. The script has to move into the theme, or the integration has to become a real app.
Photo: Glenn Carstens-Peters on Unsplash
A checklist for auditing your store
You do not get a single "script tags" screen in the Shopify admin. Treat this as a storefront and app-by-app audit.
- List every app that injects UI or tracking on the storefront. Forms, popups, email capture, announcement bars, reviews, loyalty widgets, chat, upsells. Write them down. The ones that "just appear" on every page are the suspects.
- Open the theme editor and check App embeds. Go to Online Store → Themes → Customize, then App embeds. Anything listed there is already a theme app extension. Note which ones are on. If a form app you rely on does not appear here and does not offer an App block under Add block → Apps, it may still be injecting a script tag.
- Check the app's listing and docs. Look for "theme app extension," "app embed," "app block," or "Online Store 2.0." Apps that only mention "automatically added to your theme" or "no theme changes required" without those words are more likely to still use script tags.
- View source and the Network panel. Load your homepage (and a product page) in a private window. View source and search for third-party script URLs — form and popup apps often load from their own CDN. In your browser's developer tools, open the Network panel, filter by JS, and reload. Scripts that are not part of your theme, Shopify's own bundles, or an app embed are worth investigating. You will not see a label that says "script tag," but you will see the file.
- Ask the developer, in writing. Send each suspect app a short question: "Have you migrated off the ScriptTag API to a theme app extension (app embed or app block) or a web pixel? Will our install keep working after March 1, 2027 without us doing anything?" If they say they still use script tags, ask for their migration date and whether you need to enable an app embed in the theme editor. Shopify is clear that app embeds stay off until you turn them on, and they are enabled per theme — publishing a new theme means checking again.
- Custom or agency apps. If a freelancer or an agency created a custom app in the admin and pasted a token into a third-party dashboard, that app cannot use theme app extensions. The script has to move into the theme or the integration has to become a real app. Plan time for that; it is not a toggle.
Do this before you start a theme rebuild or a peak-season theme swap. An app embed is only active on the theme you enabled it on.
Photo: Clark Street Mercantile on Unsplash
What this means for forms and popups
Forms and popups are some of the most common script-tag users, because they need to render on many pages and they often load their own CSS and JavaScript.
If your form app is still on script tags:
- The form will vanish on March 1, 2027. Contact, wholesale, waitlist, and custom-order forms that depend on that script stop rendering. You will not get a Shopify banner about it — Shopify decided not to show an install-time warning for storefront script tags.
- New installs of that app are already broken if the developer did not ship a replacement before October 1, 2026. They cannot create a script tag for a newly installed store.
- A migrated app still needs you. Replacing a script tag with an app embed is not automatic. You have to enable the embed in the theme editor on the published theme. Until you do — and until the developer deletes the old tag — you can get a double-load (two forms, doubled analytics) or a gap (neither running).
What a healthy form app looks like after the migration:
- An app embed you can see and toggle in the theme editor (this loads the form runtime).
- An app block you place on Contact, product, or landing pages so the form inherits the theme and sits in the layout like any other block.
- No silent global script that you cannot find.
That is also why the replacement is better for forms specifically. You choose where the form lives. You can run different forms on different templates. You can turn the embed off without uninstalling the app.
If you are evaluating a form app now, treat "built as a theme app extension" as a requirement, not a nice-to-have. The ScriptTag API is already write-locked.
If you already use Spectre
Spectre was built as a native Shopify theme app extension. Forms are App Blocks you place in the theme editor, and the Spectre Forms app embed loads the runtime. There is no script-tag migration on your side — the app never depended on the ScriptTag API to render.
Once the embed is on, you can add a form block to a page, pick the form, and it inherits the theme. The same builder gives you multi-step flows, conditional logic, localization, file uploads, reCAPTCHA, and funnel analytics, with submissions routing into Klaviyo, Shopify Flow, Google Sheets, or Zapier.
If you are moving off an app that is still on script tags, the work is to rebuild the form in Spectre (or another theme-app-extension app) and place the block — not to wait for a silent JavaScript file to keep working.
FAQ
Are script tags already dead? Not on the storefront. Existing tags still run until March 1, 2027. Apps cannot create or update them anymore. Order status page tags have already stopped.
What is the difference between an app embed and a script tag? A script tag is an API-injected script with no theme-editor control. An app embed is part of a theme app extension. You enable it per theme, you can see it, and you can turn it off. Shopify's migration guide treats app embeds as the replacement for ScriptTag-loaded JavaScript.
Do I need an app block and an app embed? For a form, usually yes. The embed loads the scripts and styles. The block is the form you place on a page. Analytics-only tools can skip both and use a web pixel instead.
Will Shopify migrate my apps for me? No. Each app developer has to ship a theme app extension or web pixel, and you have to enable embeds on the published theme.
What if my theme is vintage? App embeds work on vintage themes and Online Store 2.0. App blocks need JSON templates. A form app that only offers an app block may not place cleanly on a vintage theme; an app embed can still load the widget.
What about custom apps we created in the admin? Admin-created custom apps cannot use app extensions. Move the script into the theme (a custom Liquid block if you can) or rebuild the integration as a proper app. Shopify warns that putting the script in theme code takes the theme off its automatic upgrade path, so only do that when there is no extension-based option.
The takeaway
The dates are not flexible. New script tags have been blocked since October 1, 2026. Storefront tags stop running March 1, 2027. If a form or popup app cannot show you an app embed or app block in the theme editor, treat that as a migration project — not a wait-and-see.
The apps that will keep working are the ones already built the way Shopify has asked since 2021: theme app extensions, visible in the editor, enabled per theme. Spectre is one of those. If you want forms that already live there — multi-step, conditional, localized, connected to the tools you use — install Spectre.

