Microsoft Edge user agent
Modern Microsoft Edge is built on Chromium, so its user agent looks like Chrome's but carries an additional Edg/ product token near the end. That Edg/ marker is how you distinguish Edge from Google Chrome and other Chromium browsers in logs. This page explains the pattern and its pitfalls.
The Edge UA pattern
Microsoft Edge moved to the Chromium engine, so its user agent shares Chrome's shape: a legacy Mozilla prefix, a platform descriptor, an AppleWebKit token, and a Chrome product token. What sets Edge apart is an extra Edg/ token (note the spelling, without the trailing 'e') near the end of the string.
Match on the Edg/ token to identify Edge. The Chrome token alone is not enough, because every Chromium browser carries it for compatibility.
- Chromium-based: shares Chrome and AppleWebKit tokens
- Distinguishing marker: an Edg/ product token
- Match on Edg/, not the Chrome token, to identify Edge
Why the Edg/ spelling and order matter
The token is deliberately Edg/ rather than Edge/ in the desktop Chromium build, a historical naming choice. Older, pre-Chromium Edge used different tokens (such as Edge/ or EdgeHTML), so an exact-string match written for one era breaks on the other.
Match on the stable Edg/ pattern rather than a full version string, and confirm token specifics against Microsoft's documentation, since UA detail can change with releases.
How it appears in analytics and logs
A user agent that carries Chrome and AppleWebKit tokens plus an Edg/ token is Microsoft Edge on Chromium. Without the Edg/ marker it is some other Chromium browser, not Edge.
Diagnostic use case
Recognise Microsoft Edge traffic in logs and analytics by its Edg/ token, and avoid lumping it together with plain Chrome.
What WebmasterID can help detect
WebmasterID recognises Edge server-side from its Edg/ token and records a coarse browser category, so Edge is not silently merged into a generic Chrome bucket.
Common mistakes
- Counting Edge as plain Chrome because both carry a Chrome token.
- Searching for Edge/ when modern Chromium Edge uses Edg/.
- Hard-coding a full Edge version string that changes each release.
Privacy and accuracy notes
Edge's user agent describes the browser, not a person. WebmasterID stores a coarse browser category rather than the raw string of a real visitor.
Related pages
- Chrome user agent and its quirks
Chrome's user-agent string is full of historical artefacts: it claims AppleWebKit and Safari for compatibility even though Chrome uses the Blink engine. Google has also reduced the detail Chrome exposes in the UA, moving fine-grained information into User-Agent Client Hints. This page explains the pattern and the quirks.
- Browser user agents: how to read them
A browser user-agent string packs several tokens into one line: a legacy Mozilla prefix, a rendering-engine signature, the platform, and the browser itself. This page explains each part so you can read a UA without over-reading it, because the contents are client-controlled and can be copied by any client.
- Bot intelligence
Deterministic categorisation of browsers, crawlers, and automation.
Sources and verification notes
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.