Zelda: Tears of the Kingdom on Kenji-NX — Settings & Performance Guide
The Legend of Zelda: Tears of the Kingdom is one of the most demanding Nintendo Switch games you can throw at a mobile emulator — a huge open world, physics-driven building, and constant streaming of terrain. The good news: Kenji-NX can run it, and because Kenji-NX is built on the accuracy-focused Ryujinx architecture rather than Yuzu code, it handles the game’s graphics more faithfully than most Yuzu-based Android forks. The bad news: your phone matters a lot. This guide covers what to expect, the settings that matter, and fixes for the most common problems.
Legal note: Kenji-NX does not include any game files. You must own Tears of the Kingdom and dump it from your own Nintendo Switch. This site does not provide game downloads, keys, or firmware — only setup guidance. If you haven’t set up the emulator yet, start with our download page and the setup guide.
Can Kenji-NX Run Tears of the Kingdom?
Short answer: yes, on a capable phone. Tears of the Kingdom targets 30 FPS on real Switch hardware, and on a modern Snapdragon flagship with Kenji-NX 2.1.0 or newer, many players report a largely smooth experience in the overworld, with dips in the most demanding spots (the Depths, large Ultrahand contraptions, heavy weather effects).
Two things shape your experience more than anything else:
- Your SoC. Snapdragon 8 Elite and 8 Gen 3 / 8 Gen 2 phones are in the best position. Snapdragon 8 Gen 1 can work with lowered settings. Exynos and MediaTek Dimensity phones are not recommended for this game — they can’t use Turnip custom GPU drivers (see below), and their stock Vulkan drivers struggle with TotK’s rendering.
- Shader compilation. The first time you visit a new area, use a new ability, or trigger a new effect, you may see brief stutter while shaders compile. This is normal on every Switch emulator and improves the longer you play, as the shader cache builds up. Don’t judge performance by your first 20 minutes.
RAM matters too: 8 GB is a workable minimum, but 12 GB or more gives the emulator far more headroom — TotK is a memory-hungry game, and Android killing background processes mid-session is a common cause of mysterious crashes.
Recommended Settings for Tears of the Kingdom
These are starting values, not magic numbers. Apply them, play for a while, then adjust one thing at a time. (Menu names can differ slightly between Kenji-NX builds — the concepts are the same.)
| Setting | Recommended | Why |
|---|---|---|
| Graphics API | Vulkan | Best performance and compatibility on Android; required for custom Turnip drivers. |
| Resolution scale | 1x (handheld) | Higher scales multiply GPU load enormously. Raise to 1.25x–1.5x only on Snapdragon 8 Elite / 8 Gen 3 if stable. |
| Custom GPU driver | Latest Turnip (Snapdragon only) | Fixes texture glitches and improves frame pacing on Adreno GPUs. See our driver guide. |
| VSync | On | Prevents screen tearing; TotK is a 30 FPS game by design, so there’s nothing to gain by disabling it. |
| Shader cache | Enabled | Lets compiled shaders persist between sessions, so repeat visits to areas get smoother. |
| Anisotropic filtering | Auto or 4x | Sharpens ground textures at angles; 4x is cheap on flagship GPUs, leave on Auto if unsure. |
| Audio backend | Default (Cubeb) | Audio crackling under load is usually thermal throttling, not an audio setting — cool the phone first. |
| Docked mode | Off (handheld) | Handheld mode targets lower clocks and is easier on mobile GPUs; docked mode raises the load for little visual gain on a phone screen. |
Turnip GPU Drivers: Snapdragon Only
Turnip is the open-source Mesa3D Vulkan driver for Qualcomm Adreno GPUs, loaded through Kenji-NX’s custom driver mechanism to replace your phone’s stock Qualcomm driver. For Tears of the Kingdom it is close to essential: users commonly report fewer texture glitches, fewer crashes, and smoother frame pacing with a recent Turnip build than with the stock driver.
The catch: Turnip only works on Snapdragon (Adreno) phones. MediaTek Dimensity (Mali) and Samsung Exynos (Xclipse) devices cannot use it — there is no Turnip equivalent for those GPUs, so you’re stuck with the stock driver and should expect a worse experience in this particular game.
Our Turnip driver guide walks through where to find current builds and how to install them. One tip specific to TotK: if a new Turnip release causes new glitches, roll back to the previous one — driver regressions happen, and the “latest” isn’t always the best for every game.
Snapdragon 8 Elite vs Older Chips
Kenji-NX 2.1.0 was specifically optimized for the Snapdragon 8 Elite (Adreno 830): GPU stability, synchronization, and memory fixes, plus roughly 10% better performance and a smaller APK. In practice, the 8 Elite is currently the best chip for running TotK on Kenji-NX — provided you’re on a recent build with a compatible Turnip driver. (Early on, the Adreno 830 actually lacked Turnip support and could underperform the 8 Gen 3 in some emulators; community Turnip builds for the 8xx series have been catching up through 2026.)
- Snapdragon 8 Elite / 8 Gen 3: best experience; try 1x resolution first, experiment upward cautiously.
- Snapdragon 8 Gen 2: solid; mature Turnip support; stick to 1x and you’ll be comfortable in most areas.
- Snapdragon 8 Gen 1 / 8+ Gen 1: playable with lowered settings; expect dips in the Depths and heavy combat; keep the phone cool.
- Exynos 2400 / Dimensity 9000-series: not recommended for TotK — no Turnip, stock driver only, and commonly reported as unstable for this title.
Known Issues and Workarounds
These are problems commonly reported by the community — your mileage will vary by device, build, and driver version:
- Stutter when entering new areas or using new abilities: shader compilation. Normal, especially early on. It fades as the shader cache builds. Avoid judging performance in the first hour.
- Crashes in the Depths or with large Ultrahand builds: the most GPU/CPU-intensive scenes in the game. Lower the resolution scale, close all background apps, and make sure the phone isn’t thermally throttled.
- Black screen on boot: almost always a setup problem — firmware or keys missing or mismatched. Re-check the setup guide and confirm your dumped files match your game version.
- Rainbow textures or invisible models: usually a GPU driver issue on Snapdragon — update (or roll back) your Turnip driver.
- Audio crackling or slowdown after long sessions: heat. TotK at full load will thermal-throttle most phones within 20–40 minutes. Take breaks, remove the case, or play in a cool room.
- Save problems: always save in-game at regular intervals; keep a backup of your save folder before updating Kenji-NX builds.
Frequently Asked Questions
Is Tears of the Kingdom fully playable on Kenji-NX, start to finish?
Many players report completing the game on capable Snapdragon phones. That said, no emulator can promise a flawless full playthrough on every device — expect occasional hiccups, and keep saves backed up.
Do I really need Turnip drivers?
On Snapdragon: strongly recommended — it’s the single biggest visual-stability upgrade for this game. On Exynos or Dimensity: not an option, which is why those chips aren’t recommended for TotK.
Why can’t I get more than 30 FPS?
Because Tears of the Kingdom itself targets 30 FPS on real Switch hardware. Chasing higher frame rates means mods and instability; a locked, stable 30 is the realistic goal on mobile.
Where can I download the game?
We don’t provide game downloads, and neither does Kenji-NX. Buy the game, then dump it from your own Switch. Downloading game files you don’t own is piracy.
The game runs fine, then gets slow after half an hour. Why?
Almost certainly thermal throttling: sustained full load heats the SoC and the phone clocks down. Cool the phone, close background apps, and consider lowering the resolution scale for long sessions.
Can I transfer my save from a real Switch or from another emulator?
Save transfer between Switch and emulators is possible in principle but fiddly (it involves homebrew tools on a modded console and matching title versions). Back up everything before attempting it, and don’t overwrite your working save.
Next steps: grab the latest build from our download page, work through the setup guide to get firmware and keys installed correctly, then install a current Turnip driver from the driver guide. Start at 1x resolution, let the shader cache build, and only then push settings upward.