Memory cards: where they live

Cards are stored as .mcr files in the memcards folder of your ePSXe directory (epsxe000.mcr, epsxe001.mcr and so on). Config > Memory Cards assigns which files sit in Slot 1 and Slot 2. Games save to them exactly as they did on hardware — at save points, in blocks. Two practical notes: install ePSXe outside Program Files so Windows lets it write the files, and never rename a card while a game has it “inserted”.

Moving saves between emulators

The .mcr format is the PS1 standard, and ePSXe’s cards are compatible with the PC version from Android (the Play listing states this explicitly) and importable by most other PS1 emulators, including DuckStation. Individual game saves inside a card (the per-block files) can also be extracted with card manager tools if you need a single game’s save.

Save states: F1, F2, F3

• F1 — save a state to the current slot.
• F2 — cycle the active slot.
• F3 — load the state in the current slot.

States are stored in the sstates folder and are emulator- and version-specific: they do not transfer to other emulators, and a state made in an old version may not load after an update. Use states as convenience (before a hard boss, mid-dungeon), and memory cards as the permanent record. Android mirrors the same model, and v2.0.19 can sync both to Google Drive or Dropbox — see the cloud save guide.

A backup habit that works

1. After each session, copy the whole memcards folder somewhere else — cloud storage counts.
2. Name backups by date; .mcr files are tiny, so keep many.
3. If a card ever shows as corrupted in the BIOS screen, stop, restore the newest good copy, and only then keep playing. The BIOS memory card screen is also where you delete blocks when a card fills up.

Related: our Windows setup and Android setup guides both end at a working memory card configuration.

Windows and desktop: local netplay since 2.0.5

The v2.0.5 release (2016) ported local netplay from Android to the desktop builds and marked it experimental. That version’s netplay is compatible across the 2.0.5 family (Windows, Linux, macOS and Android 2.0.6-era builds). The practical rules of emulator netplay all apply: both players need the same game image, the same emulator version, and the same settings, or the two sides desync. Treat it as a LAN-party feature, not online play. There is no official server, no lobby, and no rollback netcode.

Android: local multiplayer is the real feature

On Android the stronger story is same-device multiplayer: the official listing describes support for 1–4 players and a two-player split-screen mode, with external controllers over Bluetooth or USB. For couch play on a phone or tablet — or on a TV, see ePSXe on Android TV — this is the mode that works without networking caveats. Map each pad under Preferences as in our controller guide.

Setting expectations

• No cross-internet play is offered or promised by the ePSXe team — anyone selling “online ePSXe” is describing something else, usually a VPN tunnel trick that adds lag and still desyncs.
• Synchronisation is fragile: different plugins or frame settings between players will drift apart. Standardise both setups first.
• Save states are local to each side; agree on memory-card saves for a shared campaign.

The alternative for true online play

If playing a friend online is the actual goal, RetroArch’s netplay (with the Beetle PSX core) is the more developed route in 2026 — see ePSXe vs RetroArch. ePSXe’s niche is local: same room, same network, same couch.

Windows: the cheat window

1. Launch the game first, then open the cheat code window from the emulator’s menu options while it runs.
2. Add your code in the format the window expects (GameShark/CodeBreaker-style codes for the game’s region — a US code will not fire on the European version).
3. Enable the codes you want, return to the game, and check the effect. Save a save state first: a bad code can soft-lock a session, and a state is your undo button (F1 to save).

The built-in code download (v2.0.5+)

Version 2.0.5 added an option in the cheat codes window to download cheat codes for games, using data from psxdatacenter.com. It is the low-effort route for popular titles and avoids typing long code lists by hand.

Android: cheats and scoped storage

On Android, cheat files live alongside your game data. The Android 2.0.18 update specifically added support for cheats stored in scoped storage folders, so on current Android versions keep the cheat files in the same approved folder as the game image, or the app cannot see them.

When codes refuse to work

