PS2 Memory Card Compatibility for FreeMCBoot: Official 8MB vs Clone Cards

The memory card is the whole of FreeMCBoot (FMCB). The softmod lives on the card, boots from the card, and fails if the card does not behave the way the console expects. The direct answer is this: a Sony 8MB card is the reference choice for an FMCB install, because FMCB depends on the card’s authentication behaviour, while high-capacity clone cards, especially generic 64MB and 128MB cards, often do not reproduce that behaviour reliably and are the most common hardware cause of a card that installs but does not boot, or boots once and then corrupts. If you want the least troubleshooting, install FMCB on a Sony 8MB card and keep your game saves on a second card.

That advice sounds conservative, and it is deliberately so. Memory cards are cheap compared with the time spent diagnosing a flaky install, and the card is the one component where saving money most often creates problems. This post explains why, what the capacity numbers actually mean, and how to set up cards so that system files and saves do not compete.

Why FMCB is picky about cards

A PS2 memory card is not just flash storage with a PS2-shaped connector. It participates in an authentication exchange with the console, and FMCB’s boot process depends on that exchange behaving correctly. Sony’s own cards implement it as designed. Clone cards implement it by imitation, and the quality of that imitation varies enormously between manufacturers, batches, and even individual cards from the same listing.

That variation explains the pattern people report: one clone card works, another identical-looking clone card does not; a card boots FMCB but loses saves; a card works for saves but will not hold an FMCB install. None of that means the user did the install wrong. It means the card’s imitation of the authentication behaviour is incomplete or inconsistent. The problem is also why “just buy a bigger card” is poor advice for FMCB. Capacity is not the constraint. Correct behaviour is.

Capacity: what the numbers mean and do not mean

The key point is that FMCB itself needs only a small amount of space. A larger card does not make FMCB faster, more compatible, or more capable. It only adds save space, and save space belongs on a second card anyway. Buying a 128MB clone card for FMCB is therefore paying for capacity you do not need on the system card, while accepting the highest risk category for the install itself.

There is a separate, legitimate use for a large card: holding many saves, or holding saves for many games in one place. That use is fine, but it should be on a different card from the FMCB install. If the large card fails, you lose saves, which is annoying. If the FMCB card fails, you lose the whole softmod menu until you reinstall, which is a bigger interruption. Separating the two jobs limits the damage from either failure.

The two-card setup

The setup recommended across this site is simple, and it solves several problems at once.

1. Slot 1, or your chosen system slot: the FMCB card. A Sony 8MB card with the FMCB install and nothing else competing for attention. Do not fill it with saves if you can avoid it.
2. The other slot: the save card. Your existing save card, or a second card of whatever capacity you prefer for saves. If this card is a clone and it misbehaves, the symptom is limited to saves, and the FMCB menu still boots so you can diagnose the problem with homebrew tools.
3. A spare blank card, if you can manage it. A blank PS2 memory card is useful for testing: if FMCB stops booting, try a fresh install on the spare before assuming the console is at fault.

This setup also helps with the install process itself. The installer needs a card to write to, and having a dedicated target means you are not risking a card full of saves you care about during formatting. Formatting erases the card, and that warning applies to whichever card you select in the installer, so double-check the slot before confirming.

Diagnosing card problems

Use this order, because it separates card problems from console and install-type problems.

• FMCB never appears, on a clone card: Try a Sony 8MB card with a fresh install for your console before changing anything else. If the Sony card boots, the clone card was the problem.
• FMCB appears sometimes, or after several power cycles: Suspect the card’s authentication behaviour or a worn connector. Try the other slot, wipe the contacts gently, and test a known-good card.
• FMCB boots, but saves disappear or corrupt: Suspect the save card, not the FMCB card, if they are separate. If they are the same card, separate them and retest.

One caution about testing: do not keep reformatting and reinstalling on the same suspect card and concluding the installer is broken. The installer is rarely the variable. The card is.

Buying advice without brand promises

This site does not recommend specific clone-card brands, because clone-card quality varies by batch and a recommendation that was accurate for one batch can be wrong for the next. The durable advice is structural: buy a Sony 8MB card for the FMCB install, buy capacity for saves separately, and avoid listings whose main selling point is enormous capacity on a single card for FMCB use. Also avoid any listing that sells a card by claiming it already contains FMCB or a game library. A card you prepare yourself from the v1.966 package on /download/ is a known quantity; a card whose contents were prepared by an unknown seller is not, and this site does not link to preloaded cards.

