The Jak and Daxter Trilogy Runs Natively on a Handheld. Just Not an ARM One.

2026-09-18 · Setup guide

Affiliate disclosure: This guide contains affiliate links. As an Amazon Associate, we earn from qualifying purchases at no extra cost to you. Learn more.

PS2 emulation on handhelds is still the hardest thing most people try. Jak and Daxter was always one of the rougher cases, because it pushed the PS2 hard and it does not degrade gracefully.

So here is the good news. All three Jak games now have native PC ports, and they are not emulation. They run as ordinary programs, which means a Steam Deck plays them properly rather than heroically.

And here is the part that gets misreported constantly. OpenGOAL requires x86-64 with AVX. There is no ARM build. The videos you have seen of Jak running on an Android handheld are doing something different, and if you buy hardware based on them you will be disappointed.

The Short Version

• What it is: OpenGOAL, a native reimplementation of the engine the Jak games were written in
• Games supported: Jak and Daxter: The Precursor Legacy, Jak II, and Jak 3. Only those three
• Requirement: an x86-64 CPU with AVX support
• Graphics: OpenGL 4.3, or 4.1 on macOS
• Platforms: Windows 10/11, Linux, macOS on Intel
• No ARM build exists. Not for Android, not for ARM Linux
• Steam Deck: works well, and you should use the compiled releases rather than the Launcher
• What you supply: your own copies of the games

Why This Is Not Emulation

Worth being precise, because "native port" gets used loosely.

The Jak games were written in GOAL, a Lisp dialect Naughty Dog built for themselves. That is unusual, and it turned out to matter enormously. OpenGOAL is a reimplementation of that language and its compiler, which means the project can take the game's original code and build it into a native program.

There is no PS2 being simulated. No Emotion Engine, no VU units, no timing quirks to get right. The game is compiled for your machine and runs on it directly. Our decomp vs recomp explainer covers where this sits relative to the other techniques.

Practically, that means the things that make PS2 emulation painful on handhelds simply are not present. Frame pacing is stable. There is no shader compilation stutter of the PCSX2 kind. Battery life is dramatically better, because you are not paying an emulation tax on every frame.

The ARM Problem, Clearly

This is the section that exists because the internet keeps getting it wrong.

OpenGOAL's documentation states the requirement plainly: an x86-64 CPU with AVX support. AVX is an instruction set extension that has been standard on desktop CPUs for well over a decade, and does not exist on ARM at all.

There is no aarch64 build. It is not a matter of somebody not bothering to compile one, though that would be enough on its own. The project targets x86-64 as its architecture.

So: Steam Deck yes. ROG Ally yes. Any Windows handheld yes. Retroid, AYN, Anbernic, Android phones, no.

About Those Android Videos

You will find videos showing the Jak trilogy running on Android handhelds. They are not fake, and they are not running a native ARM build, because none exists.

They are using a translation layer. Box64 or FEX takes the x86-64 binary and translates its instructions to ARM while the game runs. That is genuinely impressive engineering and it genuinely works, sometimes well.

But it is the exact overhead that native ports exist to eliminate. You take a game that runs natively on x86 and add a translation cost to make it run on ARM. The result can be playable, and it is not what the port was built to be. Our translation layers explainer covers what Box64 and FEX actually do and what each layer costs you.

If a video's title says "native on Android," it is wrong. Check whether they mention Box64 in the description. They usually do.

Setting It Up on a Steam Deck

This is the configuration most readers will actually use, and it is straightforward.

Get the release build, not the Launcher. OpenGOAL's own documentation notes that Steam Deck users will likely need the compiled releases rather than the Launcher application. Start there and save yourself the detour.

Supply your own game copies. OpenGOAL ships the engine, not the games. You provide the game data from copies you own, and the project's documentation covers the extraction process. We do not link game sources.

Add it to Steam as a non-Steam game. This gets you the proper controller configuration, the performance overlay and the power management that make handheld play pleasant. It also means the game appears in your library like anything else.

Set a frame rate cap. These games will happily run far above the PS2's original target. On a handheld, capping to your display's refresh rate is better for battery and heat than letting it run free.

What You Gain Over PCSX2

If you have tried these games through PS2 emulation on a handheld, the differences are immediate.

Stability. Emulator compatibility issues specific to these games stop existing, because there is no emulator.

Frame pacing. Native code does not have the hitching that comes from an emulator recompiling code or compiling shaders mid scene.

Battery. This is the one handheld owners notice most. Emulation overhead is constant, and removing it shows up directly in runtime.

Enhancements. Higher resolutions, widescreen handled properly rather than hacked in, and modern controller support.

The trade, as always with this category, is that it covers three games. PCSX2 covers the PS2 library. Our PS2 emulation guide covers the general case.

What to Play It On

The honest hardware advice here is short, because the architecture requirement makes the decision for you.

The

is the natural home for this. It is x86-64 with AVX, it runs Linux, the ports are well behaved on it, and the screen suits these games.

Any Windows handheld works equally well on the architecture question. The

is the obvious alternative if you would rather be on Windows.

If you own an ARM handheld and want these games, do not buy new hardware on the strength of the Android videos. Either accept the translation layer route with its overhead, or use PS2 emulation, which on a strong Android device is a more predictable experience than you might expect.

Questions People Ask

Does OpenGOAL run on Android?

No. There is no ARM build. Videos showing it on Android handhelds are running the x86-64 binary through a translation layer like Box64 or FEX, which adds overhead the native port was designed to avoid.

What is AVX and does my handheld have it?

AVX is an x86 instruction set extension, standard on desktop and laptop CPUs for over a decade. Every x86 handheld including the Steam Deck has it. No ARM device has it, because it is an x86 feature.

Which Jak games are supported?

The first three: The Precursor Legacy, Jak II, and Jak 3. The documentation is explicit that only those three are supported.

Do I need the original discs?

You need copies of the games that you own. OpenGOAL ships the engine and tooling, not the game data, and extracts what it needs from your own copies.

Is this better than PCSX2 on a Steam Deck?

For these three games, yes, on stability, frame pacing and battery life. PCSX2 remains necessary for the rest of the PS2 library.

Should I use the Launcher or the release build on Steam Deck?

The release build. OpenGOAL's documentation notes Steam Deck users will likely need the compiled releases rather than the Launcher.

Related Reading

• FEX, Box64, Proton, DXVK: What Translation Layers Actually Do
• Decomp vs Recomp: How Old Games Become PC Ports
• Every Decomp Port You Can Play on a Cheap ARM Handheld
• Recompiled Games List: Every Native PC Port by System
• Can Android Handhelds Run Recompiled Games?
• Steam Deck Retro Gaming Guide

Platform support, the AVX requirement and Steam Deck guidance come from OpenGOAL's official documentation, retrieved 18 September 2026. No performance benchmarks are quoted because we ran none.