A native Android port is a version of a game rebuilt to run directly on Android, with no emulator in between. The game's code is compiled for your phone's processor, so it usually runs faster, uses less battery and supports modern screens and controllers. Most community ports still need game files from a copy you own.
This guide explains the term in plain English, shows how a port differs from emulation, and tells you what to check before you install one.
What does "native port" mean?
"Port" means moving a game from the system it was made for to a different one. "Native" means the result runs as a normal Android app. The game talks to Android and to your phone's hardware directly, instead of passing through a program that pretends to be a console or a PC.
Most community ports start from the game's code. Sometimes the original developer has released the source code. More often, volunteers have rebuilt it by decompilation, which means turning the finished game back into readable code piece by piece. That code is then adapted for Android: new controls, new graphics code, new screen sizes.
One well-known example is Ship of Harkinian, a port of The Legend of Zelda: Ocarina of Time. It grew out of a full decompilation of the game and now runs on Android as its own app.
Native port vs emulator vs the original release
An emulator copies the original hardware in software. Your phone plays the game and plays the part of the console at the same time, which costs speed, battery and heat. A native port removes that second job.
| Native port | Emulator | Original release | |
|---|---|---|---|
| How it runs | Game code built for Android | Imitates the original system while you play | On the hardware it was made for |
| Performance cost | Low | Higher, because the phone does two jobs | None |
| Battery and heat | Usually lower | Usually higher | Not applicable |
| Extras | Widescreen, higher frame rates and mods, where the project adds them | Save states and upscaling, depending on the emulator | The game as shipped |
| Game coverage | Only games someone has ported | Most of a system's library | One game |
| Setup | Done once for each game | Done once for each system | None |
The methods in between
Not everything called a "port" is fully native. Three methods sit between a true port and an emulator:
- Static recompilation. A tool converts the game's original machine code into code your phone can run, ahead of time, before you play. The result runs as a native program, but it is a translation of the original game and not a rewrite.
- Compatibility layers. The game still thinks it is on its original platform. A layer translates what it asks for, such as graphics and system calls, into something Android understands.
- Native code execution. Some systems use the same kind of processor as your phone. Here the game's processor code runs directly on your CPU, while other software handles graphics and system features.
Each of these still puts something between the game and Android. How much speed that costs depends on how well the project is made.
Does "fully native" matter?
Less than the arguments online suggest. What matters to a player is the result: does the game run better than it does in an emulator, with less heat and less battery drain, on your device? A well-made recompiled game can beat a poor "true" port. Judge a port by how it runs, not by its label.
Why most ports need your own game files
A port is new code written or rebuilt by the project. The art, music, levels and story still belong to the game's publisher, and a project cannot share them legally. So the port ships with the engine only, and you supply the content.
In practice this means the port asks for a file from your own copy of the game on first launch. It reads the game data out of that file and saves it in a format the port can use. Without your file there is nothing to show on screen.
The exact file and version are different for every port, and many projects accept only specific versions. Always read the project's own instructions. We never link to game files, and a site that offers them next to a port is one to avoid.
Is a native port better than emulation?
When a good port exists for a game you want to play, it is usually the better choice. You can expect:
- Smoother play on the same phone, because there is no hardware to imitate.
- Lower battery use and less heat.
- Features the original never had, such as widescreen, higher frame rates, touch controls and mod support, where the project has added them.
Emulation still wins in two cases. The first is coverage: ports exist for a small number of games, and emulators cover whole libraries. The second is device support: a mature emulator may behave better on an unusual phone than a young port does. Many players use both.
How to tell a real port from a repackaged APK
Many sites offer "ported" games that are only an emulator and a copied game wrapped into one APK. These are piracy, and they are a common way to spread malware. A real port usually shows these signs:
- It has a public home. There is an official project page or code repository with named maintainers, release notes and an issue tracker.
- It asks for your own game files. A download that already contains the full commercial game is not a clean port.
- The download comes from the project. Releases come from the project's own page, not from a file locker or a page covered in fake download buttons.
- The size makes sense. A port without game data is often small. A huge "all in one" file is a warning.
- It asks for few permissions. A game does not need your contacts, SMS or call logs.
- The claims are modest. Real projects list what is broken. Fake ones promise that everything works on every phone.
Every port we cover links to the project's official page, so you always download from the source.
What you need before installing one
Requirements change from port to port, so treat this as a checklist and confirm the details on each port's page.
- A 64-bit Android phone or tablet. Most current ports target modern 64-bit ARM devices. The minimum Android version depends on the project.
- Game files from a copy you own, in the exact version the port supports.
- Free storage for the app and the extracted game data.
- Permission to install apps from outside the Play Store, since most ports are installed from an APK. Android asks you to allow this for your browser or file manager.
- A file manager, to put the game files in the folder the port expects.
- A controller, if you want one. Many ports support touch, but most older games feel better with physical buttons.
Why your phone's graphics chip matters
The same port can run well on one phone and badly on another, and the graphics chip (GPU) is often the reason.
- Phones with Snapdragon processors use Adreno GPUs. An open-source driver called Turnip exists for many of these, and some ports and emulators can load it in place of the phone's default driver to fix graphics bugs.
- Phones with MediaTek, Exynos or Tensor processors usually use Mali GPUs. Their drivers are closed, so there is no matching community driver to load. When something breaks, developers have to find the cause by trial and error with testers.
This is also why community ports cannot match official ones for device support. An official porting studio has a paid team and shelves of test devices. Most community porters are volunteers who work in their free time, often with one or two phones. Clear bug reports from players are how these ports improve.
How we test ports
We only call a port "tested" when we have run it ourselves on a real device. Each port page lists the device, the Android version, the port version, the date of the test and the result, with our own screenshots. If we have not tested something, we say so.
Read the full method on our How We Test Ports page.
Frequently asked questions
Is a native port the same as an emulator?
No. An emulator imitates the original console or computer so the unchanged game can run. A native port is the game itself, rebuilt to run on Android directly.
Are native Android ports legal?
The port's code is usually the project's own work, and many projects are open source. The game's content still belongs to its publisher, which is why ports ask you to supply files from a copy you own. Laws differ between countries, and this guide is not legal advice.
Are native ports free?
The port itself is usually free. You still need to own the original game, because the port uses its files.
Do I need to root my phone?
Usually not. Most ports install like any other APK and run on a normal, unrooted phone.
Is a recompiled game a native port?
It is close, but not the same. A recompiled game runs as native code, yet it is a machine translation of the original and not a hand-made rewrite. For players the difference is small if the game runs well.
Why does a port need a custom GPU driver?
Some games use graphics features that a phone's default driver handles badly. A newer or community-made driver can fix that. This option is mostly limited to Adreno GPUs.
Why does a port run badly on my phone when it works for others?
Different chips and drivers behave differently, and volunteer developers cannot test every device. Check the port's known issues, try the settings the project suggests, and report the problem to the project with your device model and Android version.
Does ANP host APKs or game files?
No. We link to each project's official page and never host or link to game files.
Ports to start with
Browse the Ported Games section to see every port we cover. If you know which kind of game you want, go straight to Console classics, PC classics or Handheld classics.
A good first port is one marked as tested on a device close to yours. Open its page, check the "What you need" section, and follow the setup steps in order.
