NetherSX2 vs AetherSX2: 60 FPS vs 0 Updates [2026]

Elias Virtanen
August 19, 2026
20 min read

Google Play still lists an app called AetherSX2. Open it and you will find a PlayStation 2 emulator that has not shipped a real update since its developer, known online as Tahlreth, walked away in January 2023 after what he described as “neverending impersonating, complaints, demands, and now death threats.” The app still installs. It still boots God of War II. What it will not do is get better, because nobody is working on it. That vacuum is exactly why NetherSX2 exists, and why a search for “nethersx2 vs aethersx2” now pulls close to 10,000 monthly searches in the US alone, according to keyword data pulled in August 2026.

This piece compares the three apps people actually install to play PS2 discs on an Android phone in 2026: NetherSX2, the frozen-in-place AetherSX2, and Play!, the smaller cross-platform project that takes a different technical approach entirely. We pulled specs from each project’s GitHub pages and Play Store listings, cross-checked frame rate numbers against three independent benchmark sources, and built a migration path for anyone still running the old app. NetherSX2 vs AetherSX2 is not a close call on paper, but the details of why matter if you’re picking a renderer, choosing a phone, or trying to move save files without losing 40 hours of progress.

Don’t miss new tech stories on Google

Add Tech Insider once in the Google app and our stories appear in your news suggestions.

Why PS2 Emulation on Android Suddenly Matters Again in 2026

PS2 emulation on phones was a niche hobby for years, limited by weak mobile GPUs and immature dynamic recompilers. That changed once Qualcomm’s Adreno GPUs and community Vulkan drivers caught up to the job. A Snapdragon 8 Gen 3 or 8 Elite phone now pushes PS2 titles at native or 2x internal resolution with headroom to spare, something that simply was not possible on 2019-era silicon. The catch is that the app most people associate with this hobby, AetherSX2, is not the app doing the work anymore.

NetherSX2 picked up the AetherSX2 codebase at build 3668 and kept shipping. In 2026 alone it has seen a Turnip-driver fork add explicit Snapdragon 8 Elite and 8 Gen 5 detection, a “Classic” branch aimed at older devices, and a patch branch that fixes rendering bugs the original app never addressed. Meanwhile Play!, a much older and smaller project, keeps chugging along as the one PS2 emulator that also runs natively on iOS and desktop, which matters to anyone who splits time between an Android phone and an iPhone or Steam Deck.

The demand is real and growing. “best emulators for android” alone pulls an estimated 6,600 searches a month in the US, and “ps2 emulator android” adds another 8,100, both flagged as low-competition keywords as of August 2026. People are actively hunting for an answer, and a lot of what they find is outdated guidance pointing them toward an app that will never update again.

NetherSX2 vs AetherSX2 vs Play!: The Quick Verdict

If you only read one section, read this one. NetherSX2 is the emulator to install today for the overwhelming majority of Android PS2 gaming. It carries active GitHub releases, a Google Play Store listing, Vulkan and OpenGL renderer options, and hardware-specific driver forks that target current Snapdragon chips. AetherSX2 still works as a fallback if you already have it installed and don’t want to touch a working setup, but it will not fix new bugs, add new games to its compatibility list, or support next-generation phones going forward. Play! is a specialist pick: choose it if cross-platform support matters more to you than raw frame rate, since its interpreter-first approach trades some performance for portability across Android, iOS, and desktop.

The practical takeaway for most readers: uninstall nothing yet, but install NetherSX2 alongside whatever you’re running, copy your BIOS file over, and test your usual library before you commit. Save states are not interchangeable between every NetherSX2 branch, so the migration section further down walks through the safe order of operations.

What Happened to AetherSX2: A Timeline

AetherSX2 launched as a one-person project and quickly became the default answer to “how do I play PS2 games on my phone.” That popularity came with a cost. On January 4, 2023, developer Tahlreth posted a notice on the app’s own front page announcing an indefinite suspension of development, citing sustained online harassment, impersonation, and threats against his life, as