For second-hand Sony cards, check the obvious things: the card is recognised by the console’s browser, it formats without errors, and it holds a test save across a power cycle before you trust it with an install. A card that cannot reliably hold a save should not be trusted with a system install.

FAQ

Is a Sony 8MB card required for FreeMCBoot? Not strictly required, but it is the reference choice and the lowest-risk option. Some third-party cards work, but their behaviour varies, and troubleshooting is harder when the card itself is a variable.

Why do 64MB and 128MB clone cards fail so often? Because FMCB depends on the card’s authentication behaviour, and many high-capacity clone cards do not reproduce it reliably. Capacity is not the issue; the imitation of the authentication behaviour is.

Can I use one big card for FMCB and saves together? You can, but it is not recommended. Separating the system card from the save card limits the damage when either card misbehaves, and it keeps formatting during installation from threatening your saves.

My clone card works for saves but not for FMCB. Is that normal? Yes. Saving a game and booting FMCB exercise the card differently. A card can pass the easier job and fail the harder one.

Some links on this page are affiliate links; we may earn a commission at no extra cost to you. See our Affiliate Disclosure.

FreeMCBoot vs PCSX2: Do You Need a Memory Card Exploit for the Emulator?

No, you do not need FreeMCBoot (FMCB) to use PCSX2. That is the whole answer in one sentence, and it is worth stating first because the two names appear together so often in search results. FreeMCBoot is a memory card softmod for a real PlayStation 2. PCSX2 is a PlayStation 2 emulator that runs on a PC. They solve different problems, they run on different hardware, and installing FMCB on a PS2 memory card does nothing for PCSX2 on your computer, just as installing PCSX2 on your computer does nothing for a real PS2.

The confusion is understandable. Both are associated with playing PS2 games without relying on original discs in the traditional way, both are discussed in the same forums, and both involve homebrew and loaders. But the hardware boundary is absolute: FMCB code runs on PS2 hardware from a PS2 memory card, and PCSX2 code runs on PC hardware. Neither can substitute for the other, and neither requires the other.

What each one actually is

FMCB was created by Neme and jimmikaelkael and maintained by SP193. It replaces the PS2’s standard browser behaviour with a custom menu from which you can launch homebrew, including Open PS2 Loader (OPL) for loading your own dumps from USB, a network share, a hard drive, or an MX4SIO card. PCSX2, by contrast, is a separate, independently developed emulator. It does not read an FMCB card, it does not boot from an FMCB install, and its compatibility with a given game has nothing to do with whether that game loads through OPL on real hardware.

When to choose real hardware with FMCB

Choose FMCB when the point is the real console itself. That includes playing on original hardware with original controllers on a television, using a Fat console’s internal hard drive, using light-gun or accessory hardware that only makes sense on a console, or preserving and using a PS2 you already own. FMCB is also the right choice when you want a setup that is independent of a PC: once the card is installed, the console is self-contained, and you do not need a computer nearby to play.

The limits are the ones described across this site. FMCB boots directly on most Fat and Slim consoles, but late SCPH-90000 Slims and the PS2 TV need a Fortuna or FunTuna trigger instead, as detailed in FreeMCBoot Compatibility List. FMCB alone does not add import-disc support, as explained in What FreeMCBoot Cannot Do. And USB loading on real hardware runs through the PS2’s USB 1.1 ports, so it is slower than loading on a modern PC.

When to choose PCSX2 on a PC

Choose PCSX2 when the point is convenience, visual enhancement, or a PC-centred setup. Emulation lets you play on a monitor you already use, use PC controllers and save states where the emulator supports them, and render at higher resolutions than original hardware. It also removes the need to maintain ageing console hardware, a failing disc drive, or a specific memory card.

PCSX2 has its own requirements that have nothing to do with FMCB. It needs a reasonably capable PC, its own configuration, and system files and game dumps sourced from hardware you own. This site does not provide or link to BIOS files or game images, and the same rule applies here as everywhere else: use only your own dumps. If a guide tells you to install FMCB as a step in setting up PCSX2, it is either describing a method for dumping files from a real console, which is a separate task from running the emulator, or it is conflating two unrelated tools.

