18+ archive guide
Play Banned from Equestria Offline with Ruffle Desktop
Quick answer
Download the SWF, install the official Ruffle desktop build for your operating system, then open the file with Ruffle instead of a browser. The desktop player removes browser extensions and iframe rules from the path and stores saves in a documented folder.
Why go offline
Quick answer
Offline play is for preservation, repeat sessions, and machines where the browser player is blocked. It is not required for a first try, and it is not automatically safer than the browser.
The browser player is convenient because it removes installation decisions. The offline player is convenient because it removes the browser. Once the SWF and Ruffle are local, a content blocker, a company proxy, or a browser update cannot stop the game from starting.
Offline play also makes saves easier to reason about. A desktop Ruffle build writes save data to a per-user folder instead of an opaque browser profile. You can copy that folder, inspect it, and restore it.
The tradeoff is responsibility. You have to obtain the SWF from a source you trust, verify it, keep the emulator current, and manage the files yourself. If you only want to see whether the game runs, use the browser first.
Choose your setup
Quick answer
Windows and Linux users can take a Ruffle desktop build directly. macOS users can use the universal build. Android users cannot use the desktop build; they need the browser or an APK.
A desktop Ruffle build is a native application, not a browser extension. It can use the GPU and system resources more directly, which is why Ruffle recommends it for heavier content. For a single Flash game, the difference may be modest, but the isolation from browser settings is real.
Do not install a "Flash emulator" from a random download portal. Ruffle's official builds are linked from ruffle.rs and its GitHub releases. A third-party repackage can add toolbars or change the binary, and you would have no easy way to tell.
Interactive tool
Offline setup planner
Pick your operating system and whether you already have the SWF. The planner returns the shortest valid path.
Step by step
Quick answer
Get the game file, verify it, install Ruffle from the official source, then open the SWF with Ruffle. Test one short session before you invest in a long one.
- Download the SWF from the archive's download page or the creator archive.
- Record the file's SHA-256 and compare it with any published value.
- Download Ruffle desktop from ruffle.rs or the official GitHub release.
- Extract the Ruffle archive and run the application once.
- Use Ruffle's file chooser to open the SWF, or pass the file path on the command line.
- Click inside the game window once so it receives keyboard and mouse input.
- Confirm the game starts, then locate the Ruffle save folder and note it.
On Windows, extract the Ruffle ZIP, open the folder, and run ruffle.exe. The file chooser lets you pick the SWF. On macOS, extract the universal archive, right-click the Ruffle application and choose Open the first time, then use the file chooser. On Linux, use the Flatpak build or the architecture-specific archive.
The Ruffle wiki also documents command-line usage. On Windows, "ruffle filename.swf" opens a file directly. On macOS, the executable lives inside the application bundle. On Linux Flatpak, use "flatpak run rs.ruffle.Ruffle filename.swf". These commands are useful when you want a shortcut that opens the game in one step.
Keep the SWF and the Ruffle version together in a folder with a short note. If a future Ruffle update changes behavior, you can return to the version that worked. Do not rename the SWF to something misleading; a descriptive filename is easier to verify later.
Where saves go
Quick answer
Ruffle desktop writes save data to a SharedObjects folder under the user's application data. The Ruffle wiki lists the exact path for each platform.
Back up the folder, not the whole application. The application can be reinstalled from the official release; the save data cannot be reconstructed. Copy the folder to a second drive before you update Ruffle or move to a new machine.
A restore is a file copy back into the same path, with Ruffle closed. Test it once with a short session. If the game does not see the restored save, check that you are using the same Ruffle build and the same SWF filename, because the storage key can depend on both.
| Platform | Save folder |
|---|---|
| Windows | C:\Users\<username>\AppData\Local\Ruffle\SharedObjects\ |
| macOS | /Users/<username>/Library/Application Support/ruffle/SharedObjects/ |
| Linux (non-Flatpak) | ~/.local/share/ruffle/SharedObjects/ |
| Linux (Flatpak) | ~/.var/app/rs.ruffle.Ruffle/data/ruffle/SharedObjects/ |
File safety before you open it
Quick answer
A SWF is data interpreted by Ruffle, not a Windows executable, but it can still be malicious or corrupted. Verify the source and the hash, and do not open a file that arrived as an unexpected attachment.
Flash content can contain ActionScript, and an emulator executes that code. The fact that a file ends in .swf does not make it safe. The relevant questions are the same as for any download: where did it come from, can you verify its identity, and are you opening it in a contained environment?
For a desktop setup, the containment is your user account. That is weaker than a virtual machine but stronger than installing an unknown system-wide package. If you are testing a file from an unfamiliar source, use a virtual machine or a spare computer.
If the SWF is corrupted, Ruffle may show an error or a blank window. Re-download from the same source and compare the hash. A file that changes between downloads from the same URL is a red flag.
Troubleshooting a desktop launch
Quick answer
Most desktop failures are the wrong architecture, a blocked first launch, or a missing file path. Work through those before reinstalling the operating system or the emulator.
If Ruffle opens but the game does not, try a different SWF to separate an emulator problem from a game-file problem. Ruffle's project publishes test SWFs for exactly this purpose. If a test SWF works and the game does not, the game file or its compatibility is the issue.
Report persistent emulator bugs to Ruffle's issue tracker with the Ruffle version, operating system, and a description of the SWF. Do not upload copyrighted game files to a public issue; describe the behavior instead.
- macOS blocks an unsigned first launch: right-click the app and choose Open.
- Windows SmartScreen may warn about a new download: verify the source before allowing it.
- Linux ARM users need the ARM64 build, not the x86_64 archive.
- A blank window may mean the SWF path is wrong or the file is corrupted.
- No keyboard input usually means the game window does not have focus; click inside it.
- Audio problems are often a system output issue, not a Ruffle setting.
FAQ
Is Ruffle desktop free?
Yes. Ruffle is an open-source project, and the official desktop builds are free to download from ruffle.rs and GitHub.
Can I play offline on Android?
Not with the desktop build. Android users can use the browser player or a community APK, with the caveats in the mobile guide.
Do I still need Flash Player?
No. Ruffle is an emulator and does not use Adobe Flash Player, which is discontinued.
Will my browser save transfer to desktop Ruffle?
No automatic transfer exists. Browser storage and desktop SharedObjects are separate stores.
Which Ruffle version should I use?
Start with the latest stable release. Use a nightly only if you need a specific fix and can tolerate instability.
Sources
Desktop installation steps and save paths come from the Ruffle wiki and downloads page. The archive's download page is the source for the game file options.