How to Play Dreamcast Games on Android with Flycast (2026 Setup Guide): BIOS, VMU Saves, CHD/m3u, and Performance Fixes

Short version: yes, Dreamcast games run well on Android phones and Android gaming handhelds, and the emulator to use is Flycast. It is on Google Play as an official release, so getting the app itself takes about a minute. Where most people get stuck is the setup after that: BIOS files, where Flycast expects to find them, how saves work, and what to do with games that span more than one disc. This guide walks through the whole process in the order you will actually meet it in the app, from installation and BIOS placement to VMU save settings, multi-disc games, and fixing slowdown.

One thing worth knowing up front: Flycast can boot many games without any BIOS files at all, thanks to its built-in high-level BIOS emulation (HLE). For the best compatibility, though, we strongly recommend using BIOS files dumped from your own Dreamcast. More on that below.

The Short Answer: Flycast Is the Dreamcast Emulator for Android

Flycast is an open-source Dreamcast emulator that is available both as a standalone Android app and as a core for RetroArch. It has been officially available on Google Play since July 2024, and as of August 2026 the current release is v2.6 (updated January 10, 2026). Besides the Dreamcast itself, Flycast also runs games for arcade boards built on Dreamcast-derived hardware: NAOMI, NAOMI 2, Atomiswave, and System SP. (Arcade games need their own separate BIOS sets, so this guide sticks to the home console.)

On Android you have three ways to run it:

This guide uses the standalone Flycast app, because getting it running on its own first is the easiest way to understand how the pieces fit together. If you would rather consolidate everything in RetroArch later, the BIOS and VMU concepts carry over; only a few folder locations differ, and we point those out where they matter.

Installing Flycast and First Launch

Search for “Flycast” on Google Play and install it. It is free, has no ads, and asks for very few permissions.

If you need the newest features or a specific bug fix, you can instead grab an Android nightly APK from the official Flycast GitHub project. Only use the official releases and nightly builds published by the Flycast project itself. Do not install Flycast APKs from third-party download sites, since there is no way to know what has been added to them. Because the APK comes from outside the Play Store, Android will warn you about installing apps from unknown sources; for the official build, you can allow it and continue.

When you open Flycast for the first time, the game list is empty. That is normal. Nothing will show up until you tell Flycast where your games are, which we cover in the next section.

Setting Up the BIOS (dc_boot.bin and dc_flash.bin)

The Dreamcast BIOS is the console’s system software. Flycast looks for two files:

• dc_boot.bin (the boot ROM)
• dc_flash.bin (the contents of the console’s flash memory)

Do you actually need them? Not always. Flycast ships with HLE BIOS enabled by default, which means it emulates the BIOS at a high level and can boot many games with no BIOS files present. However, some titles do not run correctly under HLE, and the Dreamcast’s own boot animation and BIOS menus (such as the VMU management screen) require the real BIOS. For the best compatibility, we strongly recommend adding BIOS files dumped from your own console.

If you add them, the file names must match exactly as shown above. A different extension or different capitalization is enough for Flycast to ignore them.

A note on the law (United States): the Dreamcast BIOS and Dreamcast games are copyrighted software. Downloading copies you do not own, or sharing your own files with others, is copyright infringement. U.S. copyright law, including the Digital Millennium Copyright Act (DMCA), also restricts circumventing copy protection, and whether making a personal backup of software you own is permitted is not clearly settled. The only approach we describe on this site is dumping the BIOS and games from a Dreamcast console and discs you personally own. This is general information, not legal advice; if you have questions about your specific situation, consult a qualified attorney. Laws differ outside the U.S., so check the rules where you live.

Once you have your files, put them somewhere Flycast can read them:

1. Open Flycast’s Settings and scroll down to Custom Paths.
2. Under BIOS Folders, tap Add and select the folder that contains dc_boot.bin and dc_flash.bin.
3. Under Content Location, tap Add and select the folder that contains your game images.

You can also place the BIOS files in the data folder inside Flycast’s home folder instead of adding a separate BIOS folder.

If you use the Flycast core in RetroArch, the location is different: the files go in a dc subfolder inside RetroArch’s system folder (system/dc/dc_boot.bin). Mixing up the standalone and RetroArch locations is the most common reason people see “BIOS not found.”

On some Android handhelds (AYN and Retroid devices, for example), you can find Flycast’s internal data folder in a file manager at Android/data/com.flycast.emulator/files/data. On many devices, Android’s storage restrictions hide this folder from file managers, and getting to it can require root. As long as your BIOS folder is set in Custom Paths, you generally never need to touch this internal folder.