Can the two work together at all?

There are narrow, indirect connections, and they are worth naming so they are not overstated. A real PS2 with FMCB can be used as part of a workflow for dumping your own games or saves, because homebrew on the console can read discs and cards. That is a dumping workflow, not a requirement for emulation, and many PCSX2 users never touch a real PS2 at all. Similarly, knowledge transfers between the two worlds: understanding OPL loading routes helps you understand game formats, and understanding emulator settings helps you diagnose why a game behaves differently on hardware versus emulation. But neither tool depends on the other, and a problem in one is not diagnosed by fixing the other.

A practical example makes the boundary clear. If a game shows a black screen in OPL on a real PS2, check file layout, loading route, and loader settings. If the same game glitches in PCSX2, check emulator settings, renderer choice, and PC hardware. A fix from one world rarely applies to the other, because the loading path is completely different.

Decision guide

• You want to play on a real PS2 on a television: Use FMCB on a supported console, with a loading route from OPL Loading Compared: USB vs SMB vs HDD vs MX4SIO.
• You want to play on a PC with enhancements: Use PCSX2, and ignore FMCB entirely for that setup.
• You own both and want both: Treat them as two separate setups with separate troubleshooting. Do not expect a fix or a file from one to apply to the other.
• You are deciding what to buy: Do not buy a PS2 or a memory card for the sake of PCSX2, and do not buy a PC upgrade for the sake of FMCB. Buy for the setup you actually intend to use.
• You already have FMCB and want to try emulation: Start PCSX2 as a fresh setup on its own terms. Your FMCB card stays in the console; it plays no role on the PC.

If your decision is real hardware, the starting point is the same as elsewhere on this site: confirm compatibility, choose a loading route, and get the v1.966 package from /download/.

FAQ

Do I need FreeMCBoot to run PCSX2? No. PCSX2 runs on a PC and does not use, read, or require an FMCB install.

Can I use my FMCB memory card with PCSX2? No, not as an FMCB card. PCSX2 does not boot from PS2 memory cards, and FMCB code runs on PS2 hardware, not on a PC.

Is a game that works in PCSX2 certain to work with OPL on a real PS2? No. Emulator compatibility and real-hardware loader compatibility are separate matters, with different causes for the same symptom.

Can FMCB help me dump my own games for PCSX2? Homebrew on a real PS2 can be part of a dumping workflow, but that is a separate task from running the emulator, and it is not a requirement for using PCSX2.

Which looks better, real hardware or PCSX2? It depends on what you value. Real hardware gives you original behaviour on a television; PCSX2 gives you PC rendering options and convenience. Neither is universally better, and the choice is about the setup, not about one tool being a version of the other.

FreeMCBoot Cross-Region Installs Explained: Normal, Cross-Model, and Multi-Install

A FreeMCBoot (FMCB) card that works perfectly on one PlayStation 2 and does nothing on another is usually not a broken card. It is usually an install made for the wrong console. The direct answer is this: a normal FMCB install is tied to the region and model family of the target console, a cross-model install widens that match to related models, and a multi-install covers several targets at once, but none of these install types changes the console’s region behaviour for original discs. If you want a card that boots on your console, install for that console, test on that console, and treat cross-region installs as a deliberate choice with trade-offs, not as a universal card.

FMCB v1.966, created by Neme and jimmikaelkael and maintained by SP193, works by replacing the standard browser behaviour with files on the memory card that match the console’s system files. That matching is why region and model matter. The console checks the card’s files against its own region and model information, and a mismatch means the custom menu simply does not appear. The installer therefore offers different install types, and understanding them is more useful than memorising which card worked for someone else online.

The three install types, plainly explained

Normal install. This is the default and the right choice for most people. The installer prepares the card for the specific console you are installing from or for, matching its region and model family. A normal install is the simplest and most predictable option when you know exactly which console will use the card. If you only have one PS2, or one PS2 you care about, use a normal install for that console and stop there.

Cross-model install. This widens the match so the card can boot on related models within the same broader family. It exists for people who move a card between similar consoles, for example between two Fat consoles or between related Slim models. The trade-off is that “related” is doing real work in that sentence: a cross-model install is not a promise that the card will boot on every PS2 ever made, and it does not bridge the late-model gap described below.

