Dolphin Emulator is one of the most popular and powerful emulators for playing Nintendo GameCube and Wii games on non-native hardware. Available on Windows, macOS, Linux, and even Android, it has also been ported to iOS (primarily through sideloading methods like AltStore, SideStore, or TrollStore). However, iOS users occasionally encounter a cryptic, frustrating error when trying to launch a game or manage virtual console titles:

"dolphin ios-fs failed to write new fst"

This error typically prevents games from booting, corrupts save states, or halts the emulation process entirely. If you are seeing this message, you are not alone. This article will explain what the error means, why it occurs specifically on iOS, and how to fix it—ranging from simple troubleshooting to advanced file system repairs.

If Dolphin is installed in a system-protected location (like C:\Program Files), it may not have permission to write to its own User folder. Right-click Dolphin.exe and select Run as administrator.

Better solution: Move Dolphin to a user-owned folder (e.g., C:\Dolphin or Desktop\Dolphin).

iOS is aggressive about storage limits. If your device has less than ~500 MB free, Dolphin may not be able to write the FST cache, especially for large dual-layer Wii games (e.g., Super Smash Bros. Brawl, Metroid Prime Trilogy).

iOS Dolphin comes in two performance modes:

If you are using a JIT-enabled build, try switching to a stable non-JIT version—the FST writer may behave better without JIT memory constraints.

If the specific ISO or WBFS file you are trying to modify has the "Read-only" attribute enabled, Dolphin cannot write the new FST.

Before jumping into fixes, identify the most likely culprit. There are four primary reasons for the "failed to write new fst" message.

The iOS port of Dolphin is not as mature as the desktop versions. Some older builds (especially from early 2023) had known issues with FST caching on iOS. Newer builds have improved filesystem handling.