How to See What Apps a Shopify Store Uses
How to see what apps a Shopify store uses by hand: confirm the store runs on Shopify, read app blocks and scripts in the page source, watch network requests, and know what no check can see.

On this page
To see what apps a Shopify store uses, read the code its storefront sends to every visitor: confirm the site runs on Shopify, open its page source and search for BEGIN app block and cdn.shopify.com/extensions, watch the browser's Network tab for third-party scripts, then read the store's privacy policy for named providers. No method sees everything. Apps that work only inside the Shopify admin, Shopify Functions and checkout extensions leave little or no trace in storefront code, so every result, from a tool or from you, is an informed guess.
For a quick first pass, ShopOpsy's free Shopify app detector reads a store's page code for you and lists the apps it recognises. It reads the same public signals as the manual checks below, so it has the same blind spots. This guide covers those manual methods, using only information any visitor's browser receives. The code markers below are what we found on live Shopify stores in October 2026; Shopify doesn't document most of them, so they can change.
Which apps can you see from the storefront?
Detector tools fetch a store's pages and compare what loads with a list of known script addresses, block names and other markers. They work from the same public signals you can read yourself, so a result is only as good as the tool's list and what the app leaves in the page.
Whether an app is visible depends on where Shopify runs it:
| How the app works | Where it runs | Visible from the storefront? |
|---|---|---|
| Theme app extension (app block or app embed) | Inside the theme | Usually, often by name |
| Script tag (older method, vintage themes) | Storefront pages | Yes, as a script address |
| App pixel | Sandbox in the visitor's browser | Partly: counted, rarely named |
| App proxy | A path on the store's own domain | Partly, through requests to that path |
| Checkout UI extension | Isolated worker in checkout | Only what it displays |
| Shopify Function (discount, delivery and payment rules) | Shopify's backend | No, only its effect |
| Admin-only app (inventory, accounting, reporting) | Shopify admin | No |
Step 1: How do you tell if a website is a Shopify store?
Before hunting for apps, answer the first question: is this a Shopify store? One or two of these checks usually settle it.
- Look at asset addresses. Right-click the page and choose View page source (Ctrl+U in Chrome on Windows, per Chrome's keyboard shortcuts). Search for
cdn.shopify.comor/cdn/shop/. Shopify's asset_url filter returns theme file addresses under/cdn/shop/, and on the stores we checked, theme files and images loaded from these paths. - Find the myshopify.com address. A store is given a
myshopify.comaddress when it signs up, according to Shopify's domains guide. Search the source forShopify.shop. On the stores we checked, it held that address even when the store used its own domain. - Try the cart endpoint. Add
/cart.jsto the store's domain. Shopify's Ajax API only works on themes hosted by Shopify, and its cart reference shows this address returning the visitor's cart as JSON. A reply that starts with"token"and lists"items"is a strong sign. - Read the response headers. Open DevTools (F12), select Network, reload, click the first document request and read its Headers. The Shopify stores we checked sent
powered-by: Shopify. Treat this as a clue only, since headers can change. - Ask the console. Type
Shopify.themein the Console tab. On a Shopify theme it returns an object with the theme's name.
What if the store is headless?
Some brands run a custom front end on top of Shopify, known as a headless storefront. Their pages may contain no theme code at all, and the /cart.js check doesn't apply, because Shopify says the Ajax API can't be used on custom storefronts. Product images may still load from cdn.shopify.com, and Shopify's headless cart docs say the cart's checkout URL sends buyers through Shopify's web checkout. Theme app extensions don't apply to these stores, so most app clues are in the Network tab.
Step 2: Search the page source for app blocks and embeds
Shopify's script tag deprecation page says theme app extensions replaced script tags in 2021, and Shopify's ScriptTag reference says apps that integrate with a theme must use theme app extensions instead of script tags to be listed on the Shopify App Store. Shopify's extension docs describe two kinds:
- App blocks sit inside theme sections, such as a reviews widget on a product page. The merchant places each one in the theme editor.
- App embeds are injected before the closing
</head>or</body>tag, for site-wide features and scripts. They stay off after installation until the merchant turns them on.
Search the page source for these strings, one at a time:
BEGIN app block
shopify-app-block
cdn.shopify.com/extensions/
var urls
?shop=What each match tells you:
BEGIN app block: On the stores we checked, each active app block and app embed sat between comments such asBEGIN app block: shopify://apps/app-handle/blocks/block-name/.... The part afterapps/is the app's handle. Sometimes it matches the app's App Store address,apps.shopify.com/app-handle; if that address doesn't open, search the App Store by name.shopify-app-block: Shopify adds theshopify-blockclass to the element that wraps a theme app extension's output, and app blocks we saw also carriedshopify-app-block. This shows you where the block sits on the page.cdn.shopify.com/extensions/: Files in an extension's assets folder are served from Shopify's CDN. On the stores we checked, the path included a readable extension name and a version number.var urlsand?shop=: Older apps add scripts through Shopify's ScriptTag API. On the stores we checked, these appeared as a list of script addresses in Shopify's header code, each ending in?shop=followed by the store's myshopify.com address. The domain in each address usually points to the vendor. Shopify's ScriptTag reference says script tags can only be used with vintage themes, so on a store with a newer theme you may find few or none.
Script tags are on their way out. Shopify's deprecation page says apps can't create or update a script tag after 1 October 2026, and script tags stop running on storefronts on 1 March 2027. Expect that list to shrink.
Which matches aren't apps?
Not everything that mentions Shopify is an app:
shopify-sectionmarks the theme's own sections. Shopify's section schema docs say every rendered section is wrapped in an element with this class.- Files under
/cdn/shopifycloud/orcdn.shopify.com/shopifycloud/appear to be Shopify's own platform code. Shopify doesn't document these paths, but on the stores we checked, the file names pointed to its web pixels manager and its built-in cookie banner. - Files under
/cdn/shop/t/belong to the theme, as the asset_url filter example shows, though a developer may have pasted app code into them.
Step 3: Watch the Network tab
The page source shows what the server sent. The Network tab shows everything the browser loads afterwards, including scripts that other scripts pull in. Chrome's Network reference documents each control used here.
- Open DevTools (F12, or Cmd+Option+I on a Mac, as Chrome's DevTools guide lists) and select Network.
- Tick Disable cache to load the page as a first-time visitor would, and Preserve log to keep requests as you move between pages.
- Reload, then click the JS filter to show scripts only.
- Type the store's own domain in the filter box and tick Invert to hide first-party requests. What remains is mostly Shopify's CDN and third-party services.
- Read the Initiator column. It shows whether the HTML parser or another script started each request, which helps you spot scripts loaded through a tag manager.
- Press Ctrl+F (Cmd+F on a Mac) to open the Search tab and search all requests and responses for a vendor's name.
Then use the store like a shopper: open a product, add it to the cart, use search and scroll to the footer. Many apps load only when they're needed. Also watch for requests to paths that start with /apps/, /a/, /tools/ or /community/ on the store's own domain. These are the prefixes Shopify allows for app proxies, which forward storefront requests to an app's server.
Why do some trackers load only after consent?
If the store shows a cookie banner, analytics and marketing scripts may wait for your choice. In regions that require consent, Shopify's banner, and consent tools that use the Customer Privacy API, hold Shopify-managed pixels until the visitor agrees. To see the full set, open a fresh private window and accept cookies, then compare with a visit where you reject them. Our Shopify cookie banner guide explains which trackers wait.
How do you spot app pixels?
App pixels are tracking extensions that merchants manage in Settings > Customer events, according to Shopify's app pixels guide. Shopify's pixels documentation says app pixels run in a strict sandbox using web workers and custom pixels run in a sandboxed iframe, so their code isn't in the page source. On the stores we checked, the source did contain a pixel list (search for webPixelsConfigList) with one entry per pixel, marked "type":"APP" or "type":"CUSTOM". App entries carried a numeric ID rather than a name, so you can count app pixels but often can't name them. Their requests still show in the Network tab. Our guide to Shopify customer events explains how pixels and consent fit together.
Step 4: Look at what the store shows you
Visible features are weaker evidence, but they fill the gaps.
- Widgets. Reviews, loyalty prompts, chat bubbles, back-in-stock forms and size charts often come from apps. Right-click the widget and choose Inspect. Class names, IDs and "Powered by" links often name the vendor.
- Checkout. Add a product, go to checkout and stop before paying. You can see payment and express checkout options, delivery options and any extra blocks, such as upsells. You can't read their code: checkout UI extensions run in an isolated web worker with no access to the page, and extensions on the information, shipping and payment steps are available only to Shopify Plus stores.
- Order status page and emails. If you're already a customer, the order status page and shipping emails can show tracking, survey or review features, and email footers often name the sending platform. Since 26 August 2026, script tags no longer run on the Order status page of any store, and Shopify's upgrade guide says stores that hadn't upgraded their Thank you and Order status pages by that date were upgraded automatically. Visible app content there now comes from customer account UI extensions, so judge that page by what renders, not by code. Our Shopify order status page guide shows what that page can contain.
Step 5: Read the privacy and cookie policies
A store's privacy policy can be the most direct list of its providers. Under the GDPR, a business that collects personal data must tell people the recipients or categories of recipients of that data, if any (Article 13(1)(e)). The UK ICO's guidance on privacy information says you can name the organisations or describe them by category. So some policies name every analytics, email and review service, while others only say "marketing providers".
Shopify links published policies in the checkout footer automatically, and the privacy policy lives at /policies/privacy-policy on the store's domain. Also check the cookie policy and the banner's preferences panel, which sometimes list each cookie and the company that sets it. Treat both as possibly out of date: a policy may still name a service the store has dropped. Our guides to the Shopify privacy policy and the Shopify cookie policy show what merchants are expected to list.
How reliable is each clue?
| Clue | What it suggests | Confidence |
|---|---|---|
BEGIN app block comment with an app handle | The app's block or embed is active in the live theme | High |
Script from cdn.shopify.com/extensions/ | A theme app extension loads files on this page | High |
Script address ending in ?shop= | A script tag is registered for this store | High that it's registered, medium that it's in use |
| Third-party script inside theme files | Code was added to the theme by hand or by an app | Medium, as it may be left over |
Request to an /apps/ proxy path | An app with a proxy is installed | Medium; the vendor isn't always clear |
| Provider named in the privacy policy | The store shares data with that company | Medium; policies lag behind changes |
| Widget that looks like a known app | Possibly that app | Low |
Leftover code is the most common false lead. Shopify says some apps add theme code that isn't removed automatically when the app is uninstalled, so a script in the theme may belong to an app the store no longer uses. If a script loads but nothing it would control appears on the page, treat it as a possible leftover.
What can't any check see?
These apps leave no reliable trace on the storefront, whatever tool you use:
- Admin-only apps for inventory, accounting, reporting, bulk editing or order routing.
- Shopify Functions. Functions customize Shopify's backend logic: new discount types, renaming or hiding delivery and payment options, and checkout validation. You may see the effect, but not which app caused it.
- Checkout UI extension code, which runs isolated from the page.
- Server-to-server integrations that sync orders, stock or customers with warehouses, ERPs or email platforms through Shopify's APIs.
- Custom apps built for one store, which won't be on any detector's list.
Results also differ by page, device and market. Shopify lets merchants customize app embeds for a specific market in the theme editor, and a store may load more trackers for visitors who accept cookies. Check several page types and, if it matters, more than one region.
What should you check before trusting a detection tool?
A tool can save time when you're checking many stores. ShopOpsy's Shopify app detector reads a store's home page or a product page, names the code that revealed each app it recognises, and lists unrecognised app blocks and script hosts separately. It reads the same page code you search in Step 2, without running the page's scripts, so it shares that method's limits and can miss apps that load later or only after consent. Before relying on any tool, check four things:
- Does it show its evidence? A useful result names the script, block or request it matched, so you can confirm it in the source.
- Does it separate Shopify's own code from apps? Platform scripts, such as the web pixels manager, aren't apps.
- Does it flag possible leftovers? Code in the theme isn't proof of an active install.
- What does a browser extension ask to access? Read the permissions it requests before you install it.
None of the three detector sites we opened for this guide explained how they measure accuracy, so treat any list as a starting point and confirm the apps that matter with Steps 2 to 5.
How do you audit the apps on your own store?
These methods work just as well for auditing your own store. Shopify names installed apps among the biggest factors in storefront performance, and its performance guide warns that too many apps loading assets can slow a store down.
- In your Shopify admin, go to Settings > Apps and list what's installed, as Shopify's uninstall guide describes.
- Open your storefront's page source and Network tab, and list every app that loads.
- Compare the two lists. Code from an app that isn't installed is leftover code. An installed app that loads on pages where it does nothing may be worth limiting.
To act on the results, switch off app embeds you don't use in the theme editor, uninstall apps you no longer need and remove leftover code on a duplicate theme. Our Shopify speed optimization checklist walks through each of those steps. ShopOpsy's apps page lists our Shopify apps: Cookify for cookie consent, Doorcheck for age verification and Topline for announcement bars, whose App Store listings are pending, and others still in development.
How do you keep the research fair?
Checking which apps a store uses is ordinary research when you stick to what any visitor's browser receives. Don't try to sign in to a store's admin, get past a password page, place orders you don't intend to keep or run automated scans at a volume that burdens the site. Read the store's terms if you plan to collect data systematically, and don't copy its text, images or app setup: knowing which reviews app a brand uses gives you no rights to its content. This is general information, not legal advice.
Troubleshooting: why can't I find any apps?
| What you see | Likely cause | What to try |
|---|---|---|
| Almost no code in the page source | Headless storefront | Use the Network tab and look at checkout |
| A password page | The store isn't open to the public | Nothing to inspect until it opens |
| No analytics or marketing scripts | Cookie banner waiting for consent | Accept cookies in a fresh private window |
| A tool lists an app you can't find | Old fingerprint, or leftover code that never runs | Ask what it matched, then search the source |
| An app appears on one page only | App blocks are placed per template | Check product, collection, cart and search pages |
| Different results on your phone | Mobile-only sections or settings | Use the DevTools device toolbar or a real phone |
Frequently asked questions
Can I see which theme a Shopify store uses?
Often. Search the source for Shopify.theme. On the stores we checked, it showed the theme name as the merchant saved it, a schema name set by the theme's developer and, for Theme Store themes, a theme_store_id. Merchants often rename their theme copies, so the schema name is usually the better clue. ShopOpsy's free Shopify theme detector reads these values for you.
Can a store hide which apps it uses?
Partly. A browser has to download every script it runs, so storefront code can always be seen. A store can still make apps harder to name, for example by loading tags through a tag manager, using custom apps or keeping features in the backend.
Sources
- About theme app extensions — Shopify developer documentation, accessed 26 October 2026.
- Configure theme app extensions — Shopify developer documentation, accessed 26 October 2026.
- Script tag deprecation — Shopify developer documentation, accessed 26 October 2026.
- Order status script tags — Shopify developer documentation, accessed 26 October 2026.
- ScriptTag object — Shopify developer documentation, accessed 26 October 2026.
- About app proxies and dynamic data — Shopify developer documentation, accessed 26 October 2026.
- About web pixels — Shopify developer documentation, accessed 26 October 2026.
- Checkout UI extensions — Shopify developer documentation, accessed 26 October 2026.
- About Shopify Functions — Shopify developer documentation, accessed 26 October 2026.
- Ajax API — Shopify developer documentation, accessed 26 October 2026.
- Cart API reference — Shopify developer documentation, accessed 26 October 2026.
- asset_url filter — Shopify developer documentation, accessed 26 October 2026.
- Section schema — Shopify developer documentation, accessed 26 October 2026.
- Create and update a cart with the Storefront API — Shopify developer documentation, accessed 26 October 2026.
- Domains — Shopify Help Center, accessed 26 October 2026.
- App pixels — Shopify Help Center, accessed 26 October 2026.
- Extend your theme with apps — Shopify Help Center, accessed 26 October 2026.
- Uninstalling apps — Shopify Help Center, accessed 26 October 2026.
- Improving your online store performance — Shopify Help Center, accessed 26 October 2026.
- Upgrading and replacing your Thank you and Order status pages — Shopify Help Center, accessed 26 October 2026.
- Adding store policies — Shopify Help Center, accessed 26 October 2026.
- Network features reference — Chrome for Developers, accessed 26 October 2026.
- Open Chrome DevTools — Chrome for Developers, accessed 26 October 2026.
- Chrome keyboard shortcuts — Google Chrome Help, accessed 26 October 2026.
- Regulation (EU) 2016/679 (General Data Protection Regulation) — EUR-Lex, accessed 26 October 2026.
- What privacy information should we provide? — Information Commissioner's Office, accessed 26 October 2026.