Multi-install. This prepares the card for several targets at once. It is the most flexible option and the one most likely to be recommended by people who install cards for friends or for multiple consoles in one household. The trade-off is complexity: more targets on one card means more ways for a single mistake to affect the result, and it still does not make the card universal. A multi-install also uses more of the card, which is another reason to use a dedicated card for FMCB rather than trying to combine system files and a large save library on one card.

None of these types should be confused with region-free disc playback. Installing FMCB for a console in another region does not make that console play original discs from other regions. That limit is a hardware matter, explained in What FreeMCBoot Cannot Do, and it applies regardless of install type.

Why a card boots on one console and not another

When a card fails on a second console, work through this list before assuming the card or the console is faulty.

The first row is by far the most common. People install on a friend’s console, take the card home, and conclude the install failed. In most cases the install succeeded exactly as asked; it was simply asked for the wrong target.

The late-model boundary is not a region problem

Late SCPH-90000 Slims with boot ROM 2.30 or newer, and the PS2 TV, do not boot standard FMCB at all, whatever install type you choose. Sony removed the update behaviour FMCB relies on from those consoles, and no normal, cross-model, or multi-install changes that, because the limitation is in the console’s read-only BIOS behaviour, not in the card’s region matching. The route for those consoles is Fortuna or FunTuna, a manual trigger from the on-screen browser, compared in FMCB vs Fortuna, FunTuna, and OpenTuna.

This distinction matters when diagnosing a failure. If the second console is a late Slim, switching install types will not fix it. Check the model, datecode, and ROM version first, using the matrix in FreeMCBoot Compatibility List. If the console is in the late group, change the route, not the install type.

Practical advice for each situation

One console, your own. Use a normal install for that console. Keep the card dedicated to FMCB and saves on a second card. Two or three consoles in one household. Consider a multi-install, but list the consoles, models, and regions first, then test the card on every console on the list before relying on it. Installing for someone else. Install for their console, not yours, or use a multi-install that explicitly includes their console. Buying a card second-hand. Treat the install type as unknown until tested. If it does not boot on your console, plan a fresh install for your console. When you need a blank card for that fresh install, a PS2 memory card gives you a fresh starting point.

Checklist

1. Write down each target console’s model, region, and, for 90000 Slims, ROM version.
2. Choose normal for one known console, cross-model for related models, multi-install for a known list of targets.
3. Do not expect any install type to add import-disc support or to fix late-model boot behaviour.
4. Test the card on every console it is meant to serve.
5. Get the v1.966 package from /download/ and keep saves on a separate card.

FAQ

What is the difference between a normal and a multi-install? A normal install targets one console’s region and model family. A multi-install prepares the card for several targets at once. Multi-install is more flexible but more complex, and it is still not universal.

Will a cross-model install make my card work on any PS2? No. It widens the match to related models, but it does not cover every model, every region combination, or late Slims, which need a different trigger entirely.

Can I install FMCB for a console in another region to make it region-free? No. The install type affects which consoles the card boots on. It does not change how a console treats original discs from other regions.

My card works on my friend’s PS2 but not mine. Is the card broken? Probably not. The most likely explanation is that it was installed for your friend’s console. Reinstall for your console, or use a multi-install that includes yours, and test it there.

Some links on this page are affiliate links; we may earn a commission at no extra cost to you. See our Affiliate Disclosure.

What FreeMCBoot Cannot Do: Imports, Backups, and Honest Limits

FreeMCBoot (FMCB) v1.966 is a memory card softmod that lets a PlayStation 2 launch homebrew from a card. That is a powerful capability, and it is also a bounded one. The honest summary is this: FMCB changes what software the console will launch from its own menu, but on its own it does not change the console’s region behaviour, it does not bypass the hardware limits that govern original discs, and it does not turn the PS2 into a different machine. Knowing those limits before you install saves more frustration than any feature list, because most disappointment with FMCB comes from expecting it to do something it was never designed to do.

FMCB was created by Neme and jimmikaelkael and maintained by SP193 through the 1.9 series. The author’s own FAQ states the limit plainly: FMCB and FHDB alone will not let you play imported games, because that is a hardware limitation that FMCB alone cannot and will not circumvent, and the same applies to burned or pirated discs. This post explains what that means in practice, and what separate tools do and do not add.

Imports: FMCB alone does not change region behaviour