The app did not disappear immediately. It stayed downloadable on Google Play for over a year while receiving zero functional updates. Google finally pulled the listing on March 10, 2024, according to a GBAtemp forum thread documenting the removal. The official GitHub readme still tells users, in Tahlreth’s own words, that the app “will continue to work for the foreseeable future,” and the project’s archive page hosts the last Play Store release, version 1.4-3064, as a direct APK download for anyone who wants it.

That frozen state is the entire reason NetherSX2 exists. Community developers forked the last usable AetherSX2came clear the original project would not return. The DroidGamers coverage from the original announcement still holds up as the clearest account of why this fork happened and how abruptly it started

NetherSX2 Explained: The Community Successor

NetherSX2 is not one monolithic app. It is a small ecosystem of forks built on the AetherSX2 3668 codebase, each maintained by different contributors for different priorities. The main NetherSX2 project, distributed through Google Play under the package com.theemulatorapp.nethersx2, ships as a full-featured PS2 emulator with per-title configuration, a cover-art library, and a choice between Vulkan and OpenGL rendering, or an automatic mode that picks for you.

Alongside the Play Store build, three GitHub-hosted variants matter. NetherSX2 Classic, maintained on the Trixarian GitHub, sticks with the older 3668 branch for maximum compatibility with older devices and games. NetherSX2-Turnip, built by developer nckstwrt, adds inbuilt support for the community Turnip Vulkan driver on Qualcomm Adreno GPUs, something the base app does not include by default. Its May 2026 release notes specifically call out new drivers tuned for Snapdragon 8 Elite and 8 Gen 5 chips and make Vulkan the default renderer instead of OpenGL, a direct response to how much faster Vulkan runs on current-generation Adreno hardware.

Version numbering across NetherSX2 forks can be confusing. A build tracked on SourceForge as v2.2n “Net Dev Build,” registered in January 2026 under maintainer dantesf, sits alongside separate release tags on GitHub like v2.2n-4248, published in January 2026 at 20.62 MB and requiring Android 8.0 or newer on arm64-v8a devices. The number after the version string, either 3668 or 4248, refers to the underlying codebase branch, and that number matters more than the version label when you’re troubleshooting a specific game.

Play! Emulator: The Cross-Platform Alternative

Play! takes a different path than the AetherSX2 family entirely. Where NetherSX2 and AetherSX2 both lean on a dynamic recompiler that translates PS2 machine code into native ARM instructions on the fly, Play! relies more heavily on an interpreter-based approach, according to comparison coverage of the PS2-on-Android space. That architecture choice trades raw speed for portability. The same Play! codebase runs on Android, iOS, Windows, macOS, and Linux, which is not something NetherSX2 or AetherSX2 can claim.

The tradeoff shows up in compatibility and performance. Play! does not have the same breadth of tested, high-frame-rate results for demanding 3D titles that NetherSX2’s Vulkan renderer produces, and unlike NetherSX2, it does not currently have a confirmed listing on the Google Play Store, meaning most users install it through direct APK builds from its GitHub releases instead. For someone who owns an iPhone and an Android phone and wants one save file and one settings profile that works on both, that portability can outweigh the frame rate gap. For someone who just wants God of War II running at 60 FPS on a single Android flagship, NetherSX2 remains the faster, better-documented choice.

Full Specs Comparison: NetherSX2 vs AetherSX2 vs Play!

The table below lines up the three emulators across the specs that actually change your day-to-day experience, from renderer choice to whether the app is still receiving code commits in 2026.

