Detection Guide · 2026
How to Detect Magento Theme on Any Website
Magento (now Adobe Commerce) powers many enterprise ecommerce sites. Detecting the active theme requires inspecting characteristic URL paths and asset locations.
Fastest way: use our free detector
Paste any URL and get the Magento theme, plugins, and stack in 2 seconds.
Open the Magento Detector →What our detector looks for
/pub/static/ asset paths
Magento 2 serves compiled assets from /pub/static/version[number]/frontend/[Vendor]/[Theme]/. The [Vendor]/[Theme] segment identifies the theme.
Where: HTML <link> and <script> tags
Mage class names and IDs
Magento generates predictable DOM structures: product-info-main, page-wrapper, .checkout-cart-index. These confirm Magento even if obfuscated.
Where: HTML element classes
Magento JS modules
/static/_requirejs/requirejs-config.js or Magento_Customer/js/ paths indicate Magento 2.
Where: JavaScript file URLs
Frontname URLs
Magento's URL patterns include /catalog/product/, /checkout/cart/, /customer/account/. These are very stable across installations.
Where: HTML <a> hrefs
Cookies
Magento sets PHPSESSID, frontend, X-Magento-Vary cookies on storefront pages.
Where: HTTP Set-Cookie headers
Manual inspection checklist
If the detector returns inconclusive results, walk through these manual checks in your browser's developer tools (right-click → Inspect):
- 1
View source. Search for '/pub/static/' — present on every Magento 2 storefront.
- 2
Look for the path segment after /frontend/ — that's the Vendor/Theme identifier.
- 3
Check for /static/version followed by a number — that's Magento's static asset versioning.
- 4
DevTools Network tab → check for requests to mage/*.js or Magento_*/js/ paths.
- 5
Look at URL structure for catalog/product/view/id/... patterns.
Why identify a site's stack?
Three legitimate reasons: competitive research (which tools is the leader in your space using?), lead qualification (does this prospect's site qualify for your service?), and migration planning (you need to know the current stack before quoting a redesign).
All of the above are public-record activities — every signal we check is visible in the page's HTML or HTTP response, the same data anyone with View Source can see. We just parse it faster and present it cleanly.
What detection can't tell you
Detection identifies what's running. It can't tell you why a site chose that stack, how much they spend on it, who their developer is, or what their roadmap is. For those, talk to a human.
It also can't see through aggressive caching, headless setups, or themes built from scratch without the framework's default markers. We flag low-confidence detections so you know when to dig deeper.