A PS2 is region-locked for original discs by hardware. Installing FMCB does not remove that lock. If you insert an original disc from another region into a console with only FMCB installed, the console will still refuse it in the same way it did before. This surprises people because FMCB feels like a complete transformation of the console, but the transformation is at the menu and launcher level, not at the region-check level.

That does not mean region is irrelevant to FMCB in other ways. FMCB installs themselves are region-aware: the install type must match the target console, and cross-region installs are a separate topic with their own pitfalls, covered in FreeMCBoot Cross-Region Installs Explained. The distinction to keep is between running homebrew, which FMCB enables, and changing how the console treats original discs from other regions, which FMCB alone does not do.

If imported original discs are your main goal, you need to research that goal separately rather than assuming FMCB covers it. Some users combine FMCB with other approaches, and some use a hardware modification, compared in FreeMCBoot vs Modchip. Either way, treat “FMCB equals region-free” as a claim to be sceptical of wherever you read it.

Backups and burned discs: FMCB is not a disc loader

A related misunderstanding is that installing FMCB automatically lets the console play burned discs. It does not. FMCB launches homebrew from the memory card; it does not by itself change how the disc drive authenticates a disc. Disc-based loading is handled by separate tools with their own requirements and limits, and those tools are not part of the v1.966 package.

That separation matters for two reasons. First, if a guide promises that FMCB alone unlocks disc backups, it is conflating FMCB with other tools. Second, the correct way to think about game loading with FMCB is through loaders: OPL loads your own game dumps from USB, a network share, a hard drive, or an MX4SIO card, while ESR is a separate program for discs prepared in DVD-video format. Those loaders are compared in OPL vs ESR vs HDLoader, and the loading routes are compared in OPL Loading Compared: USB vs SMB vs HDD vs MX4SIO.

Throughout this site, “your own dumps” means games you own and have dumped yourself. This site does not link to game images, BIOS files, or preloaded drives or cards, and you should treat any source offering those as a separate matter from FMCB itself.

What FMCB does not include

Because the v1.966 package is often described as if it were a complete homebrew suite, here is the correction in one place.

The exFAT point deserves emphasis because it appears on many download pages. FMCB v1.966 does not itself add exFAT support to the console. When people talk about loading large files from exFAT drives with an FMCB setup, they are talking about what modern OPL builds can do once launched. Attributing exFAT to FMCB is a category error, and it leads people to expect exFAT handling during installation, where it does not apply.

Hardware limits FMCB does not remove

FMCB runs within the PS2’s hardware, and the hardware’s limits still apply.

• USB speed: The PS2’s USB ports are USB 1.1. FMCB does not make them faster. USB loading works, but it is slow compared with network or hard drive loading, and that is a hardware fact, not a configuration mistake.
• Late-model boot behaviour: On late SCPH-90000 Slims and the PS2 TV, FMCB does not boot on its own at all, because Sony removed the update behaviour it relies on. The route there is a Fortuna or FunTuna trigger, not a stronger FMCB install. See FreeMCBoot Compatibility List.
• Disc drive condition: FMCB does not repair a failing laser or drive mechanism. If you need a disc entry point for the first install, a dead drive is still a problem, even though disc-free loading afterwards does not need the drive.
• Memory card authentication: FMCB depends on the card’s authentication behaviour. That is why a Sony 8MB card is the reference choice and why some high-capacity clone cards fail, as explained in PS2 Memory Card Compatibility for FreeMCBoot.
• No online or system update: FMCB does not add online features, system updates, or compatibility with later PlayStation consoles. It is a PS2 menu and launcher exploit, nothing broader.

What FMCB does well, stated without exaggeration

Within those limits, FMCB does something genuinely useful: it gives a supported PS2 a persistent homebrew menu without opening the console or soldering anything. From that menu you can launch a file manager, a loader for your own dumps, emulators for older systems, and other homebrew programs. On Fat consoles you can also boot from an internal hard drive through FHDB. That combination, persistent but removable, is the real appeal, and it does not need exaggerated claims to be worthwhile.

Checklist: set expectations before installing