Spec	NetherSX2	AetherSX2	Play!
Development status (2026)	Active, multiple forks shipping updates	Frozen since January 2023	Active, slower release cadence
Base codebase	AetherSX2 build 3668, forked and updated	Original PCSX2-derived Android port	Independent, own codebase
Latest tracked version	v2.2n-4248 / Turnip May 2026 build	v1.4-3064 (final release)	Rolling GitHub builds, no fixed version cadence found
Google Play Store listing	Yes (com.theemulatorapp.nethersx2)	Removed March 10, 2024	Not confirmed in current listings
Minimum Android version	Android 8.0 (Oreo)	Android 8.0 (Oreo) at time of last release	Varies by build, typically Android 8.0+
CPU architecture	ARM64 or x86_64	ARM64	ARM64 (Android build)
Minimum RAM	2 GB (4 GB+ recommended)	2 GB (as documented at launch)	Not formally specified; 4 GB+ recommended in practice
Renderer options	Vulkan and OpenGL, selectable or automatic	Vulkan and OpenGL	OpenGL-focused, limited Vulkan support
Adreno Turnip driver support	Built-in via NetherSX2-Turnip fork	Not supported, no Turnip integration	Not applicable
Save state cross-compatibility	Not compatible between 3668 and 4248 branches	Single branch, no cross-compatibility issue	Own save format, incompatible with NetherSX2/AetherSX2
Cross-platform builds	Android only	Android only	Android, iOS, Windows, macOS, Linux
BIOS requirement	Yes, user-supplied	Yes, user-supplied	Yes, user-supplied (with some HLE experimentation)
Source availability	Open source, multiple public GitHub repos	Open source, archived GitHub repo	Open source, active GitHub repo
Price	Free	Free	Free

Benchmark Results: FPS Across Three Independent Sources

Frame rate is where the NetherSX2 vs AetherSX2 gap becomes visible in numbers rather than talking points. None of these figures come from a single standardized lab test, since no PS2-on-Android benchmark suite is widely adopted, but pulling from three separate communityially with the Turnip driver on Adreno GPUs, holds a steadier frame rate than AetherSX2 did on the same class of games

Game	Emulator / Settings	FPS	Source
God of War II	NetherSX2, Vulkan, 2x resolution, MTVU on (Snapdragon 855+ class)	60 (stable, rated “Perfect”)	aetherrsx2apk.com Compatibility Database
Shadow of the Colossus	NetherSX2, Vulkan, native resolution, EE underclock -2 (Snapdragon 8 Gen 1 class)	25-30 (matches original console)	aetherrsx2apk.com Compatibility Database
Shadow of the Colossus	NetherSX2, Vulkan enabled	58	ps2biospro.com, “7 Best PS2 Emulators for Android in 2025”
God of War 2	AetherSX2, 2x resolution	55-60	gadgetspecs.my, “Best Phones for Emulation & Retro Gaming (2026)”
Kingdom Hearts	AetherSX2, native resolution	45-55	gadgetspecs.my, “Best Phones for Emulation & Retro Gaming (2026)”
Shadow of the Colossus	Generic PS2-on-Android setup	20-30	stereoindex.com, PS2/PSP Android guide

Two patterns stand out. First, Shadow of the Colossus is consistently the hardest game on this list to pin down, with figures ranging from 20 to 58 FPS depending on renderer and resolution settings, which tells you the game is unusually sensitive to configuration rather than that the sources disagree wildly. Second, the highest and most stable numbers across every source come from NetherSX2 runs using Vulkan, not AetherSX2 runs on OpenGL, which lines up with community guidance from Android Authority’s coverage of the NetherSX2 branch split.

Performance by Hardware Tier

Chip generation and GPU vendor change which renderer you should even bother enabling. Qualcomm’s Adreno GPUs, found in every Snapdragon phone, have the best Vulkan driver support in the Android PS2 scene right now, largely thanks to the community Turnip driver that NetherSX2-Turnip bundles directly. A Snapdragon 8 Gen 3 or newer phone running that fork should default to Vulkan and expect the 55-60 FPS range on most licensed titles at 2x internal resolution.

Mali-based GPUs, common in MediaTek Dimensity and Samsung Exynos chips, are a rougher ride. NetherSX2’s own patch notes flag that older Mali devices can hit rendering issues or outright crashes on Vulkan in specific titles, Dark Cloud 2 being the most cited example, and recommend switching to OpenGL to get past the broken scenes. That is a real practical limitation: if you’re shopping for a phone specifically for PS2 emulation and you’re choosing between a Snapdragon and a Dimensity chip at a similar price, the Snapdragon side has meaningfully better driver support today.

