Open-source project
stenzek/duckstation avatar
stenzek/duckstation

DuckStation needs your own BIOS dump and an SSE4.1 CPU, or the slower fallback build

Fast PlayStation 1 emulator for x86-64/AArch32/AArch64/RV64

11,015 stars992 forksC++NOASSERTION

At a glance

What is it?
A PlayStation emulator written in C++ with a JIT recompiler for four CPU families and hardware renderers spanning D3D11, D3D12, OpenGL, Vulkan and Metal. It is not a turnkey download: you supply the BIOS, you match the instruction set of your CPU to the right build, and you choose whether the updater tracks a tested channel or one compiled from every commit.
Who is it for?
Pick DuckStation if you own a PlayStation, can dump its BIOS, and want an emulator whose stated goal is accuracy without hack options. Steer away if you need an Android build, a Windows 7 machine, or permission to ship a preconfigured setup to other people, since none of those are on offer.
Can I use it commercially?
Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
Is it still maintained?
Yes. The repository received new commits within the last day.
What is it written in?
Mainly C++, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • stenzek/duckstation11,015 ★ · +289
Star history
Repository2026-09-222026-11-15
stenzek/duckstation10.7k11k

289 Stars in the last 54 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

No BIOS image is bundled, so the emulator cannot start until you dump one

The first thing DuckStation asks for is a file it deliberately refuses to ship. A PS1 or PS2 BIOS ROM image is required both to start the emulator and to play games, and no ROM image comes with it for legal reasons; the stated route is to dump it from your own console using Caetla or other means. That makes the dump the first thing every user does and the first thing that goes wrong. Any hardware version or region is accepted, which sounds forgiving until you read the next clause: mismatching game regions and BIOS regions may cause compatibility issues. So a working dump is not the same as a correct dump.. There is no way to evaluate this project at all before you have that file.

SSE4.1 decides which build you run, and the fallback is slower by design

The releases carry more than one binary for the same emulator. On x86 machines the normal build wants a CPU with the SSE4.1 instruction set, which the project equates to every Intel part made after 2007 and every AMD part made after 2011. Older processors are not abandoned, they are served by a separate SSE2 build pulled from the same releases page, and the trade is stated plainly: lower performance on hardware that could not run the normal build. The rest of the floor is spelled out the same way. The CPU must be x86-64, AArch32 or armv7, AArch64 or ARMv8, or RISC-V RV64. The GPU needs OpenGL 3.1, OpenGL ES 3.1, Direct3D 11 Feature Level 10.0, or Vulkan 1.0. Input has to be SDL, XInput or DInput compatible, and DualShock 3 pads on Windows need the official drivers bundled with PlayStation Now.

Windows 7 and 8 are locked out entirely, and the last build that fits is unsupported

The Windows requirement is a hard floor, not a recommendation. DuckStation requires Windows 10 or 11, specifically version 1809 or newer, and it will not run on Windows 7, 8 or 8.1 at all. The reasoning offered is a security one, that running those releases should be treated as a risk and the advice is to move to something a vendor still supports. For anyone who cannot move, the project names the exact escape hatch: v0.1-5624 is the last version that will run on those systems, reachable through the old releases repository. The caveats attached to it are as firm as the door itself. Do not expect assistance with those builds, and they are no longer supported. For an old machine that will never be upgraded, that means running a frozen build with an abandoned updater, which is the security posture the project just argued against. Windows users also pick between an installer that extracts to a user-local programs directory and creates optional Start Menu and Desktop shortcuts, or a zip archive for a portable setup.

The updater tracks either the tested channel or one built from every commit

Automatic updates come in two flavours, and the difference is how much testing stands behind the binary. Stable releases are less frequent and track the latest release on GitHub, and they are the ones described as having had more testing. Preview releases are built whenever a commit lands on the repository, track the GitHub pre-release, and are described as containing builds that have had minimal testing and may carry bugs or issues. The updater defaults to whichever channel you downloaded from, and the channel can be changed under Settings, Interface, Updates. Pick that default carelessly on a machine you rely on and you have opted into untested code without ever making a choice. There is a second ceiling worth knowing: the main releases page keeps only the last 30 releases because of automatic updater limitations, and anything older has to come from the separate old-releases repository. Recent tags follow the same rolling pattern, with a latest rolling release and a preview build alongside numbered versions such as v0.1-12083.

Preloading disc images to RAM trades memory for the disc sleeping mid-frame

