✅ Updated Nov 2026
Affiliate Disclosure: As an Amazon Associate, we earn from qualifying purchases. Links marked "Check on Amazon" are affiliate links — learn more.
⭐ Key Takeaways
Quick answer: Our top pick is SanDisk Ultra Flair 32 GB USB 3.0 Flash Drive, with Zerone 128 MB Memory Card for PS2 as a strong alternative.

Every PlayStation 2 memory card save is trapped on the console side of the fence. The card has no connector a PC can read, and the console’s own browser copies saves only between cards, never off them. The way out is homebrew on the console itself: a Free McBoot card lets the PS2 launch uLaunchELF, a file browser that sees the memory card and a USB stick at the same time.

As an Amazon Associate, we earn from qualifying purchases.

This guide walks the hardware side of that bridge: what Free McBoot is and how a card gets one, how to prepare a USB stick the PS2 will actually read, how uLaunchELF packages a save into a single transfer file, and what to do with that file on the PC so it ends up inside PCSX2.

This article contains affiliate links; if you buy through them we may earn a commission at no extra cost to you.

Quick Answer

Boot uLaunchELF from your Free McBoot card, open the memory card in its FileBrowser, mark your save, choose Copy, then psuPaste it onto a FAT32 USB stick as one .psu file. On the PC, open that file with PS2 Save Builder or import it with mymc, and the save lands in PCSX2 ready to load.

The Key That Opens the Console: Free McBoot

Free McBoot, usually shortened to FMCB, is an exploit installed on a memory card itself. It installs as a signed system update, which is why it needs a card with accurate MagicGate support — official Sony cards are the reliable choice, as some third-party cards cannot hold the required per-card signature. With an FMCB card inserted, the PS2 boots to its normal browser with extra menu entries added, and those entries launch homebrew such as uLaunchELF.

Two limits matter first. FMCB does not work on consoles running firmware 2.30 or 2.50, which covers most late SCPH-90000-series slims and the PS2 TV; the ConsoleMods wiki documents OpenTuna as the alternative there. And installing FMCB has a bootstrap problem: launching its installer once itself needs a way to run unsigned code. The documented routes are a pre-configured card bought or borrowed ready-made, the FreeDVDBoot burned-disc exploit, a second already-modded console, or a modchip’s DEV1 boot mode. This guide starts from a working FMCB card.

Step One: Prepare a USB Stick the PS2 Can Read

uLaunchELF’s documentation lists FAT12, FAT16 and FAT32 read/write support for USB storage, with one catch: only the first readable partition is used. In practice the reliable recipe is a stick formatted FAT32 with an MBR partition table. NTFS, exFAT and GPT drives typically show up empty or freeze the browser — the most common reason this transfer appears broken.

Keep the stick modest, and format it on your PC first — the PS2’s USB ports are USB 1.1-era hardware, plain smaller sticks behave best, and formatting erases the stick.

Step Two: Package the Save With uLaunchELF

Launch uLaunchELF from the FMCB menu and open its FileBrowser. Devices appear under short names: mc0:/ is the memory card in slot 1, mc1:/ is slot 2, mass:/ is the USB stick, and cdfs:/ is the disc in the drive. Browse into mc0:/ and you will see one folder per save, each displayable by game title read from its icon file.

Mark the save folder with Cross (Cross marks several at once for batch trips), then press R1 to open the operations menu and choose Copy. Browse to mass:/, open the R1 menu again, and choose psuPaste. That choice is the heart of this guide. A plain Paste copies loose files and drops the card attributes and timestamps that are part of the save. mcPaste, the older option, preserves those attributes but leaves you with a folder of files. psuPaste does both jobs: it writes the save as one self-contained .psu file, attributes included, that PC tools can open directly.

One caution from the uLaunchELF documentation: a few games validate saves partly by timestamp, so keep the original save untouched on the card and work on copies.

What a .psu File Actually Is

The .psu format began as the EMS USB save format, and a .psu file is best understood as the save’s folder, sealed. Inside the single file sit the save’s directory name, every file that was in it, and the memory card attributes and timestamps for each entry, all uncompressed.

That design explains two behaviours that confuse people. The save’s identity lives inside the file, in its folder name and data — renaming the .psu on your PC changes nothing about which game or regional edition it belongs to. And a .psu is not tied to its source card: it unpacks onto any card or card image, as long as the game matches the save’s edition.

Step Three: Convert the File and Land It in PCSX2

On the PC, two free tools cover every destination. PS2 Save Builder is the format workshop: it opens save containers in the common formats — .psu, .max, .xps, .cbs and others — shows the files inside, and can extract them as a plain folder or re-save the save in a different container format. That covers the awkward cases: a save that arrived as a Code Breaker .cbs from a cheat disc, or an old Action Replay .max archive, can be re-saved as a .psu every other tool accepts.

For a PCSX2 file card, mymc finishes the job: it opens the card image and imports the .psu directly. Its author documents two warnings worth repeating — it edits card images in place, so always open a backup copy, and it exports only .max and .psu despite importing more formats.

Folder memory cards skip mymc entirely. A folder card stores each save as an ordinary folder on your PC, named for the save itself. Extract the .psu’s contents with PS2 Save Builder and place the save folder inside the folder card’s directory. PCSX2 then sees it as a save that was always on that card. Either way, boot the game and confirm the save appears in its load menu before calling the transfer done.

The Reverse Trip: PC Saves Back to Real Hardware