1. Confirm your console is in a direct-boot group, or plan for Fortuna/FunTuna if it is a late Slim.
2. Decide which loader and loading route you will use, because FMCB alone does not load games.
3. Add OPL, uLaunchELF, or other homebrew separately; do not expect them inside the v1.966 package.
4. Use only your own dumps, and do not look to FMCB for import or disc-bypass features it does not provide.
5. Get the package from /download/ and install for the console you will actually use.

FAQ

Does FreeMCBoot make my PS2 region-free? No, not on its own. FMCB alone does not change how the console treats original discs from other regions, which is a hardware limitation.

Does the v1.966 download include OPL and uLaunchELF? No. The package contains only what FMCB itself needs. OPL, uLaunchELF, and ESR are separate programs that you add yourself or obtain through a bundle.

Does FMCB add exFAT support to my PS2? No. exFAT loading is a feature of modern OPL builds. FMCB launches the loader; the loader handles the filesystem.

If FMCB cannot do those things, why install it? Because what it does do is still substantial: a persistent, removable homebrew menu on a supported console, from which you can launch loaders, file managers, and other homebrew for your own library.

Fat vs Slim PS2 for FreeMCBoot: Which Route to Choose

If you already own a PlayStation 2, the Fat versus Slim question is mostly answered for you: use the console you have, and pick the loading route that fits it. If you are choosing a console to buy or to set up for FreeMCBoot (FMCB) v1.966, the difference comes down to one thing. Fat consoles can take an internal hard drive, while Slim consoles cannot, so Slim setups rely on USB, a network share, or a memory-card-slot adapter. FMCB itself boots directly on most Fat consoles and most Slim consoles, with the important exception of late SCPH-90000 Slims, which need a Fortuna or FunTuna trigger instead.

That distinction is worth stating plainly, because a lot of buying advice treats “Slim” as a single category. It is not. An early Slim and a late Slim can need completely different approaches, and the full model breakdown is in FreeMCBoot Compatibility List. This post compares the two hardware families so you can choose a route, not just a console shape.

Boot behaviour: mostly the same, with one exception

FMCB is a memory card softmod that replaces the standard browser behaviour with a custom menu. On a supported console, you insert the card, power on, and the FMCB menu appears. That behaviour is the same on Fat consoles and on supported Slim consoles. There is no Fat-only or Slim-only version of FMCB v1.966 to choose between; the same package and installer apply, and the install type you select in the installer matters more than the console’s size.

The exception is the late Slim group: SCPH-90000 consoles from the third quarter of 2008 onwards, identified by datecode 8C and later and by boot ROM 2.30 or newer. Those consoles do not boot FMCB on their own, because Sony removed the update behaviour FMCB relies on. The route for those consoles is Fortuna or FunTuna, which you trigger manually from the on-screen browser by selecting the memory card and backing out to the main menu. It works, but it is a different daily experience from auto-boot, and you should factor that in before you choose a late Slim deliberately. The PS2 TV sits in the same late-model group.

Early Fat consoles deserve one footnote. The Fortuna family was not ported to the earliest SCPH-10000 and SCPH-15000 models, but those consoles are in the FMCB direct-boot group, so this only matters when you are comparing trigger options, not when you are deciding whether FMCB itself applies.

Loading routes compared

Once FMCB or a Fortuna-family trigger is running, you still need a way to load homebrew and your own game backups. This is where Fat and Slim diverge in practice.

The Fat advantage is the internal drive. It keeps everything inside the console, avoids the PS2’s slow USB ports for loading, and, through FHDB, can even boot from the drive itself rather than from a card. The trade-offs are a network adapter, a drive, setup time, and the FHDB capacity caveat covered in FMCB vs FHDB.

The Slim advantage is simplicity and size. Every Slim has a built-in network port, so network-share loading needs no adapter, and USB loading needs nothing more than a drive. The drawback is that USB loading runs through USB 1.1 ports, which are slow and picky about modern drives, so many Slim owners later move to a network share or MX4SIO.

Disc drive, video output, and controllers

Two practical differences have nothing to do with FMCB and everything to do with living with the console. Fat consoles have a disc tray and a larger, noisier drive mechanism that is now old enough to be a failure point on many units. Slim consoles have a top-loading drive that is simpler mechanically, but the laser still ages on both families. If you need a disc-based entry point, such as FreeDVDBoot, to install FMCB in the first place, the condition of the drive matters more than whether the console is Fat or Slim. See FreeMCBoot vs FreeDVDBoot for how entry points work.

