Emulation
PCSX2

The reference PlayStation 2 emulator.
All PS2 emulatorsOn PS2
Recommended- Accuracy
- High
- BIOS or firmware
- Required
A BIOS dumped from your own PS2 is required: follow the BIOS guide on the official PCSX2 website. Dump your own discs as ISO files (DVD) following the official disc guide; CHD saves space. Leave the graphics API on Automatic unless a game misbehaves, then try Vulkan. A good internal resolution is 3x for a 1080p screen and 6x for 4K, if your graphics card allows it. Settings can be changed per game in the game's Properties. Use in-game saves on a memory card as your real saves; save states may stop working after an update. A processor with AVX2 support makes the biggest difference.
Overview
PCSX2 is a free, open-source emulator for the PlayStation 2. An emulator is a program that imitates a console, so your computer can run that console's games. PCSX2 has been developed for more than 20 years, and its own project page says recent versions run most games at full speed, including titles such as Final Fantasy X and Devil May Cry 3. It runs on Windows, macOS and Linux.
It is made for anyone who wants to replay PS2 games on a computer, with extras the real console did not have: sharper pictures, save states, widescreen patches, cheats, achievements and the use of a modern controller.
Two things to know before you start. First, PCSX2 cannot start any game without a BIOS dumped from your own PS2 (explained below). Second, it asks a lot of the processor, so a very old or very low-power computer will struggle.
Key words explained
BIOS: a small program stored inside the console that starts it up and provides basic services to games. An emulator needs a copy of it, because games expect it to be there.
Disc image: one file that contains the full copy of a game disc. ISO is the common format for DVDs. Older CD-based games are dumped as a BIN file with a CUE or TOC file next to it.
CHD: a compressed disc image format. It takes less disk space than an ISO and loses nothing.
Graphics API (also called renderer): the way PCSX2 talks to your graphics card. Vulkan, Direct3D, OpenGL and Metal are different ways of doing so. Each has strengths on different computers.
Internal resolution: the size of the picture PCSX2 draws before showing it on your screen. The PS2 drew small pictures; a higher value makes the game sharper but needs a stronger graphics card.
Memory card: on the PS2, the device that held your game saves. PCSX2 imitates it with a file or a folder.
Save state: a snapshot of the whole emulated console at one moment. It is not the same as a save made with the game's own menu (an in-game save).
Patch and cheat: small text files with instructions that change a game while it runs. Patches improve it (for example widescreen); cheats change gameplay (for example infinite health).
Portable mode: PCSX2 keeps all its data in its own folder instead of in your Documents folder.
System requirements
These are the figures from the official requirements page. PassMark is a public benchmark site that gives a score to each processor and graphics card; you can look up yours by name.
Minimum: Windows 10, macOS 11 (Big Sur) or Ubuntu 22.04 or another Linux distribution; a processor with SSE4.1 and two physical cores with SMT, with a PassMark single-thread rating of at least 1500; a graphics card supporting Vulkan 1.1, Direct3D 11 or OpenGL 3.3 with a PassMark G3D Mark of at least 600; 8 GB of memory.
Moderate (closer to a comfortable setup): Windows 11, a recent macOS or Linux; a processor with AVX2 and four physical cores, with a single-thread rating of at least 2000; a graphics card supporting Vulkan 1.3, Direct3D 12, OpenGL 4.6 or Metal (Mac only), with a G3D Mark of at least 6000 and 4 GB of video memory; 16 GB of memory.
PCSX2 does not run on phones. On Android, see ARMSX2.
What you need
1. The PS2 BIOS. PCSX2 will not start games without it, and there is no free replacement. It is copyrighted, so it is never included with the emulator: it must be dumped from your own PlayStation 2. The official BIOS guide explains the method step by step.
2. Your games, as disc images. The official disc dumping guide explains how to copy a disc you own on Windows, macOS and Linux.
DVD games are dumped to an .iso file.
CD games are dumped as .bin plus .cue or .toc files. The guide notes that PCSX2 does not read the .cue or .toc file itself, so follow the guide for these discs. An .iso of a CD can break some games, because it keeps only one audio track and uses a different sector size.
3. A controller (optional but recommended). A PlayStation or Xbox pad usually works well. A keyboard also works, but PS2 games are designed for two analog sticks.
Disc image formats and CHD
The game list window of PCSX2 states the formats it reads: .bin and .iso (plain disc images), .mdf (Media Descriptor File), .chd (Compressed Hunks of Data), .cso and .zso (compressed ISO) and .gz (a gzip-compressed ISO). The simplest choice is a plain ISO. The compressed formats exist to save disk space.
CHD is the most common compressed choice. A disc image is a long file, often several gigabytes, and CHD squeezes it without losing any data, so the game plays the same. To convert an image you dumped yourself, use chdman, the free tool shipped with MAME. It is a command-line tool, which means you type a command in a terminal (on Windows, Command Prompt or PowerShell) instead of clicking buttons. This conversion is a feature of chdman and not of PCSX2, and the PCSX2 documentation does not describe it, so check chdman's own help (run chdman with the word help) if a command does not match.
Download MAME from its official page and extract it. chdman is one of the files inside.
Open a terminal in the folder that holds chdman and your ISO.
For a DVD game, run: chdman createdvd -i game.iso -o game.chd (replace game with the real file name).
For a CD game dumped as BIN and CUE, the matching command is chdman createcd. PCSX2 itself does not read the .cue file, so only use this if you know the CHD result starts correctly.
Add the new .chd to your game folder, refresh the game list, and start it. It worked if the game boots as before. Keep your ISO until the CHD is tested.
Installation
Get PCSX2 only from the official download page. There are two builds. Stable is updated every few months and changes less, so it is the safe choice for beginners. Nightly is updated continually with the newest changes, and may break more often. The steps below follow the official running guide.
Windows. First install the latest x64 version of the Microsoft Visual C++ Redistributable, a Microsoft component the program needs. Then choose one method:
Installer (Stable only): download the .exe, double-click it, click Yes when Windows asks, and follow the setup wizard.
Portable (Stable or Nightly): download the portable archive (a .7z file), extract it into its own folder (7-Zip, or Extract All on recent Windows 11), then double-click the pcsx2-qt program. To keep all data in that folder, create an empty file named portable.ini or portable.txt next to the program before the first start.
macOS.
Download the macOS build, a .tar.xz archive.
Double-click the archive in Finder to extract the application.
Drag the application into the Applications folder, then open it from there.
If macOS offers to install Rosetta (a compatibility layer from Apple), click Install.
Linux. Use the AppImage or the Flatpak from Flathub.
Flatpak: install net.pcsx2.PCSX2 from Flathub or your software center. The official page warns its sandbox can cause file-access problems.
AppImage: download it, make it executable (in a terminal, chmod +x followed by the file path, or tick the executable option in the file's Properties), then double-click it.
First setup
The first time PCSX2 opens, a setup wizard starts with a Welcome screen. It offers the interface language, a theme and the option Enable Automatic Updates. The later screens guide you through the BIOS, the folder of your games and your controller. Everything can be changed afterwards in Settings.
BIOS: the BIOS is a set of files. Put them in one folder, then tell PCSX2 where it is (Settings > BIOS once the wizard is closed). Select your BIOS in the list. If the list is empty, PCSX2 found no usable BIOS in that folder.
Game folder: add the folder that holds your disc images (Settings > Game List). PCSX2 scans it and shows your games in the main window.
Controller: see the Controls section below.
Start a game: double-click it in the list. It worked if the PlayStation 2 logo or the game's intro appears.
Controls and hotkeys
Controller mapping means telling PCSX2 which button of your real controller acts as which button of the virtual PS2 controller. The emulated pad is a DualShock 2, with two analog sticks, vibration and pressure-sensitive buttons that a few games use. The steps below follow the official controller guide.
Open Settings > Controllers.
Choose your Input Sources. SDL is recommended. XInput (Windows only) is a backup for Xbox-type pads, and DInput (Windows only) is a last resort.
Select Controller Port 1 first, because most games expect player one there.
Click Automatic Mapping at the top right and choose your controller in the list. The buttons, sticks and vibration are filled in for you.
If an error says automatic mapping is not supported, map by hand: click a button in PCSX2, then press the matching button on your controller, and repeat for each button and stick.
Keyboard: if you have no controller, PCSX2 starts with a keyboard layout for port 1. The arrow keys are the directional pad, W A S D the left stick, T F G H the right stick, K is Cross, L is Circle, J is Square, I is Triangle, Enter is Start and Backspace is Select. These are the program's defaults and may change in future versions.
Hotkeys are keys that control PCSX2 itself rather than the game. Change them in Settings > Hotkeys: click a line and press the key or combination you want. The defaults the program ships with, as found in its source code, include:
Space: pause or resume.
Escape: open the pause menu.
Alt + Enter: switch between fullscreen and window.
F1: save a state to the selected slot. F2: select the next slot (Shift + F2: previous). F3: load a state from the selected slot.
F4: turn the frame limit on or off. The frame limit keeps the game at its normal speed.
Tab: turn fast-forward on or off. Period (.): fast-forward while held.
F8: take a screenshot. F9: switch between hardware and software rendering. F5: change the deinterlacing method. F6: change the aspect ratio.
Ctrl + M: mute.
Some hotkeys, such as Reset or Shut Down, have no default key. Assign one yourself if you want it, ideally a button combination on your controller. Choose keys that do not clash with other programs, such as the keyboard layout of Steam's controller support, which can send unwanted keys and open the pause menu by accident.
Big Picture mode
Big Picture mode is a full-screen menu made to be used with a controller, for example when the computer is connected to a TV. You browse your games, change settings and start games without a mouse. Open it from the System menu with Start Big Picture Mode, or with the Big Picture button of the toolbar.
Graphics settings
Graphics options are in Settings > Graphics, in tabs: Display, Rendering, Hardware Fixes, Upscaling Fixes, Texture Replacement, Post-Processing, Media Capture and Advanced. The defaults are chosen to work with as many games as possible. Change one option at a time and test. For a single game, right-click it in the list and choose Properties: the settings there apply only to that game. While a game runs, they are in Settings > Game Properties. The help texts below come from the program's own tooltips.
Renderer. This is the Renderer drop-down at the top of the Graphics page. It chooses the technology used to draw the picture. Automatic selects the best one for your hardware and is the default; the official guide says: when in doubt, leave it on Automatic. The choices are:
Vulkan: accurate and fast on all systems, but it can be unstable on Intel integrated graphics, and it needs up-to-date graphics drivers.
OpenGL: accurate, reasonable on Nvidia, unstable on Intel and slow on AMD. It is always slower than Vulkan.
Direct3D 12 (Windows): the least accurate, it cannot emulate some blending effects. It needs a graphics card that supports it.
Direct3D 11 (Windows, labelled Legacy): same accuracy as Direct3D 12 and slightly slower.
Metal (macOS only): the choice made for Macs.
Software Renderer: draws with the processor instead of the graphics card. It is the most accurate and needs a strong processor.
When to change it: only if a game shows missing pieces, wrong colors, crashes or stutters. Try Vulkan first (or Metal on a Mac), then OpenGL. You can also switch quickly from a running game with Debug > Switch Graphics API.
Internal resolution. In the Rendering tab, the Internal Resolution drop-down sets the size at which the game is drawn. Native (PS2) is the default and looks like the original console, small and soft on a modern screen. Higher values draw more pixels, so the picture is sharper, but the graphics card works harder. The labels in the list say what each step is about:
2x Native: about 720p (HD).
3x Native: about 1080p (Full HD). This is a good target for a 1080p screen.
4x Native: about 1440p. 5x: about 1800p.
6x Native: about 2160p (4K). Choose it for a 4K screen only if your graphics card is strong.
How to choose: pick the step that matches your screen height, play, and look at the performance counters (see below). If the speed drops below 100%, lower the step. The tooltip warns that a non-native resolution may cause minor graphical issues in some games, such as thin lines or misplaced effects, and that video scenes (FMV) stay unchanged because they are pre-rendered files.
Texture filtering. Textures are the images wrapped around objects. Filtering decides how their pixels are blended when shown larger than they are. In the Rendering tab:
Bilinear (PS2): the default. It filters what the game asked the PS2 to filter, so it looks closest to the original.
Nearest: no blending, so textures look blocky.
Bilinear (Forced): blends everything, even where the game did not ask for it. It can look smoother but may cause glitches.
Bilinear (Forced Excluding Sprites): the same, except for sprites (flat 2D elements, often menus and effects).
Blending accuracy. Blending is how the graphics chip of the PS2 mixes a new pixel with the one already on screen, used for transparency, fog and light effects. The Blending Accuracy option sets how closely PCSX2 copies it. Basic (Recommended) is the default. A higher setting emulates more of it accurately, but the tooltip warns that the speed penalty grows with it. Raise it only for a game that shows wrong shadows, missing light effects or odd transparency, and lower it again if the game slows down. Direct3D cannot do some blending, as noted above.
Other useful options:
Display tab, Aspect Ratio: the default, Auto Standard (4:3/3:2 Progressive), adapts to widescreen patches.
Display tab, Apply Widescreen Patches and Apply No-Interlacing Patches: automatically load these patches when a game starts. Both are off by default and the tooltips say they can cause issues. A no-interlacing patch removes the flicker lines some games show on modern screens.
Hardware Fixes and Upscaling Fixes tabs: per-game workarounds. Leave them alone unless told otherwise.
If the game runs slowly, the official performance guide suggests this check:
Turn on the performance counters in Settings > Graphics > OSD, then take a screenshot while the game is slow. It helps to find the bottleneck and to ask for help.
Patches, widescreen and cheats
The official patch documentation explains that patches and cheats are text files containing commands that PCSX2 applies to a game while it runs. There are three kinds.
Patches: quality-of-life improvements such as widescreen support and no-interlacing. PCSX2 reads them from its patches folder and a built-in archive. Turn them on or off on the Patches page of the game's Properties.
Cheats: changes to gameplay. PCSX2 reads them from its cheats folder. Turn them on in the Cheats page of the game's Properties, and make sure Enable Cheats is on in Settings > Emulation (or per game on that page).
Compatibility patches: essential fixes stored in a built-in database. They are on by default (Enable Compatibility Patches in the Advanced settings) and you normally never touch them.
Files are named after the game's serial number and a checksum of its program, for example SCES-50916_6A8F18B9.pnach. You do not need to type this: with the game running, choose Tools > Edit Cheats or Tools > Edit Patches to create the file for it. Use Reload Patches (a hotkey) after editing.
Widescreen: a game made for 4:3 televisions normally looks stretched on a wide screen. A widescreen patch redraws the scene for 16:9. Turn on Apply Widescreen Patches in Settings > Graphics > Display (or in a single game's Properties). Not every game has one. The indicator at the bottom right of the window shows the patches that are active, which is how you can check it worked.
Achievements
RetroAchievements is a free service that adds achievements (goals and trophies) to classic games. PCSX2 supports it. You need a free account on its website.
Create an account on the RetroAchievements website.
In PCSX2, open Settings > Achievements.
Tick Enable Achievements, then click Login and enter your username and password. The page then says you are logged in.
Start a game. When PCSX2 scans the game, popups appear for unlocks. The Open Achievements List hotkey in Settings > Hotkeys shows the goals.
Hardcore Mode is the challenge version of achievements. It also tracks leaderboards, but it disables save states, cheats and slow-down functions, and takes effect after a system reset. It is off by default, so leave it off if you want to use save states.
Saves
There are two kinds of saves, and it matters to know the difference.
In-game saves are made with the game's own menu. They are stored on a virtual memory card, as on the real console. This is the reliable way to keep your progress.
Save states freeze the whole machine at one moment, wherever you are in the game, even where the game does not allow saving. The official guide says they are not a replacement for memory cards, are not guaranteed to work across PCSX2 versions, and burn in cheats, patches and any game error. Use them as a bookmark.
To use save states, press F1 to save to the selected slot and F3 to load it, or use the System > Save State and Load State menus. F2 selects the next slot. It worked if a message confirms the slot.
PCSX2 has two memory card types. A file card is one .ps2 file, in 8, 16, 32 or 64 MB; 8 MB is the most compatible. A folder card keeps saves in a folder on your computer, has unlimited capacity and makes saves easy to copy or delete, but some games are not compatible with it. Folder card saves do not show in the PS2 BIOS browser directly; the guide explains how to manage them with its Change Disc menu. See the memory card guide. PCSX2 includes two virtual memory cards by default.
Where files are stored: by default PCSX2 writes its data to your Documents folder; in portable mode it is next to the program. To open it, choose Tools > Open Data Directory, or Settings > Memory Cards > Browse. Cards are in the memcards folder. Copy the data folder to back up your progress. The patches and cheats folders are in the same place.
If PCSX2 shows a save state incompatibility error, the official guide says to install the exact version named in the error, load the state, save normally in the game, then go back to your current version. More details are in the general guide.
Updating
If you left Enable Automatic Updates on in the wizard, PCSX2 can offer updates itself. Otherwise download the new version from the official page. Back up your data folder first, and remember that save states may not load after an update, while memory cards do.
Common problems
No BIOS in the list: the folder set for the BIOS contains no valid dump. Check the folder and your dump.
The game list is empty: the game folder was not added, or the files are not disc images. Add the folder in the game list settings and refresh.
Black screen or the game does not load: the dump is probably corrupt. Right-click the game, choose Properties, and click Verify under the disc track list. A green check means the dump is fine; a red cross means you must dump the disc again.
The game is slow: see the performance checks above. Lower the internal resolution first and update your graphics drivers.
Glitches, missing effects or crashes after a change: put the setting back, go back to Automatic, or try Vulkan, then check the game's page in the compatibility list.
The game looks stretched on a wide screen: turn on Apply Widescreen Patches, or set the aspect ratio in the Display tab.
A save state refuses to load: it was made with another version. See the Saves section.
Anything else: update PCSX2, then read the general troubleshooting guide.
Going further
ARMSX2: based on PCSX2, for Android phones and ARM devices.
PixelArk only links to official pages. We do not provide BIOS files or keys: dump them from the hardware you own.
Logos are trademarks of their respective owners, shown only to identify each project.