What does browser support look like for wasm64 right now?

If support isn't universal yet, I'm wondering if it's possible to distribute WASM32 + WASM64 alongside where the JavaScript selects the correct file to download according to the browser's capabilities.

What does browser support look like for wasm64 right now?

Here's what emscripten's change log say:

3.1.72 - 11/19/24

• The MEMORY64 setting is no longer experimental. At time of writing all browsers still require a flag to run the resulting binaries but that should change in the coming months since the proposal is now at stage 4. (Fix build with Android NDK r18 #22864)

If support isn't universal yet, I'm wondering if it's possible to distribute WASM32 + WASM64 alongside where the JavaScript selects the correct file to download according to the browser's capabilities.

It could be interesting for performance oriented apps, but for most of the uses, this is overkill, as usually, the target is to have the smallest payload possible to load faster.

I haven't tested, but I highly suspect that our WebXR code will break with WASM64, due to all the messy pointer math that's happening to send data between the C++ and JavaScript sides. However, if there are issues, it should be pretty easy to fix.

What does browser support look like for wasm64 right now?

If support isn't universal yet, I'm wondering if it's possible to distribute WASM32 + WASM64 alongside where the JavaScript selects the correct file to download according to the browser's capabilities.

I think you had a point. I'm thinking doing that for JSPI in the future also.

As of February 2026, it looks like all browsers except Safari support wasm64: https://caniuse.com/wf-wasm-memory64