Video output is the same on both families: the PS2 outputs analogue signals, and most modern setups use a component cable or a PS2-to-HDMI converter. Controllers are shared too: a standard DualShock 2 works on both, and a replacement DualShock 2 controller fits either console.

Which route should you choose?

Use this decision list rather than a single recommendation, because the right answer depends on the console in front of you.

• You own a Fat console: Start with FMCB on a card, then decide between USB loading for simplicity and an internal drive for a larger library. The internal drive is the Fat’s distinctive advantage, but it is optional, not required.
• You own an early or mid Slim (70000 to 790xx, or a 90000 with ROM below 2.30): Start with FMCB on a card and USB loading, then move to a network share or MX4SIO if USB speed or drive compatibility frustrates you.
• You own a late 90000 Slim (ROM 2.30 or newer): Plan for Fortuna or FunTuna from the start, with the manual trigger as part of the daily routine. Do not buy accessories assuming standard FMCB auto-boot.
• You are buying a console specifically for this: A Fat console gives you the most routes, including the internal drive, while an early Slim gives you the smallest footprint with standard FMCB boot. A late Slim is fine if you accept the manual trigger, but it should be a conscious choice, not a surprise. For second-hand consoles, eBay PS2 listings are one place to check condition and included accessories before you commit.

Whichever family you choose, keep the FMCB card dedicated to that job and keep game saves on a second card.

Checklist

1. Confirm your model, datecode, and ROM version using the matrix in the compatibility list.
2. If the console is a late 90000 Slim, choose the Fortuna/FunTuna route and accept the manual trigger.
3. Pick a loading route: USB for simplicity, network share for speed without new hardware, internal drive for Fat libraries, MX4SIO for card-slot loading.
4. Check the disc drive only if you need a disc entry point for the first install.
5. Get the v1.966 package from /download/ and install for the console you will actually use.

FAQ

Is FMCB better on Fat or on Slim? Neither, for FMCB itself. Boot behaviour is the same on supported consoles of both families. The difference is in loading routes, where Fat adds the internal drive option.

Can a Slim use an internal hard drive? No. Slim consoles have no internal drive bay. Their routes are USB, network share, or MX4SIO.

Does a Slim need a network adapter for network loading? No. Slim consoles have a built-in network port. Fat consoles need a network adapter for both network loading and internal drive use.

Should I avoid late 90000 Slims entirely? Not necessarily, but go in with open eyes. The Fortuna/FunTuna trigger works, it just requires a manual step every time, where standard FMCB boots on its own.

Some links on this page are affiliate links; we may earn a commission at no extra cost to you. See our Affiliate Disclosure.

FreeMCBoot Compatibility List: Every PS2 Model, Datecode, and ROM Version

FreeMCBoot (FMCB) v1.966 runs on almost every PlayStation 2, but not on every one in the same way. The short answer is this: most Fat consoles and most Slim consoles boot FMCB directly from a memory card, while late SCPH-90000 Slims with boot ROM 2.30 or newer, and the PS2 TV, do not boot FMCB on their own and need a different trigger, such as Fortuna or FunTuna. If you are unsure about your console, check its model number, its datecode, and its ROM version before you install anything, because those three details decide which route applies to you.

FMCB is a memory card softmod. It was created by Neme and jimmikaelkael and has been maintained by SP193 through the 1.9 series, with v1.966, released on 2019-04-13, as the latest stable release. It replaces the standard on-screen browser behaviour with a custom menu that can launch homebrew from the card. It does not replace the console BIOS, and removing the card returns the console to its standard behaviour. That design is why model details matter so much: FMCB depends on the console’s built-in update and browser behaviour, and Sony changed that behaviour in late production runs.

How to identify your console

Start with the label on the bottom or back of the console. You need three pieces of information, and each one answers a different question.

• Model number (SCPH-xxxxx): This tells you the hardware family, Fat or Slim, and roughly where the console sits in the production run.
• Datecode: This is a small code on the label, such as 8C, that tells you roughly when the console was made. For the SCPH-90000 series, the datecode is the first warning sign, because the change that blocks FMCB arrived during 2008 production.
• ROM version (ROMVER): This is the decisive check. You can read it with a homebrew file manager such as uLaunchELF once you have a way to run homebrew, or from information shown by other entry-point tools. If the model and datecode disagree, trust the ROM version.

