Shopify is ending script tags on the online store. A changelog post dated August 24, 2026 set two dates. From October 1, 2026, apps can no longer create or update script tags. From March 1, 2027, Shopify stops injecting existing script tags into storefront pages, so any script still loaded that way stops running. The first date has passed. The second is a little over three months away.
Script tags were the original way for apps to add JavaScript to a theme. Shopify’s deprecation guide notes that theme app extensions replaced them in 2021. Older apps, and many custom apps built for a single store, still use them.
What changed on October 1 and what happens on March 1
Since October 1, the scriptTagCreate and scriptTagUpdate mutations in the GraphQL Admin API return an error, and the REST ScriptTag resource rejects POST and PUT requests. This applies to every API version, so pinning an app to an older version does not delay it. Existing script tags keep running for now, and apps can still read and delete them.
On March 1, 2027 those existing tags stop loading. Shopify’s storefront migration guide is direct about the effect: the script stops loading and any feature that depends on it stops working on that store. Leftover script tag records do nothing after that date, so there is no need to clean them up then.
The order status page ran on an earlier schedule. Script tags there had already stopped on Plus stores and were set to stop on all other stores on August 26, 2026. Any app with a display scope of order_status or all should already have moved that part of its code.
Which replacement fits which script
Shopify points to three replacements, depending on what the script does.
- Scripts that load JavaScript on storefront pages move to an app embed block in a theme app extension. Embeds work on vintage and Online Store 2.0 themes.
- Scripts that only collect analytics, conversion or customer behavior data move to a web pixel. Merchants approve the pixel scopes at install or update, and pixels need no theme editor step.
- Customizations on the order status page move to customer account UI extensions.
App blocks also exist, but they only work on themes with JSON templates, so Shopify does not treat them as a general replacement.
Migration steps for app developers
The storefront guide sets out four steps. Build a theme app extension with an app embed block. Send the merchant to the theme editor with a deep link that activates the embed. Confirm the embed is active on the published theme. Then delete the script tag with scriptTagDelete.
The order of those steps matters. Delete the script tag before the embed is confirmed and the store has a gap where neither runs. Leave both on and the script loads twice, which can double-count analytics events or render a widget two times. Embeds are also enabled per theme, so a merchant who publishes a new theme may need to switch the embed on again.
To find tags, run the scriptTags query with a token your app already holds for the store. Developers who maintain one custom app per client have to check each store individually. We would keep a simple spreadsheet per store with the tag source URL, its replacement and the date the embed was confirmed live.
Custom apps and hardcoded scripts
Custom apps created in the Shopify admin cannot use app extensions or web pixels, so they have no extension-based path. Shopify’s guidance is to move the script into the theme, preferably in a custom Liquid block, or through the code editor if needed. That route has costs. The script stays in the theme after the app is removed, and editing theme code takes the theme off its automatic upgrade path. Shopify suggests it only when the app cannot use extensions.
Some third-party services ask merchants to paste an access token into their dashboard so they can add a script. Shopify says those services need to release a real app that uses a theme app extension or a web pixel.
What merchants should check now
Shopify had planned a banner warning merchants about apps that use script tags, but the storefront guide says it has decided not to show it for now. A store can therefore reach March 1 without any notice in the admin.
Our suggestion is to ask each vendor whose app runs code on your storefront whether it still uses script tags, and when it will switch. Then open the theme editor, go to App embeds and note which embeds are on for your live theme. For custom apps and scripts an agency added, ask your developer to run the scriptTags query against your store so you have a definite list. We would schedule any resulting theme changes for January, after holiday trading and well before the March 1 cutoff.





