Skip to content

Download

Pick your OS.

Each shortcut opens the project’s GitHub releases—we don’t host files or mirrors here.

Download now

Stable builds for daily play · nightlies when you need a specific fix.

Trusted source. Grab PCSX2 from the project’s GitHub releases (or follow the checklist on this page). Avoid “PCSX2 + emulator pack” sites that wrap the binary in installers with unrelated software.

Checksums. When the release notes publish hashes, verify them after download—especially if you fetched the file through a VPN, corporate proxy, or mirror.

Stable vs nightly. Stable tracks tested releases. Nightly (or PR) builds can fix a game you care about but may also introduce regressions; keep a known-good stable installer handy.

PCSX2 download and PlayStation 2 emulation banner

After you download

You’ll need a legal BIOS dump from your own console for most retail games, then a clean folder or ISO for each title. Our Setup page orders those steps the same way forum helpers expect.

Linux notes

AppImage is a common zero-install path; distro packages may lag behind upstream. If you use Flatpak or similar, confirm you’re pulling from a maintainer you trust and that updates track security fixes.

Windows: installer vs portable

The installer registers shortcuts and is familiar to most users. A portable folder is handy when you want the emulator, memcards, and settings on one drive—just back up the whole directory before major upgrades.

Install or extract to a path you control (not a random temp folder) so antivirus quarantine does not silently delete DLLs.

Verifying what you downloaded

When release notes publish SHA-256 or other hashes, compare after download—especially on laptops that sleep mid-download or on metered connections that retry partial files.

File names should match the asset list on the official releases page; unexpected double extensions (.exe.exe) are a red flag.

Stable, nightly, and PR builds—what people mean

  • Stable — tagged releases the project expects most players to run; best match for guides and screenshots.
  • Nightly / CI — fresher code; great when release notes or issues mention your exact bug, but expect occasional regressions.
  • Pull-request artifacts — experimental; only grab these when a developer links them for a specific test matrix.

macOS notes

Apple Silicon vs Intel matters for which build you pick. Gatekeeper may prompt the first launch—if you did not sideload from a sketchy mirror, approving the official binary is normal. See upstream docs for the current Metal-focused guidance.

Linux notes

AppImage keeps dependencies predictable; distro packages can lag. Ensure 64-bit userspace, working Vulkan drivers for your GPU vendor, and that your user can access /dev/input devices for pads.

After download (reminder)

You still need a legal BIOS for most retail games, clean game dumps, and a few minutes in settings—walk through Setup in order so you do not skip the memcard format step or point the game list at an empty folder.

More on this site: Setup · FAQ · Support