A common mistake is to stop at the model number. Two consoles with the same SCPH-90000 model number can need completely different approaches, one booting FMCB directly and the other needing a manual trigger. The datecode narrows it down, and the ROM version settles it.

The compatibility matrix

Read the table with two qualifications. First, “in general” means the route is the expected one for that group, not a promise about every individual unit, because region, prior modifications, and card quality can still affect the result. Second, datecode 8C is a transition period rather than a sharp dividing line: the change was introduced during that production window, so some 8C units may behave one way and others the other way. That is exactly why the ROM version check matters more than the datecode alone.

Why late Slims are different

Sony removed the update behaviour that FMCB relies on from late Slim consoles, starting with boot ROM 2.30. Because the console BIOS is read-only memory, that behaviour cannot be added back by software on the card alone. The practical consequence is simple: a standard FMCB install on a late Slim will not appear at power-on, even if the install itself completed without an error message.

Fortuna and FunTuna work around this with a different trigger: open the on-screen browser, select the memory card, and back out to the main menu, which launches the homebrew menu. That is usable, but it is not auto-boot, and a card prepared for a late Slim should be tested on your own console rather than assumed to behave like a standard FMCB card.

There is one more boundary worth knowing. The Fortuna family was not ported to the earliest SCPH-10000 and SCPH-15000 models. Those early Fat consoles are in the FMCB direct-boot group, so this limitation mainly matters if you are comparing trigger options rather than choosing FMCB itself. See FMCB vs Fortuna, FunTuna, and OpenTuna for the full comparison.

Fat versus Slim: what changes in practice

For FMCB itself, the Fat versus Slim distinction matters less than the ROM version. Both families boot FMCB directly in the groups above. The difference is what you can attach afterwards: Fat consoles can take an internal hard drive through a network adapter (the FHDB route in FMCB vs FHDB), while Slim consoles load from USB, a network share, or MX4SIO, compared in OPL Loading Compared: USB vs SMB vs HDD vs MX4SIO.

If you are choosing between a Fat and a Slim you already own, do not choose on FMCB compatibility alone. Choose on the loading route you actually want, the condition of the disc drive if you still need one for an entry point, and the accessories you already have.

Region and card notes

FMCB installs are tied to the target console’s region and model family, and the installer offers cross-model and multi-install options. Choosing the wrong type is a common reason a card boots on one console and not another, detailed in FreeMCBoot Cross-Region Installs Explained. Keep a second card for saves, and treat the FMCB card as a system card.

Card quality matters as well. A Sony 8MB card is the reference choice, because FMCB depends on the card’s authentication behaviour and some high-capacity clone cards do not reproduce it reliably. A blank Sony 8MB PS2 memory card is the straightforward starting point; the full trade-offs are in PS2 Memory Card Compatibility for FreeMCBoot.

Checklist before you install

1. Read the model number and datecode from the console label.
2. Confirm the ROM version where possible, and treat ROM 2.30 or newer on a 90000-series Slim as the Fortuna/FunTuna case.
3. Decide the loading route first (USB, network share, hard drive, or MX4SIO), because it affects which accessories you need.
4. Use a dedicated card for FMCB and keep your saves on a second card.
5. Get the v1.966 package from /download/ and follow the installer for your entry point, rather than copying files to the card with a PC file manager, which does not produce a working FMCB install.

FAQ

Does FreeMCBoot work on all PS2 Slims? No. Most Slims work, but late SCPH-90000 Slims with boot ROM 2.30 or newer do not boot FMCB on their own. Those consoles need a Fortuna or FunTuna trigger instead.

How do I know if my 90000 Slim is affected? Check the datecode first: 8C and later is the affected production window. Then confirm the ROM version, because 8C was a transition period and the ROM version is the decisive check.

Does the PS2 TV work with FreeMCBoot? Not with standard FMCB auto-boot. The PS2 TV is in the same late-model group as the affected 90000 Slims, so a Fortuna-family trigger is the relevant route where supported.

Can I just try a standard install and see what happens? You can, but a failed boot tells you less than a ROM check tells you in advance. If the console is in the late group, plan for the manual trigger from the start instead of repeating a standard install.

Some links on this page are affiliate links; we may earn a commission at no extra cost to you. See our Affiliate Disclosure.