Affiliate disclosure: This guide contains affiliate links. As an Amazon Associate, we earn from qualifying purchases at no extra cost to you. Learn more.
mGBA is the go-to emulator for Game Boy Advance games. It is fast, remarkably accurate, and runs on practically any device. While most handhelds can play GBA games through a generic core, mGBA gets the small details right, from tricky games that need precise timing to oddball cartridges with solar sensors and tilt controls. If you care about GBA games playing exactly as they should, mGBA is the emulator to use.
This guide covers installing mGBA, adding the optional BIOS, getting the display looking right, and handling the special features some GBA games use. We frame all of this around playing games you already own.
Affiliate disclosure: This page contains affiliate links. As an Amazon Associate, we earn from qualifying purchases at no extra cost to you.
Why mGBA Over a Generic Core
Many handhelds default to a general-purpose GBA core, and those work fine for most games. mGBA goes further with better accuracy and compatibility. It handles the trickiest games correctly, supports the GBA's special hardware features, and stays light enough to run on weak devices. It is also available both as a standalone app and as a RetroArch core, so it fits any setup.
mGBA as a Standalone App or RetroArch Core
You have two ways to run mGBA.
RetroArch core. The mGBA core is the easiest option on most firmware. It plugs into your existing RetroArch setup, with shaders, save states, and per-game settings. For muOS, KNULLI, ArkOS, and similar firmware, this is usually the way to go.
Standalone app. On Android handhelds and PC handhelds, the standalone mGBA app gives you a dedicated interface and a few extra options. Good if you want GBA gaming in its own app.
For most people, the RetroArch core is the simplest path. Our RetroArch setup guide covers installing cores.
What You Need
- Any retro handheld, since GBA is light to emulate
- mGBA as a core or standalone app
- An optional GBA BIOS file
- Your own GBA games
Step 1: Install mGBA
In RetroArch, open the core downloader and grab the mGBA core. On Android, install the standalone mGBA app from the Play Store or the official source. On a Steam Deck, EmuDeck can set up GBA emulation with mGBA for you.
Always download from official sources.
Step 2: Add the BIOS (Optional but Recommended)
mGBA includes a built-in BIOS replacement, so games run without an official BIOS. Adding the real GBA BIOS improves accuracy and shows the authentic boot animation. The file is small and commonly named gba_bios.bin.
You must dump the BIOS from a GBA you own. We do not link to BIOS downloads. Place it in your RetroArch system folder, or point the standalone app to it in settings.
Step 3: Add Your Games
GBA games are single files, usually with a .gba extension, and they need no special handling. Drop them in your GBA games folder, scan the folder in your frontend, and you are ready to play.
Step 4: Display Settings
GBA games look great with the right setup. A few tips:
- Integer scaling. Keeps pixels crisp and even on a modern screen.
- Color correction. The original GBA screen was dim and washed out. Many emulators offer a GBA color mode that adjusts the palette to look right. Try it both ways.
- LCD shader. A subtle LCD-grid shader recreates the handheld look. Our RetroArch shaders guide covers presets.
GBA games also fit a widescreen handheld nicely, since the GBA used a wide aspect ratio.
Step 5: Special GBA Features
Some GBA cartridges used unusual hardware. mGBA handles these well.
- Solar sensor games. Boktai used a real sunlight sensor. mGBA lets you simulate the sensor level so you can play without the original cart's sensor.
- Tilt and gyro games. A few games used motion sensors. mGBA can map these to buttons or device motion.
- Rumble. Some games supported rumble. On a handheld with a rumble motor, mGBA can drive it.
If a special-feature game acts strangely, check the core options for the matching sensor setting.
Troubleshooting
Game runs but saves do not stick. Some games use different save types. mGBA usually auto-detects them, but you can set the save type manually in the core options if a game will not save.
A game has timing glitches. This is exactly what mGBA is good at avoiding. Make sure you are using mGBA and not a generic core, and add the real BIOS for maximum accuracy.
Colors look washed out or too dark. Toggle the GBA color correction setting until it looks right to you.
Getting the Screen Size Right
The GBA screen was 240x160. That is a small, awkward number, and it is why GBA games can look either perfect or slightly mushy depending on one setting.
Multiply by whole numbers and every original pixel becomes an even block:
| Scale | Output | Fits comfortably on |
|---|---|---|
| 3x | 720x480 | Most 640x480 and 720p handhelds |
| 4x | 960x640 | 720p and above |
| 5x | 1200x800 | 1080p handhelds |
| 6x | 1440x960 | 1080p, with cropping |
Pick the largest whole multiple that fits inside your panel, then let the emulator letterbox the rest. If you instead stretch the image to fill the screen exactly, some original pixels become two screen pixels and others become three, which is what produces that faintly uneven, shimmery look when you scroll.
Our integer scaling explainer covers the principle in full.
One nice bonus: the GBA's 3:2 screen is much closer to a modern widescreen handheld than a 4:3 system like the SNES, so GBA games waste less glass than most retro systems.
Save Types, and Why a Game Might Not Save
This is the single most common mGBA problem, and it has a specific cause worth understanding.
GBA cartridges did not all save the same way. Different games used different save chips, and the emulator has to pick the right type. mGBA auto-detects correctly for the overwhelming majority of the library.
When it gets it wrong, the symptom is distinctive: the game plays perfectly but your progress vanishes, either immediately or the next time you load. If that happens, set the save type manually in the core or app options rather than assuming the file is broken.
Two habits worth having:
Back up your save files, not just save states. They are separate things. A save state is a snapshot of the emulator's memory; a save file is the game's own save data. Our save state management guide covers keeping both safe.
Test that a new game saves early. Play to the first save point and confirm it sticks before investing hours.
Link Cable Games
Worth setting expectations here, because it comes up constantly.
A number of GBA games used the link cable for trading and multiplayer. Emulated link cable support is possible in some setups, but it is fiddly, it varies by platform, and on a handheld running a single instance it generally is not practical.
If link functionality is the specific thing you want, that is one of the few areas where original hardware still has a real advantage. For single player, which is the vast majority of the library, emulation is comfortably better than the original.
Frequently Asked Questions
Is mGBA better than a generic GBA core?
For accuracy, yes. Most games run fine on a generic core, but mGBA gets the difficult ones right, handles the special cartridge hardware such as solar and tilt sensors, and stays light enough to run on weak devices. It is the safer default.
Do I need a GBA BIOS to use mGBA?
No. mGBA includes a built-in BIOS replacement and games run without the real file. Adding a BIOS dumped from a GBA you own improves accuracy slightly and gives you the authentic boot animation.
Why does my GBA game not save?
Almost always the save type. GBA cartridges used several different save chips and the emulator has to pick the right one. mGBA auto-detects correctly for nearly all games, but when it does not, the game plays fine and your progress disappears. Set the save type manually in the options.
Should I use mGBA standalone or the RetroArch core?
The RetroArch core for most handhelds, especially on Linux firmware like muOS, KNULLI or ArkOS, since it plugs into a setup you already have. The standalone app suits Android and PC handhelds where you want GBA in its own dedicated interface.
Why do GBA games look washed out?
The original GBA screen was dim and unlit, so games were authored with bright, high contrast palettes to compensate. On a modern backlit screen those colours look oversaturated. Colour correction modes adjust for this. Try it both ways, since it is genuinely a taste question.
What scale should I use on a 1080p handheld?
5x, giving 1200x800, is usually the largest whole multiple that fits cleanly. Whole number scaling keeps every original pixel an even block, which is what stops the image shimmering when you scroll.
Can I play GBA link cable games?
Not practically on a single handheld. Emulated link support exists in some setups but it is fiddly and platform dependent. Link play is one of the few places original hardware still wins.
Recommended Handhelds
GBA runs on anything, so pick based on screen and comfort. The GBA's widescreen ratio suits a horizontal device. The
is a clamshell with a great layout for GBA games. For a tiny pocket option, the handles the whole library beautifully.Ready to build a library? See our 25 best GBA games list. For more Nintendo portable classics, check our best Game Boy and Game Boy Color games list. New to emulation? Start with our RetroArch setup guide.

