A Shopify store owner may get no warning before March 1, 2027, the day Shopify stops loading script tags on storefronts. A script tag is the older way an app puts its JavaScript on a store's pages, and anything that still arrives that way on that date stops running. Since October 1, 2026, apps haven't been able to create or update one on any API version, though existing tags keep running and apps can still read and delete them. Script tags on the order status page were on an earlier schedule and have already stopped.
Where the full list lives
I ran into the first problem in early November while working on a checker for this deadline. The API query for script tags returns only the tags of the app that's asking, so no one call shows every app's script tags on a store. The page customers load is the one place that shows all of them.
So I read the homepage source of one large public Shopify store, once, after checking its robots.txt. Its script tags sat in a function called asyncLoad, as a list of 7 URLs. Two of them began with //cdn.shopify.com/proxy/ and a hash, with the real address after that, and I had to strip the front to see whose script it was. For one of the 7, the address alone didn't tell me which app it came from.
App embeds, the replacement, showed up as HTML comments of the form <!-- BEGIN app block: shopify://apps/<app-handle>/blocks/... -->. There were 6, all from different apps than the script tags, so nothing was loading twice. That's one store, and others may look different.
How to check a store
- Open the storefront homepage in a desktop browser and view the page source.
- Search for
asyncLoadand copy every URL in that list. - For any URL that starts with
cdn.shopify.com/proxy/, read the part after the hash to find the real address. - Search for
BEGIN app block. Each match is an app embed that's already on. - Match the two lists by app, going by each script's host. My checker does this with a table from script host to app, and a host that isn't in the table stays unjudged instead of guessed.
A script tag with no embed from the same app is one that stops on March 1. One that does have an embed loads twice until then, which Shopify's docs say can double-count analytics or show the app's UI twice.
The source only shows embeds that are switched on. An embed that's off, or one left behind by a removed app, shows up only in the theme's settings, so page source alone can't tell you that the fix is already installed and just needs turning on.
What to do with each one
Shopify's docs split it by where the script comes from. If it's an app built with Shopify's developer tools, the developer has to release an app embed, and the store owner then turns it on in the theme editor. An embed is on per theme, so it needs checking again after a different theme is published. A custom app created directly in the Shopify admin can't use app extensions at all, so someone has to move the script into the theme, and editing theme code takes the theme off its automatic upgrade path. And if a service had the store create an app and paste its access token into their dashboard, that service has to release a real app.
I'd look at the admin-created custom apps first. No developer update is coming for those.
Takeaway
If you've checked a store, what did you find: script tags from apps that are still maintained, or ones somebody added years ago?
If you'd rather hand the check to someone, my profile says how to reach me.
This post was drafted with AI help. The numbers and facts come from my own logs and repo.
Top comments (0)