• Region mismatch — the most common cause. Match code region to disc region.
• Interpreter mode: v2.0.5 fixed cheat support when running in interpreter mode; on older builds, codes could silently fail there.
• Master/enabler codes: some code sets need their master code entered and enabled first.
• Timing: codes that modify memory continuously can destabilise specific games — enable one at a time when troubleshooting, and see the troubleshooting hub if a game starts crashing only with codes on.

Cheats are single-player fun; they have no place in any competitive or netplay context, and ePSXe’s local netplay (see netplay guide) assumes both sides run the same setup.

Windows: Config > Gamepad

1. Connect the controller before launching ePSXe — pads plugged in mid-session are the top cause of the controller not working problem.
2. Open Config > Gamepad > Port 1 > Pad 1 and choose the pad type: DualShock for analog games, Digital for early titles.
3. Click each input box and press the physical control. Map the d-pad as well as the left stick — many PS1 games ignore the stick entirely.
4. For XInput pads, v2.0.5 swapped the vibration actuators to match the real PSX left/right — if rumble feels mirrored on an old config, re-save the profile.

Android: Preferences > Gamepad

Pair the controller in Android’s Bluetooth settings first, then map it inside the app. The official listing confirms support for Bluetooth and USB gamepads (WiiMote, Sixaxis, Xbox 360-era pads, Moga, Ipega class devices) plus analog sticks. For two-player games, ePSXe for Android supports up to 4 players and a two-player split-screen mode — see netplay and multiplayer.

Choosing a pad for PS1 games

A d-pad-centric layout matters more than extra buttons: PS1 games live on the d-pad and four face buttons. Our best controller for ePSXe guide compares the usual suspects — 8BitDo’s SN30 Pro style pads, GameSir’s mobile controllers, PowerA and the budget Logitech F310 — with the trade-offs stated plainly.

Quick checks when inputs misbehave

• Wrong port mapped (the game reads Port 1 only in most menus).
• Pad type set to DualShock for a digital-only game, or the reverse.
• Another app (Steam, a mapper tool) intercepting the controller on Windows.
• On Android, the pad paired to a different profile or connected after launch.

Where the settings live

Config > Video, select the Pete’s OpenGL2 core plugin, then Configure. One clarification first: the official ePSXe zip ships with an empty plugins folder — the core plugins are part of the emulator itself in the 2.0.x line, while the classic standalone Pete’s plugins belong to the older external-plugin ecosystem. If a guide tells you to drop DLLs into the folder for a 2.0.x install, it is describing the 1.x era.

A sane baseline

• Internal X/Y resolution: High (2x) to start; Very High only if the GPU shrugs at 2x.
• Texture filtering: option 2 (extended) as a baseline; move up for 3D games, down if 2D sprites fringe.
• Hi-Res textures: off by default — some games smear FMV and menus with it on.
• GTE accuracy: on. It steadies vertices within the limits of the plugin approach (it is not DuckStation-style PGXP).
• Framebuffer effects: full/standard, not disabled — transitions and battle effects depend on them.
• Threading mode (2.0.x): the added 2-thread and effects modes can help slower CPUs; leave the default if performance is already full speed.
• FPS limit: use the plugin’s limiter or ePSXe’s, not both fighting — one limiter, set to auto.

The Nice / Fast buttons are your reset switch

The plugin panel’s Nice and Fast presets are the fastest diagnostic in ePSXe: if a game breaks, click Fast, confirm it runs, then re-apply your HD choices one at a time. Half of all “this game is incompatible” reports are one plugin checkbox — this is also step one of our black screen fix.

When OpenGL2 is the wrong tool

Some games lean on exact software rendering behaviour. If a title shows missing layers, wrong colours or invisible menus under OpenGL2 but runs on the internal core, believe the internal core — accuracy beats resolution for that game. The broader settings context is in best graphics settings, and the plugin architecture itself in how ePSXe’s plugin system works.

Choose the right video plugin first