Basic Settings: Resolution, Renderer, and Controllers

With your BIOS and content folders set, your games should now appear in the list. Before you start playing, check these settings; they make the first session go a lot more smoothly.

On the renderer: if OpenGL runs your games without problems, stay on OpenGL. If things feel sluggish, try Vulkan; on some devices it is noticeably faster. If Vulkan causes graphical glitches, switch back.

Most Bluetooth gamepads are detected automatically as soon as they are paired. If a button does something unexpected, open the controller mapping screen in Flycast’s settings and remap it there. Touch controls work, but for fighting games and racing games a physical controller makes a clear difference.

VMU (Memory Card) and Save Data Management

On real hardware, Dreamcast games saved to the VMU (Visual Memory Unit), a memory card that plugged into the controller and had its own small screen. Flycast emulates the VMU in software.

By default, every game shares the same virtual VMU. That makes it easy for one game’s saves to crowd out or overwrite another’s, so change this setting before you play anything:

1. Open Settings and go to the Controls tab.
2. Scroll to the bottom and turn on Per Game VMU A1.
3. Tap Done, then restart the app and confirm the setting stuck.

With this enabled, each game gets its own separate VMU file. If the setting does not stay on after a restart, some users have reported that reinstalling the app fixed it.

On devices where you can access it, the per-game VMU files are created in Android/data/com.flycast.emulator/files/data, with names along the lines of …_vmu_save_A1.bin.

If you want to bring over a VMU file from another emulator or from saves you have backed up from your own VMU, place the VMU file in the same folder as the game image before you launch that game for the first time. Flycast will pick it up on first launch.

Multi-Disc Games: GDI, CHD, and m3u Playlists

Dreamcast disc images (the GD-ROM discs the console used) come in several formats. For Android, here is the order of preference:

Games that span multiple discs, like Shenmue, will not let you continue past Disc 1 if you load a single disc image on its own. The fix is an .m3u playlist that groups the discs together:

1. Create a new plain-text file in the same folder as the disc images.
2. Write the file name of each disc on its own line, in order: Disc 1, Disc 2, and so on.
3. Save the file with the .m3u extension instead of .txt.

Now launch the .m3u file from the game list instead of an individual disc. When the game asks you to change discs, Flycast switches to the next image automatically. The .m3u works the same way whether your discs are CHD, CUE, or GDI files.

If you plan to keep a sizable collection of CHD files on your device, storage becomes a real consideration. A reasonably fast, high-capacity microSD card (look for the A2 and UHS speed ratings on the packaging) keeps load times down and gives you room to grow.

Fixing Slowdown and Stuttering

The Dreamcast launched in North America in 1999, and a reasonably recent Android device has more than enough power to emulate it. If games still stutter, work through these steps in order:

1. Try the other renderer. Vulkan and OpenGL behave differently depending on your device’s GPU driver. Vulkan is faster on some devices, but it has been reported to cause rendering glitches or unstable frame rates on others, including some Adreno GPUs. If you are on Vulkan and seeing problems, switch to OpenGL; if you are on OpenGL and it is slow, try Vulkan.
2. Lower the internal resolution. Drop it to native (1x). If that alone does not help, the resolution is probably not the problem, so move on to the next step.
3. Switch Transparent Sorting to Per Triangle. Flycast lets you choose how transparent graphics are sorted: Per Pixel is more accurate but heavier, while Per Triangle is faster. In games with lots of transparency effects, trading a little accuracy for speed can clear up slowdown.
4. Check heat and power management. If games run fine at first but slow down after a long session, the cause is usually thermal throttling, where the chip slows itself down as it heats up. No emulator setting fixes that; let the device cool, remove a thick case, or check your device’s performance or power mode.

Common Problems and How to Fix Them

Wrapping Up

With Flycast, Dreamcast games run comfortably on Android phones and handhelds. Three things to remember:

• Install Flycast from Google Play. If you need a nightly build, get it only from the official Flycast GitHub project.
• Flycast can boot many games with its built-in HLE BIOS, but for the best compatibility add dc_boot.bin and dc_flash.bin dumped from your own console, with the file names matching exactly.
• Turn on Per Game VMU A1 and use .m3u playlists for multi-disc games, or you risk mixed-up saves and getting stuck at Disc 1.

Get those three right and you will avoid nearly every problem people hit on their first setup.