The disc handling is the part that tells you what the author thinks emulation is for. DuckStation reads straight from CD as well as from bin/cue images, MAME CHD, single-track ECM, MDS/MDF, CCD, and unencrypted PBP formats, and it can preload a disc image into RAM specifically to avoid disk sleeping hitches. That is a memory versus consistency trade and it is the right one for a machine that spins down an idle drive mid cutscene. Note the qualifier on PBP: unencrypted formats only. Multi-disc games are merged in the list and grid views with a shared memory card between discs, and PPF patches are detected and applied automatically, so the messy parts of a retail disc release are handled for you rather than asked of you. What none of this changes is the requirement from the first section. Format coverage is broad, and it is still unreachable without a BIOS you dumped yourself.

Two interfaces, per-game settings, and a controller port for eight devices

The frontend is doubled by design. DuckStation ships a fully featured Qt interface and a separate fullscreen TV interface built on Dear ImGui, which is what you get on a television or handheld rather than a desktop. Configuration follows the game rather than the install, through controller presets and per-game configuration, and memory cards can be switched automatically for each game so a two disc title does not reuse the wrong save. Hardware coverage is generous: multitap support covers up to eight devices, GunCon and Justifier lightguns are simulated with the mouse, NeGcon pads are handled, and rumble is forwarded to the host controller. Vertical and TATE shoot em games get screen rotation, audio is time stretched when you are not at 100 percent speed, and fast boot skips the BIOS splash. The cost of this density is discoverability.

Hack options are discouraged, so some enhancements break compatibility by definition

The stated philosophy is accuracy, and it has a cost that shows up in game behaviour. The goal is to be as accurate as possible while keeping performance suitable for low-end devices, and hack options are explicitly discouraged, with the expectation that the default configuration supports all playable games and that only some of the enhancements carry compatibility issues. That is a narrower promise than any game running everywhere.. The accuracy work is visible in the renderer: PGXP for geometry precision, texture correction and depth buffer emulation, and accurate blending through Rasterizer Order Views or Fragment Shader Interlock, on top of a hardware renderer offering true 24-bit colour, upscaling and texture filtering, or a vectorized multi-threaded software renderer for machines without a usable GPU path.

Redistribution covers unmodified releases only, and preconfigured settings count as a modification

The licensing position is narrower than the open source framing around the project suggests. Redistributing unmodified releases and code is permitted under the terms cited as CC-BY-NC-ND, with a preference stated that people link to the project site instead, and one line does the real work: pre-configured settings and packages are considered modifications. So the binary can circulate, and a copy with your settings baked in cannot. For anyone building a themed package, a starter configuration or a hand-off image for another person, that is the dividing line, and the non-commercial and no-derivatives clauses sit behind it as well. The repository metadata does not resolve this to a single identifier, which means the licensing question is answered by the statement rather than by a machine readable licence file. On the maintenance side the picture is clear enough: the last push is dated 2026-11-02 and binaries are built automatically with every commit and push, including the macOS 13.3 and newer universal builds.

Editorial conclusion

Pick DuckStation if you own a PlayStation, can dump its BIOS, and want an emulator whose stated goal is accuracy without hack options. Steer away if you need an Android build, a Windows 7 machine, or permission to ship a preconfigured setup to other people, since none of those are on offer. Before the first launch, confirm your CPU supports SSE4.1 so you do not land on the slower build, read the region notes against your BIOS dump, and decide deliberately whether the updater should follow the tested channel or the per-commit one.

Frequently asked questions

Is DuckStation a PS1 or PS2 emulator?

It simulates the Sony PlayStation console and calls itself a PlayStation 1 emulator. A PS1 or PS2 BIOS ROM image is required to start it, and you can use an image from any hardware version or region.

Is using DuckStation legal?

No ROM image is provided with the emulator for legal reasons. The stated route is to dump the BIOS from your own console using Caetla or other means.

Is DuckStation discontinued?

Binaries are automatically built with every commit and push, and the releases carry a latest rolling release plus a preview build. The last push is dated 2026-11-02.

how to use duckstation without bios

There is no way to do so. A BIOS ROM image is required to start the emulator and to play games, and the emulator will not run without one.

how to install duckstation on pc

Windows builds come as an installer that extracts to a user-local programs directory with optional shortcuts, or as a zip archive for a portable setup. Binaries also exist for Linux as an AppImage and for macOS 13.3 and newer as universal builds, all via GitHub Releases.

Official sources

  1. Issues
  2. README
  3. Releases
  4. stenzek/duckstation on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/stenzek-duckstation.svg)](https://hysenlabs.com/projects/stenzek-duckstation)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/stenzek-duckstation.svg)](https://hysenlabs.com/projects/stenzek-duckstation)

Was this useful?