Microsoft Edge

At a glance

• Browser class: chromium (the user agent has a Chrome/<number> token).
• Excluded components: none.
• Chromium-only components that are ok: device_memory, heap_limit, ua_client_hints, ua_versions, keyboard_layout.
• Skipped on purpose on desktop: audio_latency.
• Lab sample: none.

What works

All of the Chrome desktop list applies:

• the graphics group (canvas and WebGL with the double render, WebGL parameters, the unmasked renderer and vendor, and WebGPU where Edge offers it);
• device_memory, heap_limit and keyboard_layout;
• ua_client_hints: the brands are whatever Edge reports, without versions and with the GREASE brand removed; ua_versions adds the full versions outside the ids;
• fonts, font preferences, offline audio, Math, codecs, locale, storage presence, permission states and the display preference queries.

WhiskerJS has no Edge-specific code. It reads the same APIs in the same way; any difference from Chrome comes from what Edge itself returns.

What is unavailable or blocked

• audio_latency: unavailable / skipped on desktop, to avoid a console autoplay warning.
• apple_pay and private_click: the plain value none.
• ua_client_hints and ua_versions end with he=blocked when a Permissions Policy refuses the detailed hints.
• keyboard_layout is blocked in cross-origin iframes.
• webgpu: depends on the Edge version, the operating system and the GPU.

What WhiskerJS excludes and why

Nothing. The chromium row of the exclusion table is empty. If an extension or setting adds noise to canvas or WebGL readback, the double render reports noisy with ruleId render_mismatch for that run. The known-answer probes also catch noise that is the same on both reads (noisy / seeded_noise, for canvas, webgl_image and audio). From Chromium 146, device_memory carries the tag ;c146.

Edge and Chrome on the same device

Both are class chromium, so browser_class is the same. Expect differences in:

• ua_client_hints: the brand list;
• vendor_flavors, plugins and media_codecs, where the builds differ;
• fonts and graphics, usually not, because they follow the operating system and GPU.

The structuredId shows this directly: the browser group differs while gpu, fonts and device often match. See Comparing two results.

Integrity flags to expect

The same as in Chrome: automation_webdriver under WebDriver control, headless_user_agent and headless_markers for headless builds, software_renderer with hardware acceleration off or on remote desktops, the lie checks (native_tampering, prototype_lie) with extensions that override functions, ua_ch_mismatch with user-agent switchers, and vm_renderer on virtual desktops. Headless Edge is classed chromium since signalsVersion 9, like headless Chrome.

Early lab observations

There is no lab data for Edge yet. The early, small sample at signalsVersion 1 covered Mac Chrome, Mac Safari, iPhone Chrome and iPhone Safari only.

Testing it yourself

Open the live demo in Edge and in Chrome on the same machine and compare the structuredId groups. The lab mode copies one line per run. Nothing is sent anywhere.

Support table for Microsoft Edge

Expected status of every component in this browser at signalsVersion 9, from the support matrix (updated 2026-10-26). Basis "code" means expected from the library code and documentation, not yet measured; "lab" means seen in the early lab sample.

Component	Status	Basis	Note
apple_pay	none	code	No ApplePaySession: reports the plain value none.
audio	ok	code	noisy / seeded_noise if the audio known-answer probe sees noise.
audio_latency	unavailable	code	Skipped (unavailable / skipped): creating an AudioContext here would print a console warning.
browser_class	ok	code	Class chromium.
canvas	ok	code	noisy / render_mismatch or seeded_noise if an extension or setting adds noise to readback.
canvas_readback	ok	code
color_depth	ok	code
color_gamut	ok	code
content_blockers	ok	code	none, or the bait names a content blocker hid.
cpu_architecture	ok	code
device_memory	ok	code	From Chromium 146 the value carries the tag ;c146 (new buckets).
dynamic_range	ok	code
font_preferences	ok	code
fonts	ok	code
fonts_canvas	ok	code
forced_colors	ok	code
hardware_concurrency	ok	code	Read 16 times; noisy / read_varies if the reads disagree. Some browsers cap or round the value.
heap_limit	ok	code
intl_locale	ok	code
keyboard_layout	ok	code	navigator.keyboard.getLayoutMap() is a Chromium desktop API; blocked in cross-origin iframes.
languages	ok	code
math	ok	code
media_codecs	ok	code
noise_profile	ok	code	canvas=exact,webgl=exact,audio=exact on a stock browser; webgl=na without WebGL.
pdf_viewer	ok	code
permissions	ok	code
pixel_ratio	ok	code
platform	ok	code
plugins	ok	code
prefers_contrast	ok	code
private_click	none	code	No attributionSourceId on anchors: reports the plain value none.
reduced_motion	ok	code
screen_frame	ok	code
screen_resolution	ok	code
speech_voices	ok	code	Digest of the voice list, or none; some browsers fill the list late.
storage	ok	code
time_zone	ok	code
touch_support	ok	code
ua_client_hints	ok	code	he=blocked when a Permissions Policy refuses the detailed hints.
ua_versions	ok	code
vendor	ok	code
vendor_flavors	ok	code
webgl_image	ok	code	noisy / render_mismatch or seeded_noise if an extension or setting adds noise to readback.
webgl_params	ok	code	Where WebGL 1 is available; unavailable / no_context without it.
webgl_renderer	ok	code
webgl_vendor	ok	code
webgpu	varies	code	Depends on browser version, operating system and GPU; needs a secure context. unavailable / no_api without navigator.gpu, no_context without an adapter.

Questions and answers

Related pages