Budget hardware still works, just with lower ceilings. found both usable, but the 695 needed lower internal resolution and, in some cases, EE core underclocking to hold a stable frame rate in demanding 3D titles. A widely cited guideline from the PS2 emulation community pegs Snapdragon 845 or better with 6 GB or more of RAM as the practical floor for smooth NetherSX2 performance across a normal game library

Pricing and Total Cost of Ownership

None of these three apps charge a purchase price, so “pricing” here means something closer to distribution friction and hidden costs, like which store you can trust and what you have to

Cost factor	NetherSX2	AetherSX2	Play!
App purchase price	Free	Free	Free
Ads or in-app purchases	None reported in current listing	None; app was never monetized	None
Distribution trust level	Google Play listing plus verifiable GitHub source	Play Store listing removed; only archive/GitHub mirrors remain	GitHub-only, no store listing to verify against
BIOS cost	$0 if dumped from a PS2 you own; must be sourced legally by the user	$0, same requirement	$0, same requirement
Recommended phone tier	Snapdragon 8-series flagship or upper-mid-range for full Vulkan benefit	Any device that already ran it acceptably before 2023	No specific tier; performance scales down more gracefully but caps lower
Hidden cost	Occasional branch-switching between 3668 and 4248 for game-specific bugs	Zero future compatibility fixes for new phones or Android versions	Lower overall performance ceiling versus NetherSX2’s Vulkan path

The real cost of sticking with AetherSX2 is not measured in dollars. It’s measured in the games that will never get compatibility fixes and the phones released after 2023 that never got official testing against the app. NetherSX2 vs AetherSX2 on pure “does it cost money” grounds is a tie. On “will this still work on the phone I buy in 2027” grounds, it isn’t close.

Real-World Examples: Six Scenarios Across the Three Emulators

• Flagship Vulkan run: A Snapdragon 8 Gen 3 phone running NetherSX2-Turnip holds a stable 60 FPS in God of War II at 2x internal resolution with MTVU enabled, matching the top-end figures in the aetherrsx2apk.com compatibility database.
• Mid-range compromise: A Snapdragon 8 Gen 1 device running Shadow of the Colossus on NetherSX2 with native resolution and a mild EE underclock lands in the 25-30 FPS range, intentionally matching the original PS2 release rather than chasing a higher, unstable number.
• Handheld emulation device: Retro-focused Android handhelds in the Retroid Pocket and AYN Odin families run NetherSX2’s per-title configuration profiles well, since their Snapdragon chipsets generally fall into the “good Adreno Vulkan support” bracket this article flags above.
• Legacy save migration: A player moving from an old AetherSX2 archive build (v1.4-3064) to NetherSX2 finds their memory card imports cleanly, but only after confirming which NetherSX2 branch, 3668 or 4248, matches what they were running before.
• Mali GPU fallback: A MediaTek Dimensity phone running Dark Cloud 2 hits rendering glitches on NetherSX2’s Vulkan path and has to switch to OpenGL, exactly the scenario NetherSX2’s own patch notes warn about for older Mali hardware.
• Branch-specific bug avoidance: A player trying to run NASCAR or Colin McRae Rally finds both titles broken on the newer 4248 branch and has to fall back to NetherSX2 Classic’s 3668 branch to get correct visuals, per the project’s own release notes.

Vulkan vs OpenGL Rendering: Why It Matters Here

Renderer choice is the single setting that most changes your experience across all three emulators, and it’s worth understanding rather than just toggling blindly. Vulkan is a lower-level graphics API that gives the emulator more direct control over the GPU, which generally translates into higher and more stable frame rates when the driver support is solid. OpenGL is the older, more universally compatible fallback, slower in most cases but far less likely to produce the rendering glitches that show up on newer Vulkan drivers running against unusual PS2 shader effects.

NetherSX2’s own Play Store listing lets users pick Vulkan, OpenGL, or an automatic mode, and the NetherSX2-Turnip fork went as far as flipping the default from OpenGL to Vulkan in its May 2026 release, a decision the maintainers made specifically because current Snapdragon 8-series Adreno drivers had matured enough to make Vulkan the safer default rather than the risky one. AetherSX2 offered the same two renderer options back when it was still updated, but never received the driver-level tuning for post-2023 chips that NetherSX2’s forks have since added.

