Microsoft Edge User Agent Strings for Windows, macOS, Android, iOS & Xbox

Latest Microsoft Edge User Agent Strings by Platform

The current Edge user agent on Windows — the string most servers see:

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/150.0.0.0 Safari/537.36 Edg/150.0.0.0

Two things to notice: the version tokens are reduced to 150.0.0.0 (the real build, 150.0.4078.65, is only exposed via Client Hints), and because Edge is the Chromium UA plus an Edg/ token, any naive check for "Chrome/" also matches Edge. Here is the full platform table:

Note the platform freezes: Windows 11 still says "Windows NT 10.0", macOS is locked to Catalina's "10_15_7", and Android always reports "Android 10; K" regardless of the real device. One asymmetry worth knowing: Edge on iOS reports the real iOS version (26_5_0 above) because third-party WebKit browsers are not covered by Safari's frozen-UA policy — Safari itself still reports an 18_x token on iOS 26. See our Safari user agents reference for that side of the story.

Edg vs EdgA vs EdgiOS vs Edge: The Token System

Microsoft uses a different identifier token per platform — and the presence or absence of a final "e" matters a lot when you're debugging detection code:

Warning for anyone maintaining older code: "Edg" (modern, Chromium) and "Edge" (legacy, EdgeHTML) are different browsers. Microsoft explicitly recommends mapping them to different names so legacy EdgeHTML workarounds are never applied to modern Edge — and when parsing, always test the Edge tokens before "Chrome", since every desktop and Android Edge UA contains a Chrome token too.

Modern Edge (Chromium) vs. Legacy Edge (EdgeHTML)

The original Microsoft Edge ran on Microsoft's own EdgeHTML engine and identified itself with the Edge/ token — version 18 was its last release:

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.102 Safari/537.36 Edge/18.19582

On January 15, 2020, Microsoft replaced it with the Chromium-based Edge (jumping the version number from 18 straight to 79), which renders with the same Blink engine as Google Chrome and appends Edg/ instead. The missing "e" was deliberate: years of "Edge" sniffing code had accumulated EdgeHTML-specific workarounds, and a fresh token let the new browser start clean. Edge Legacy was retired in 2021 and never supported Client Hints — its UA string was its only detection mechanism. The one place the legacy token survives is the Xbox browser, which is Chromium Edge underneath but keeps a frozen "Edge/44.18363.8131" token for compatibility.

Detecting Edge with User-Agent Client Hints (UA-CH)

Because the UA string is now frozen and reduced, Microsoft's guidance is: use feature detection where possible, and User-Agent Client Hints when you genuinely need to know the browser. Edge sends three low-entropy headers with every HTTPS request, and servers can request more via Accept-CH:

Sec-CH-UA: "Chromium";v="150", "Microsoft Edge";v="150", "Not_A Brand";v="99"
Sec-CH-UA-Mobile: ?0
Sec-CH-UA-Platform: "Windows"

Accept-CH: Sec-CH-UA-Full-Version-List, Sec-CH-UA-Platform-Version

In JavaScript, the same data is available through navigator.userAgentData. Always iterate the brands array — the "Not_A Brand" GREASE entry varies its spelling and position on purpose to break brittle parsers:

// navigator.userAgentData exists only in Chromium browsers —
// Firefox and Safari always need the UA-string fallback below.
function isEdge() {
  if (!navigator.userAgentData) return false;
  return navigator.userAgentData.brands.some(
    (b) => b.brand === "Microsoft Edge"
  );
}

// Full version is high-entropy: async, opt-in, and the browser may decline.
// Use fullVersionList — uaFullVersion is deprecated.
async function edgeFullVersion() {
  const data = await navigator.userAgentData.getHighEntropyValues(["fullVersionList"]);
  const edge = data.fullVersionList.find((b) => b.brand === "Microsoft Edge");
  return edge ? edge.version : null; // e.g. "150.0.4078.65"
}

For browsers without navigator.userAgentData, or for server-side parsing, fall back to the token system:

// Test Edge tokens BEFORE "Chrome" — the Edge UA contains Chrome/150.0.0.0 too.
function detectEdgeFlavor(ua) {
  const m = ua.match(/\b(EdgiOS|EdgA|Edg|Edge)\/([\d.]+)/);
  if (!m) return null;
  const flavors = {
    Edg: "Edge on desktop (Chromium)",
    EdgA: "Edge on Android",
    EdgiOS: "Edge on iOS/iPadOS (WebKit)",
    Edge: "Edge Legacy (EdgeHTML, retired) or Xbox",
  };
  return { flavor: flavors[m[1]], version: m[2] };
}

Bonus tip: since the UA string reports "Windows NT 10.0" on Windows 11, the only web-exposed way to tell Windows 10 from Windows 11 is the Sec-CH-UA-Platform-Version hint — a major version of 13 or higher means Windows 11.

How to Check and Change Edge's User Agent

• Check it: type edge://version in the address bar — the exact user agent appears under "User agent". Or run navigator.userAgent in the DevTools console (F12).
• Change it: in DevTools, press Ctrl+Shift+P (Cmd+Shift+P on macOS), type "network conditions", open Show Network conditions, uncheck "Use browser default" under User agent, then pick a preset or enter a custom string. The same panel includes a User agent client hints editor. The override lasts only while DevTools is open for that tab.
• Good to know: Edge Stable ships Microsoft-supplied per-site UA overrides for compatibility (see edge://compat/useragent) — so the UA a particular website receives from Edge can differ from the default. One more reason server-side UA sniffing is unreliable.

Remember that spoofing the UA never changes the engine — to see how your site really behaves in Edge, test on real Edge browsers online, including older Edge Chromium versions, as part of your cross browser testing.

Frequently Asked Questions About Edge User Agents

What is the user-agent for Microsoft Edge?

On Windows, the current Microsoft Edge user agent is: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/150.0.0.0 Safari/537.36 Edg/150.0.0.0. It is the standard Chromium user agent with an Edg/ token appended, and the version numbers are intentionally reduced to major.0.0.0 — the full build number is only exposed through User-Agent Client Hints.

What is Microsoft Edge's current version?

As of July 17, 2026, the current stable version of Microsoft Edge is Edge 150 — build 150.0.4078.65 on desktop (released July 9, 2026) and on Android and iOS (released July 13, 2026). Edge 151 is expected the week of July 30, 2026. You can check your exact version and user agent by typing edge://version in the address bar.

Can my user agent be used to track me?

Partly. The user agent is sent with every request and historically carried enough detail (exact build, OS version, device model) to be a meaningful browser-fingerprinting signal when combined with other data — it cannot identify you alone, but it narrows you down. That is why Chromium reduced the UA string: Edge now reports frozen version and platform tokens (Edg/150.0.0.0, Windows NT 10.0, Android 10; K), and detailed data moved to User-Agent Client Hints, where high-entropy values like full version and CPU architecture are only shared when a site explicitly requests them.

What is the difference between Edg, EdgA, EdgiOS, and Edge?

They are platform identifiers: Edg is Chromium-based Edge on desktop (Windows, macOS, Linux), EdgA is Edge on Android, EdgiOS is Edge on iPhone and iPad, and plain Edge belongs to the retired EdgeHTML-based Edge Legacy (and survives as a frozen compatibility token in the Xbox browser). Microsoft deliberately chose "Edg" without the final e so the new browser would not trigger old Edge Legacy detection code and its workarounds.

What is my User Agent?