Three PlayStation 1 emulators are still fighting for a spot on your PC, phone, or Steam Deck in October 2026, and they are not converging toward one winner. DuckStation ships a new build almost every time its lone maintainer pushes a commit. ePSXe keeps a separate, slower-moving Android app alive alongside its older PC build. RetroArch, through its Beetle PSX HW core, treats the PS1 as one of more than 200 systems it can load rather than a dedicated product. Picking between them is less about which emulator is “best” and more about which release model, platform list, and BIOS workflow fits how you actually play.
This comparison breaks down the current state of all three: GitHub’s DuckStation preview channel, which shipped a build dated October 15, 2026, ePSXe’s Android 2.0.19 release from May 2026 (with a Play Store bump on July 10), and the Beetle PSX HW core documented by Libretro’s own core library. We cover specs, rendering backends, BIOS handling, pricing, five real-world use cases, a migration path between the three, and a verdict backed by the data in the tables below.
Don't miss new tech stories on Google
Add Tech Insider once in the Google app and our stories appear in your news suggestions.
Why PS1 Emulation Still Matters in 2026
The original PlayStation library is three decades old, but interest in playing it accurately has not faded. DuckStation alone pulls roughly 18,100 monthly searches in the US, and “ps1 emulator” adds another 8,100, according to keyword-volume data gathered for this piece. That volume outpaces plenty of modern console topics, and it reflects a simple reality: PS1 games are small, run on almost any hardware built in the last decade, and are frequently the easiest way to replay a childhood library without digging out a CRT and a memory card.
What changed is not the games, it is the tooling around them. DuckStation has become the default recommendation in most 2026 setup guides, including the official DuckStation setup walkthrough on this site, because it ships continuous builds and runs natively on Steam Deck. ePSXe, once the standard choice in the 2000s, now survives mostly as a paid-feeling Android app with periodic updates. RetroArch never tried to be a PS1 specialist at all. It is a frontend, and Beetle PSX HW is just one of the cores it can load, which changes the entire value proposition.
Part of what makes this three-way comparison worth revisiting right now is timing. All three projects pushed meaningful updates inside the same rough window this year: DuckStation’s rolling builds in October, ePSXe’s Android refresh in May with a Play Store bump in July, and the Beetle PSX HW core profile dated late March. That is unusual. PS1 emulation tends to go quiet for long stretches once a project reaches “good enough,” so three active update cycles landing in the same year is a reasonable signal that none of these projects has been abandoned, even if their pace differs wildly.
What Is DuckStation?
DuckStation is a standalone PlayStation 1 emulator written in C++ by developer Connor McLaughlin, who goes by “stenzek” on GitHub. It uses a JIT recompiler that targets four CPU families, and it ships hardware renderers covering Direct3D 11, Direct3D 12, OpenGL, Vulkan, and Metal, according to the project’s own repository documentation. That breadth of rendering backends is unusual for a single-system emulator and is part of why DuckStation runs well on everything from an aging Windows laptop to an Apple Silicon Mac to a Steam Deck.
The release model is the most distinctive thing about the project. Instead of quarterly or yearly version numbers, DuckStation’s GitHub releases page builds automatically on every commit and push. The repository’s “latest” tag pointed to a build dated October 13, 2026, while a separate preview build landed October 15, 2026 under commit 00e2997. That is a two-day gap between two different release channels, which is a pace no other PS1 emulator in this comparison comes close to matching.
DuckStation supports Windows, Linux, macOS (with universal builds), Android, and Steam Deck/SteamOS. It is free to download, and because the source lives on GitHub under stenzek’s account, technically inclined users can build it themselves. The project’s exact licensing terms are not auto-classified by GitHub, so anyone planning commercial use should read the repository’s LICENSE file directly rather than assume a specific open-source license applies.
What Is ePSXe?
ePSXe is the oldest name in this comparison. It built its reputation in the early 2000s as one of the first PS1 emulators accurate enough for mainstream use, and it still exists today in two separate forms: a PC build and a dedicated Android app. The official ePSXe for Android changelog lists version 2.0.19 as its most recent update, released in May 2026, with the Google Play listing showing a further store-side update on July 10, 2026.
That May 2026 update added an Oboe sound engine option for lower audio latency, improved CHD disc-image support, Dropbox and Google Drive integration for cloud-synced saves, updated shader handling, and support for Android SDK 35. Per the Google Play listing, the Android app supports virtual touchscreen controls, hardware button mapping for devices like the Xperia Play, and Bluetooth or USB controllers including the WiiMote, Sixaxis, Xbox 360 pad, Moga, and iPega lines, along with save states, memory card emulation, and 2x/4x enhanced-resolution software rendering.
What ePSXe does not have is DuckStation’s release cadence or its modern rendering backend list. Updates arrive a few times a year rather than daily, and the project has not published the kind of multi-backend hardware renderer breakdown that DuckStation and Beetle PSX HW both document. For users who already have ePSXe configured and working, that stability can be a feature rather than a flaw, but it does mean the project is playing catch-up on newer graphics APIs.
What Is RetroArch’s Beetle PSX HW Core?
RetroArch is not a PS1 emulator. It is a multi-system frontend built around the libretro API, and it can load more than 200 cores covering systems from the Atari 2600 through the PSP, according to a 2026 breakdown on staresback.gg’s RetroArch cores guide. For PlayStation 1 games specifically, the relevant core is Beetle PSX HW, a hardware-accelerated fork of the Mednafen PSX engine.
Beetle PSX HW supports both a software renderer and hardware-accelerated rendering through OpenGL 3.3 and Vulkan, per Libretro’s own core documentation. It implements PGXP, a geometry and texture correction technique that fixes the warped polygons and jittery textures PS1 games are known for, with both perspective-correct texturing and subpixel precision modes. The core also supports PBP and CHD compressed disc formats, and its officially documented platform list covers Linux, macOS, and Windows, though RetroArch itself as a frontend extends well beyond that to Android, iOS, and multiple consoles.
One detail sets Beetle PSX HW apart from both standalone emulators: it does not strictly require a user-supplied BIOS. A RetroBIOS reference page documenting the core lists an embedded 512KB OpenBIOS implementation that serves as a high-level-emulation fallback when no official BIOS file is present, with automatic region selection between Japanese, North American, and European firmware. Authentic BIOS dumps remain preferable for maximum compatibility, but the fallback lowers the barrier for first-time setup.
DuckStation vs ePSXe vs RetroArch: Full Specs Comparison
Here is how the three stack up across the features that actually affect day-to-day use, pulled from each project’s own documentation and release notes.
| Feature | DuckStation | ePSXe | RetroArch (Beetle PSX HW) |
|---|---|---|---|
| Project type | Standalone emulator | Standalone emulator (PC + separate Android app) | Multi-system frontend running a libretro core |
| Maintainer | Connor “stenzek” McLaughlin | Legacy ePSXe development team | Libretro core contributors (incl. Zapeth, simias, TinyTiger) |
| Most recent build cited (Oct. 2026) | Preview build Oct. 15, 2026 (commit 00e2997); “latest” tag Oct. 13, 2026 | Android v2.0.19, May 2026; Play Store update July 10, 2026 | Core profile dated March 29, 2026 (v0.9.44.1) |
| Release cadence | Automated build on every commit/push | A handful of updates per year | Tied to RetroArch’s broader core-update cycle |
| Platforms | Windows, Linux, macOS, Android, Steam Deck/SteamOS | Windows (PC build), Android (separate app) | Linux, macOS, Windows officially for the core; RetroArch itself also reaches Android, iOS, and consoles |
| Rendering backends | Direct3D 11, Direct3D 12, OpenGL, Vulkan, Metal | Software rendering with 2x/4x enhancement | Software renderer, OpenGL 3.3, Vulkan |
| PGXP geometry/texture correction | Yes | Not documented in current official sources | Yes (perspective-correct texturing and subpixel precision) |
| BIOS handling | Requires a user-supplied BIOS dump | Requires a user-supplied BIOS dump | Accepts a user BIOS, falls back to an embedded OpenBIOS HLE implementation with automatic region selection |
| Save states and memory cards | Yes | Yes, plus Dropbox/Google Drive cloud sync on Android | Yes, via RetroArch’s universal save-state system |
| Controller support | Broad native support, including Steam Deck input | Touchscreen plus Bluetooth/USB pads (WiiMote, Sixaxis, Xbox 360, Moga, iPega) | Inherits RetroArch’s full input-remapping layer |
| Compressed disc formats | CHD and others supported | CHD support improved in the May 2026 update | PBP and CHD supported |
| Steam Deck / EmuDeck integration | Bundled by default in EmuDeck installs | Not typically bundled | RetroArch itself is bundled; Beetle PSX HW is a default PS1 core option |
Performance and Rendering: What the Benchmarks Actually Show
None of the three projects has published a standardized, cross-emulator frames-per-second benchmark run on identical hardware, so treat any specific FPS number you see elsewhere with skepticism. What the official documentation does support is a clear picture of rendering capability, and that is where the real differences show up.
DuckStation’s five rendering backends, confirmed in its own repository description, give it the widest hardware reach of the three. Direct3D 12 and Metal support in particular matter for users on recent Windows and Apple Silicon hardware, where those APIs tend to outperform older OpenGL paths. Beetle PSX HW, per Libretro’s documentation, covers software rendering plus OpenGL 3.3 and Vulkan, which is a narrower set but still modern enough for upscaled, high-resolution PS1 output. ePSXe’s public documentation describes software rendering with 2x/4x enhancement rather than a full hardware-accelerated pipeline, which is the clearest technical gap between it and the other two.
PGXP is the other performance-relevant feature worth tracking. Both DuckStation and Beetle PSX HW implement it, correcting the PS1’s signature polygon jitter and texture warping, a side effect of the console’s lack of sub-pixel precision in its original hardware. Beetle PSX HW’s documentation specifically separates perspective-correct texturing from subpixel precision as two toggles rather than one blanket setting, which gives advanced users finer control over the trade-off between accuracy and the small performance cost PGXP introduces. Current official ePSXe documentation does not describe an equivalent feature, which is one reason upscaled PS1 visuals look noticeably cleaner on the other two.
The Retro Replay entry on Beetle PSX HW adds a practical performance note: the core supports both software and hardware rendering, and hardware rendering is what unlocks the higher internal resolution and PGXP combination. That matches the pattern across all three emulators in this comparison. Software rendering is more accurate to the original but caps out at native resolution, while hardware rendering trades a small amount of authenticity for upscaling headroom.
BIOS Requirements: The Detail That Decides Setup Time
Every PS1 emulator needs to run the console’s original firmware to boot games accurately, and how each project handles that requirement is one of the most practical differences in this comparison. DuckStation and ePSXe both expect you to supply your own BIOS dump, typically pulled from a physical console you own, before games will load with full accuracy.
Beetle PSX HW takes a different approach. Per the RetroBIOS documentation, the core ships with a 512KB OpenBIOS implementation built directly into the binary, which acts as a high-level-emulation fallback when no official BIOS file is present. The core automatically selects between Japanese, North American, and European firmware behavior based on the disc’s region, and it also allows overriding that selection with a PSP, PS3, or OpenBIOS alternative if needed. That makes Beetle PSX HW the fastest of the three to get a game running from zero, though authentic BIOS files remain the safer choice for games that are sensitive to exact firmware behavior.
Typical BIOS Folder Structure
bios/
scph1001.bin # NA BIOS
scph5501.bin # NA BIOS (v4.1)
scph5500.bin # JP BIOS
scph5502.bin # EU BIOS
DuckStation and RetroArch both scan a dedicated BIOS folder on first launch and will flag missing or mismatched files before you try to boot a game, which avoids the cryptic black-screen failures that plagued older emulator setups.
Platform and Device Support Compared
Platform reach is where DuckStation separates itself most clearly from the other two. Its documentation confirms builds for Windows, Linux, macOS (with a universal binary covering both Intel and Apple Silicon Macs), Android, and native Steam Deck/SteamOS support. That is five actively maintained platforms from a single codebase.
ePSXe splits its platform support into two separate products rather than one unified build: a Windows PC application and a standalone Android app that gets its own changelog and its own Google Play listing. That separation means improvements to one do not automatically carry over to the other, which likely explains why the Android app’s May 2026 feature list, covering Oboe audio and cloud-save sync, has no confirmed PC-side equivalent in current documentation.
RetroArch, as the frontend, has the broadest theoretical reach of all three. It runs on practically every modern platform, including game consoles themselves through homebrew channels. But the Beetle PSX HW core specifically is only officially documented on Linux, macOS, and Windows, so Android or iOS users relying on RetroArch for PS1 games should confirm the core builds cleanly on their specific RetroArch mobile build before assuming full feature parity with the desktop version.
Development Activity: Who Is Actually Fixing Bugs Right Now
Release cadence is a useful proxy for how alive a project is, and the gap between these three emulators is stark. DuckStation’s GitHub repository builds automatically on every commit and every push, which is why two separate release channels, the “latest” tag and the preview channel, produced dated builds just two days apart in the middle of October 2026. That kind of pace means fixes for newly discovered game-specific bugs can land within days rather than months.
Beetle PSX HW’s development activity runs through the broader libretro and RetroArch core-update pipeline rather than a dedicated PS1-only team. The core profile referenced in official documentation is dated March 29, 2026, which does not mean the core has gone untouched since then, but it does mean updates are tied to RetroArch’s wider release cycle instead of a PS1-specific roadmap. Contributors like Zapeth, simias, and TinyTiger are credited with specific pieces of the core, from PBP/CHD format support to the OpenGL and Vulkan renderers, which suggests an actively maintained but distributed effort rather than one lead developer driving every change.
ePSXe sits at the other end of the spectrum. Its most recent documented feature update landed in May 2026, with a Play Store metadata refresh following in July. That is a perfectly normal cadence for a mature, feature-complete app, but it also means ePSXe is less likely to pick up fixes for a newly discovered compatibility issue as quickly as DuckStation, where the next commit could already be in testing.
Common Setup Problems and How Each Emulator Handles Them
Most PS1 emulation complaints trace back to one of three issues: a missing or mismatched BIOS, a disc image in the wrong format, or a controller that is not mapped correctly. All three emulators in this comparison handle these differently enough that it is worth knowing which failure mode you are likely to hit.
Missing-BIOS errors are the most common first-run problem, and they look different depending on the emulator. DuckStation and ePSXe will both refuse to boot a game cleanly without a valid BIOS file sitting in the expected folder, and DuckStation’s interface flags the specific file it cannot find rather than failing silently. Beetle PSX HW sidesteps the problem for a first boot entirely thanks to its embedded OpenBIOS fallback, though games that depend on exact BIOS-level timing behavior may show glitches under the fallback that would not appear with an authentic dump.
Disc-format issues come up most often with older rips in BIN/CUE or raw ISO form. All three emulators in this comparison support the compressed CHD format, which is smaller and faster to load than uncompressed images, and converting an existing library to CHD before importing it into any of the three tends to eliminate a chunk of “game won’t load” reports. ePSXe’s May 2026 update specifically called out improved CHD handling, which suggests this was a known pain point the project was actively working through.
Controller mapping problems are the easiest to fix but the most common source of first-session frustration. DuckStation’s native Steam Deck input handling avoids most of this on Valve’s handheld specifically. ePSXe’s Android app leans on hardware-button mapping profiles for known devices like the Xperia Play alongside generic Bluetooth and USB pad support. RetroArch inherits its input-remapping system across every core it loads, so once you have configured a controller for one system in RetroArch, Beetle PSX HW should recognize the same mapping automatically.
Pricing and Licensing: What Each One Actually Costs
All three options are free to download on desktop, but the details differ enough to matter for mobile users and anyone considering commercial or redistribution use.
| Emulator | PC Price | Mobile Price | Licensing Notes | Support Model |
|---|---|---|---|---|
| DuckStation | Free | Free (Android) | Source hosted on GitHub under stenzek’s account; check the repository’s LICENSE file before any commercial use, since GitHub does not auto-classify its terms | Community-driven, GitHub issue tracker |
| ePSXe | Free download for the PC build | Not listed in the current Google Play snapshot used for this guide; historically a paid download | Closed-source, proprietary distribution model | Developer-maintained changelog on epsxe.com |
| RetroArch (Beetle PSX HW) | Free | Free | Open source under the libretro project umbrella | Libretro team and core-specific contributors |
The practical upshot: if you want zero-cost PS1 emulation on both desktop and mobile with no separate purchase, DuckStation and RetroArch both clear that bar comfortably. ePSXe’s PC build is free, but its Android app does not have a confirmed free price point in the sources used for this comparison, which is worth checking directly on the Play Store before you commit to that path on a phone or tablet.
Real-World Use Cases: Five Scenarios That Pick the Winner for You
The specs tables above matter less than the context you are actually playing in. These five scenarios cover the situations most readers land in, and each one points toward a different emulator rather than a single universal answer.
- Steam Deck handheld sessions. DuckStation is the default PS1 emulator bundled by EmuDeck installs and runs natively on SteamOS, which makes it the path of least resistance for anyone emulating PS1 titles on Valve’s handheld. You get Vulkan rendering, PGXP, and controller mapping without touching a configuration file.
- Android-only phone or tablet gaming. ePSXe’s dedicated Android app, now at version 2.0.19 with Dropbox and Google Drive save sync, targets players who specifically want a mobile-first PS1 experience with touchscreen and Bluetooth controller support built in. DuckStation’s Android build is a close competitor here, but ePSXe’s cloud-save integration is a feature DuckStation’s documentation does not describe in the same way.
- Running 30 different retro systems from one app. If PS1 games are only part of a wider retro library that also includes SNES, Genesis, or PSP titles, RetroArch’s single-frontend model with Beetle PSX HW as one of 200-plus cores avoids juggling separate standalone emulators for every console. One settings menu, one save-state system, one place to remap a controller.
- Chasing the most accurate upscaled visuals. Both DuckStation and Beetle PSX HW implement PGXP correction alongside hardware rendering, making them the two best options for players who want clean, high-resolution PS1 output without the warped geometry the original hardware produced. DuckStation’s extra Direct3D 12 and Metal backends give it a slight edge on newer hardware specifically.
- Setting up PS1 emulation for the first time with no BIOS on hand. Beetle PSX HW’s embedded OpenBIOS fallback, documented by RetroBIOS, lets a first-time user boot a game before sourcing an authentic BIOS dump, which DuckStation and ePSXe do not offer as a built-in option. It is the lowest-friction way to confirm an emulator setup actually works before investing time in sourcing firmware.
Who Should Use Which Emulator: Recommendations
Matching the right emulator to the right player matters more than chasing whichever one claims the newest build number. Here is how to think about the decision based on how you actually plan to play.
- Pick DuckStation if you want the most actively developed standalone PS1 emulator, plan to play on Steam Deck, or want the widest set of modern rendering backends including Direct3D 12 and Metal.
- Pick ePSXe if you already have a working configuration from years of use and specifically want a dedicated Android app with cloud-synced saves rather than a general-purpose frontend.
- Pick RetroArch with Beetle PSX HW if you emulate more than one console and want a single interface, settings menu, and save-state system across all of them.
- Pick Beetle PSX HW specifically if you do not yet have a BIOS dump and want to start playing immediately using the embedded OpenBIOS fallback.
- Pick DuckStation or Beetle PSX HW over ePSXe if visual accuracy matters to you, since both implement PGXP geometry and texture correction that ePSXe’s current documentation does not describe.
Migration Guide: Switching Between DuckStation, ePSXe, and RetroArch
Moving your PS1 library between these three emulators is mostly a matter of carrying over two things: your BIOS files and your save data. Here is the practical path for each direction.
Moving From ePSXe to DuckStation
- Locate your existing BIOS dump files from your ePSXe installation folder.
- Copy those BIOS files into DuckStation’s dedicated
biosfolder, which DuckStation scans automatically on first launch. - Export your ePSXe memory card files and move them into DuckStation’s memory card directory, matching the region naming convention DuckStation expects.
- Re-import your disc images (ISO, BIN/CUE, or CHD); DuckStation reads the same common formats ePSXe uses, so a direct copy of your ROM library should work without reformatting.
- Note that save states are not cross-compatible between the two emulators. You will need to load a game from a memory card save rather than an ePSXe save state if you want to continue mid-game.
Moving From RetroArch to a Standalone Emulator (or Vice Versa)
- RetroArch stores BIOS files in its own
systemdirectory rather than a per-core folder, so copy BIOS dumps there if moving into RetroArch, or copy them out to DuckStation’s or ePSXe’s expected folder if moving away. - RetroArch’s save states use a core-specific format tied to Beetle PSX HW, so they will not load in DuckStation or ePSXe directly. Memory card saves are the portable format to carry between all three.
- If you are moving from RetroArch to DuckStation specifically to take advantage of its broader rendering backend list or Steam Deck integration, keep your disc images in CHD format, since all three emulators in this comparison support it.
- Reconfigure controller bindings in the new emulator rather than assuming they will carry over automatically, since each project uses its own input-mapping system.
- Test PGXP settings fresh in the destination emulator if visual accuracy matters to you, since DuckStation and Beetle PSX HW expose PGXP through different menus with different default toggles.
Pros and Cons of Each Emulator
DuckStation
- Pro: Five rendering backends, the widest of any emulator in this comparison
- Pro: Continuous build pipeline means fixes land fast
- Pro: Native Steam Deck and EmuDeck integration
- Pro: PGXP geometry and texture correction for cleaner upscaled visuals
- Con: Rolling preview builds can occasionally introduce regressions between releases
- Con: Licensing terms require checking the repository directly rather than a clearly labeled standard license
ePSXe
- Pro: Long track record and a dedicated Android app with cloud-save sync
- Pro: Broad Bluetooth/USB controller support for mobile play
- Con: No confirmed PGXP-equivalent feature in current official documentation
- Con: Separate PC and Android codebases mean feature parity is inconsistent
- Con: Slower release cadence, with updates measured in months rather than days
RetroArch (Beetle PSX HW)
- Pro: One frontend for 200-plus emulated systems, not just the PS1
- Pro: Embedded OpenBIOS fallback lets you start without sourcing a BIOS dump first
- Pro: PGXP support with separate perspective-correct and subpixel toggles
- Con: Officially documented platform list for the core itself is narrower than DuckStation’s
- Con: RetroArch’s general-purpose interface has a steeper learning curve than a single-purpose PS1 emulator
How This Compares to the Broader Emulation Landscape
PS1 emulation is one of the more settled corners of the retro-gaming scene compared to newer, more demanding targets. Switch emulation has splintered since Nintendo’s legal pressure shut down the two biggest projects in that space, leaving successors like Eden and Citron to split the community, as covered in our Eden vs. Citron comparison. PS3 emulation is still actively contested between multiple Android-focused projects, a dynamic detailed in our ARMSX3 vs. DukePS3 vs. RPCS3 breakdown. By contrast, DuckStation, ePSXe, and Beetle PSX HW are not locked in the kind of legal or technical standoff those newer systems face, which is part of why PS1 emulation has stayed stable enough to focus on polish rather than survival.
That stability also shows up in how PS1 emulation gets bundled into bigger projects. EmuDeck, the installer many Steam Deck owners use to set up a full retro library in one pass, defaults to DuckStation for PS1 titles while also offering RetroArch’s Beetle PSX HW core as an alternative, a setup covered in detail in our guide on the Steam Deck’s current hardware lineup. That default choice is itself a signal of where the community consensus currently sits, even without a formal, independently verified compatibility benchmark to point to.
The Verdict: Which PS1 Emulator Should You Use in 2026?
Based on the documented facts in this comparison, DuckStation is the strongest default choice for most players. It supports more platforms (five, against RetroArch’s officially documented three for the Beetle PSX HW core and ePSXe’s two separate apps), ships more rendering backends, and updates faster than either alternative, with builds landing just two days apart in mid-October 2026 alone.
RetroArch’s Beetle PSX HW core is the right call specifically when PS1 emulation is one piece of a much bigger retro setup, or when you want to start playing before sourcing a BIOS dump, thanks to its embedded OpenBIOS fallback. ePSXe remains a legitimate option for players who already have it configured, particularly on Android where its cloud-save integration is a genuine convenience, but its slower update pace and narrower rendering feature set put it behind the other two on raw capability as of October 2026.
None of the three is objectively wrong. The data shows a clear capability gap in DuckStation’s favor on platform reach and rendering backends, but the right pick still comes down to whether you need a single-purpose PS1 tool, a mobile-first app, or a frontend that spans dozens of other consoles at the same time.
It is also worth revisiting this comparison periodically rather than treating it as settled. DuckStation’s rolling-build model means its feature list a few months from now could look different from what is documented here, and RetroArch’s core-update cycle moves on its own schedule independent of any single system. ePSXe’s slower pace is the one variable most likely to stay constant, which is itself useful information if predictability matters more to you than chasing the newest rendering backend.
Frequently Asked Questions
Is DuckStation better than ePSXe?
DuckStation supports more rendering backends, more platforms, and updates far more frequently than ePSXe, based on each project’s own documentation as of October 2026. DuckStation also implements PGXP geometry and texture correction, a feature not documented in ePSXe’s current official materials. ePSXe still has value for Android users who want its specific cloud-save and controller integration, but on raw technical capability, DuckStation is ahead.
Do I need a BIOS file for DuckStation, ePSXe, or RetroArch?
DuckStation and ePSXe both require a user-supplied BIOS dump to run games with full accuracy. RetroArch’s Beetle PSX HW core is the exception: it ships an embedded 512KB OpenBIOS implementation that works as a fallback when no BIOS file is present, with automatic region detection, though an authentic BIOS remains the more reliable option for maximum compatibility.
Which PS1 emulator works best on Steam Deck?
DuckStation is the default PS1 emulator bundled by EmuDeck for Steam Deck setups and includes native Steam Deck/SteamOS support directly in its own build list. RetroArch with the Beetle PSX HW core is also available on Steam Deck and offers the advantage of handling other retro systems in the same interface.
Is RetroArch the same thing as an emulator?
Not exactly. RetroArch is a frontend built on the libretro API that loads individual “cores,” each of which emulates a specific system. For PlayStation 1 games, the relevant core is Beetle PSX HW. RetroArch itself provides the interface, input handling, and save-state system, while the core does the actual emulation work.
Can I use PGXP to fix wobbly PS1 graphics in all three emulators?
PGXP geometry and texture correction is documented in both DuckStation and RetroArch’s Beetle PSX HW core, with Beetle PSX HW offering separate toggles for perspective-correct texturing and subpixel precision. Current official ePSXe documentation does not describe an equivalent feature, which means the warped polygon effect common to unmodified PS1 emulation is more likely to show up there.
Is ePSXe free on Android?
The current Google Play listing used for this comparison did not display a price, so check the Play Store directly before downloading. Historically, the Android app has carried a one-time purchase cost separate from any free PC build, so do not assume it will match DuckStation’s or RetroArch’s fully free download model without confirming first.
Can I transfer my save files between DuckStation, ePSXe, and RetroArch?
Memory card saves are the most portable format between the three, since all of them emulate standard PS1 memory cards. Save states, however, are tied to each emulator’s internal format and are not cross-compatible, so a save state created in RetroArch’s Beetle PSX HW core will not load in DuckStation or ePSXe, and vice versa.
Which emulator gets updated most often?
DuckStation has the fastest release cadence of the three by a wide margin. Its GitHub releases page builds automatically on every commit and push, which produced two separate build releases just two days apart in mid-October 2026. ePSXe’s Android app, by comparison, saw its most recent feature update in May 2026 with a store-side bump in July, and Beetle PSX HW’s update cycle is tied to RetroArch’s broader core-release schedule.