The practical rule that’s emerged from the community by mid-2026: default to Vulkan on any Snapdragon 8-series phone, and keep OpenGL as your immediate fallback the moment a specific game shows graphical corruption, particularly on Mali GPU devices where Vulkan support is less mature across the board.

BIOS Requirements and the Legal Line

All three emulators share the same non-negotiable requirement: none of them ship a PS2 BIOS file, and none of them will boot a game without one. NetherSX2’s own GitHub documentation states this directly, telling users the app “does not include PlayStation 2 BIOS files or game ROMs” and that they “must legally provide your own.” That means dumping the BIOS from a PS2 console you physically own, using a memory card and one of the established BIOS-dumping methods the emulation community has documented for years, not downloading a BIOS file from a random site.

The same logic extends to game files. Ripping an ISO from a disc you own for personal backup and play is the legal model these tools are built around; downloading ROMs of games you don’t own is not, regardless of which emulator you’re using. This isn’t unique to PS2 emulation, but it’s worth restating because NetherSX2’s Play Store presence, unlike AetherSX2’s now-removed listing, puts it under more direct scrutiny, and staying inside that legal lane is part of why the app has stayed available.

How These Mobile Builds Compare to PCSX2 on Desktop

None of these three Android apps are unrelated to the PC emulation scene. AetherSX2 started life as a fork of PCSX2, the long-running desktop PS2 emulator, adapted to run on ARM chips instead of x86 processors. NetherSX2 inherited that lineage second-hand, since it forked AetherSX2 rather than PCSX2 directly, but the underlying emulation logic, from EE core timing to GS plugin behavior, traces back to the same desktop project. If you’ve already set up PCSX2 on a Windows or Linux machine, a lot of the vocabulary carries over directly: MTVU, EE cyclerate, and internal resolution scaling all mean the same thing on a phone as they do on a desktop GPU.

The practical gap is compatibility breadth rather than core architecture. PCSX2 on a modern desktop GPU still edges out every Android option on raw compatibility percentage and upscaling headroom, simply because a discrete GPU has far more thermal and power budget than a phone chip does. What NetherSX2 has closed is the frame rate gap on the specific, well-tested titles most people actually play, God of War II and Kingdom Hearts among them. For someone deciding between a phone and a handheld PC for PS2 gaming on the go, the honest answer is that NetherSX2 gets you most of the way to a PCSX2-quality experience in specific, popular games, while a Windows handheld running PCSX2 still wins on library-wide compatibility.

Storage, ISOs, and Game File Management

PS2 games are large by retro-emulation standards. A single ISO typically runs anywhere from 700 MB to over 4 GB depending on whether the disc used CD or DVD media, and a modest ten-game library can eat 20 to 30 GB of phone storage before you’ve added save data or shader caches. All three emulators expect you to manage that storage yourself, since none of them include any form of game distribution or download feature.

NetherSX2’s Play Store build organizes ISOs through a cover-art library that scans a folder you point it to, which makes managing a larger collection noticeably easier than AetherSX2’s flatter file browser ever was. Compressed formats like CHD can shrink storage needs significantly compared to raw ISO files, and NetherSX2 supports them, which matters most on phones that shipped with 128 GB of storage or less and no microSD expansion. Play!’s file handling is more basic across its supported platforms, reflecting its smaller contributor base, though it covers the same core CD and DVD formats the other two apps expect.

Migration Guide: Moving From AetherSX2 to NetherSX2

If you’re still running AetherSX2 and want to move to an actively maintained app without losing progress, follow this order rather than uninstalling first and figuring it out after.

