WordPress Theme & Plugin Detector
Paste the HTML source of any page to detect its WordPress theme, active plugins, and the tech stack behind it (Elementor, Divi, WooCommerce, Gutenberg and more). Everything runs in your browser.
Paste the full HTML source of a page. This tool does not load URLs - it inspects the HTML you paste. Tip: open the page, press Ctrl+U (Cmd+Option+U on Mac) for View Source, then copy everything.
About this tool
The WordPress Theme and Plugin Detector reads the same public clues a developer looks for when they want to know what powers a site: the asset paths, class names, and meta tags baked into a page's HTML. Paste a page's source and it reports whether the site runs WordPress, which theme is active, which plugins it can find, and the wider tech stack such as Elementor, Divi, WooCommerce, or the block editor.
How detection works
WordPress serves its files from predictable locations. Themes live under /wp-content/themes/<name>/ and plugins under /wp-content/plugins/<name>/, and each enqueued stylesheet or script usually carries a ?ver= query string. The tool scans every link, script, and image reference for those paths, pulls out the theme and plugin slugs, and reads versions where they are exposed. It also looks at the generator meta tag, body classes, and well-known fingerprints (for example et_pb_ for Divi or wp-block- for the block editor).
Why paste HTML instead of a URL
A browser cannot read the HTML of another website directly because of cross-origin security rules, and ToolCreek never fetches pages on a server for you. Pasting the source keeps the whole process in your browser with zero requests, which is faster, completely private, and works even on staging sites or pages behind a login that you can already see.
What it can and cannot find
- Front-end only. It detects plugins and themes that add visible CSS, JavaScript, or markup to the page. Plugins that only run in the admin or do background work leave no front-end trace.
- Renamed or proxied paths. Some security plugins and CDNs rewrite
wp-contentpaths, which can hide or rename themes and plugins. - Versions. Version numbers come from
?ver=strings and the generator tag, which site owners can strip or fake.
Treat the result as strong evidence rather than absolute proof, and combine it with your own judgement.
About the WordPress Theme & Plugin Detector
This WordPress theme detector inspects a page's pasted HTML source to tell you whether a site runs WordPress, which theme is active, and which plugins it can find. As a theme checker and theme finder it reads the markup for fingerprints like wp-content/themes/ and wp-content/plugins/ paths, ?ver= version strings, the generator meta tag, and body classes, and it doubles as a plugin detector that flags tech such as Elementor, Divi, WooCommerce, and the block editor. It never fetches a URL. You paste the HTML and it runs 100% in your browser.
How it works
- Open the target page in your browser, then view its source. Press Ctrl+U on Windows or Option+Command+U on a Mac, or use the browser menu's View Source option.
- Select all of the source and copy it.
- Paste the HTML into the input box on this page.
- Read the results: whether WordPress was detected, the active theme name, any plugins found, and tech like Elementor, Divi, WooCommerce, and the block editor.
Features
- Detects WordPress from telltale markup including wp-content paths, the generator meta tag, and standard body classes.
- Identifies the active theme by reading the wp-content/themes/ folder name in stylesheet and asset URLs.
- Finds plugins by scanning wp-content/plugins/ asset paths and known signatures.
- Flags popular tech such as Elementor, Divi, WooCommerce, and the Gutenberg block editor.
- Fully client-side. You paste HTML, nothing is uploaded, and no URL is fetched.
Frequently asked questions
How does the detection actually work?
It scans the pasted HTML for WordPress fingerprints. The strongest signals are asset URLs that include wp-content/themes/ and wp-content/plugins/, which reveal the theme folder and plugin slugs. It also reads ?ver= query strings on CSS and JS files for version numbers, the generator meta tag, and body classes the editor and themes add.
Why are some plugins not detected?
Detection relies on front-end traces in the HTML. Plugins that only run in the admin area, or that add no CSS, JS, or markup to the public page, leave nothing to find. Caching, asset bundling, and optimization plugins can also merge or rename files so individual plugin paths disappear.
Why might a renamed wp-content folder or a CDN hide things?
Some sites rename or move wp-content for hardening, and many serve assets from a CDN on a different domain. Both change the URL paths the detector looks for, so the usual wp-content/themes/ and wp-content/plugins/ fingerprints may not appear even though the site really runs WordPress.
Are the version numbers reliable?
Treat them as hints, not facts. Versions come from ?ver= strings on assets and from the generator tag. Many sites strip the generator tag, set a fixed cache-busting ?ver= value, or fake the number for security, so a missing or odd version does not prove much.
Why does it inspect pasted HTML instead of fetching a URL?
Browsers block cross-origin requests through CORS, so a tool running in your browser cannot reliably fetch another site's HTML. Pasting the source keeps everything local: the tool never reaches out to a server, and your URLs are never fetched on your behalf.