DuskPort

What Is Dusk? Twilight Princess PC Port Explained (2026)

Dusk is a native PC port of Zelda Twilight Princess — not an emulator, not a ROM hack. Here's exactly what it is, how it works, and why it matters.

Published 2026-05-10

If you’ve been seeing the name “Dusk” all over Reddit, Twitter, and gaming news in the past day, but you’re not sure what it is, here’s the short version:

Dusk is the first native PC port of The Legend of Zelda: Twilight Princess. It was released by the TwilitRealm team on May 9, 2026, and runs on Windows, macOS (Apple Silicon + Intel), Linux (x86 + ARM), Android, and iOS. It is open-source under CC0-1.0, completely free, and requires you to supply your own legally-dumped GameCube disc. The Steam Deck runs the Linux x86_64 build.

That’s the headline. The rest of this page explains what makes it different from an emulator, where it came from, and why it’s a milestone for fan ports of Nintendo games.

How Dusk Works (Decomp + Port)

Three categories often get confused. Let’s separate them clearly.

It’s not an emulator

Emulators like Dolphin simulate the original GameCube hardware in software. They take the original game’s binary and translate it instruction-by-instruction at runtime. This works, but it’s heavy: you’re effectively running a GameCube CPU and GPU on top of your own CPU and GPU.

Dusk is different. Dusk is the game itself, rebuilt as a Windows / Mac / Linux / phone application. There is no GameCube CPU being simulated. The code that draws Hyrule, animates Link, and handles physics has been compiled directly for your machine. That’s why it runs smoothly on phones and on a Steam Deck — work that emulators struggle with.

It’s not a ROM hack

ROM hacks modify the original ROM and play it through an emulator. Dusk doesn’t modify the ROM; it doesn’t even contain the ROM. The ROM is a separate file you supply.

What Dusk contains is the entire source code of Twilight Princess, hand-rewritten in C++, recompiled into platform-native binaries.

It’s the original game, rebuilt as native code

The cleanest analogy: imagine someone took the original Twilight Princess, rewrote it in modern code without changing any gameplay, then released that rewrite as a normal app. That’s what Dusk is.

This kind of project is called a port in the loose sense, or more specifically a decomp-based reimplementation. It’s the same category as Ship of Harkinian (Ocarina of Time) or 2 Ship 2 Harkinian (Majora’s Mask) — both built on similar decompilation projects.

Where It Came From

The 5+ year zeldaret/tp decompilation

You can’t have a native port until you have the source code, and Nintendo never released Twilight Princess’s source. So a community of reverse-engineers spent 5 years and 9 months reconstructing it.

The project — zeldaret/tp on GitHub — started in August 2020. Hundreds of contributors over the years hand-rewrote C++ code that, when compiled with the original GameCube toolchain, produces a binary byte-identical to the retail disc.

By December 2025, all GameCube versions (NA, EU, Japan) reached 100% byte-matching. That was the milestone that made Dusk possible.

For the full story, read How Twilight Princess Got Decompiled (2020–2026).

The Aurora framework

Decompiled source code by itself can’t run on Windows or your phone — it’s still GameCube source code, written for GameCube hardware. To run it elsewhere, you need a portability layer that translates GameCube graphics calls, audio, and controller input into something modern platforms understand.

That’s what Aurora does. It’s a cross-platform framework whose maintainers contributed to Dusk. Aurora is to Dusk what LibSDL is to many indie games: the layer that lets one codebase target many platforms.

TP’s 20th birthday timing

This is not an accident. Twilight Princess originally launched in November 2006. Releasing Dusk in May 2026 sets up a celebration window leading to the 20th anniversary in November 2026. The TwilitRealm announcement explicitly framed v1.0.0 as “Happy (early) 20th birthday to Twilight Princess!”

Expect texture packs, mods, and content updates to align with the anniversary.

Why It’s a Big Deal

First native (no emulator) Twilight Princess on PC

Before Dusk, playing TP on PC meant Dolphin. Dolphin is excellent, but it has limits: heavy CPU use, framerate issues tied to GameCube’s 30 Hz timing, no clean mobile story.

Dusk is the first native option. It runs at full speed on hardware that struggles to emulate the GameCube. It supports framerates the original engine can’t natively reach. It runs on phones.

5 platform families day one

Most fan ports launch on Windows first, then maybe Linux a year later, then maybe a community-maintained Mac build, and never mobile. Dusk launched on Windows, macOS, Linux (incl. Steam Deck), iOS, and Android simultaneously. This is unusual to the point of being a flex.

CC0 license — public domain dedication

Dusk’s code is dedicated to the public domain under CC0-1.0. This means anyone can fork, modify, redistribute, or even sell derivatives without restriction. The TwilitRealm team made an explicit choice to ensure the project outlives them: even if the original team disappears, the code is permanently free.

This is significantly more permissive than most open-source licenses (MIT, GPL, etc.).

The short answer: yes, with one caveat.

The decomp itself ships no Nintendo assets

The zeldaret/tp source code contains zero Nintendo assets. No textures, no audio, no models, no level data. It’s only the code — and that code was hand-rewritten by humans, not copied. Nintendo’s copyright covers the original disc; it does not extend to a clean-room reimplementation written from scratch.

This is established legal precedent. The Mario 64 PC port, Ship of Harkinian, the OOT/MM decomps — all use the same approach. Nintendo has filed DMCAs against ROM distribution, but never successfully against clean-room decomps that ship no assets.

You must dump your own disc

Dusk requires you to provide your own GameCube Twilight Princess disc image. SHA-1 verification means a dump from a real retail disc you own. This is the legal trick that makes the whole thing work: you own the original game, you’re allowed to make a personal backup, and you can run that backup through any program you choose.

Dusk does not and will not provide ROMs.

Why this passes

The legal logic is:

  1. Reverse-engineering for interoperability is protected (Sega v. Accolade, 1992).
  2. Personal backups of media you own are protected (varying jurisdictions, but generally accepted in DMCA-exemption rulings).
  3. Code that doesn’t copy any of Nintendo’s actual code or assets cannot infringe their copyright.

Dusk satisfies all three.

For a deeper legal explainer, see Are decomp ports legal? (coming soon).

How to Get Dusk Today

If you’re sold:

  1. Read the Pillar guide — full feature breakdown
  2. Pick your platform — 6 platform-specific install guides
  3. Dump your disc legally — required first step

You’ll be playing within 30 minutes.

Dusk vs the Other “Dusk”

Quick disambiguation, because Google has been mixing these up:

Dusk (Twilight Princess port)DUSK (the FPS)
MakerTwilitRealm (2026)New Blood Interactive (2018)
TypeNative port of Zelda TPOriginal retro-FPS
GenreAction-adventureFirst-person shooter
Runs onWin/Mac/Linux/Deck/iOS/AndroidWin/Mac/Linux/Switch/PS5/Xbox
LicenseFree, open source (CC0)Commercial ($20 on Steam)

If you’re searching for the Zelda port, add “twilight princess” or “TwilitRealm” to disambiguate. Searching just “Dusk” in 2026 still mostly returns the FPS, because it’s been around longer and has more SEO weight.

That ambiguity will probably resolve in a few months as Dusk-the-port accumulates coverage. For now, search smarter.

Where to Go Next

Last updated: 2026-05-10.

← Pillar guide · Decomp explained →