1. Locate your AetherSX2 save data and memory card files in the app’s storage folder before touching anything else, and copy the entire folder to your phone’s main storage or a cloud backup.
2. Back up your BIOS file separately. You’ll need to re-import it into the new app rather than assuming it carries over automatically.
3. Keep AetherSX2 installed rather than uninstalling it immediately. Running both apps side by side costs you storage space but gives you a fallback if something breaks during migration.
4. Install NetherSX2 from the Google Play listing for the standard experience, or pull a GitHub release directly if you specifically want the Turnip Vulkan driver fork for a Snapdragon 8-series phone.
5. Decide between the 3668 and 4248 branches before importing anything. If you play racing or rally titles like NASCAR or Colin McRae Rally, start on the 3668 branch, since 4248 has documented graphical bugs in those specific games.
6. Import your BIOS file into NetherSX2’s settings menu first, and confirm the app recognizes it before importing anything else.
7. Copy your memory card files into NetherSX2’s save folder. Note that save states, not memory card saves, do not carry over between the 3668 and 4248 branches, so in-game saves are the safer format to rely on during migration.
8. Reconfigure your controller mapping. Button layouts and touch control positions do not automatically transfer between apps.
9. Set your renderer. Start with Vulkan on Snapdragon 8-series hardware, or OpenGL if you’re on a Mali GPU device or notice graphical corruption in specific titles.
10. Test your regular game library end to end before uninstalling AetherSX2, checking cutscenes and save/load cycles specifically, since those are where compatibility gaps tend to show up first.

Use Cases: Which Emulator Fits Your Setup

The right answer depends more on your phone’s chipset and your priorities than on brand loyalty to whichever app you installed first.

• Flagship Snapdragon owner chasing max frame rate: NetherSX2-Turnip, Vulkan renderer set as default, targeting the 55-60 FPS range on demanding 3D titles.
• Budget or mid-range MediaTek/Exynos owner: Base NetherSX2 with OpenGL as the default renderer, switching to Vulkan only on titles you’ve confirmed run cleanly.
• Someone with a working AetherSX2 setup who doesn’t want to touch it yet: Keep it running for now, but install NetherSX2 alongside it and start testing, since AetherSX2 will not support new phones or Android versions going forward.
• Racing and rally game fans: NetherSX2 Classic on the 3668 branch specifically, to avoid the documented graphical bugs the newer 4248 branch introduces in those titles.
• Cross-platform player splitting time between iOS and Android, or wanting a desktop build too: Play!, accepting a lower performance ceiling in exchange for one codebase across every device you own.
• Retro handheld device owner (Retroid Pocket, AYN Odin and similar): Latest NetherSX2 APK from GitHub, using its per-title configuration system to tune settings game by game rather than relying on one global preset.

Pros and Cons of Each Emulator

NetherSX2

Pros: Actively maintained across multiple forks, available on Google Play, Vulkan driver support tuned for current Snapdragon chips, per-title configuration, free with no ads or in-app purchases.

Cons: Fragmented into multiple branches and forks that can confuse new users, save states not compatible across the 3668/4248 split, some titles have documented bugs on the newer branch, Vulkan rendering issues on older Mali GPUs.

AetherSX2

Pros: Simple, single-branch app with no version confusion, still functional for anyone with an existing working setup, well-documented compatibility list built up over years of active use before 2023.

Cons: No development since January 2023, removed from Google Play in March 2024, no support for phones or Android versions released after the freeze, no Turnip driver integration for current Snapdragon GPUs.

Play!

Pros: True cross-platform support across Android, iOS, Windows, macOS, and Linux, active GitHub development, useful for players who want one consistent app across multiple devices.

Cons: No Google Play listing to verify against, generally lower performance ceiling than NetherSX2’s Vulkan path, smaller community and less documented game-by-game compatibility data than the AetherSX2 family.

Common Problems and How to Fix Them

Most of the complaints in NetherSX2 and AetherSX2 communities boil down to a handful of repeatable issues. Stuttering in cutscenes on NetherSX2 usually traces back to the wrong renderer for your GPU vendor, so if you’re on a Mali chip and seeing hitching during full-motion video, switch from Vulkan to OpenGL before changing anything else. Crashes specifically in Dark Cloud 2 or similar titles on older Mali hardware are a known Vulkan rendering issue documented in NetherSX2’s own patch notes, and the fix is the same renderer swap.

