ePSXe’s defining design decision is its plugin architecture: instead of one monolithic emulator, the core delegates graphics (GPU), sound (SPU), CD-ROM (CDR) and input to swappable components. Understanding that model explains ePSXe’s strengths, its quirks, and half of all its troubleshooting.
The classic model (1.x era)
In the 2000s, plugins were separate files — DLLs in the plugins folder — written by independent developers. Pete Bernert’s GPU plugins (including Pete’s OpenGL2) became the standard; sound and CD-ROM plugins had their own ecosystems. This openness is why ePSXe could be tuned for everything from a Pentium-era PC to early HD experiments, and why period guides read like shopping lists of plugin combinations.
The 2.0.x reality: cores inside
The modern line internalised the key pieces: GPUCORE and Pete’s OpenGL2 exist as core plugins inside the emulator, alongside the internal SPU and CDR cores. Tellingly, the official 2.0.18 package ships with an empty plugins folder — the architecture survived, the DLL hunt mostly didn’t. Release notes still speak the plugin language: v2.0.5 added threading modes to the Pete’s OpenGL2 core plugin and ported GPUCORE threading from Android; v2.0.18’s sound work happened in “SPUCORE”. On Android there is likewise an official OpenGL plugin companion app. When we say “plugin settings” on this site (for example in the OpenGL2 guide), we mean these built-in cores.
Why it still matters in 2026
- Per-problem fixes: most ePSXe faults isolate to one subsystem, and the fix is swapping that core’s mode — the entire shape of our troubleshooting hub.
- Per-game tuning: a game that breaks on OpenGL2 may be perfect on the internal core; the architecture makes that a setting, not a different emulator.
- The cost: interactions multiply (two frame limiters, plugin-specific quirks), and there is no single “correct” configuration — the trade modern monolithic designs (DuckStation) deliberately gave up for consistency.
The honest summary
Plugins were ePSXe’s genius and remain its personality: flexible, tunable, occasionally bewildering. Modern emulators integrated everything and won on polish; ePSXe’s model still wins when one specific game needs one specific subsystem bent to its will — or when the hardware underneath is old enough that shedding work is the whole game (low-end guide).
