Development10 min read
Shopify script tag deprecation: find what stops working on March 1, 2027
Shopify script tag deprecation: find scripts your store still loads, identify their apps, activate replacements and check the March 1, 2027 deadline.
By Hamza Ahmad AslamAI & WordPress Developer | Speed Optimization & Site Security

On this page
- What changes on March 1, 2027?
- How common are old Shopify script tags?
- How do you find script tags on your Shopify store?
- Step 1: Open your live storefront
- Step 2: View the page source
- Step 3: Search for asyncLoad
- Step 4: Separate old script tags from app embeds
- Step 5: Match each domain to an installed app
- How do you make a script tag inventory?
- What should replace each script tag?
- How do you activate a Shopify app embed?
- What if the script only tracks visitors or purchases?
- Why should you avoid running both versions?
- How can a developer audit script tags?
- Check the storefront with curl
- Query script tags through the Admin API
- What should you do with scripts nobody owns?
- An installed app is no longer used
- An old agency created a custom app
- No installed app matches the domain
- What should you check if Shopify script tags stop working?
- What is the migration checklist?
- What should you check after removing the old scripts?
- Frequently asked questions
Shopify script tag deprecation means apps that still load storefront code through the old ScriptTag API will stop doing so on March 1, 2027. You can find the affected scripts in your storefront's page source, match them to installed apps and check whether each replacement is active before the deadline.
What changes on March 1, 2027?
Shopify will stop injecting script tags into storefront pages on March 1, 2027. If your reviews, chat, pop-ups or another feature still depends on one, that feature will stop loading. Your Shopify admin will not necessarily show an error.
A script tag lets an app load JavaScript without editing theme code. Shopify introduced theme app extensions as the replacement in 2021.
Shopify's changelog post of August 24, 2026 (opens in a new tab) and its developer guides establish these dates:
| Date | What changes |
|---|---|
| August 28, 2025 | Script tags stop running on the Order status page for Shopify Plus stores. |
| August 26, 2026 | Script tags stop running on the Order status page for all other stores. |
| October 1, 2026 | Apps can no longer create or update script tags on any Admin API version. Existing tags keep running. |
| March 1, 2027 | Shopify stops injecting script tags into storefronts. Features still depending on them stop loading. |
The October restriction affects GraphQL scriptTagCreate and scriptTagUpdate, plus REST POST and PUT. Older API versions cannot bypass it.
The scriptTags query and scriptTagDelete mutation remain available for audits and cleanup.
The storefront deadline also applies to vintage themes. App embed replacements support vintage and Online Store 2.0 themes.
How common are old Shopify script tags?
On November 1, 2026 I checked the public home pages of 206 Shopify storefronts, one request each, reading the script tag list Shopify prints in each page; 120 of them still loaded at least one script tag. It is one day's sample, so read it as a sign of how common this still is, not as a measurement of all stores.
A script tag's presence does not prove that its feature will break. The app might already have a working replacement while its old tag remains installed.
How do you find script tags on your Shopify store?
You can check a public storefront using a desktop browser. You do not need an API token or access to theme code.
Step 1: Open your live storefront
Open your store's public home page in a desktop browser.
Use a logged-out session so you see what customers see. A password-protected store shows its password page instead. Use an authorized session to inspect the actual storefront.
Check the published theme rather than an unpublished preview.
Step 2: View the page source
Right-click the page and choose View page source.
You can also use:
- Windows or Linux:
Ctrl+U - macOS Chrome:
Cmd+Option+U
The browser opens a tab containing the HTML returned by the server. Use this instead of the Elements panel in developer tools.
Step 3: Search for asyncLoad
Use your browser's Find command and search for:
asyncLoad
Look for a block containing:
var urls = [
Read the web addresses inside the list. Each represents a script tag Shopify is injecting into that page.
The domain often identifies the vendor. The ?shop= parameter commonly contains your store's .myshopify.com address.
Some addresses contain \/ instead of /, or \u0026 instead of &. These are escaped characters in the page source. They do not change the domain.
If there is no asyncLoad block, this check finds no injected script tags on that page. Other JavaScript can still run through theme code or app extensions.
Step 4: Separate old script tags from app embeds
Only the addresses inside the var urls list are the script tags identified by this inspection method.
Script files elsewhere in the page load through other methods and are not affected by this change. App embed files, for example, commonly use cdn.shopify.com addresses containing /extensions/.
Shopify documents that theme app extension assets are hosted on its CDN. The /extensions/ address pattern is something you can observe in page source, not a guaranteed URL format from Shopify's documentation.
Step 5: Match each domain to an installed app
In Shopify admin:
- Open Settings > Apps.
- Review the installed apps.
- Compare their names and vendors with your script domains.
- Open each likely app's details or Shopify App Store listing.
- Contact the app's support team if you cannot identify a domain.
For example, example-reviews.example might belong to a reviews app. That domain is an illustrative placeholder.
A matching domain is a clue, not proof. Some apps host scripts through separate companies.
Shopify scopes script tags to the app that created them. Uninstalling an app automatically removes its tags. Every address still injected through the list therefore belongs to an installed app.
Recently uninstalled apps matter when investigating theme code left behind, rather than active ScriptTag records.
How do you make a script tag inventory?
Copy this table into a document or spreadsheet. Record one row per address.
All rows, domains and app names below are illustrative examples.
| Script address (domain) | App or vendor | Still used? | Replacement | Done on published theme? |
|---|---|---|---|---|
| example-reviews.example (illustrative) | Example Reviews | Yes | App embed | No |
| example-chat.example (illustrative) | Example Chat | Yes | App embed | Yes |
| example-tracking.example (illustrative) | Example Tracking | Unknown | Web pixel | No |
For each row, keep the full URL alongside the domain. A developer may need it to identify the exact record.
Use the final column to record whether the replacement works on the published storefront. Web pixels do not require a theme-editor activation step.
What should replace each script tag?
The replacement depends on what the code does. Shopify explains the available approaches in its storefront migration documentation (opens in a new tab).
| What the script does | Replacement | Who handles it |
|---|---|---|
| Displays reviews, chat, pop-ups, badges or other storefront features | App embed block in a theme app extension | App developer builds it; merchant activates it |
| Collects only analytics or conversion events | Web pixel | App developer implements it |
| Sends events to a service without a supported app | Custom pixel | Merchant or developer maintains it |
| Belongs to an app the store no longer needs | Uninstall the app | Store owner or manager |
| Belongs to an admin-created custom app that cannot use extensions | Move into theme code or replace the app | Developer or service provider |
An app embed can also load JavaScript without displaying a visible widget.
How do you activate a Shopify app embed?
App embeds start disabled after installation. An app cannot activate one automatically for the merchant.
To enable a replacement:
- Open Online Store in Shopify admin.
- Select Edit theme for the published theme.
- Select the App embeds icon in the editor sidebar.
- Find the replacement app's embed.
- Turn its toggle on.
- Select Save.
- Check the feature on the live storefront.
These steps follow Shopify's theme app embed instructions (opens in a new tab).
If the embed is missing, ask the vendor whether its app supports the replacement.
App embeds are enabled per theme. Before publishing another theme, open its App embeds panel and activate the required embeds. Market configurations can also have their own app embed settings, so check those where applicable.
What if the script only tracks visitors or purchases?
Use the vendor's web pixel replacement when available. Web pixels collect customer events without requiring activation in the theme editor.
If no suitable app pixel exists, a developer can consider a custom pixel under Settings > Customer events.
Shopify says adding and using custom pixels is unsupported by Shopify. Some pixel code does not work in the pixel sandbox, so the third-party vendor may need to help.
Remove or modify previous tracking code, including code in theme.liquid, to avoid counting events twice. Follow Shopify's custom pixel instructions (opens in a new tab).
Why should you avoid running both versions?
Before March 1, 2027, the old tag can run alongside its replacement.
If both execute the same functionality, analytics events might be counted twice or a widget might appear twice.
Keep the old feature working until its replacement is ready. Then have the responsible app remove its old tag.
After the deadline, leftover script tag records no longer load storefront code.
How can a developer audit script tags?
An agency can extract addresses from the storefront, then query the Admin API for an app it maintains.
Check the storefront with curl
Run this command in a shell with curl, grep and sed available. Replace the example domain with the live store.
curl -s https://your-store.com/ | grep -o 'var urls = \[[^]]*\]' | grep -oE 'https?:[^"]+' | sed 's|\\/|/|g'
It extracts addresses from the var urls list and unescapes slashes. Some addresses retain \u0026 where the page has &; the domain stays readable.
Empty output means the command found no matching list. Check the page manually before concluding there are no tags. A password page or changed HTML format can also produce an empty result.
Query script tags through the Admin API
For an app your agency maintains, run this GraphQL Admin API query using that app's authenticated session:
query {
scriptTags(first: 50) {
nodes {
id
src
displayScope
}
pageInfo {
hasNextPage
endCursor
}
}
}
src gives the address, displayScope identifies where the tag was intended to load and id identifies the record.
The query requests up to 50 records. If hasNextPage is true, fetch the next page using after with the returned endCursor.
The query returns only tags accessible to that app, not every app's tags on the store.
The official scriptTags reference (opens in a new tab) documents its arguments and fields.
Once the replacement works, the app developer can use scriptTagDelete to remove the old record. This operation requires the appropriate script tag access.
What should you do with scripts nobody owns?
Unknown ownership needs investigation before removal.
An installed app is no longer used
Ask whether the business still needs its features. Check for connections to tracking, customers or store operations before uninstalling.
Uninstalling removes the app's script tags. Some apps leave theme code behind, so check the app listing or support instructions for additional cleanup.
Make code changes on a duplicate theme, not the live theme.
An old agency created a custom app
Some stores use admin-created custom apps for outside services or older integrations.
These apps cannot use Shopify app extensions or web pixels. Whoever maintains the integration must move its storefront script into the theme, using a custom Liquid block where possible or the code editor otherwise.
Editing theme code takes the theme off its automatic upgrade path. The service can instead supply a replacement app that supports extensions.
No installed app matches the domain
Contact likely vendors through Settings > Apps. Send the full script address and ask whether their app owns it.
Ask what replacement they provide and whether it needs activation.
Avoid deleting unfamiliar code until you know its purpose.
For help identifying owners and coordinating replacements, the Shopify script tag audit and cleanup service covers this work.
What should you check if Shopify script tags stop working?
If a widget disappears, check its app status, the published theme's App embeds panel and the storefront's asyncLoad list.
Before March 1, 2027, a failure can come from the app, theme settings or another integration issue.
After the deadline, check whether the app has supplied a replacement and whether the merchant activated it.
For analytics, verify events using the vendor's supported testing tools.
What is the migration checklist?
Use this checklist for each store you maintain.
- Open the live storefront and find the
asyncLoadscript tag addresses. - Record each domain, full URL and suspected app in the inventory table.
- Match every script to an installed app or confirm its owner with support.
- Decide whether the feature is still required and which replacement it needs.
- Ask the vendor or developer to prepare the replacement without disabling the working feature prematurely.
- Activate required app embeds on the published theme and check any other theme scheduled for publication.
- Verify each widget or tracking feature, then have the responsible app remove its old script tag where appropriate.
- Check the storefront page source again after the changes to confirm the expected old addresses are gone.
- Repeat the storefront and feature checks on or after March 1, 2027.
What should you check after removing the old scripts?
Check that required widgets work and analytics events are not duplicated.
Use the Core Web Vitals budget calculator to plan loading and interaction budgets if replacement scripts add JavaScript work.
Compare field data with lab measurements using the guide to why PageSpeed can look good while Core Web Vitals fail.
Keep the completed inventory with the store's maintenance records.
Frequently asked questions
Will my Shopify store break on March 1, 2027?
The storefront itself does not shut down because of this change. Features that still depend on Shopify injecting legacy script tags will stop loading. Check your storefront's asyncLoad list and ask the responsible app vendors whether their replacements are active.
Why did my Shopify reviews or chat widget stop showing?
An app embed may be disabled on the published theme, or the app might still depend on a legacy script tag. Open Online Store, edit the published theme and check App embeds. If the embed is enabled but the widget remains missing, contact the app vendor with the affected page address.
Do I need to delete old Shopify script tags?
Shopify does not require you to delete leftover script tag records after March 1, 2027, because they no longer load storefront code. Before that date, remove old tags once their replacements work to avoid duplicate widgets or analytics events. The app that owns a tag is responsible for its API cleanup.
Does Shopify script tag deprecation affect vintage themes?
Yes. Shopify's March 1, 2027 removal applies to storefront script tags regardless of whether the store uses a vintage theme or an Online Store 2.0 theme. App embed blocks support both theme types, but the merchant must activate the required embed on the theme being published.
Is the Shopify Order status page part of the March 2027 change?
The Order status page followed an earlier schedule. Script tags stopped running there for Shopify Plus stores on August 28, 2025 and for all other stores on August 26, 2026. The March 1, 2027 deadline concerns storefront script tag injection.
How this article was made: drafted with AI assistance from a researched brief, then checked against primary documentation before publishing.
Share this article
Keep reading
Development7 min read
"This block contains unexpected or invalid content": fixing validation errors
If you searched for "block validation failed WordPress," the editor is telling you that stored block markup no longer matches what the current save() function generates from the attributes it can parse.
- Gutenberg Blocks
- WordPress
- JavaScript
Development7 min read
WordPress Script Modules: load ES modules the WordPress way
WordPress Script Modules are the core API for registering and loading front-end ES modules with named dependencies. Since WordPress 6.5, you can let WordPress build the import map, preload static module dependencies, and print the module entry point in the right order.
- WordPress
- JavaScript
- Performance
Performance9 min read
Why a WooCommerce variation selector feels slow
When a WooCommerce variation dropdown is slow, record the attribute selection itself before changing caching, hosting, or the variation count. Check whether the delay happens in browser JavaScript, during a variation request, or while the page updates price, stock, and availability.
- WooCommerce
- Performance
- JavaScript