Skip to Content
Platform.Ontology

Cross-origin isolation (SharedArrayBuffer, COOP, COEP)

A site can opt into an isolated mode that unlocks SharedArrayBuffer, precise timers and Wasm threads.

Works without askingThings a page can doComputeWeb browsersWhile you use it

In one line

Can switch on a locked down mode that unlocks fast shared memory for the page

A site can opt into an isolated mode that unlocks SharedArrayBuffer, precise timers and Wasm threads.

Isolation trades openness (no cross-origin popups or unmarked embeds) for power. Sites with it get memory sharing and 5 microsecond timers, which are also better side channel tools.

What it can and can't do

What the user does: Nothing. It happens when the site loads with the right security headers set.

It can

  • Share memory between background threads for heavy apps like games and editors
  • Run the page's own code with very precise timers
  • Start multi threaded compiled code inside the page

It cannot

  • Open popups that stay linked to other sites while isolation is on
  • Load embedded videos, ads or widgets that are not marked to allow it
  • Turn itself on without the site's own server sending the right headers
  • See anything in other tabs or other sites

How it differs between platforms: Works in Chrome, Edge, Firefox and Safari, including on iPhone and Android.

Browser support

BrowserStatusFirst versionReleasedNote
ChromeSupported872020-11-17None
EdgeSupported872020-11-19None
FirefoxSupported722020-01-07None
SafariSupported15.22021-12-13None
Safari on iPhoneSupported15.22021-12-13All iOS browsers use WebKit
Chrome on AndroidSupported872020-11-17None
Samsung InternetSupported14.02021-04-17None

How a site asks for it

APICross-Origin-Opener-Policy: same-origin; Cross-Origin-Embedder-Policy: require-corp or credentialless; self.crossOriginIsolated
Browser compat keysapi.Window.crossOriginIsolated
api.SharedArrayBuffer
How access is grantednone
What the user seesNone (no browser prompt)
Needs a secure context (HTTPS)No
Needs a user gestureNo
Activationnone
How long it lastsSet per document via headers
How to take it backNothing to revoke (no permission is stored)
Inside an iframeEmbedded frames need CORP or CORS (require-corp) or credentialless mode

Typical flow

  1. Server sends COOP and COEP headers
  2. crossOriginIsolated becomes true
  3. SharedArrayBuffer and fine timers become available

Data you get

Shape: none

No individual data fields. The signal is the access itself.

Technical limits

  • SharedArrayBuffer requires crossOriginIsolated (Chrome 92, Firefox 79, Safari 15.2)
  • COEP require-corp: every subresource needs CORP or CORS; credentialless mode available in Chrome 96 and Firefox 119
  • COOP same-origin severs window.opener to cross-origin popups (breaks OAuth popups unless same-origin-allow-popups)
  • Isolated pages get performance.now at 5 microsecond resolution (Chrome) instead of 100 microseconds
  • Chrome on Android got SharedArrayBuffer under the same rule in 92

The story

What it is

A site can switch on a locked down mode that unlocks very fast, shared memory tricks.

For you

You never see a prompt. A big web app just runs smoother, but some embedded widgets, like a video or ad frame, may refuse to load until their owners add the right labels.

For makers

Makers flip this on to get shared memory and multi threaded compiled code, which game engines and heavy editors need. The cost is that every third party embed on the page must opt in too, which is a real project for ad heavy sites.

Where you see it

TypeExampleApps
gamesA Unity or Unreal game exported to the browser uses several worker threads at once, which only works when the page is isolated.Unity WebGL games, Unreal web exports
creativeA web video editor trims and renders clips using many CPU threads so the preview stays smooth.Clipchamp, CapCut web
productivitySpreadsheets and CAD tools in the browser share one big block of memory between workers to crunch numbers faster.AutoCAD web
developerAn in browser coding sandbox runs a whole Node style environment and needs shared memory to do it.StackBlitz WebContainers
securitySecurity teams use isolation to make sure that a page cannot be read by other sites' scripts, a defence against Spectre style attacks.None named
adsAd networks must retag their frames and scripts so a publisher can turn isolation on without breaking ad slots.Google Ad Manager

Risks

  • Broken embeds
  • Timing attacks if misconfigured

What the platform says

  • Google: Cross-origin isolation. Chrome's web.dev guide says isolation unlocks powerful features like SharedArrayBuffer and high precision timers, in exchange for stricter rules about embeds.

Good uses and abuse

Legitimate uses

  • Wasm threads
  • High resolution profiling
  • Large in-browser apps

Known abuse

  • Fast timer side channels (Spectre style) if isolation fails
  • Hidden memory sharing between workers

Scores

ScoreValueMeaning
Sensitivity1 of 5How revealing the data is
Utility4 of 5How useful it is to honest apps
Friction1 of 5How much the user has to do
Fingerprint bitsNot ratedRough identifying entropy, when known

History

  • 2018-01, Chrome 64: SharedArrayBuffer disabled by Spectre
  • 2020-07, Chrome 92: SharedArrayBuffer re-enabled only for crossOriginIsolated
  • 2021-09, Chrome 96: COEP credentialless
  • 2023-10, Firefox 119: COEP credentialless

Sources

How well checked: Based on official documentation.

On this page