This document contains information specific to the Android release, for more general ES-DE documentation refer to the User guide as well as the general FAQ.
It's also generally recommended to read the Frequently Asked Questions (FAQ) for Android document prior to diving into the information in this document.
You can buy the Android APK from our Patreon page:
https://www.patreon.com/es_de
Table of contents:
[[TOC]]
When you first start ES-DE you will be greeted by a welcome screen, this is part of the configurator, the ES-DE onboarding interface. The configurator is easy to use and will guide you through the necessary setup steps.
As a first step you need to give ES-DE the required storage access permission or it will not be able to function. Just enable the setting and the configurator will proceed to the next step. Next you will need to define a application data directory where your settings, scraped media, custom collections and so on will be stored. By default this will be placed in the ES-DE directory in the root of your device's internal storage, and this directory will be created for you automatically.
After this step you need to select a ROMs directory where your game files will be stored, by default this will be named ROMs and will be located in the root of you device's internal storage. You can however choose to place this on an SD card if you want to, just change the path using the Android file selector GUI. If you do change the path to the SD card you will however need to manually create the ROMs directory as well as to delete the empty directory that was created for you in the built-in storage.
The next step is optional, and it's whether to create the game systems directory structure inside your ROMs folder. Performing this will also create systeminfo.txt files in each system directory. These files contain information about the system such as what file extensions and emulators that are supported. They are not mandatory for the app to function, they are only there for your convenience. In general it's recommended to create the system directories, although you could remove the ones you don't need afterwards for a slightly faster app startup speed.
This is basically the onboarding process, and ES-DE should now start up. Just be aware that you need to place at least one game with a supported file extension in the ROMs directory tree or ES-DE will only show an information dialog about missing games.
Also note that ES-DE does not install any emulators, you need to install those separately. There is more information about that topic later in this document.
If you need to re-run the configurator for some reason then the easiest way is to go into the Android Apps setting screen and revoke the storage access permissions under Special app access. This will make the configurator run automatically next time you start ES-DE. Another way to force it to start is to clear the app's storage under Storage & cache but this is normally not recommended as it also deletes all themes you have downloaded using the theme downloader. A third option would be to rename either the ES-DE or ROMs directory as this will also trigger the configurator on next app startup.
By default the touch input overlay will be enabled which makes it possible to use ES-DE without a controller or physical keyboard by overlaying virtual buttons on top of the ES-DE interface. If you are using a device which has a built-in controller you may however want to disable this feature. That is done via the Enable touch overlay option in the Input device settings menu on the main menu. Just be aware that disabling this option on a device where you have no other input method than touch will lock you out of the application.
If you accidentally disable the touch overlay you can force the configurator to run as explained in the previous section above, this will reset the touch overlay setting as long as you have at least pressed the Begin setup button. Another option would of course be to temporarily plug in a controller or keyboard to enable the setting via its menu entry. A third option would be to manually edit the es_settings.xml file in the ES-DE application data directory. The setting you are after is named InputTouchOverlay which should be changed from false to true.
Apart from this there are numerous options for the touch overlay, like the ability to change its size, opacity and fade-out time. Setting the fade-out to zero will make it permanently visible. See the User guide for a complete reference of all app settings and features.
Almost all files saved and used by ES-DE are kept in the shared storage on either the device's built-in storage or on the SD card. This means that uninstalling the ES-DE app will not remove any of that data. The only thing that will be deleted are themes that have been downloaded using the built-in theme downloader, as it's not possible to store these in the ES-DE application data directory for technical reasons.
There are a few challenges with emulation on Android. Some emulators on the Google Play store have not been updated for a long time, and some emulators are not available on the Play store at all. For these reasons you will need to sideload some manually downloaded APKs for a good emulation setup. There is a section later in this document describing the best place to get hold of each supported emulator.
Thankfully sideloading emulators is easy to do, the exact producedure for how to install APKs manually is not covered here but there are many resources available online on how to accomplish this.
There is also the F-Droid app store as an alternative to Google Play, and this service contains a couple of emulators that are not present on the Play store, or that are present there but haven't been updated for a very long time.
A number of emulators support the FileProvider API which makes it possible for ES-DE to temporarily provide storage access to the game file on launch. This means that most of the time no access permission needs to be setup in the emulator upfront. Access can however only be passed for single files, so for systems that support multi-file games such as disc-based games in .bin/.cue format SAF URIs are often used instead. For those emulators you will therefore generally need to manually provide scoped storage access to each game system directory. Note that it's not supported to give access to the root of the entire ROM directory for emulators that use scoped storage, it has to be for the specific system. For instance /storage/emulated/0/ROMs/n64 rather than /storage/emulated/0/ROMs.
Adding to the FileProvider API confusion is the fact that some emulators will only launch games when using this API even though they need to have scoped storage access setup within the emulator upfront. FPseNG and FPse are two examples of this. So there is unfortunately no definitive rule regarding the use of the FileProvider API, it all depends on how the emulator has implemented the functionality.
Some emulators like RetroArch are still using an older storage access method and for those emulators this is not something you need to consider.
The following emulators are configured for FileProvider access:
- 2600.emu
- DroidArcadia
- FPseNG (still needs scoped storage to be setup in emulator)
- FPse (still needs scoped storage to be setup in emulator)
- GBA.emu
- GBC.emu
- Lynx.emu
- MD.emu (genesis, mastersystem, megadrive, megadrivejp)
- NES.emu
- NGP.emu
- PCE.emu (pcengine, supergrafx and tg16 systems)
- Ruffle
- Swan.emu
Some of these emulators require BIOS files, so they still need to be configured before they can be used with ES-DE.
While it's possible to split the game system directories across multiple storage devices this is not recommended. First it's tedious to setup, but more importantly it breaks portability for the installation. For instance you can't easily migrate between the different operating systems that ES-DE support and your custom collections will not be portable at all, as they will instead contain absolute paths to your games.
The way ES-DE works is that you have a defined ROMs directory which corresponds to the %ROMPATH% variable that is used throughout the es_systems.xml file and the custom collections files. For example this is the system configuration for the samcoupe system:
<system>
<name>samcoupe</name>
<fullname>MGT SAM Coupé</fullname>
<path>%ROMPATH%/samcoupe</path>
<extension>.dsk .DSK .mgt .MGT .sad .SAD .sbt .SBT .7z .7Z .zip .ZIP</extension>
<command label="Speccy (Standalone)">%EMULATOR_SPECCY% %ACTION%=android.intent.action.VIEW %DATA%=%ROMSAF%</command>
<platform>samcoupe</platform>
<theme>samcoupe</theme>
</system>Here the path tag is using the %ROMPATH% variable to keep it relative to the base ROMs directory as selected via the onboarding configurator when you first installed ES-DE. If you relocate your ROMs directory to a different storage device, or copy it to another device altogether or if you synchronize your games across Android and Linux, macOS or Windows then everything will still work correctly.
Similarly custom collection files contain the %ROMPATH% variable too, such as this:
%ROMPATH%/amiga/OoopsUp.lha
%ROMPATH%/amiga/PacMania.lha
%ROMPATH%/samcoupe/Manic Miner.zip
%ROMPATH%/samcoupe/Prince of Persia.zip
This makes your custom collections portable if you move your ROMs directory and you can also transfer the collections between various devices and operating systems while keeping everything working seamlessly.
If you still insist on relocating some game system directories to another storage device then you need to make custom system configuration entries for them. See the Game system customization section of the User guide for details on how this is accomplished. In short you need to create an es_systems.xml file in the ES-DE/custom_systems directory and replace the %ROMPATH% variable with an absolute path for the specific systems you want to relocate.
You can find the bundled es_systems.xml file for Android here (which contains configuration for all supported systems):
https://gitlab.com/es-de/emulationstation-de/-/tree/stable-3.0/resources/systems/android
Here's an example of a custom es_systems.xml file that relocates the samcoupe system:
<?xml version="1.0"?>
<systemList>
<system>
<name>samcoupe</name>
<fullname>MGT SAM Coupé</fullname>
<path>/storage/719F-3A7F/ROMs/samcoupe</path>
<extension>.dsk .DSK .mgt .MGT .sad .SAD .sbt .SBT .7z .7Z .zip .ZIP</extension>
<command label="Speccy (Standalone)">%EMULATOR_SPECCY% %ACTION%=android.intent.action.VIEW %DATA%=%ROMSAF%</command>
<platform>samcoupe</platform>
<theme>samcoupe</theme>
</system>
</systemList>This example points the samcoupe directory to the external storage device /storage/719F-3A7F which may for instance be an SD card.
Note that doing the opposite, i.e. placing your primary ROMs directory on external storage and relocating a specific system to internal storage requires you to use the /storage/emulated/0 path, you can't use /sdcard in the path tag.
Here's again an example for the samcoupe system:
<?xml version="1.0"?>
<systemList>
<system>
<name>samcoupe</name>
<fullname>MGT SAM Coupé</fullname>
<path>/storage/emulated/0/ROMs/samcoupe</path>
<extension>.dsk .DSK .mgt .MGT .sad .SAD .sbt .SBT .7z .7Z .zip .ZIP</extension>
<command label="Speccy (Standalone)">%EMULATOR_SPECCY% %ACTION%=android.intent.action.VIEW %DATA%=%ROMSAF%</command>
<platform>samcoupe</platform>
<theme>samcoupe</theme>
</system>
</systemList>If going for this configuration, adding samcoupe games to a custom collection would end up with something like the following:
%ROMPATH%/amiga/OoopsUp.lha
%ROMPATH%/amiga/PacMania.lha
/storage/emulated/0/ROMs/samcoupe/Manic Miner.zip
/storage/emulated/0/ROMs/samcoupe/Prince of Persia.zip
This is obviously a non-portable collection.
You can relocate as many systems as you want, you just need to place them all within the systemList tag pairs in ES-DE/custom_systems/es_systems.xml.
As of ES-DE 3.0.2 there is experimental support for launching native Android apps and games from inside ES-DE. For the time being it does however require that you use a separate app to import your apps and games into ES-DE. But following this initial setup launching native apps and games works just like launching games for any other system.
First head to this GitHub repository and download the ES Applauncher APK:
https://github.com/schattenphoenix/es_applauncher/releases
Many thanks to Alex Pferdmenges for developing this app!
After installing the APK on your device and giving it the necessary permissions you'll see a list of your apps and you can classify the ones you want as games, and you can disable the ones you want to skip via the Game and Disable checkboxes on the right side of the screen. You can also choose to extract the icons for these apps and store them into one of the media folders inside the ES-DE/downloaded_media directory. The Media dir dropdown at the top of the screen lets you select the media type. It's generally recommended to use screenshots or covers or you can skip this step altogether as most of these icons are pretty low resolution anyway.
To populate the androidapps and androidgames system directories press the save icon in the upper right corner of the screen and select your ROMs directory from the selector interface. For example this could be ROMs directly on internal storage, or on your SD card. Just press the Use this folder button and the directories and files will be generated for you. Now you can start ES-DE and launch these apps and games directly.
Note that it seems like ES Applauncher has issues working correctly on some Android 10 devices.
It's also possible to scrape Android apps and games using ScreenScraper, but at the time of writing the amount of entries in their database is somehow limited. It's therefore encouraged to participate in improving this situation by contributing metadata and media to their database, this will benefit everyone in the long run.
A built-in import tool for native Android apps and games is also planned for a future ES-DE release.
To run ES-DE as the home app (launcher) you'll select it accordingly from the Apps section of the Android Settings app. When in this mode the ability to quit the app is completely disabled as it doesn't make sense to exit the home app. Therefore the Quit ES-DE entry on the main menu is removed and the Back button/back swipe exits app option in the Other settings menu and its corresponding functionality is disabled.
Apart from this it works as you'd expect, ES-DE will start automatically when rebooting the device and pressing the home button will return to ES-DE regardless of which app you have running.
If the operating system runs out of memory when a game is running it will kill ES-DE even if it's set as home app. If this happens ES-DE will reload whenever you return from the game or if you press the home button. This is simply how Android works.
Also be aware that the version check that runs on app startup may not be able to complete successfully when ES-DE is set as the home app, as the device may not have network connectivity enabled yet just after rebooting.
It's generally a very good idea to import your native Android apps into ES-DE prior to setting it as the home app, this way you can easily access things like the Settings app. Note however that even if you somehow lock yourself out of the system by setting ES-DE as the home app and not having any native apps added you can still always access the Settings app via the Android notification shade. On most devices you access this by swiping down from the top of the screen. After swiping down, just select the cogwheel icon to start the Settings app. From there you can change the home app to something else than ES-DE, should you need to.
- Poor performance/low frame rate after startup on some devices, which seems to happen randomly and is usually resolved by itself within 10 to 30 seconds.
- The Android soft keyboard causes rendering issues when navigating using a controller or physical keyboard, as such the ES-DE built-in keyboard is enabled by default for the time being. For testing purposes the Android soft keyboard can be enabled via the Enable virtual keyboard option in the UI settings menu. If only using touch input the issue is not present. This problem is believed to be caused by a bug in the SDL library so it probably needs to be resolved there.
- Using a mounted USB storage device for the ES-DE and/or ROMs directories will lead to the configurator exiting after finishing the setup instead of launching ES-DE. Restarting ES-DE manually will lead to a successful startup. If the option to create the system directories was selected in the configurator then this will have to be executed again from inside ES-DE. Note that using a mounted USB storage device leads to a very crippled setup anyway, as for example RetroArch can't read any games from such devices (i.e. from the /mnt/media_rw/ directory tree). Only emulators supporting scoped storage will be usable in such a setup.
Below are specific instructions and considerations for all supported emulators.
The RetroArch release from the Google Play store is problematic. It does not contain all emulator cores and a number of people have reported issues launching games from ES-DE (apparently it doesn't work at all on some devices). For these reasons it's strongly recommended to use the 64-bit release from the RetroArch website instead, or to install it from the Samsung Galaxy Store, Amazon Appstore or the F-Droid store.
https://retroarch.com
https://galaxystore.samsung.com/detail/com.retroarch
https://www.amazon.com/dp/B09753XRVF
https://f-droid.org/en/packages/com.retroarch
Be aware that you need to manually install every core you want to use from inside the RetroArch user interface, and you also need to install all necessary BIOS files. The Android release of RetroArch is pretty unforgiving and will usually just present a black screen on game launch if the core file or the BIOS file is missing, and it will hang there until Android realizes the app is not responding and displays a popup where you can choose to kill the process.
Although the emulator entry is named AetherSX2 the recommended release of this emulator is actually the NetherSX2 patched version as the AetherSX2 release on the Google Play store doesn't work correctly and probably can't be used with ES-DE at all. You'll need to search for this APK online, the filename you'll want is 15210-v1.5-4248-noads.apk
If you prefer to apply the NetherSX2 patch yourself (i.e. build the APK) then you can find all relevant information here:
https://github.com/Trixarian/NetherSX2-patch
The original Citra emulator project is no longer alive, but there is a fork that should work as a drop-in replacement. The Citra MMJ fork is also a viable alternative. Both of these emulators are available for download from their GitHub sites.
https://github.com/PabloMK7/citra/releases
https://github.com/weihuoya/citra/releases
This emulator can be installed from the Play store. There is a paid version as well named ColEm Deluxe (ColEm+ ColecoVision Emulator is the store listing name).
Although this emulator supports both the Adam and ColecoVision systems it can unfortunately not do both interchangeably. In order to play Adam games you need to go into the Emulation settings in ColEm and tick the Coleco Adam box. And likewise you'll need to untick it any time you want to play a ColecoVision game. This is true for launching games from ES-DE as well as starting them from inside the emulator GUI.
https://play.google.com/store/apps/details?id=com.fms.colem
https://play.google.com/store/apps/details?id=com.fms.colem.deluxe
The Play store version is somehow up to date and could be used, otherwise the F-Droid store version is up to date, or you could download the latest release directly from their website.
https://play.google.com/store/apps/details?id=org.dolphinemu.dolphinemu
https://f-droid.org/en/packages/org.dolphinemu.dolphinemu
https://dolphin-emu.org/download
Although it's not normally recommended to use the unofficial Dolphin forks because they are mostly ancient and have been surpassed by the mainline Dolphin releases, there could still be situations where it's useful. For example on weaker devices where the older release would work better.
There are multiple MMJR forks in existence, but the ones supported by ES-DE are Dolphin.MMJR.v11505.apk and MMJR.v2.0-17878.apk which can be downloaded from here:
https://archive.org/details/dolphin-and-citra-fork-backup
This emulator can be installed from the Play store as a paid app. Note that it does not support launching of zipped game files.
https://play.google.com/store/apps/details?id=com.dsemu.drastic
This emulator can be downloaded directly from their website.
http://amigan.1emu.net/releases
The Play store version of this emulator is getting frequent updates and is therefore recommended.
https://play.google.com/store/apps/details?id=com.github.stenzek.duckstation
This emulator can be downloaded from their GitHub site.
https://github.com/EKA2L1/EKA2L1/releases
There does not seem to be a way to launch individual EKA2L1 games from a frontend application on Android, instead ES-DE will simply launch the EKA2L1 user interface and you'll have to manually start your game from there.
This emulator can be installed from the Play store as a paid app.
https://play.google.com/store/apps/details?id=com.epsxe.ePSXe
These set of emulators also known as the "Robert Broglia" emulators consist of 2600.emu, C64.emu, GBA.emu, GBC.emu, Lynx.emu, NEO.emu, NES.emu, NGP.emu, MD.emu, MSX.emu, PCE.emu, Snes9x EX+, Saturn.emu and Swan.emu
You can install them via Google Play (as paid apps) or download them from their GitHub automatic build system.
https://play.google.com/store/apps/developer?id=Robert+Broglia
https://github.com/Rakashazi/emu-ex-plus-alpha/actions
There are also some BIOS files and similar that are needed to run these emulators, and which can be downloaded from their website.
This RetroArch core is a good port of the official PICO-8 game engine which does not exist on Android. It's not shipped with RetroArch by default though so you need to manually install it. After downloading it you'll need to place the core inside's RetroArch's downloads directory and then install it from the RetroArch app.
You must use the 64-bit version with the filename libfake08-arm64.so and it has to be renamed to fake08_libretro_android.so before you install it into RetroArch. Details on how to manually install cores in RetroArch can be found on the Internet, but the short version is to use the Install or Restore a Core entry in the Load Core menu. Fake-08 can be downloaded from their GitHub site.
https://github.com/jtothebell/fake-08/releases
Flycast is not available on the Play store or the F-Droid store, but it can be downloaded from their GitHub site.
https://github.com/flyinghead/flycast/releases
This emulator can be installed from the Play store. There is a paid version as well named fMSX Deluxe (fMSX+ MSX/MSX2 Emulator is the store listing name).
https://play.google.com/store/apps/details?id=com.fms.fmsx
https://play.google.com/store/apps/details?id=com.fms.fmsx.deluxe
These emulators can be installed from the Play store as a paid apps. FPseNG is the more modern version so it's probably best to go for that. Note that these emulators do not support .chd files.
https://play.google.com/store/apps/details?id=com.emulator.fpse64
https://play.google.com/store/apps/details?id=com.emulator.fpse
This emulator can be installed from the Play store.
https://play.google.com/store/apps/details?id=com.fms.ines.free
This Atari Jaguar emulator can be downloaded from their website. Just be aware that it's very old and has not been updated for modern Android releases, so it may be finicky on some devices or it may not work at all.
After installing the emulator, open it and go to the settings tab, then choose "Select ISO and BIOS directory" and navigate to the ROMs/atarijaguar folder. It seems like you also need to start the game from inside the emulator before you can run it from ES-DE. Starting a game will create a savestate file. If you now exit the emulator and run the game from ES-DE you'll see a list of savestate files, just select the correct one to start the game.
http://www.arts-union.ru/node/23
This emulator can be installed from the Play store or the F-Droid store, or it can be downloaded from their GitHub site.
https://play.google.com/store/apps/details?id=ru.playsoftware.j2meloader
https://f-droid.org/en/packages/ru.playsoftware.j2meloader
https://github.com/nikita36078/J2ME-Loader/releases
This emulator can be downloaded from their GitHub site.
https://github.com/woesss/JL-Mod/releases
This emulator which is forked from Citra can be downloaded from their GitHub site.
https://github.com/Lime3DS/Lime3DS/releases
These emulators can be installed from the Play store. It's strongly recommended to go for the MAME4droid 2024 version as this is updated with a recent MAME release while the older MAME4droid is using an ancient MAME release.
Note that for MAME4droid 2024 there's an exception when it comes to setting up the ROM path. Instead of selecting each separate system directory (as is done on most other standalone emulators) you must select the root of the ROMs directory tree. To change the ROM path open Settings in MAME4droid 2024, then select General and then Change ROMs path. After restarting the emulator choose External storage and then the ROMs directory which contains all your ES-DE system directories. If you instead choose a specific system directory like ROMs/arcade or ROMs/neogeo then only that specific system will work when launching games from ES-DE.
https://play.google.com/store/apps/details?id=com.seleuco.mame4d2024
https://play.google.com/store/apps/details?id=com.seleuco.mame4droid
Be aware that MAME4droid 2024 requires specific input configuration for some systems. For instance to navigate the mouse cursor when using touch input you'll need to got into the Settings menu, then Input, then Touch controller and change Mode to Analog Stick.
If using a physical controller for mouse input (via the thumbstick) then you will need to map the mouse buttons to physical controller buttons. You do this via the MAME input settings. Bring up the MAME menu by pressing both thumbsticks, or by pressing the Start and Coin buttons on the touch overlay. Go into Input Settings then Input Assignments (this system) where you can assign physical buttons to the mouse buttons.
For some systems you will need to explictly set the Start and Select buttons in the same fashion as when configuring the mouse buttons. Otherwise you'll not be able to start any games.
There are a few more things that you may need to configure for some systems, but that's beyond the scope of this document and should be covered by the MAME emulator documentation.
This emulator can be installed from the Play store as a paid app.
https://play.google.com/store/apps/details?id=com.fms.mg
This emulator can be installed from the Play store but it's quite buggy. Every time you add a new game to the ROM directory you need to start the emulator and manually refresh the game list or you won't be able to launch the game from ES-DE.
https://play.google.com/store/apps/details?id=me.magnum.melonds
This emulator can be installed from the Amazon Appstore or the Google Play store. The Pro version is recommended to avoid annoying ads.
https://www.amazon.com/dp/B09L5FB7T4
https://play.google.com/store/apps/details?id=org.mupen64plusae.v3.fzurita.pro
https://play.google.com/store/apps/details?id=org.mupen64plusae.v3.fzurita
This emulator is very similar to M64Plus FZ and it can be downloaded from their GitHub automatic build system.
https://github.com/mupen64plus-ae/mupen64plus-ae/actions
These emulators can be installed from the Play store as paid apps. There are also free/Lite versions available for these emulators but they have not been updated in years and don't run on modern devices. As such they are not supported by ES-DE.
https://play.google.com/store/apps/details?id=com.fastemulator.gba
https://play.google.com/store/apps/details?id=com.fastemulator.gbc
Nesoid is not available on the Play store but it can be installed from the F-Droid store, or it can be downloaded from their GitHub site.
https://f-droid.org/en/packages/com.androidemu.nes
https://github.com/proninyaroslav/nesoid/releases
Although NooDS is available via the Play store that version does not allow game launching from ES-DE. To get that to work instead use the version from their GitHub site. Also note that this emulator does not support launching of zipped game files.
https://github.com/Hydr8gon/NooDS/releases
Although OpenBOR is working fine on Android it's not possible to properly integrate it with a frontend, you'll instead need to install your game PAKs into the /sdcard/OpenBOR/Paks directory and create dummy .openbor files for your games in ROMs/openbor and after launching a game from ES-DE you need to manually start it from inside the OpenBOR GUI. There are more detailed setup instructions in the OpenBOR section of the User guide.
You can download OpenBOR from their GitHub site, the version named OpenBOR v3.0 Build 6391 has for example been proven to work well.
https://github.com/DCurrent/openbor/releases
This emulator is in early development and there currently seems to be no way to run a game directly from ES-DE. Instead the emulator GUI will be displayed on game launch and you will need to manually select the game from there. Note that the Android build of this emulator is named pandroid, but as the overall project name is Panda3DS it will be referred to as such in ES-DE. This emulator can be downloaded from their GitHub site.
https://github.com/wheremyfoodat/Panda3DS/releases
The Pizza Boy GBA and Pizza Boy GBC emulators can be installed from the Play store. There are Basic (free) versions and Pro (paid) versions available. As of writing this, the Basic version of the GBA emulator does not seem to be able to launch games from ES-DE, but the Pro version is working fine. Both the Basic and Pro versions of the GBC emulator are working correctly.
https://play.google.com/store/apps/details?id=it.dbtecno.pizzaboygba
https://play.google.com/store/apps/details?id=it.dbtecno.pizzaboygbapro
https://play.google.com/store/apps/details?id=it.dbtecno.pizzaboy
https://play.google.com/store/apps/details?id=it.dbtecno.pizzaboypro
This PlayStation 2 emulator can be downloaded from their website.
https://www.purei.org/downloads.php
The Play store version of this emulator is getting frequent updates and is therefore recommended. There is a paid Gold version as well which is functionally identical to the free version.
Make sure that you press the Browse button in PPSSPP when you're adding scoped storage access to your games directory or you will not be able to launch any games from ES-DE.
https://play.google.com/store/apps/details?id=org.ppsspp.ppsspp
https://play.google.com/store/apps/details?id=org.ppsspp.ppssppgold
This emulator can be downloaded from their GitHub site.
https://github.com/torokati44/ruffle-android/releases
This 3DO Interactive Multiplayer emulator can be downloaded from their website. Just be aware that it's very old and has not been updated for modern Android releases, so it may be finicky on some devices or it may not work at all.
You need to place the BIOS file in the game system directory, i.e. in the ROMs/3do folder. The file panafz10.bin with MD5 checksum 51f2f43ae2f3508a14d9f56597e2d3ce has been proven to work.
After installing the emulator, open it and go to the settings tab, then choose "Select ISO and BIOS directory" and navigate to the ROMs/3do folder. It seems like you also need to start the game from inside the emulator before you can run it from ES-DE. Starting a game will create a savestate file. If you now exit the emulator and run the game from ES-DE you'll see a list of savestate files, just select the correct one to start the game.
http://www.arts-union.ru/node/23
This emulator can be installed for free from the Play store and can later be upgraded to the Premium version from inside the application.
https://play.google.com/store/apps/details?id=io.recompiled.redream
ScummVM can be installed from the Play store. There are also daily builds available on their GitHub site. Such a build may be required to be able to launch games from ES-DE until the Play store version has been updated.
https://play.google.com/store/apps/details?id=org.scummvm.scummvm\ https://buildbot.scummvm.org/#/dailybuilds
This emulator is not in active development any longer, but the latest release can be found on archive.org.
https://archive.org/details/skyline-edge-all-versions
This emulator can be installed from the Play store. There is a paid version as well named Speccy Deluxe (Speccy+ ZX Spectrum Emulator is the store listing name).
Although this emulator supports both the Sinclar ZX Spectrum and MGT SAM Coupé systems it can unfortunately not do both interchangeably. In order to play SAM Coupé games you need to go into the Emulation settings in Speccy and select Sam Coupe from the Computer Model selection screen. And likewise you'll need to change it back any time you want to play a ZX Spectrum game. This is true for launching games from ES-DE as well as starting them from inside the emulator GUI.
https://play.google.com/store/apps/details?id=com.fms.speccy
https://play.google.com/store/apps/details?id=com.fms.speccy.deluxe
Although Visual Pinball is working fine on Android it's not possible to properly integrate it with a frontend, you'll instead need to install your tables inside the app and create dummy .vpinball files for your games in ROMs/vpinball and after launching a table from ES-DE you need to manually start it from inside the Visual Pinball GUI. There are more detailed setup instructions in the Visual Pinball section of the User guide.
You can download Visual Pinball from their GitHub automatic build system.
https://github.com/vpinball/vpinball/actions
This PlayStation Vita emulator can be downloaded from their GitHub site. Refer to the User guide for detailed game setup instructions.
https://github.com/Vita3K/Vita3K-Android/releases
In order to use Winlator to run Windows games you need to use a specific fork named Winlator Cmod as mainline Winlator does not offer frontend support. The Cmod fork can be downloaded from their GitHub page:
https://github.com/coffincolors/winlator
There are two variants of the fork, Glibc and PRoot, both of which come with some pros and cons with regards to compatibility and performance. The Glibc variant is the default emulator in ES-DE, so to use PRoot instead you'll need to select its alternative emulator entry.
In addition to the official repository there are multiple Winlator builds floating around the Internet, but these have not been extensively tested with ES-DE.
It's beyond the scope of this document to describe how to install games in Winlator, but once it's done and you've created a shortcut to your game from inside the container you can export it via the Export for Frontend option in the Winlator user interface. This will generate a .desktop file that you can place in the ROMs/pcarcade, ROMs/type-x or ROMs/windows folder and launch from ES-DE. You can alternatively set the Frontend Export Path setting from inside the Winlator Settings screen to avoid the manual step of moving the .desktop file.
This emulator can be installed from the Play store. Note that only the paid Pro version supports game launching from ES-DE. Also note that .bin/.cue files can't be launched for the time being, only .chd files seem to work. This needs to be fixed in the emulator so nothing can be done in ES-DE to work around that limitation.
https://play.google.com/store/apps/details?id=org.devmiyax.yabasanshioro2.pro
This is clearly not a complete list of Android devices, but rather those we know have been tested with ES-DE and for which there is a known status.
| Manufacturer | Model | Android release | Supported | Known issues | Comment |
|---|---|---|---|---|---|
| Abxylute | One | 12 | Yes | None | |
| Alldocube | iPlay50 mini Pro | 13 | Yes | None | |
| Anbernic | RG353V | 11 | Yes | None | |
| Anbernic | RG405M | 12 | Yes | None | Limited RAM capacity for this device makes it unsuitable for demanding themes and large game collections |
| Anbernic | RG405V | 12 | Yes | None | Limited RAM capacity for this device makes it unsuitable for demanding themes and large game collections |
| Anbernic | RG505 | 12 | Yes | None | Limited RAM capacity for this device makes it unsuitable for demanding themes and large game collections |
| Anbernic | RG556 | 13 | Yes | None | |
| Anbernic | RG ARC | 12 | Yes | None | LineageOS |
| Anbernic | RG Cube | 13 | Yes | None | |
| AYANEO | Pocket Air | 12 | Yes | None | |
| AYANEO | Pocket S | 13 | Yes | None | |
| Ayn | Odin (Base/Pro) | 10 | Yes | None | |
| Ayn | Odin Lite | 11 | Yes | None | |
| Ayn | Odin 2 (Base/Pro/Max) | 13 | Yes | Minor audio issues | |
| Pixel 2 XL | 11 | Yes | None | ||
| Pixel 3 XL | 12 | Yes | None | ||
| Pixel 4a | 13 | Yes | None | ||
| Pixel 4a 5G | 14 | Yes | None | ||
| Pixel 6 | 14 | Yes | None | ||
| Pixel 6 Pro | 14 | Yes | None | ||
| Pixel 6a | 14 | Yes | None | ||
| Pixel 7 Pro | 13 | Yes | None | ||
| Pixel 8 Pro | 14 | Yes | None | ||
| Pixel Fold | 14 | Yes | None | ||
| Pixel Tablet | 14 | Yes | None | ||
| GPD | XD Plus | 11 | Yes | None | LineageOS |
| Honor | 20 lite | 10 | Yes | None | |
| Honor | Magic5 Pro | 13 | Yes | None | |
| Huawei | Mate 10 Pro | 10 | Yes | None | |
| Huawei | Mate 20 Pro | 10 | Yes | None | |
| Huawei | MatePad 11 (2021) | 13 | Yes | None | |
| Infinix | Zero 30 5G | 13 | Yes | None | |
| Kinhank | G1 | 11 | No | Unable to install | Possibly 32-bit operating system? |
| Kinhank | Super Console X5 Pro | 12 (TV) | No | None | Custom 64-bit Android TV OS |
| Lenovo | Legion Y700 (2022) | 12 | Yes | None | |
| Lenovo | Legion Y700 (2023) | 13 | Yes | None | |
| Lenovo | Xiaoxin Pad Pro 2021 | 11 | Yes | None | |
| LG | V60 ThinQ | 13 | Yes | None | |
| Logitech | G Cloud | 11 | Yes | None | |
| Meta | Quest 3 | 12 ? | Yes | None | |
| Microsoft | Surface Duo 2 | 12 | Unclear | Unclear | Conflicting reports of whether this device works or not |
| Motorola | Moto G60 | 12 | Yes | None | |
| Motorola | Moto G84 | 13 | Yes | None | |
| Motorola | Moto G100 | 12 | Yes | None | |
| Motorola | Moto G200 5G | 12 | Yes | None | |
| Motorola | Moto G Pro / G Stylus | 12 | No | Fails at configurator/onboarding | |
| Nintendo | Switch | 11 | Yes | None | Switchroot |
| Nokia | 5.4 | 12 | Yes | None | |
| Nokia | 7 Plus | 10 | Yes | None | |
| Nvidia | Shield Pro (2015/2019) | 11 (TV) | Yes | None | Limited RAM capacity for this device makes it unsuitable for demanding themes and large game collections |
| OnePlus | 6T | 11 | Yes | None | |
| OnePlus | 7 Pro | 14 | Yes | None | |
| OnePlus | 8 Pro | 13 | Yes | None | |
| OnePlus | 12 | 14 | Yes | None | |
| OnePlus | Nord 2 | 13 | Yes | None | |
| OnePlus | Open | 14 | Yes | None | |
| Oppo | A15 | 10 | Yes | None | |
| Oppo | Find X5 Pro | 14 | Yes | None | |
| Oppo | Reno5 | 12 | Yes | None | |
| Raspberry | Pi 4/400 | 13, 14 | Yes | None | Low-power GPU so ES-DE may run a bit sluggish |
| Raspberry | Pi 5 | 15 | Yes | None | Very poor GPU performance, runs at almost double speed in Raspberry Pi OS so likely a driver issue |
| Razer | Edge | 13 | Yes | None | |
| Realme | GT2 | 12 | Yes | None | |
| Retroid | Pocket 2+ | 11 | Yes | None | |
| Retroid | Pocket 2s | 11 | Yes | None | |
| Retroid | Pocket 3 | 11 | Yes | None | |
| Retroid | Pocket 3+ | 11 | Yes | None | |
| Retroid | Pocket 4 | 13 | Yes | None | |
| Retroid | Pocket 4 Pro | 13 | Yes | None | |
| Retroid | Pocket Flip | 11 | Yes | None | |
| Samsung | Galaxy A17 | 11 | Yes | None | |
| Samsung | Galaxy A20 | 10 | Yes | No write access to SD card | ROMs folder can be moved to SD card after setup and be used in read-only mode |
| Samsung | Galaxy A52 | 13 | Yes | None | |
| Samsung | Galaxy A52s 5G | 14 | Yes | None | |
| Samsung | Galaxy A54 | 13 | Yes | None | |
| Samsung | Galaxy A71 5G | 13 | Yes | None | |
| Samsung | Galaxy M52 5G | 13 | Yes | None | |
| Samsung | Galaxy Note 9 | 10 | Yes | None | |
| Samsung | Galaxy Note 20 | 13 | No | Fails at configurator/onboarding | |
| Samsung | Galaxy Note 20 Ultra 5G | 13 | Yes | None | |
| Samsung | Galaxy S9+ | 10 | Yes | None | |
| Samsung | Galaxy S10 | 12 | Yes | None | |
| Samsung | Galaxy S20 | 13 | Yes | None | |
| Samsung | Galaxy S20 FE | 13 | Yes | None | |
| Samsung | Galaxy S22 Ultra | 14 | Yes | None | |
| Samsung | Galaxy S23 | 14 | Yes | None | |
| Samsung | Galaxy S23+ | 14 | Yes | None | |
| Samsung | Galaxy S23 Ultra | 14 | Yes | None | |
| Samsung | Galaxy S24 Ultra | 14 | Yes | None | |
| Samsung | Galaxy Tab A7 | 12 | Yes | None | |
| Samsung | Galaxy Tab S9 5G | 14 | Yes | None | |
| Samsung | Galaxy Tab S7+ | 13 | Yes | None | |
| Samsung | Galaxy Tab S7 FE | 13 | Yes | None | |
| Samsung | Galaxy Tab S9 | 14 | Yes | None | |
| Samsung | Galaxy Tab S9+ | 14 | Yes | None | |
| Samsung | Galaxy Z Fold 3 | 14 | Yes | None | |
| Samsung | Galaxy Z Fold 4 | 14 | Yes | None | |
| Sony | Xperia 1 V | 14 | Yes | None | |
| Ulefone | Note 6P | 11 | Yes | None | |
| vivo | X Fold+ | 14 | Yes | None | |
| Wiko | Voix | 12 | No | Fails at configurator/onboarding | Probably a bug in the firmware/OS image as a libc system call fails |
| Xiaomi | Mi 10t | 12 | Yes | None | |
| Xiaomi | Mi 11i | 13 | Yes | None | |
| Xiaomi | Pad 5 | 13 | Yes | None | |
| Xiaomi | Poco F3 | 11 | Yes | None | |
| Xiaomi | Poco X5 | 12 | Yes | None | |
| Xiaomi | Redmi Note 10 Pro | 13 | Yes | None | |
| Xiaomi | Redmi Note 11 | 11 | Yes | None | |
| ZTE nubia | RedMagic 7 Pro | 13 | Yes | None | |
| ZTE nubia | RedMagic 8 Pro | 13 | Yes | None | |
| ZTE nubia | RedMagic 9 Pro | 14 | Yes | None |
All emulators are RetroArch cores unless marked as (Standalone)
The @ symbol indicates that the emulator is deprecated and will be removed in a future ES-DE release.
| System name | Full name | Default emulator | Alternative emulators | Needs BIOS | Recommended game setup |
|---|---|---|---|---|---|
| 3do | 3DO Interactive Multiplayer | Opera | Real3DOPlayer (Standalone) | Yes | |
| adam | Coleco Adam | MAME4droid 2024 [Diskette] (Standalone) | MAME4droid 2024 [Tape] (Standalone), MAME4droid 2024 [Cartridge] (Standalone), MAME4droid 2024 [Software list] (Standalone), ColEm (Standalone) |
Yes for MAME4droid 2024 | |
| ags | Adventure Game Studio Game Engine | Placeholder | |||
| amiga | Commodore Amiga | PUAE | PUAE 2021 | Yes | See the specific Commodore Amiga and CDTV section in the user guide |
| amiga1200 | Commodore Amiga 1200 | PUAE | PUAE 2021 | Yes | See the specific Commodore Amiga and CDTV section in the user guide |
| amiga600 | Commodore Amiga 600 | PUAE | PUAE 2021 | Yes | See the specific Commodore Amiga and CDTV section in the user guide |
| amigacd32 | Commodore Amiga CD32 | PUAE | PUAE 2021 | Yes | See the specific Commodore Amiga and CDTV section in the user guide |
| amstradcpc | Amstrad CPC | Caprice32 | CrocoDS, MAME4droid 2024 (Standalone) |
Yes for MAME4droid 2024 | Single archive or disk file |
| android | Google Android | Placeholder | |||
| androidapps | Android Apps | Native apps | No | ||
| androidgames | Android Games | Native apps | No | ||
| apple2 | Apple II | MAME4droid 2024 (Standalone) | Yes | See the specific Apple II section in the user guide | |
| apple2gs | Apple IIGS | MAME4droid 2024 (Standalone) | Yes | See the specific Apple IIGS section in the user guide | |
| arcade | Arcade | MAME - Current | MAME 2010, MAME 2003-Plus, MAME 2003, MAME 2000, MAME4droid 2024 (Standalone), MAME4droid (Standalone), NEO.emu (Standalone), FinalBurn Neo, FB Alpha 2012, Geolith, Flycast, Flycast (Standalone) |
Depends | See the specific Arcade and Neo Geo section in the user guide |
| arcadia | Emerson Arcadia 2001 | DroidArcadia (Standalone) | MAME4droid 2024 (Standalone) | No | Single archive or ROM file |
| archimedes | Acorn Archimedes | MAME4droid 2024 [Model A440/1] (Standalone) | MAME4droid 2024 [Model A3000] (Standalone), MAME4droid 2024 [Model A310] (Standalone), MAME4droid 2024 [Model A540] (Standalone) |
Yes | |
| arduboy | Arduboy Miniature Game System | Arduous | Ardens | No | Single archive or .hex file |
| astrocde | Bally Astrocade | MAME4droid 2024 (Standalone) | Yes | Single archive or ROM file | |
| atari2600 | Atari 2600 | Stella | Stella 2014, Stella 2023, 2600.emu (Standalone) |
No | Single archive or ROM file |
| atari5200 | Atari 5200 | a5200 | Atari800 | Yes | Single archive or ROM file |
| atari7800 | Atari 7800 ProSystem | ProSystem | MAME4droid 2024 (Standalone) | Yes | Single archive or ROM file |
| atari800 | Atari 800 | Atari800 | Yes | ||
| atarijaguar | Atari Jaguar | Virtual Jaguar | IrataJaguar (Standalone), MAME4droid 2024 (Standalone) |
Yes for MAME4droid 2024 | Single archive or ROM file |
| atarijaguarcd | Atari Jaguar CD | Placeholder | |||
| atarilynx | Atari Lynx | Handy | Beetle Lynx, Lynx.emu (Standalone) |
No | Single archive or ROM file |
| atarist | Atari ST [also STE and Falcon] | Hatari | Yes | Single archive or image file for single-diskette games, .m3u playlist for multi-diskette games | |
| atarixe | Atari XE | Atari800 | Yes | ||
| atomiswave | Sammy Corporation Atomiswave | Flycast | Flycast (Standalone) | Depends | Single archive file |
| bbcmicro | Acorn Computers BBC Micro | MAME4droid 2024 (Standalone) | Yes | Single archive or diskette image file | |
| c64 | Commodore 64 | VICE x64sc Accurate | VICE x64 Fast, VICE x64 SuperCPU, VICE x128, C64.emu (Standalone) |
No | Single archive or image file for tape, cartridge or single-diskette games, .m3u playlist for multi-diskette games |
| cdimono1 | Philips CD-i | SAME CDi | MAME4droid 2024 (Standalone) | Yes | Single .bin/.cue pair |
| cdtv | Commodore CDTV | PUAE | PUAE 2021 | Yes | |
| chailove | ChaiLove Game Engine | ChaiLove | |||
| channelf | Fairchild Channel F | FreeChaF | MAME4droid 2024 (Standalone) | Yes | Single archive or ROM file |
| coco | Tandy Color Computer | MAME4droid 2024 [Cartridge] (Standalone) | MAME4droid 2024 [Tape] (Standalone) | Yes | See the specific Tandy Color Computer section in the user guide |
| colecovision | Coleco ColecoVision | blueMSX | Gearcoleco, MSX.emu (Standalone), ColEm (Standalone) |
Yes | Single archive or ROM file |
| consolearcade | Console Arcade Systems | MAME - Current | MAME4droid 2024 (Standalone), Flycast, Flycast (Standalone), Play! (Standalone) |
Depends | See the specific Console Arcade Systems section in the user guide |
| cps | Capcom Play System | MAME - Current | MAME 2010, MAME 2003-Plus, MAME 2003, MAME 2000, MAME4droid 2024 (Standalone), MAME4droid (Standalone), FinalBurn Neo, FB Alpha 2012, FB Alpha 2012 CPS-1, FB Alpha 2012 CPS-2, FB Alpha 2012 CPS-3 |
Depends | |
| cps1 | Capcom Play System I | MAME - Current | MAME 2010, MAME 2003-Plus, MAME 2003, MAME 2000, MAME4droid 2024 (Standalone), MAME4droid (Standalone), FinalBurn Neo, FB Alpha 2012, FB Alpha 2012 CPS-1 |
Depends | |
| cps2 | Capcom Play System II | MAME - Current | MAME 2010, MAME 2003-Plus, MAME 2003, MAME 2000, MAME4droid 2024 (Standalone), MAME4droid (Standalone), FB Alpha 2012, FB Alpha 2012 CPS-2 |
Depends | |
| cps3 | Capcom Play System III | MAME - Current | MAME 2010, MAME 2003-Plus, MAME 2003, MAME 2000, MAME4droid 2024 (Standalone), MAME4droid (Standalone), FB Alpha 2012, FB Alpha 2012 CPS-3 |
Depends | |
| crvision | VTech CreatiVision | MAME4droid 2024 (Standalone) | Yes | Single archive or ROM file | |
| daphne | Daphne Arcade LaserDisc Emulator | MAME4droid 2024 (Standalone) | DirkSimple | Depends | See the specific LaserDisc Games section in the user guide |
| desktop | Desktop Applications | Placeholder | |||
| doom | Doom | PrBoom | No | ||
| dos | DOS (PC) | DOSBox-Pure | DOSBox-Core, DOSBox-SVN, VirtualXT |
No | See the specific DOS / PC section in the user guide |
| dragon32 | Dragon Data Dragon 32 | MAME4droid 2024 Dragon 32 [Tape] (Standalone) | MAME4droid 2024 Dragon 32 [Cartridge] (Standalone), MAME4droid 2024 Dragon 64 [Tape] (Standalone), MAME4droid 2024 Dragon 64 [Cartridge] (Standalone) |
Yes | See the specific Dragon 32 and Tano Dragon section in the user guide |
| dreamcast | Sega Dreamcast | Flycast | Flycast (Standalone), Redream (Standalone) |
No | In separate folder interpreted as a file, with .m3u playlist if multi-disc game |
| easyrpg | EasyRPG Game Engine | EasyRPG | No | ||
| electron | Acorn Electron | MAME4droid 2024 [Tape] (Standalone) | MAME4droid 2024 [Diskette DFS] (Standalone), MAME4droid 2024 [Diskette ADFS] (Standalone) |
Yes | Single archive, or single tape or diskette image file |
| emulators | Emulators | Native apps | No | ||
| epic | Epic Games Store | Placeholder | |||
| famicom | Nintendo Family Computer | Mesen | Nestopia UE, FCEUmm, QuickNES, NES.emu (Standalone), iNES (Standalone), Nesoid (Standalone) |
No | Single archive or ROM file |
| fba | FinalBurn Alpha | FB Alpha 2012 | FB Alpha 2012 Neo Geo, FB Alpha 2012 CPS-1, FB Alpha 2012 CPS-2, FB Alpha 2012 CPS-3 |
Yes | |
| fbneo | FinalBurn Neo | FinalBurn Neo | Yes | ||
| fds | Nintendo Famicom Disk System | Mesen | Nestopia UE, FCEUmm, NES.emu (Standalone), iNES (Standalone), Nesoid (Standalone) |
Yes | Single archive or ROM file |
| flash | Adobe Flash | Ruffle (Standalone) | No | Single .swf file | |
| fm7 | Fujitsu FM-7 | MAME4droid 2024 [FM-7 Diskette] (Standalone) | MAME4droid 2024 [FM-7 Tape] (Standalone), MAME4droid 2024 [FM-7 Software list] (Standalone), MAME4droid 2024 [FM77AV Diskette] (Standalone), MAME4droid 2024 [FM77AV Tape] (Standalone), MAME4droid 2024 [FM77AV Software list] (Standalone) |
Yes | For tape files you need to manually start the cassette player from the MAME menu after the "load" command, as well as entering the "run" command after loading is complete |
| fmtowns | Fujitsu FM Towns | MAME4droid 2024 (Standalone) | Yes | See the specific Fujitsu FM Towns section in the user guide | |
| fpinball | Future Pinball | Placeholder | |||
| gamate | Bit Corporation Gamate | MAME4droid 2024 (Standalone) | Yes | Single archive or ROM file | |
| gameandwatch | Nintendo Game and Watch | Multi (MESS) | MAME4droid 2024 Local Artwork (Standalone), MAME4droid 2024 (Standalone), Handheld Electronic (GW) |
No | See the specific LCD handheld games section in the user guide |
| gamecom | Tiger Electronics Game.com | MAME4droid 2024 (Standalone) | Yes | Single archive or ROM file | |
| gamegear | Sega Game Gear | Genesis Plus GX | Genesis Plus GX Wide, Gearsystem, SMS Plus GX, PicoDrive, MasterGear (Standalone) |
No | Single archive or ROM file |
| gb | Nintendo Game Boy | Gambatte | SameBoy, Gearboy, TGB Dual, DoubleCherryGB, Mesen-S, bsnes, mGBA, VBA-M, GBC.emu (Standalone), My OldBoy! (Standalone), Pizza Boy GBC (Standalone) |
No | Single archive or ROM file |
| gba | Nintendo Game Boy Advance | mGBA | VBA-M, VBA Next, gpSP, GBA.emu (Standalone), My Boy! (Standalone), NooDS (Standalone), Pizza Boy GBA (Standalone) |
No | Single archive or ROM file |
| gbc | Nintendo Game Boy Color | Gambatte | SameBoy, Gearboy, TGB Dual, DoubleCherryGB, Mesen-S, bsnes, mGBA, VBA-M, GBC.emu (Standalone), My OldBoy! (Standalone), Pizza Boy GBC (Standalone) |
No | Single archive or ROM file |
| gc | Nintendo GameCube | Dolphin | Dolphin (Standalone), Dolphin MMJR (Standalone), Dolphin MMJR2 (Standalone) |
No | Disc image file for single-disc games, .m3u playlist for multi-disc games |
| genesis | Sega Genesis | Genesis Plus GX | Genesis Plus GX Wide, PicoDrive, MD.emu (Standalone) |
No | Single archive or ROM file |
| gmaster | Hartung Game Master | MAME4droid 2024 (Standalone) | Yes | Single archive or ROM file | |
| gx4000 | Amstrad GX4000 | Caprice32 | CrocoDS, MAME4droid 2024 (Standalone) |
No | Single archive or ROM file |
| intellivision | Mattel Electronics Intellivision | FreeIntv | MAME4droid 2024 (Standalone) | Yes | Single archive or ROM file |
| j2me | Java 2 Micro Edition (J2ME) | J2ME Loader (Standalone) | JL-Mod (Standalone), SquirrelJME |
No | Single .jar file |
| kodi | Kodi Home Theatre Software | Placeholder | |||
| laserdisc | LaserDisc Games | MAME4droid 2024 (Standalone) | DirkSimple | Depends | See the specific LaserDisc Games section in the user guide |
| lcdgames | LCD Handheld Games | Multi (MESS) | MAME4droid 2024 Local Artwork (Standalone), MAME4droid 2024 (Standalone), Handheld Electronic (GW) |
No | See the specific LCD handheld games section in the user guide |
| lowresnx | LowRes NX Fantasy Console | LowRes NX | No | Single ROM file | |
| lutris | Lutris Open Gaming Platform | Placeholder | |||
| lutro | Lutro Game Engine | Lutro | |||
| macintosh | Apple Macintosh | MAME4droid 2024 Mac SE Bootable (Standalone) | MAME4droid 2024 Mac SE Boot Disk (Standalone), MAME4droid 2024 Mac Plus Bootable (Standalone), MAME4droid 2024 Mac Plus Boot Disk (Standalone) |
Yes | See the specific Apple Macintosh section in the user guide |
| mame | Multiple Arcade Machine Emulator | MAME - Current | MAME 2010, MAME 2003-Plus, MAME 2003, MAME 2000, MAME4droid 2024 (Standalone), MAME4droid (Standalone), NEO.emu (Standalone), FinalBurn Neo, FB Alpha 2012, Geolith, Flycast, Flycast (Standalone) |
Depends | See the specific Arcade and Neo Geo section in the user guide |
| mame-advmame | AdvanceMAME | Placeholder | |||
| mastersystem | Sega Master System | Genesis Plus GX | Genesis Plus GX Wide, SMS Plus GX, Gearsystem, PicoDrive, MD.emu (Standalone), MasterGear (Standalone) |
No | Single archive or ROM file |
| megacd | Sega Mega-CD | Genesis Plus GX | Genesis Plus GX Wide, PicoDrive, MD.emu (Standalone) |
Yes | |
| megacdjp | Sega Mega-CD [Japan] | Genesis Plus GX | Genesis Plus GX Wide, PicoDrive, MD.emu (Standalone) |
Yes | |
| megadrive | Sega Mega Drive | Genesis Plus GX | Genesis Plus GX Wide, PicoDrive, MD.emu (Standalone) |
No | Single archive or ROM file |
| megadrivejp | Sega Mega Drive [Japan] | Genesis Plus GX | Genesis Plus GX Wide, PicoDrive, MD.emu (Standalone) |
No | Single archive or ROM file |
| megaduck | Creatronic Mega Duck | SameDuck | MAME4droid 2024 (Standalone) | No | Single archive or ROM file |
| mess | Multi Emulator Super System | Multi (MESS) | Depends | ||
| model2 | Sega Model 2 | MAME - Current | MAME4droid 2024 (Standalone) | Yes | See the specific Arcade and Neo Geo section in the user guide |
| model3 | Sega Model 3 | Placeholder | |||
| moto | Thomson MO/TO Series | Theodore | |||
| msx | MSX | blueMSX | fMSX, fMSX (Standalone), MSX.emu (Standalone) |
Yes except for fMSX standalone | |
| msx1 | MSX1 | blueMSX | fMSX, fMSX (Standalone), MSX.emu (Standalone) |
Yes except for fMSX standalone | |
| msx2 | MSX2 | blueMSX | fMSX, fMSX (Standalone), MSX.emu (Standalone) |
Yes except for fMSX standalone | |
| msxturbor | MSX Turbo R | blueMSX | fMSX, MSX.emu (Standalone) |
Yes | |
| mugen | M.U.G.E.N Game Engine | Placeholder | Yes | ||
| multivision | Othello Multivision | Gearsystem | MasterGear (Standalone) | No | Single archive or ROM file |
| naomi | Sega NAOMI | Flycast | Flycast (Standalone) | Yes | Single archive file + .chd file in subdirectory if GD-ROM game |
| naomi2 | Sega NAOMI 2 | Flycast | Flycast (Standalone) | Yes | Single archive file + .chd file in subdirectory if GD-ROM game |
| naomigd | Sega NAOMI GD-ROM | Flycast | Flycast (Standalone) | Yes | Single archive file + .chd file in subdirectory if GD-ROM game |
| n3ds | Nintendo 3DS | Citra | Citra (Standalone), Citra Canary (Standalone), Citra MMJ (Standalone), Lime3DS (Standalone), Panda3DS (Standalone) |
No | Single ROM file |
| n64 | Nintendo 64 | Mupen64Plus-Next | M64Plus FZ (Standalone), Mupen64Plus AE (Standalone), ParaLLEl N64 |
No | Single archive or ROM file |
| n64dd | Nintendo 64DD | Mupen64Plus-Next | M64Plus FZ (Standalone), Mupen64Plus AE (Standalone), ParaLLEl N64 |
Yes | |
| nds | Nintendo DS | melonDS DS | melonDS, melonDS (Standalone), melonDS Nightly (Standalone), DeSmuME, DeSmuME 2015, DraStic (Standalone), NooDS (Standalone) |
No | Single archive or ROM file |
| neogeo | SNK Neo Geo | FinalBurn Neo | Geolith, NEO.emu (Standalone), MAME4droid 2024 (Standalone), MAME4droid (Standalone) |
Yes | See the specific Arcade and Neo Geo section in the user guide |
| neogeocd | SNK Neo Geo CD | NeoCD | FinalBurn Neo, MAME4droid 2024 (Standalone) |
Yes | .chd (NeoCD and MAME4droid 2024 only) or .cue file |
| neogeocdjp | SNK Neo Geo CD [Japan] | NeoCD | FinalBurn Neo, MAME4droid 2024 (Standalone) |
Yes | .chd (NeoCD and MAME4droid 2024 only) or .cue file |
| nes | Nintendo Entertainment System | Mesen | Nestopia UE, FCEUmm, QuickNES, NES.emu (Standalone), iNES (Standalone), Nesoid (Standalone) |
No | Single archive or ROM file |
| ngage | Nokia N-Gage | EKA2L1 (Standalone) | Yes | See the specific Symbian and Nokia N-Gage section in the User guide | |
| ngp | SNK Neo Geo Pocket | Beetle NeoPop | RACE, NGP.emu (Standalone) |
No | Single archive or ROM file |
| ngpc | SNK Neo Geo Pocket Color | Beetle NeoPop | RACE, NGP.emu (Standalone) |
No | Single archive or ROM file |
| odyssey2 | Magnavox Odyssey 2 | O2EM | MAME4droid 2024 (Standalone) | Yes | Single archive or ROM file |
| openbor | OpenBOR Game Engine | OpenBOR (Standalone) | No | See the specific OpenBOR section in the User guide | |
| oric | Tangerine Computer Systems Oric | MAME4droid 2024 (Standalone) | Yes | See the specific Tangerine Computer Systems Oric section in the user guide | |
| palm | Palm OS | Mu | |||
| pc | IBM PC | DOSBox-Pure | DOSBox-Core, DOSBox-SVN, VirtualXT |
No | See the specific DOS / PC section in the user guide |
| pc88 | NEC PC-8800 Series | QUASI88 | Yes | ||
| pc98 | NEC PC-9800 Series | Neko Project II Kai | Neko Project II | ||
| pcarcade | PC Arcade Systems | Winlator Cmod Glibc (Standalone) | Winlator Cmod PRoot (Standalone) | No | See the Winlator section elsewhere in this document |
| pcengine | NEC PC Engine | Beetle PCE | Beetle PCE FAST, Beetle SuperGrafx, PCE.emu (Standalone) |
No | Single archive or ROM file |
| pcenginecd | NEC PC Engine CD | Beetle PCE | Beetle PCE FAST, Beetle SuperGrafx, PCE.emu (Standalone) |
Yes | |
| pcfx | NEC PC-FX | Beetle PC-FX | Yes | ||
| pico8 | PICO-8 Fantasy Console | Fake-08 | Retro8 | No | See the specific PICO-8 section in the User guide |
| plus4 | Commodore Plus/4 | VICE xplus4 | No | Single archive or image file for tape, cartridge or single-diskette games, .m3u playlist for multi-diskette games | |
| pokemini | Nintendo Pokémon Mini | PokeMini | No | ||
| ports | Ports | ECWolf (Wolfenstein 3D) | NXEngine (Cave Story), OpenLara (Tomb Raider), Super Bros War |
Yes for ECWolf | |
| ps2 | Sony PlayStation 2 | AetherSX2 (Standalone) | Play! (Standalone) | Yes for AetherSX2 | |
| ps3 | Sony PlayStation 3 | Placeholder | |||
| ps4 | Sony PlayStation 4 | Placeholder | |||
| psp | Sony PlayStation Portable | PPSSPP | PPSSPP (Standalone) | No | Single disc image file |
| psvita | Sony PlayStation Vita | Vita3K (Standalone) | Yes | See the specific Sony PlayStation Vita section in the User guide | |
| psx | Sony PlayStation | Beetle PSX | Beetle PSX HW, PCSX ReARMed, SwanStation, DuckStation (Standalone), ePSXe (Standalone), FPseNG (Standalone), FPse (Standalone) |
Yes | .chd file for single-disc games, .m3u playlist for multi-disc games |
| pv1000 | Casio PV-1000 | MAME4droid 2024 (Standalone) | No | Single archive or ROM file | |
| quake | Quake | TyrQuake | vitaQuake 2, vitaQuake 2 [Rogue], vitaQuake 2 [Xatrix], vitaQuake 2 [Zaero] |
No | |
| samcoupe | MGT SAM Coupé | Speccy (Standalone) | No | Single archive or ROM file | |
| satellaview | Nintendo Satellaview | Snes9x - Current | Snes9x 2010, Snes9x 2005 Plus, Snes9x EX+ (Standalone), bsnes, bsnes-hd, bsnes-mercury Accuracy, Mesen-S |
||
| saturn | Sega Saturn | Beetle Saturn | YabaSanshiro, Yaba Sanshiro 2 (Standalone), Yabause, Saturn.emu (Standalone) |
Yes | .chd file for single-disc games, .m3u playlist for multi-disc games |
| saturnjp | Sega Saturn [Japan] | Beetle Saturn | YabaSanshiro, Yaba Sanshiro 2 (Standalone), Yabause, Saturn.emu (Standalone) |
Yes | .chd file for single-disc games, .m3u playlist for multi-disc games |
| scummvm | ScummVM Game Engine | ScummVM | ScummVM (Standalone) | No | See the specific ScummVM section in the user guide |
| scv | Epoch Super Cassette Vision | MAME4droid 2024 (Standalone) | Yes | Single archive or ROM file | |
| sega32x | Sega Mega Drive 32X | PicoDrive | No | Single archive or ROM file | |
| sega32xjp | Sega Super 32X [Japan] | PicoDrive | No | Single archive or ROM file | |
| sega32xna | Sega Genesis 32X [North America] | PicoDrive | No | Single archive or ROM file | |
| segacd | Sega CD | Genesis Plus GX | Genesis Plus GX Wide, PicoDrive, MD.emu (Standalone) |
Yes | |
| sfc | Nintendo SFC (Super Famicom) | Snes9x - Current | Snes9x 2010, Snes9x 2005 Plus, Snes9x EX+ (Standalone), bsnes, bsnes-hd, bsnes-mercury Accuracy, Beetle Supafaust, Mesen-S |
No | Single archive or ROM file |
| sg-1000 | Sega SG-1000 | Genesis Plus GX | Genesis Plus GX Wide, Gearsystem, blueMSX, MasterGear (Standalone) |
No | Single archive or ROM file |
| sgb | Nintendo Super Game Boy | Mesen-S | SameBoy, mGBA |
Single archive or ROM file | |
| snes | Nintendo SNES (Super Nintendo) | Snes9x - Current | Snes9x 2010, Snes9x 2005 Plus, Snes9x EX+ (Standalone), bsnes, bsnes-hd, bsnes-mercury Accuracy, Beetle Supafaust, Mesen-S |
No | Single archive or ROM file |
| snesna | Nintendo SNES (Super Nintendo) [North America] | Snes9x - Current | Snes9x 2010, Snes9x 2005 Plus, Snes9x EX+ (Standalone), bsnes, bsnes-hd, bsnes-mercury Accuracy, Beetle Supafaust, Mesen-S |
No | Single archive or ROM file |
| solarus | Solarus Game Engine | Placeholder | |||
| spectravideo | Spectravideo | blueMSX | |||
| steam | Valve Steam | Placeholder | |||
| stv | Sega Titan Video Game System | MAME - Current | MAME4droid 2024 (Standalone), MAME4droid (Standalone) |
Yes | Single archive file |
| sufami | Bandai SuFami Turbo | Snes9x - Current | Snes9x 2010, Snes9x 2005 Plus, Snes9x EX+ (Standalone), bsnes, bsnes-hd, bsnes-mercury Accuracy |
||
| supergrafx | NEC SuperGrafx | Beetle SuperGrafx | Beetle PCE, PCE.emu (Standalone) |
No | Single archive or ROM file |
| supervision | Watara Supervision | Potator | MAME4droid 2024 (Standalone) | No | Single archive or ROM file |
| supracan | Funtech Super A'Can | MAME4droid 2024 (Standalone) | Yes | Single archive or ROM file. You need a supracan.zip archive that contains a valid internal_68k.bin file and an empty file named umc6650.bin | |
| switch | Nintendo Switch | Skyline (Standalone) | Yes | ||
| symbian | Symbian | EKA2L1 (Standalone) | Yes | See the specific Symbian and Nokia N-Gage section in the User guide | |
| tanodragon | Tano Dragon | MAME4droid 2024 [Tape] (Standalone) | MAME4droid 2024 [Cartridge] (Standalone) | Yes | See the specific Dragon 32 and Tano Dragon section in the user guide |
| tg16 | NEC TurboGrafx-16 | Beetle PCE | Beetle PCE FAST, Beetle SuperGrafx, PCE.emu (Standalone) |
No | Single archive or ROM file |
| tg-cd | NEC TurboGrafx-CD | Beetle PCE | Beetle PCE FAST, Beetle SuperGrafx, PCE.emu (Standalone) |
Yes | |
| ti99 | Texas Instruments TI-99 | MAME4droid 2024 (Standalone) | Yes | See the specific Texas Instruments TI-99 section in the user guide | |
| tic80 | TIC-80 Fantasy Computer | TIC-80 | No | Single .tic file | |
| to8 | Thomson TO8 | Theodore | |||
| triforce | Namco-Sega-Nintendo Triforce | Placeholder | |||
| trs-80 | Tandy TRS-80 | Placeholder | |||
| type-x | Taito Type X | Winlator Cmod Glibc (Standalone) | Winlator Cmod PRoot (Standalone) | No | See the Winlator section elsewhere in this document |
| uzebox | Uzebox Open Source Console | Uzem | |||
| vectrex | GCE Vectrex | vecx | MAME4droid 2024 (Standalone) | Yes for MAME4droid 2024 | Single archive or ROM file |
| vic20 | Commodore VIC-20 | VICE xvic | No | Single archive or tape, cartridge or diskette image file | |
| videopac | Philips Videopac G7000 | O2EM | MAME4droid 2024 (Standalone) | Yes | Single archive or ROM file |
| virtualboy | Nintendo Virtual Boy | Beetle VB | No | ||
| vpinball | Visual Pinball | Visual Pinball (Standalone) | No | See the specific Visual Pinball section in the user guide | |
| vsmile | VTech V.Smile | MAME4droid 2024 (Standalone) | Yes | Single archive or ROM file | |
| wasm4 | WASM-4 Fantasy Console | WASM-4 | No | Single .wasm file | |
| wii | Nintendo Wii | Dolphin | Dolphin (Standalone), Dolphin MMJR (Standalone), Dolphin MMJR2 (Standalone) |
No | |
| wiiu | Nintendo Wii U | Placeholder | |||
| windows | Microsoft Windows | Winlator Cmod Glibc (Standalone) | Winlator Cmod PRoot (Standalone) | No | See the Winlator section elsewhere in this document |
| windows3x | Microsoft Windows 3.x | DOSBox-Pure | No | ||
| windows9x | Microsoft Windows 9x | DOSBox-Pure | No | ||
| wonderswan | Bandai WonderSwan | Beetle Cygne | Swan.emu (Standalone) | No | Single archive or ROM file |
| wonderswancolor | Bandai WonderSwan Color | Beetle Cygne | Swan.emu (Standalone) | No | Single archive or ROM file |
| x1 | Sharp X1 | X Millennium | MAME4droid 2024 [Diskette] (Standalone), MAME4droid 2024 [Tape] (Standalone) |
Yes for MAME4droid 2024 | Single archive or diskette/tape file |
| x68000 | Sharp X68000 | PX68k | MAME4droid 2024 (Standalone) | Yes | |
| xbox | Microsoft Xbox | Placeholder | |||
| xbox360 | Microsoft Xbox 360 | Placeholder | |||
| zmachine | Infocom Z-machine | MojoZork | No | ||
| zx81 | Sinclair ZX81 | EightyOne | No | ||
| zxnext | Sinclair ZX Spectrum Next | Placeholder | |||
| zxspectrum | Sinclair ZX Spectrum | Fuse | Speccy (Standalone) | No | Single archive or ROM file |