How to See What Apps Any Shopify Store Is Running
Every Shopify store you visit is quietly running a stack of apps — review widgets, email pop-ups, upsell tools, loyalty programs, chat bubbles — and most of them leave fingerprints right in the page. If you've ever looked at a competitor's store and wondered how they built that "frequently bought together" section, or you're trying to figure out why your own store loads slowly, you can usually find out in a few minutes without any special access.
This guide walks through every practical method, from a five-second look at the page to purpose-built scanners, and — just as importantly — where each method falls short. Because the honest truth is that no method from the outside sees everything, and knowing the blind spots matters as much as knowing the tricks.
Why anyone bothers checking
There are really two reasons people want to see a store's apps, and they shape which method is worth your time.
The first is competitor research. If a rival store is doing something clever — a slick bundle builder, a subscription option, a particular review layout — the app behind it is often something you can install too. Seeing their stack is a shortcut to "how did they do that."
The second is auditing your own store. Apps accumulate. You install one for a sale, another for a season, a third for an experiment, and a year later you're paying for six things and can't remember what half of them do — or worse, you uninstalled some and their code is still loading and slowing your store down. Looking at your own stack from the outside, the way a visitor's browser sees it, is a surprisingly useful reality check.
Both goals use the same techniques. Let's go through them.
Method 1: Read the page source yourself
This costs nothing and requires no tools — just your browser. On any Shopify store, right-click and choose "View Page Source" (or press Ctrl+U on Windows, Cmd+Option+U on a Mac). You'll get the raw HTML the store sent your browser, and apps leave clear traces in it.
What to look for:
- App asset URLs. Shopify serves app code from a predictable address that looks like
cdn.shopify.com/extensions/<some-id>/<app-name>/.... The app name in that path often tells you exactly which app it is —judgeme,loox,sezzle-widget, and so on. - Vendor script domains. Many apps load code from their own servers. Spotting
static.klaviyo.commeans the store runs Klaviyo;loox.iomeans Loox reviews;static.rechargecdn.commeans Recharge subscriptions. A quick search of the page (Ctrl+F) for ".com" or ".io" surfaces these fast. - The theme. Search the source for
Shopify.themeand you'll usually find the theme's name and whether it's a paid theme from the Shopify Theme Store.
This method is transparent and free, but it's tedious, and you need to recognize the fingerprints to make sense of what you're seeing. It's a great way to confirm a specific suspicion ("are they using Klaviyo?") and a slow way to inventory a whole stack.
Method 2: Look at the storefront with your eyes
Before you touch any code, a lot of a store's stack is visible just by browsing it. Apps that add visible features announce themselves:
- Star ratings and review sections under products point to a reviews app (Judge.me, Loox, Yotpo, Okendo, and others each have a recognizable look).
- A chat bubble in the corner is a support app like Gorgias or Tidio.
- A "Subscribe and save" option means a subscriptions app.
- Buy-now-pay-later messaging ("4 payments of...") indicates Sezzle, Klarna, Afterpay, or similar.
- A spin-to-win wheel or email pop-up is a marketing/pop-up app.
Browsing a product page and adding something to the cart will surface far more than the homepage alone, because review widgets, upsells, and payment options concentrate on product and cart pages. This method won't name the exact app every time, but it tells you what kinds of apps are in play, which is often what you actually care about.
Method 3: Browser extensions
Several free browser extensions detect the technology on any site you visit and will flag Shopify apps among the results. General-purpose ones identify the broad tech stack; a few are built specifically for Shopify and recognize a decent catalog of apps. Install one, visit a store, click the icon, and you get a list.
The upside is speed and zero learning curve. The downsides: coverage varies a lot between extensions, some clutter their results with things that aren't really "apps" (payment icons, analytics tags), and you're trusting a third party with your browsing. Still, for a quick look, an extension is the least-effort option.
Method 4: Dedicated scanner tools
This is the category built for exactly this job: paste a store URL into a website and it reports the apps, often with extra detail like the theme, estimated costs, or the marketing pixels the store runs. Scanners do the fingerprint-reading from Method 1 automatically and against a large catalog, so they name apps you'd have to look up by hand.
These tools differ in what they emphasize. Some are aimed squarely at competitor research and lead with "see what your competitors use." Others focus on the self-audit angle — for example, StackGander scans a store across several page types and reports not just the app list but an estimated monthly app spend and any leftover embeds from apps that look uninstalled, which is useful if you're trying to trim your own bill rather than copy someone else's. The right scanner depends on which of the two goals above you have.
A quick note on reading scanner results critically: a bigger "detected" number isn't automatically better. Some tools pad their counts with payment icons (Visa, Apple Pay) and analytics pixels, which every store has and which tell you nothing about the store's actual paid apps. When comparing tools, look at whether they surface the paid apps that matter, not just the count.
What none of these methods can see
Here's the part most guides skip. Scanning a store from the outside — by any method above — has real blind spots, and pretending otherwise leads you to wrong conclusions.
- Backend-only apps are invisible. Accounting, inventory, shipping-label, and fulfillment apps don't add anything to the storefront, so nothing you do from the outside will reveal them. A store can run a dozen backend apps that no scanner will ever show.
- Tag-manager-injected tracking hides. Many stores load their analytics and ad pixels through Google Tag Manager, which fires them after the page's JavaScript runs. A tool that reads the raw page (rather than running a full browser) won't see those pixels at all. So a short pixel list doesn't mean a store isn't tracking heavily — it may just be routing everything through a tag manager.
- Custom and private apps don't fingerprint. A store that built its own app, or uses a private one, won't match any catalog. You'll see that something is there, but not what it is.
None of this makes external scanning useless — it's genuinely good at finding the common, storefront-visible, paid apps, which is most of what drives both competitor research and app-spend audits. It just isn't complete, and any tool claiming it sees everything is overselling.
A practical workflow
If you just want a fast answer, use a scanner or an extension and move on. If you want to be thorough — say you're seriously reverse-engineering a competitor or cleaning up your own store — combine methods:
- Browse the storefront, including a product page and the cart, and note the visible features.
- Run the store through a scanner to get named apps and, if you care about cost, an estimated spend.
- Spot-check anything surprising by viewing the page source yourself.
- Remember the blind spots — assume there are backend apps and possibly tag-manager tracking you can't see.
Auditing your own store
If the store you're checking is your own, the outside view is a starting point, not the whole picture. It'll show you the storefront-visible apps and roughly what they cost, which is often enough to spot redundancy — two review apps, an old pop-up tool you forgot about, leftover code from something you uninstalled. For the complete and exact picture, including backend apps and precise billing, you'd look at your Shopify admin's billing and installed-apps pages directly. But the outside scan is the fast way to notice that you have a problem worth investigating — the "wait, I'm paying for how many apps?" moment that sends you into the admin to clean house.
The short version
You can see most of what any Shopify store runs in a few minutes: browse it, read the page source, use an extension, or paste it into a scanner. Each method trades effort for completeness, and all of them share the same blind spots — backend apps, tag-manager-hidden tracking, and custom apps stay out of view. Pick the method that matches your goal, read the results with a critical eye, and remember that the absence of evidence isn't evidence of absence. For a quick, named inventory of a store's apps plus an estimate of what they cost per month, a purpose-built scanner is the fastest path; for anything deeper, combine it with a look at the page yourself.