WebAssembly (threads, SIMD, memory limits)
Runs compiled code at near native speed inside the page, with up to 4 GB of memory (16 GB with memory64 in Chrome).
In one line
Can run fast compiled code inside the page, within memory limits
Runs compiled code at near native speed inside the page, with up to 4 GB of memory (16 GB with memory64 in Chrome).
A site can run heavy code (games, codecs, Photoshop-class tools) with no install. The same speed makes in-browser miners and side channel timing code practical.
What it can and can't do
What the user does: Nothing. It happens when the page loads, such as a game, editor or video tool.
It can
- Run apps made in languages like C++ or Rust inside the page
- Use up to 4 GB of memory per page; Chrome can go to 16 GB with memory64
- Use several threads at once when the site is isolated
It cannot
- Skip the browser's rules for web code; it runs in the same safe sandbox
- Reach your files, camera or other apps on its own
- Use more memory than the limit the browser sets
- Run after you close the page
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 57 | 2017-03-09 | None |
| Edge | Supported | 16 | 2017-10-17 | None |
| Firefox | Supported | 52 | 2017-03-07 | None |
| Safari | Supported | 11 | 2017-09-19 | None |
| Safari on iPhone | Supported | 11 | 2017-09-19 | All iOS browsers use WebKit |
| Chrome on Android | Supported | 57 | 2017-03-16 | None |
| Samsung Internet | Supported | 7.0 | 2018-03-16 | None |
How a site asks for it
| API | WebAssembly.instantiate(); SharedArrayBuffer threads; SIMD; memory64 |
| Browser compat keys | api.WebAssemblyapi.WebAssembly.Memory |
| How access is granted | none |
| What the user sees | None (no browser prompt) |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | No |
| Activation | none |
| How long it lasts | While the page lives |
| How to take it back | Nothing to revoke (no permission is stored) |
| Inside an iframe | No iframe flag; CSP script-src needs 'wasm-unsafe-eval' to compile |
Typical flow
- Fetch .wasm
- Compile and instantiate
- Call exports
Data you get
Shape: none
No individual data fields. The signal is the access itself.
Technical limits
- wasm32 memory max 65536 pages = 4 GiB per memory in Chrome and Firefox; Safari and mobile browsers often cap lower (about 1 to 2 GiB in practice)
- memory64 raises the limit to 16 GiB in V8 (Chrome 133, Firefox 134); real allocations still fail when RAM is short
- Threads need SharedArrayBuffer and cross-origin isolation (COOP and COEP)
- SIMD: Chrome 91, Firefox 89, Safari 16.4; also tail calls (Chrome 112), GC (Chrome 119, Firefox 120, Safari 18.2)
- Under a CSP without 'wasm-unsafe-eval', compile is blocked (Chrome 97)
- Sandbox: no direct OS access, only imports provided by JavaScript
The story
What it is
A page can run big, compiled programs in your browser at near desktop speed.
For you
You open a web app and it feels like a desktop program. Photoshop or a 3D game loads in a tab without an install.
For makers
Makers can bring huge existing programs to the web without rewriting them. This is how big games, CAD and design tools reach anyone with a link.
Where you see it
| Type | Example | Apps |
|---|---|---|
| creative | Figma runs its design engine as WebAssembly so large files stay smooth. | Figma, Photoshop web |
| games | Unity and Unreal games run in a tab, and Doom style ports run at full speed. | Unity WebGL games |
| video | A web conferencing client uses it to compress and clean video and audio. | Zoom web, Google Meet |
| productivity | AutoCAD and Google Earth run in a browser tab using compiled code. | AutoCAD web, Google Earth |
| security | Attackers can hide crypto miners or obfuscated code in compiled form, harder to inspect. | None named |
| developer | Developers run Python or full databases in the browser with no server. | Pyodide, SQLite wasm |
Risks
- Hidden miners
- Hard to inspect code
What the platform says
- W3C: WebAssembly. The WebAssembly site pitches it as a fast, safe binary format that runs in browsers next to JavaScript.
Good uses and abuse
Legitimate uses
- Games
- Video and image processing
- Local ML inference
Known abuse
- Cryptojacking
- Timing side channels
- Fast fingerprint and bot code
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 1 of 5 | How revealing the data is |
| Utility | 5 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | 1 | Rough identifying entropy, when known |
History
- 2017-03, Chrome 57: WebAssembly 1.0 in all major browsers
- 2021-05, Chrome 91: Wasm SIMD ships
- 2024-12, Safari 18.2: WasmGC ships
- 2025-02, Chrome 133: Memory64 ships
Related capabilities
Related
- Cross-origin isolation (SharedArrayBuffer, COOP, COEP). Can switch on a locked down mode that unlocks fast shared memory for the page
Sources
How well checked: Based on official documentation.