Fast PlayStation 1 emulator for x86-64/AArch32/AArch64/RV64
Fast PlayStation 1 emulator for x86-64/AArch32/AArch64/RV64
Features | Downloading and Running | Building | Disclaimers
Latest Builds for Windows 10/11 (x64/ARM64), Linux (AppImage x64/ARM32/ARM64), and macOS (13.3+ Universal): https://github.com/stenzek/duckstation/releases/tag/latest
Discord Server: https://www.duckstation.org/discord.html
DuckStation is an simulator/emulator of the Sony PlayStation(TM) console, focusing on playability, speed, and long-term maintainability. The goal is to be as accurate as possible while maintaining performance suitable for low-end devices. "Hack" options are discouraged, the default configuration should support all playable games with only some of the enhancements having compatibility issues.
A PS1 or PS2 "BIOS" ROM image is required to to start the emulator and to play games. You can use an image from any hardware version or region, although mismatching game regions and BIOS regions may have compatibility issues. A ROM image is not provided with the emulator for legal reasons, you should dump this from your own console using Caetla or other means.
DuckStation features a fully-featured frontend built using Qt, as well as a fullscreen/TV UI based on Dear ImGui.
Other features include:
Binaries of DuckStation for Windows x64/ARM64, Linux x86_64/ARM32/ARM64 (in AppImage format), and macOS Universal Binaries are available via GitHub Releases and are automatically built with every commit/push.
As per the terms of CC-BY-NC-ND, redistribution of unmodified releases and code is permitted. However, we would prefer if you linked to https://www.duckstation.org/ instead. Please note that pre-configured settings and packages are considered modifications.
For x86 machines (most systems), you will need a CPU that supports the SSE4.1 instruction set for the "normal" build. This includes all Intel CPUs manufactured after 2007, and AMD CPUs manufactured after 2011. If you have a CPU that is older, you will need to download the "SSE2" build from the releases page, which has lower performance but still supports these CPUs.
The main releases page is limited to the last 30 releases due to automatic updater limitations. Older releases can be downloaded from https://github.com/duckstation/old-releases/releases.
The automatic updater in DuckStation has two channels: "Stable" and "Preview".
By default, the updater will track the channel you downloaded from. You can change the channel in Settings -> Interface -> Updates.
DuckStation requires Windows 10/11, specifically version 1809 or newer. If you are still using Windows 7/8/8.1, DuckStation will not run on your operating system. Running these operating systems in 2026 should be considered a security risk, and I would recommend updating to something which receives vendor support. If you must use an older operating system, v0.1-5624 is the last version which will run. But do not expect to receive any assistance, these builds are no longer supported.
Windows builds are provided in two formats:
To use the installer, simply download the installer from the releases page, run it, and follow the prompts.
The installer is still a new addition, so if you encounter issues please let us know via Discord.
To use the archive or portable installation, follow these steps:
duckstation-windows-arm64-release.zip instead.portable.txt in the same directory as the executable.duckstation-qt-x64-ReleaseLTCG.exe. Follow the Setup Wizard to get started.If you get an error about vcruntime140_1.dll being missing, you will need to update your Visual C++ runtime. You can do that from this page: https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist. Specifically, you want the x64 runtime, which can be downloaded from https://aka.ms/vs/17/release/vc_redist.x64.exe.
DuckStation is provided for x86_64/ARM32/ARM64 Linux in AppImage formats.
The AppImages require a distribution equivalent to Ubuntu 22.04 or newer to run.
DuckStation-arm64.AppImage.chmod a+x on the downloaded AppImage -- following this step, the AppImage can be run like a typical executable. Alternatively, in your file manager of choice, enable execute permissions via the file properties dialog.If you were previously using the Flatpak package, to migrate your data from the Flatpak to the AppImage, you can run the following command:
mv ~/.var/app/org.duckstation.DuckStation/config/duckstation ~/.local/shareYou will need to re-add your game directories after switching to the AppImage.
Universal macOS builds are provided for both x86_64 (Intel) and ARM64 (Apple Silicon).
macOS Ventura (13.3) is required, as this is also the minimum requirement for Qt.
To download:
DuckStation.app, optionally moving it to your desired location first.If you receive a message about the app being from an unidentified developer:
Unfortunately this is required as Apple requires code signing for apps to be run without warnings, and I do not have a code signing certificate since a yearly cost is out of the question for a project which brings in zero revenue.
You will need a device with armv7 (32-bit ARM), AArch64 (64-bit ARM), or x86_64 (64-bit x86). 64-bit is preferred, the requirements are higher for 32-bit, you'll probably want at least a 1.5GHz CPU.
Download from Google Play: https://play.google.com/store/apps/details?id=com.github.stenzek.duckstation
No support is provided for the Android app, it is free and your expectations should be in line with that. Please do not email me about issues about it, or ask for help, you will be ignored.
To use:
If you have an external controller, you will need to map the buttons and sticks in settings.
A number of PAL region games use LibCrypt protection, requiring additional CD subchannel information to run properly. libcrypt not functioning usually manifests as hanging or crashing, but can sometimes affect gameplay too, depending on how the game implemented it.
For these games, make sure that the CD image and its corresponding SBI (.sbi) file have the same name and are placed in the same directory. DuckStation will automatically load the SBI file when it is found next to the CD image.
For example, if your disc image was named Spyro3.cue, you would place the SBI file in the same directory, and name it Spyro3.sbi.
CHD images with built-in subchannel information are also supported.
If you are playing directly from a disc and your
No open issues yet, or sync has not completed.