Find the MSFS 2024 WASM folder on Steam and Microsoft Store, what its cache does, why it may be missing, and when to rebuild it.
Microsoft Flight Simulator 2024 does not have one universal WASM folder. On PC, each WASM-enabled package normally gets a cache at <MSFS data root>\Packages\<package-name>\work\wasm. It stores generated files used to run WebAssembly aircraft systems and gauges; it is not the Community folder and should not be used to install add-ons.
Where are the default MSFS 2024 WASM paths?
The default Windows location depends on whether Microsoft Flight Simulator 2024 came from Steam or the Microsoft Store/Xbox app.
| Platform | Default package cache path |
|---|---|
| Microsoft Store or Xbox app on Windows | %LOCALAPPDATA%\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\Packages\<package-name>\work\wasm |
| Steam | %APPDATA%\Microsoft Flight Simulator 2024\Packages\<package-name>\work\wasm |
Paste the relevant path up to Packages into File Explorer, then open the package identifier followed by work\wasm. Package identifiers do not always resemble the aircraft's name. Windows treats wasm and WASM as the same folder name.
Custom Windows profile redirection can change the base location. Moving the Community or content library also does not necessarily move this runtime cache, so start with the app-data paths above rather than the aircraft's installation directory.
Xbox Series X|S, PS5 and PS5 Pro users cannot browse or clear the folder. WASM content may still run internally, but direct file-system maintenance is limited to PC.
What is the WASM folder used for?
WASM lets an add-on run compiled WebAssembly code inside the simulator's controlled environment. Complex aircraft use it for functions such as avionics, flight-management logic, electrical systems, engine simulation and custom gauges.
Two locations are easily confused:
- The package's
modulesdirectory commonly contains the developer-supplied.wasmmodule. This is part of the aircraft or add-on itself. - The package's
work\wasmdirectory contains runtime-generated or cached files created while MSFS loads that module. This is normally the folder meant by instructions to “clear the WASM cache”.
Not every aircraft needs WASM. Liveries, simple scenery and aircraft using only other instrument technologies may never create a WASM cache.
Why is the WASM folder missing?
The folder is often absent because the relevant WASM aircraft has not yet been loaded far enough for Microsoft Flight Simulator 2024 to generate it.
- Load the aircraft into a flight, wait for the cockpit to initialise, close the simulator, then check again.
- Look under the package's internal identifier, not just its marketed aircraft name.
- Confirm that you are checking the Steam or Microsoft Store path that matches your installation.
- Remember that streamed or protected packages may not expose their source
modulesdirectory even when a runtime cache exists. - Check that the aircraft actually uses WASM; many add-ons do not.
Is the WASM folder the same as the Community folder?
No. The Community folder stores complete third-party packages, while work\wasm stores package-specific runtime data. Our instructions for finding the MSFS Community folder cover its default and custom locations.
A mistake we see constantly is placing a downloaded aircraft directly into work\wasm. Install its complete package in the proper location instead; our aircraft package installation walkthrough explains the required folder structure.
Can I safely delete the MSFS 2024 WASM cache?
Yes, a package's work\wasm cache can usually be rebuilt safely when troubleshooting blank instruments, module-loading errors or problems that began after an aircraft update. It does not uninstall the aircraft, but the simulator must be closed before you change it.
- Exit MSFS 2024 completely. Check that it is no longer running before editing package files.
- Open the affected package. Go to its
workdirectory using the appropriate path above. - Rename the cache. Change
wasmtowasm.oldrather than deleting it immediately. - Load the same aircraft. MSFS should generate a fresh cache; the first cockpit load may take longer than usual.
- Remove the backup after testing. If rebuilding changes nothing, close the simulator before restoring or deleting folders again.
Do not delete the package's source .wasm files or its entire work directory unless the aircraft developer explicitly instructs you to do so. Rebuilding a cache also cannot repair an incomplete, incompatible or outdated aircraft package.