Sending a save the other way is the same road reversed. Export it from PCSX2 as a .psu — from mymc with a file card, or by packing the save’s folder with PS2 Save Builder with a folder card. Copy the .psu onto the FAT32 stick, boot uLaunchELF, mark the file on mass:/, choose Copy, then browse to mc0:/ and psuPaste. uLaunchELF unpacks it into a normal save folder on the real card.

Before pasting, check the card has free space — and if a save for the same game edition already exists on it, export that save to the stick first, because the paste overwrites it.

The Hardware That Makes the Trip Easier

SanDisk Ultra Flair 32 GB USB 3.0 Flash Drive

SanDisk Ultra Flair 32 GB USB 3.0 Flash Drive

SanDisk Ultra Flair 32 GB USB 3.0 Flash Drive

Check price on Amazon

The shuttle for the console leg. Its small capacity is exactly the point: a stick this size formats to FAT32 without argument and is the class PS2 USB hardware handles most predictably.

Specs:
– Model SDCZ73-032G-G46, 32 GB capacity
– USB 3.0 interface, backward compatible with USB 2.0
– Read speeds up to 150 MB/s on a PC
– Metal casing

See it on Amazon

Zerone 128 MB Memory Card for PS2

Zerone 128 MB Memory Card for PS2

Zerone 128 MB Memory Card for PS2

Check price on Amazon

A spare card earns its keep twice here: an FMCB install can be written to it without touching your original card, and later it serves as a safe paste target that never holds your only copy of anything.

Specs:
– 128 MB capacity
– Compatible with PlayStation 2 fat and slim models
– Works with Free McBoot setups
– Plug and play, no drivers or setup

See it on Amazon

SanDisk 256 GB High Endurance microSDXC Card

SanDisk 256 GB High Endurance microSDXC Card

SanDisk 256 GB High Endurance microSDXC Card

Check price on Amazon

SD-based memory card devices for the PS2 store their virtual cards on microSD, and wLaunchELF lists those devices alongside real cards. A high-endurance card suits that always-in-the-console duty, and doubles as storage for a library of .psu exports.

Specs:
– Model SDSQQNR-256G-GN6IA, 256 GB capacity
– Class 10, U3 and V30 speed ratings
– Read speeds up to 100 MB/s
– Rated for continuous recording workloads

See it on Amazon

UGREEN USB 3.0 SD Card Reader

UGREEN USB 3.0 SD Card Reader

UGREEN USB 3.0 SD Card Reader

Check price on Amazon

When a save lives on the microSD inside an SD-based card device, this reader is how the PC side reaches it: pull the card, read it directly, and copy .psu files or virtual-card backups without booting the console.

Specs:
– Model 40752
– USB 3.0 interface, up to 5 Gbps
– SD and microSD slots, UHS-I support
– Works with Windows, macOS and Linux

See it on Amazon

Samsung T7 Portable SSD 1 TB

Samsung T7 Portable SSD 1 TB

Samsung T7 Portable SSD 1 TB

Check price on Amazon

The archive at the end of the workflow. Card images, folder-card directories and years of .psu exports occupy a small corner of this drive, and a fast, separate archive makes the back-up-first rule effortless.

Specs:
– Model MU-PC1T0T/AM, 1 TB capacity
– USB 3.2 Gen 2 interface
– Read speeds up to 1,050 MB/s
– AES 256-bit hardware encryption

See it on Amazon

How to Choose

Choose the psuPaste route described here if your saves start on a real card and you want them preserved exactly, attributes and all. It is the only route where the console itself does the packaging.

Choose PS2 Save Builder as your centre of operations if your saves arrive in mixed formats — cheat-device archives, downloads from the .max era, .psu files from the console. Converting everything to one format before it touches PCSX2 prevents most surprises.

For the landing, choose the folder-card route if you live in PCSX2 day to day; extracting a save folder is the shortest path. Choose mymc if you prefer one card image you can back up as a single file.

Who Should Skip

Skip this if your PS2 is one of the late slims on firmware 2.30 or 2.50 and you have no other way to run homebrew — FMCB will not boot, and the console leg depends on it. Look at OpenTuna or an SD-based card device first. Skip it, too, if you never play on real hardware: saves born in PCSX2 need no transfer. And if your card holds the only copy of a save you care about, duplicate it by any route available before experimenting.

FAQ

Can I just copy the save folder with a plain Paste?

You can, but you should not. A plain Paste drops the memory card attributes and timestamps that form part of the save, and some games validate them. psuPaste preserves everything and produces the file PC tools expect.

My USB stick shows up empty in uLaunchELF. What is wrong?

Almost always the formatting. uLaunchELF reads FAT12, FAT16 and FAT32 and uses only the first readable partition; in practice it wants FAT32 with an MBR partition table. NTFS, exFAT and GPT drives appear empty or freeze the browser. Reformat the stick on your PC and try again.

Does mymc work with folder memory cards?

No — mymc opens file-card images only. For a folder card, extract the .psu’s contents with PS2 Save Builder and place the save folder in the folder card’s directory instead.

Will a transferred save work with any copy of the game?

Only the edition it was made with: the save’s identity and regional product code are stored inside the .psu, and the game enforces the match. A North American save will not load in the European release, in PCSX2 or on hardware.

Final Verdict

The hardware side of PS2 save transfer is a three-part chain, and every part is free: Free McBoot to open the console, uLaunchELF’s psuPaste to seal a save into a .psu with its attributes intact, and PS2 Save Builder or mymc to land it in PCSX2. The failure points are mundane — a wrongly formatted stick, a plain Paste, a mismatched game edition — and all avoidable. Keep your original card untouched, work on copies of your own saves, and they travel both directions as often as you like.

Explore Our Guides & Free Tools