Open Config > Video. For HD output, choose Pete’s OpenGL2 core plugin (settings in depth in our OpenGL2 guide). For a problem game, drop to the internal GPU core at native resolution — if the glitch disappears, the plugin settings were the cause. The official recommended spec (fast dual-core CPU, 512 MB RAM, OpenGL 2.0 + GLSL card) covers native resolution comfortably; upscaling is what asks more of the GPU.

The settings that matter

• Internal resolution: 2x–3x on a mid-range GPU is the sweet spot. Higher values mostly sharpen menus, not models, and can introduce slowdowns in framebuffer-heavy games.
• Texture filtering: use an extended/filtered setting for 3D textures, but expect occasional seams in 2D-heavy games. If sprites develop black outlines, reduce filtering first.
• GTE accuracy: enabling the accuracy options reduces the classic PS1 polygon wobble. Be clear about what this is not: ePSXe has no native PGXP like DuckStation’s — see the honest note in ePSXe vs DuckStation.
• Framebuffer effects: keep them enabled (or on a middle setting) for games with screen transitions and effects; disabling them is a common cause of missing effects and some black screens.
• Use FPS limit: on, with the limit set to auto/60 (NTSC) — this also prevents the games running too fast problem.

2D games: a different recipe

For sprite-based games, native resolution with a CRT-style shader usually looks better than aggressive upscaling. On Android v2.0.19, the fixed CRT shaders and the new CAS and MMPX shaders are designed exactly for this case.

Per-game profiles beat one global setup

PS1 emulation rewards per-game tweaks: one title wants framebuffer effects maxed, the next breaks with the same setting. Change one thing at a time, note what fixed the game, and keep the global profile conservative. If a game still misbehaves after a plugin reset, check the troubleshooting hub before assuming the rip is bad.

Why the BIOS is different from the emulator

ePSXe itself is freeware. The PlayStation BIOS is not: it is Sony’s copyrighted firmware, and neither the ePSXe team nor Google Play distributes it. The readme inside the official ePSXe package states the rule plainly — you may only be in possession of the copyrighted BIOS if you are legally entitled to do so. A BIOS file downloaded from a random site fails that test, which is why our download page removed its old BIOS link entirely rather than relabelling it.

Which BIOS file do you need?

ePSXe expects a .bin image in its bios folder (Config > BIOS on PC; Preferences > BIOS on Android). The commonly used dumps are SCPH1001 (North America), SCPH7502 (Europe) and SCPH1000 (Japan) — match the region of the games you ripped. One BIOS from your own console is enough to start; region-free booting is not something any emulator can promise for every title.

The legal route: dump your own console

1. Get a console. A used original PlayStation or PSone is inexpensive second-hand — our buying guide covers what to check, and marketplaces like eBay are the usual source.
2. Dump the firmware. Community dumping methods read the BIOS from real hardware (for example via a serial-link cable or a memory-card exploit on the console itself). The process produces a .bin file from your machine — that file is yours in a way a download never is.
3. Copy and select it. Put the .bin in ePSXe’s bios folder and select it in the BIOS settings, then restart the emulator.
4. Back it up. Keep a copy with your save backups (see the cloud save guide) so you never have to dump it twice.

“But everyone else offers the download”

They do — and it is still Sony’s firmware being redistributed without a licence, often bundled with files nobody can verify. The checksum printed for one popular BIOS package does not even match the known scph1001.bin checksum, so there is no way to know what those files really are. Owning the console is also what makes your game rips straightforward: dump your firmware, rip your discs (here is how), and your whole setup is clean.

What about the built-in HLE BIOS?

ePSXe can fall back to high-level emulation (HLE) of the BIOS for some titles — v2.0.18 improved HLE support for specific games — but HLE is a compatibility fallback, not a replacement. Some games misbehave or refuse to boot with it. If you see the missing BIOS error, the real fix is a proper dump from your own hardware.

1. Install from Google Play

