Detection Guide · 2026
How to Detect Moodle Theme on Any Website
Moodle is the world's most-used learning management system. Detection involves finding Moodle-specific URL paths, JavaScript globals, and theme directory references.
Fastest way: use our free detector
Paste any URL and get the Moodle theme, plugins, and stack in 2 seconds.
Open the Moodle Detector →What our detector looks for
/theme/[name]/ asset paths
Moodle serves the active theme from /theme/[theme-name]/. The path is visible in CSS and JS imports.
Where: HTML <link> and <script> tags
M.cfg JavaScript object
Moodle exposes window.M.cfg containing wwwroot, sesskey, and theme info. M.util.* utilities are also Moodle-specific.
Where: Inline <script>
moodlepluginurl and M.str.*
Moodle's localization system populates M.str at page load — a strong Moodle signal.
Where: JavaScript runtime
MoodleSession cookie
Moodle sets a MoodleSession cookie on authenticated requests.
Where: HTTP Set-Cookie headers
/login/index.php login form
The default Moodle login lives at /login/index.php and has very stable HTML markup.
Where: URL path
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 '/theme/' or 'M.cfg' — Moodle-specific.
- 2
Look for 'moodle' in HTML class names or comments.
- 3
DevTools Console → type M.cfg — if defined, the site is Moodle and the response reveals the theme.
- 4
Check for /pluginfile.php URLs — Moodle's file serving endpoint.
- 5
Visit /login/index.php on the site — the markup is highly recognizable.
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.