Shopify Script Tags Are Being Switched Off. Here's What Breaks.

Shopify is switching off script tags. Not deprecating them in the usual sense, where the old thing quietly keeps working for years — switching them off. On 1 March 2027, Shopify stops injecting script tags into storefronts entirely, and anything that depended on one stops running.

There is an earlier date that matters more, because it is much closer. From 1 October 2026, the scriptTagCreate and scriptTagUpdate mutations start returning errors, and the REST endpoint rejects POST and PUT. Existing tags keep running until March, but no app can create a new one after October.

If you run a Shopify store, some of the apps you have installed almost certainly use script tags. Most merchants will find out when something stops working.

When an app needs to run JavaScript on your storefront, it has to get that JavaScript onto the page. A script tag was the original way: the app registers a URL with Shopify, and Shopify injects a <script> pointing at it into every page of your store.

It is a blunt instrument. The app has no control over where in the page it loads, the merchant has no visibility of it in the theme editor, and it runs on every page whether it is needed there or not. It was replaced in 2021 by theme app extensions — which is why this deprecation has been signposted for five years.

The reason it survived so long is that it works, and rewriting a shipped app is unrewarding work that produces nothing a merchant can see. Which is exactly the kind of work that gets deferred until a deadline arrives.

This is the part that catches development teams out. Most Shopify breaking changes are scoped to an API version, so an app pinned to an older version carries on unaffected until it upgrades.

Not this one. The deprecation applies across all API versions, including older ones. There is no version to pin to that defers it, and no configuration that opts out. The date is the date.

One narrow exception worth knowing: the deprecation targets script tags with a display scope of online_store. Order status page script tags are on their own, earlier timeline and are not covered by these dates.

Two things, depending on what the script was doing.

For anything that renders or interacts with the storefront — a widget, a badge, a popup, a chat launcher — the replacement is an app embed block, shipped as part of a theme app extension. The merchant activates it in the theme editor, which means they can see it, position it, and turn it off. The asset is served from Shopify's CDN and versioned with the extension.

For anything that only collects analytics or conversion data, the replacement is a web pixel. Pixels run in a sandboxed environment built for exactly this, and they need no action from the merchant at all.

It is worth saying that this is not a case of Shopify breaking something useful for no reason. App embed blocks are better than script tags in every direction that matters to a merchant.

A script tag is invisible. You cannot see it in your theme editor, you cannot control where it loads, and when you uninstall the app it is supposed to be removed — but stale script tags on stores whose apps were removed years ago are a routine finding in storefront audits.

An app embed block is visible in the theme editor, positioned by the merchant, and disappears cleanly when the app is uninstalled. It also loads from Shopify's own CDN rather than a third-party server, which removes a DNS lookup and a point of failure from every page of your store.

The October date is the one to plan against, not March. After 1 October you cannot create a new script tag, which means any install flow that registers one at install time breaks for new merchants on that day — even though existing merchants are fine until March.

That asymmetry is worth reading twice. An app that registers its script tag during OAuth will appear to work fine for its existing user base and fail silently for every new install, five months before the deadline everyone is planning around.

If you are shipping a new app now, there is no decision to make: build the theme app extension. Script tags are not an option for anything new.

Deadlines like this are the tax on running a store built from other people's software. You did not choose script tags, you cannot migrate them yourself, and the work sits with developers who may or may not be paying attention.

The defence is an audit habit. Once or twice a year, list what is actually running on your storefront — every app, every script, every permission it holds — and remove what you no longer use. Most stores we look at are carrying code from apps they cancelled years ago.

This deprecation is a good excuse to do it. The deadline is real, the audit is an afternoon, and the performance you get back is yours to keep.