Open the ePSXe for Android listing on Google Play (publisher: epsxe software s.l.) and install it. The app is rated 4.48 from about 53,000 reviews on Google Play, with over a million installs — a useful sanity check that you have the genuine listing and not a clone.

2. Add your BIOS and games

The app includes no games and no BIOS. Copy a BIOS file dumped from your own PlayStation (see the legal BIOS guide) and disc images ripped from your own games into a folder on the phone, then set the BIOS path in Preferences > BIOS. Supported images include BIN/CUE, ISO, IMG, PBP and CHD — v2.0.19 improved CHD support further.

3. Grant storage access (scoped storage)

On modern Android versions the app can only see folders you approve. When prompted, grant access to the exact folder holding your BIOS and games; if a game does not appear in the scanner, the folder permission — not the game file — is almost always the problem. The 2.0.18 update added cheat support inside scoped storage folders, and v2.0.19 targets SDK 35 for current Android releases.

4. Pick a renderer and sound engine

• Video: start with the hardware renderer; switch to the OpenGL plugin for HD upscaling on a strong phone, or the software renderer if a game glitches.
• Sound: v2.0.19 added the Oboe sound engine — select it in sound preferences for lower audio latency.
• Shaders: v2.0.19 fixed the CRT shaders and added CAS and MMPX shaders for sharper 2D games.

5. Controls: touch or a real pad

The virtual touchscreen pad works, but a Bluetooth controller is the single biggest upgrade for PS1 games on a phone. Pair it before launching the app and map it under Preferences; the app supports 1–4 players and a two-player split-screen mode. Our controller guide and the controller buying guide cover the details.

6. Protect your saves

v2.0.19 added Google Drive support and updated the Dropbox API, so memory cards and save states can sync off the device. Turn it on before a long RPG — our cloud save guide walks through it.

1. Download and extract ePSXe 2.0.18

Download the Windows package from the official ePSXe website via our download page. The file is ePSXe2018.zip (1,551,309 bytes). You can verify it before extracting: its SHA-256 is ec0d0e235f839261818acc5118cd810a7193b0fbcbd339517f884dffc31792bb. Extract the whole zip into its own folder (for example C:\Games\ePSXe) — do not run ePSXe.exe from inside the zip window, and avoid Program Files, which can block memory card and config writes.

2. Add your BIOS (from your own console)

ePSXe does not include a BIOS, and the BIOS is copyrighted Sony firmware — the ePSXe readme says you may only possess it if you are legally entitled to it. Dump it from a PlayStation you own (see our legal BIOS guide), place the .bin file in the bios folder inside your ePSXe directory, then open Config > BIOS, select it and save. Skipping this step is the number one cause of the missing BIOS error and black screens.

3. Run the configuration wizard

On first launch, ePSXe walks you through BIOS, video, sound, CD-ROM and controllers. Sensible defaults for a modern PC:

• Video: Pete’s OpenGL2 core plugin for HD upscaling, or the internal GPU core for maximum compatibility. Details in our OpenGL2 settings guide.
• Sound: the internal SPU core. v2.0.18 improved its reverb and volume handling.
• CD-ROM: the internal WNT/W2K core if you play from images; an ASPI-style plugin is only relevant for real discs in old drives.
• Controllers: plug the pad in before you start mapping — see the controller setup guide.

4. Load your first game

Use File > Run ISO and pick an image ripped from your own disc: BIN/CUE, ISO, IMG, PBP, or CHD (v2.0.18 added CHD support for ISOs; our CHD guide covers converting your rips). If the game window stays black, work through the black screen fix before changing random settings.

5. Two settings worth changing immediately

• Options > DPI Awareness: new in v2.0.18 — enable it if menus look blurry on a high-resolution display.
• Config > Memory Cards: pick two .mcr files so saves behave like real cards. F1/F2/F3 handle save states (save, choose slot, load). Our memory card guide explains the difference.

That is a complete, honest setup. Everything else — prettier graphics, cheats, netplay — builds on this base, and the tutorials index collects those guides.