How to Disable the Google Chrome ‘Enable WebAssembly Baseline Compiler’ Flag

The WebAssembly Execution Engine

WebAssembly (Wasm) is the technology that allows complex applications, like 3D games and video editors, to run inside Google Chrome at near-native speeds. To achieve this performance, Chrome utilizes a multi-tiered compilation system. The “Enable WebAssembly Baseline Compiler” flag controls the first tier of this system, known as Liftoff. When a website loads Wasm code, the Baseline Compiler (Liftoff) kicks in immediately, translating the code into executable machine instructions as quickly as possible so the application starts instantly, even if the resulting code isn’t perfectly optimized. Later, a slower but more efficient optimizing compiler (TurboFan) takes over to refine the code.

While this tiered approach is brilliant for performance—giving you fast startup times followed by high sustained speeds—it introduces complex logic into the browser’s execution engine. In highly secure environments, or when debugging specific Wasm memory crashes, developers might need to force Chrome to skip the rapid baseline compiler and only use the strict, heavily optimized execution tier. Disabling the baseline compiler forces Chrome to evaluate Wasm code differently, which can occasionally bypass specific edge-case bugs found in the Liftoff engine, though it comes at the cost of slightly slower application startup times.

How to Turn Off the Wasm Baseline Compiler

You can force Chrome to disable the first-tier WebAssembly compiler via the experimental flags menu.

  1. Open Google Chrome.
  2. Click inside the main address bar at the top of the browser window.
  3. Type chrome://flags and press Enter.
  4. On the “Experiments” page, use the search bar to look for Enable WebAssembly Baseline Compiler.
  5. If the flag is available, click the dropdown menu next to it and change it from “Default” (or Enabled) to Disabled.
  6. Click the blue Relaunch button at the bottom of the screen.

Upon restarting, Chrome will no longer use the Liftoff baseline compiler for WebAssembly execution, forcing all Wasm code to be processed by alternative execution tiers.

Get the best tech tips delivered straight to your inbox.

Join thousands of readers mastering Apple, Google, Microsoft, and Linux.