DuckStation Android Emulator Adds Multi-Threaded Shader And Pipeline Compilation In New Preview Builds
Saturday, September 19, 2026By Indie Kings | September 18, 2026
Updated September 18, 2026: DuckStation, the PlayStation 1 emulator for Android, can now compile shaders and graphics pipelines across multiple CPU threads. The new Preview builds aim to cut the time spent building shader caches instead of raising frame rates, per VideoCardz.
DuckStation's latest Preview builds ship a graphics-heavy update. The emulator now spreads shader and pipeline compilation across CPU cores, and it reworks the shader cache with a UID-based lookup system, per VideoCardz on September 17.
Table of Contents
- What Changed In The Update
- Which Graphics Backends Are Covered
- The Reworked Shader Cache
- What This Means For Players
- FAQ
- Bottom Line
What Changed In The Update
The biggest change is multi-threaded shader compilation. DuckStation can now send shader cache misses to its asynchronous task system instead of compiling everything in sequence, per VideoCardz.
The same approach was later added to graphics pipeline creation. Together, both changes let Android devices with multiple CPU cores build the graphics state faster when the emulator hits something that is not already cached.
- Multi-threaded shader compilation.
- Multi-threaded graphics pipeline creation.
- Reworked shader cache with a UID-based lookup system.
- Enabled on Direct3D 11, Direct3D 12, Vulkan, and Metal.
Which Graphics Backends Are Covered
Not every backend gets the new path. The multi-threaded compilation is enabled for four of DuckStation's renderers.
| Backend | Multi-threaded compilation |
|---|---|
| Direct3D 11 | Enabled |
| Direct3D 12 | Enabled |
| Vulkan | Enabled |
| Metal | Enabled |
| OpenGL | Excluded |
OpenGL is excluded because DuckStation does not mark shader compilation through that backend as thread-safe, per VideoCardz. Android users who run the OpenGL renderer will not see the new compilation path.
The Reworked Shader Cache
The update also changes how DuckStation stores and looks up cached shaders. A UID-based lookup system replaces the older approach, which should make cache hits faster to find after a game has been compiled once.
These changes are not aimed at raising emulation frame rates, per VideoCardz. Instead, they reduce the time spent compiling shaders and pipelines when DuckStation encounters content it has not prepared yet.
What This Means For Players
The difference shows up most after changing graphics settings, clearing the shader cache, or running configurations where many shaders have to be prepared at once. Those moments should now take less wall-clock time on multi-core phones and tablets.
DuckStation already runs the vast majority of the PS1 library at full speed on modern Android hardware, so this update targets polish around stutter and loading windows rather than raw performance. The changes are in the Preview channel, per VideoCardz.
FAQ
Does the DuckStation update make PS1 games run faster?
Not directly. The multi-threaded shader and pipeline compilation cuts the time spent preparing shaders, rather than raising in-game frame rates.
Which graphics backends support the new compilation?
Direct3D 11, Direct3D 12, Vulkan, and Metal. OpenGL is excluded because DuckStation does not treat its shader compilation as thread-safe.
When will I notice the difference?
Mostly after changing graphics settings, clearing the shader cache, or playing a title that needs many shaders prepared at once.
Is the update in the stable version of DuckStation?
No, it is in the latest Preview builds, per VideoCardz.
Does it work on older Android devices?
It helps most on devices with multiple CPU cores, since the new path distributes compilation work across threads.
Does this affect DuckStation on PC?
The multi-threaded compilation applies to supported backends broadly, and the same build infrastructure covers desktop Android emulation environments where DuckStation runs.
Bottom Line
DuckStation's Preview update is a quality-of-life win for PS1 emulation on Android. Multi-threaded shader and pipeline compilation shortens the hitches that happen when new shaders need building, and the UID-based cache makes repeat runs cleaner. It does not chase higher FPS, which the emulator mostly does not need on current hardware.