Save states that refuse to load after an update are almost always a branch mismatch. If you jumped from 3668 to 4248 or back, your save states will not carry over, though standard in-game memory card saves generally will. NASCAR and Colin McRae Rally players seeing broken visuals on a fresh NetherSX2 install should specifically check whether they’re on the 4248 branch and roll back to NetherSX2 Classic’s 3668 branch if so, per the project’s documented release notes.

Anyone still running AetherSX2 who starts seeing crashes after an Android system update should treat that as the app finally showing its age. There is no patch coming. That’s the point where migrating to NetherSX2, using the guide above, stops being optional.

The Verdict: Which PS2 Emulator Should You Install in 2026

NetherSX2 wins this comparison on every measurable axis that matters for day-to-day use in 2026: it’s actively developed, it has a Google Play listing you can trust, it hits higher and steadier frame rates than AetherSX2 ever did on the same class of hardware, and it has dedicated driver forks tuned for the Snapdragon chips shipping in phones right now. AetherSX2 was the right answer in 2022. It is not the right answer anymore, not because it stopped working, but because it stopped improving three years ago and the phones on shelves today were never part of its testing.

Play! earns a narrower recommendation. If cross-platform support across Android, iOS, and desktop is a genuine requirement rather than a nice-to-have, it’s the only one of these three that delivers it, and that’s worth the performance tradeoff for the right user. For everyone else asking “what’s the best PS2 emulator for Android right now,” the answer is NetherSX2, specifically the Turnip build if you’re on a recent Snapdragon flagship, and the Classic 3668 branch if you’re troubleshooting a specific older title or running on more modest hardware.

Frequently Asked Questions

Is AetherSX2 still safe to use in 2026?

The app still installs and runs, and the developer’s own GitHub readme says it will keep working for the foreseeable future. It received no security or compatibility updates since January 2023, though, and Google removed it from the Play Store in March 2024, so anyone downloading it now has to rely on archive builds rather than an official, current listing.

What is the difference between NetherSX2 3668 and 4248?

They’re two different codebase branches. 3668 is the older, more broadly compatible branch, better suited to titles like NASCAR and Colin McRae Rally that have documented graphical bugs on the newer build. 4248 is the newer branch with more recent fixes and features, but save states from one branch will not load on the other.

Do I need a BIOS file to use NetherSX2?

Yes. NetherSX2’s own documentation states plainly that it does not ship a BIOS or game files, and requires users to legally dump their own BIOS from a PS2 console they own. The same requirement applies to AetherSX2 and Play!.

Is NetherSX2 on the Google Play Store?

Yes, under the package name com.theemulatorapp.nethersx2, offering Vulkan and OpenGL rendering options directly from the store listing. AetherSX2’s listing was removed in March 2024, and Play! does not currently have a confirmed Play Store presence.

Which is faster, Vulkan or OpenGL, for PS2 emulation on Android?

Vulkan is generally faster on current Snapdragon Adreno GPUs, which is why NetherSX2-Turnip made it the default renderer in its May 2026 release. On older Mali GPUs, found in many MediaTek and Exynos chips, OpenGL is often the more stable choice due to documented Vulkan rendering issues in specific games.

Can I transfer AetherSX2 saves to NetherSX2?

Standard in-game memory card saves generally transfer cleanly since NetherSX2 was built on the AetherSX2 3668 codebase. Save states are less reliable, especially if you end up on NetherSX2’s newer 4248 branch, since save states are not compatible between the 3668 and 4248 branches.

What phone do I need to run PS2 games well on Android?

A widely cited community baseline puts Snapdragon 845 or better with 6 GB or more of RAM as the floor for smooth performance. For the best results with NetherSX2-Turnip’s Vulkan default, a Snapdragon 8-series flagship from the last two to three years gives the most consistent frame rates across demanding titles.

Is Play! a good alternative to NetherSX2?

It’s a good alternative specifically for cross-platform use, since it runs on Android, iOS, Windows, macOS, and Linux from one codebase. For pure Android performance, NetherSX2’s Vulkan renderer and Turnip driver support generally outperform Play!’s more interpreter-heavy approach.

Related Coverage