Discord Server: https://discord.gg/Buktv3t
Latest Builds for Windows and Linux (AppImage) https://github.com/stenzek/duckstation/releases/tag/latest
Available on Google Play: https://play.google.com/store/apps/details?id=com.github.stenzek.duckstation
Game Compatibility List: https://docs.google.com/spreadsheets/d/1H66MxViRjjE5f8hOl5RQmF5woS1murio2dsLn14kEqo/edit
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 "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.
Older entries are available at https://github.com/stenzek/duckstation/blob/master/NEWS.md
DuckStation features a fully-featured frontend built using Qt, as well as a fullscreen/TV UI based on Dear ImGui. An Android version has been started, but is not yet feature complete.
Other features include:
Binaries of DuckStation for Windows x64/ARM64, Linux x86_64 (in AppImage format), and Android ARMv7/ARMv8 are available via GitHub Releases and are automatically built with every commit/push. Binaries or packages distributed through other sources may be out of date and are not supported by the developer, please speak to them for support, not us.
Windows 10 is the only version of Windows supported by the developer. Windows 7/8 may work, but is not supported. I am aware some users are still using Windows 7, but it is no longer supported by Microsoft and too much effort to get running on modern hardware. Game bugs are unlikely to be affected by the operating system, however performance issues should be verified on Windows 10 before reporting.
Once downloaded and extracted, you can launch the emulator with
To set up:
C:\Users\YOUR_USERNAME\Documents\DuckStation\bios. If you don't want to use the Documents directory to save the BIOS/memory cards/etc, you can use portable mode. See User directory.
Settings->Add Game Directory.
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://support.microsoft.com/en-au/help/2977003/the-latest-supported-visual-c-downloads. Specifically, you want the x64 runtime, which can be downloaded from https://aka.ms/vs/16/release/vc_redist.x64.exe.
Windows 7 users, TLS 1.2 is not supported by default and you will not be able to use the automatic updater or RetroAchievements. This knowledge base article contains instructions for enabling TLS 1.1/1.2: https://support.microsoft.com/en-us/topic/update-to-enable-tls-1-1-and-tls-1-2-as-default-secure-protocols-in-winhttp-in-windows-c4bd73d2-31d7-761e-0178-11268bb10392
The Qt frontend includes an automatic update checker. Builds downloaded after 2020/08/07 will automatically check for updates each time the emulator starts, this can be disabled in Settings. Alternatively, you can force an update check by clicking
Help->Check for Updates.
The DuckStation fullscreen UI is available for the Universal Windows Platform and Xbox One.
To use on Xbox One:
Change Viewbutton, select
View Details, and change
Change Viewbutton will open the quick menu.
NOTE: I'd recommend using a USB drive for saving memory cards, as the local state directory will be removed when you uninstall the app.
DuckStation does support Linux, but no support will be provided by the developer due to the huge range and variance of distributions. AppImage builds are provided, but we are not obliged to provide any assistance or investigate any issues, i.e. use at your own risk. However, these binaries may be incompatible with older Linux distros (e.g. Ubuntu distros earlier than 20.04 LTS) due to older distros not providing newer versions of the C/C++ standard libraries required by the AppImage binaries. If you are using a packaged version of DuckStation from another source, please do not ask us for assistance and speak to your packager instead.
Linux users are encouraged to build from source when possible and optionally create their own AppImages for features such as desktop integration if desired.
duckstation-nogui-x64.AppImagefor your desired frontend.
chmod a+xon the downloaded AppImage -- following this step, the AppImage can be run like a typical executable.
MacOS builds are no longer provided, as I cannot support a platform which I do not own hardware for, and I'm not spending $1000+ out of my own pocket for a machine which I have no other use for.
You can still build from source, but you will have to debug any issues encountered yourself.
If anyone is willing to volunteer to support the platform to ensure users have a good experience, I'm more than happy to re-enable the releases.
A prebuilt APK is now available for Android. 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 link: https://www.duckstation.org/android/duckstation-android.apk
Preview/beta download link: https://www.duckstation.org/android/duckstation-android-beta.apk
Changelog link: https://www.duckstation.org/android/changelog.txt
If you have an external controller, you will need to map the buttons and sticks in settings.
DuckStation is available as a libretro core, which can be loaded into a frontend such as RetroArch. It supports most features of the full frontend, within the constraints and limitations of being a libretro core.
The DuckStation libretro core is not covered by the GPL license, but is still completely free to use. The only restriction is that COMMERCIAL DISTRIBUTION IS PROHIBITED. By downloading the libretro core, you agree that you will not distribute it with any paid applications, services, or products.
The core is maintained by a third party, and is not provided as part of the GitHub release. You can download the core through the RetroArch buildbot/core updater, or from the links below. The changelog is viewable at https://www.duckstation.org/libretro/changelog.txt
By default, DuckStation will emulate the region check present in the CD-ROM controller of the console. This means that when the region of the console does not match the disc, it will refuse to boot, giving a "Please insert PlayStation CD-ROM" message. DuckStation supports automatic detection disc regions, and if you set the console region to auto-detect as well, this should never be a problem.
If you wish to use auto-detection, you do not need to change the BIOS path each time you switch regions. Simply place the BIOS images for the other regions in the same directory as the configured image. This will probably be in the
bios/ subdirectory. Then set the console region to "Auto-Detect", and everything should work fine. The console/log will tell you if you are missing the image for the disc's region.
Some users have been confused by the "BIOS Path" option, the reason it is a path and not a directory is so that an unknown BIOS revision can be used/tested.
Alternatively, the region checking can be disabled in the console options tab. This is the only way to play unlicensed games or homebrew which does not supply a correct region string on the disc, aside from using fastboot which skips the check entirely.
Mismatching the disc and console regions with the check disabled is supported, but may break games if they are patching the BIOS and expecting specific content.
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
git clone --recursive https://github.com/stenzek/duckstation.git -b dev).
duckstation.slnin the root, or "Open Folder" for cmake build.
duckstation-qt-x64-Release.exeor whichever config you used.
Requirements (Debian/Ubuntu package names):
git) (Note: needed to clone the repository and at build time)
git clone https://github.com/stenzek/duckstation.git -b dev).
cd build-release && cmake -DCMAKE_BUILD_TYPE=Release -GNinja ...
NOTE: macOS is highly experimental and not tested by the developer. Use at your own risk, things may be horribly broken.
brew install cmake)
brew install sdl2)
brew install qt5)
git clone https://github.com/stenzek/duckstation.git -b dev).
git clone https://github.com/stenzek/duckstation-ext-mac.git dep/mac.
cmake -DCMAKE_BUILD_TYPE=Release -DBUILD_NOGUI_FRONTEND=OFF -DBUILD_QT_FRONTEND=ON -DUSE_SDL2=ON -DQt5_DIR=/usr/local/opt/[email protected]/lib/cmake/Qt5 ... You may need to tweak
Qt5_DIRdepending on your system.
Nis the number of CPU cores in your system for a faster build.
The "User Directory" is where you should place your BIOS images, where settings are saved to, and memory cards/save states are saved by default. An optional SDL game controller database file can be also placed here.
This is located in the following places depending on the platform you're using:
So, if you were using Linux, you would place your BIOS images in
~/.local/share/duckstation/bios. This directory will be created upon running DuckStation
for the first time.
If you wish to use a "portable" build, where the user directory is the same as where the executable is located, create an empty file named
in the same directory as the DuckStation executable.
Your keyboard or game controller can be used to simulate a variety of PlayStation controllers. Controller input is supported through DInput, XInput, and SDL backends and can be changed through
Settings -> General Settings.
To bind your input device, go to
Settings -> Controller Settings. Each of the buttons/axes for the simulated controller will be listed, alongside the corresponding key/button on your device that it is currently bound to. To rebind, click the box next to the button/axis name, and press the key or button on your input device that you wish to bind to. When binding rumble, simply press any button on the controller you wish to send rumble to.
DuckStation releases ship with a database of game controller mappings for the SDL controller backend, courtesy of https://github.com/gabomdq/SDL_GameControllerDB. The included
gamecontrollerdb.txt file can be found in the
database subdirectory of the DuckStation program directory.
If you are experiencing issues binding your controller with the SDL controller backend, you may need to add a custom mapping to the database file. Make a copy of
gamecontrollerdb.txt and place it in your user directory (or directly in the program directory, if running in portable mode) and then follow the instructions in the SDL_GameControllerDB repository for creating a new mapping. Add this mapping to the new copy of
gamecontrollerdb.txt and your controller should then be recognized properly.
Icon by icons8: https://icons8.com/icon/74847/platforms.undefined.short-title
"PlayStation" and "PSX" are registered trademarks of Sony Interactive Entertainment Europe Limited. This project is not affiliated in any way with Sony Interactive Entertainment.