OPL vs ESR vs HDLoader: Which PS2 Loader Is for What

Open PS2 Loader (OPL), ESR, and HDLoader are three different answers to the question of how a PlayStation 2 loads software, and comparing them as if they were three versions of the same program misses the point. The direct answer is this: OPL is the general-purpose loader for your own dumps from USB, a network share, a hard drive, or an MX4SIO card; ESR is a specialised program for discs prepared in DVD-video format through the DVD player path; and HDLoader is the older hard-drive loader that OPL has largely superseded for most users. For a new setup, start with OPL. Consider ESR only for its specific disc use, and consider HDLoader mainly if you are maintaining an older hard-drive setup or researching how PS2 loading evolved.

None of these loaders ships inside the FreeMCBoot (FMCB) v1.966 package. FMCB, created by Neme and jimmikaelkael and maintained by SP193, provides the menu from which you launch homebrew. OPL, ESR, and HDLoader are separate homebrew programs that you add yourself or obtain through a bundle such as the Noobie package. Keeping that separation clear prevents the common mistake of installing FMCB and then wondering why no loader appears: the loader is a second step, not part of the softmod package.

OPL: the general loader

OPL is the loader to learn first, because it covers the most situations. It loads your own dumps from four routes, compared in OPL Loading Compared: USB vs SMB vs HDD vs MX4SIO: a USB drive, a network share over SMB, an internal hard drive on a Fat console, and an MX4SIO card in a memory card slot. It also supports virtual memory cards, so saves for loaded games can live on the same storage as the games rather than only on a physical card, and it supports themes and per-game settings for titles that need specific handling.

OPL’s breadth is also its learning curve. Each route has its own folder layout, with DVD and CD folders at the root for the corresponding disc types, and each route has its own failure modes: USB fragmentation and drive pickiness, network share configuration, hard drive preparation on Fat consoles, and adapter and card compatibility for MX4SIO. The loader is not the hard part; matching the route to your console and storage is. Modern OPL builds also handle exFAT loading where the route supports it. That filesystem support belongs to OPL, not to FMCB, and it should not be expected during FMCB installation itself.

Choose OPL if you are setting up a new system, if you want one loader for several storage routes, or if you want virtual memory cards and per-game settings. For most FMCB users, OPL is not just the default choice; it is the only loader they will ever need.

ESR: the disc specialist

ESR works through a different path entirely. It uses the PS2’s DVD player behaviour to run discs that have been prepared in DVD-video format, so that the console treats the disc as video content and then hands control to the prepared software. That is a clever and specific mechanism, and it is useful in a narrow situation: you have a disc prepared in that format and a console and drive that can read it, and you want to run that disc’s contents.

ESR is not a general game loader. It does not load dumps from USB, a network share, or a hard drive, and it does not replace OPL for a library stored on those routes. It also depends on the disc drive in a way OPL’s disc-free routes do not, so a failing drive affects ESR use directly. If your goal is a disc-free library, ESR is the wrong tool for the job, however well it works for its own purpose. If your goal is specifically to run a DVD-video-format disc, ESR is the tool designed for that purpose, and OPL will not substitute for it.

A note on scope: this site covers ESR as a loader category, not as a method for obtaining discs. Use only your own discs and dumps, and treat any source offering prepared discs or game images as outside the scope of FMCB setup.

HDLoader: the predecessor

HDLoader came earlier, when internal hard drive loading on Fat consoles was the new capability and the tooling around it was simpler. It loads games from an internal hard drive on a Fat console through the network adapter, and for a period it was the standard way to do that. Its historical importance is real, and many older guides still refer to it, which is why it appears in comparisons at all.

For a new setup, HDLoader is largely superseded by OPL. OPL covers hard drive loading on Fat consoles as one of its routes, alongside USB, network, and MX4SIO loading, and it adds virtual memory cards, themes, and ongoing development that HDLoader, as an older tool, does not match. HDLoader remains relevant in two situations: maintaining an existing hard-drive setup that already uses it and works, where changing loaders would be disruption without benefit, and understanding older documentation that assumes HDLoader’s layout and behaviour. In both cases, the decision is about continuity, not about HDLoader being better for a fresh install.

Comparison table

Choosing in practice

• New setup, any console: OPL, with a loading route chosen from the OPL routes comparison.
• Disc prepared in DVD-video format: ESR, for that disc, with a working drive.
• Existing Fat hard-drive setup already on HDLoader and working: Leave it alone unless you have a specific reason to move to OPL.
• Researching an old guide that mentions HDLoader: Its hard-drive concepts carry over to OPL’s hard drive route, but its specific layout and settings do not automatically transfer.

FAQ

Is OPL included with FreeMCBoot v1.966? No. The v1.966 package contains only what FMCB itself needs. OPL is a separate program that you add yourself or obtain through a bundle.

Can ESR load games from a USB drive? No. ESR is for discs prepared in DVD-video format through the DVD player path. USB loading is OPL’s job.

Should a new user choose HDLoader or OPL? OPL, in almost every case. HDLoader is relevant mainly for maintaining an older hard-drive setup that already uses it.

Can I use more than one loader? Yes. Loaders are separate programs launched from the FMCB menu, so you can keep OPL for your library and ESR for its specific disc use on the same console.

Why do old guides mention HDLoader so much if OPL superseded it? Because HDLoader was the standard hard-drive loader when those guides were written. Its concepts carry over to OPL’s hard drive route, but for a fresh install, OPL is the current general loader.

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

OPL Loading Compared: USB vs SMB vs HDD vs MX4SIO

Open PS2 Loader (OPL) is the loader most FreeMCBoot (FMCB) users end up with, and the first real decision after installing FMCB is not which loader to use, but where your games will live. The direct answer is this: USB is the simplest route and the slowest, a network share (SMB) is fast without new console hardware on a Slim but needs a PC on the same network, an internal hard drive is the most integrated route but only for Fat consoles, and MX4SIO is a card-slot adapter route that suits Slim owners who want faster loading than USB without a network setup. There is no single best route, only a best fit for your console, your network, and your patience for setup.

OPL is a separate homebrew program from FMCB. FMCB v1.966 provides the menu from which you launch OPL; OPL itself finds and loads your own game dumps. Filesystem support, folder layout, and loading behaviour belong to OPL, not to FMCB. In particular, exFAT support is a feature of modern OPL builds, not of FMCB itself.

The four routes at a glance

USB: start here, understand its limits

USB loading is where most people start, because it needs nothing beyond a drive. The PS2’s USB ports are USB 1.1, so loading is slow compared with the other routes, and that is a hardware fact, not a setting to fix. The ports are also picky: modern high-capacity USB 3 drives often behave worse than older, smaller USB 2 drives, and a drive that works on a PC may still be unreliable on the PS2.

USB setup also has file-layout rules that apply across routes. OPL expects DVD and CD folders at the root for the corresponding disc types, and file names that avoid characters OPL cannot parse. Fragmentation matters for USB loading on FAT32 in particular: a fragmented file can stutter or fail where a file copied in one pass plays. If you need a drive to start with, a basic USB drive is the straightforward purchase, but buy it for testing the route, not as a final library solution, until you know USB suits you.

SMB: the network route

SMB loading shares your game folder from a PC or server over the local network, and OPL on the console reads from that share. On a Slim, the built-in network port means no adapter purchase is needed. On a Fat, you need a network adapter, the same part used for an internal drive. The advantage is speed without the PS2’s USB bottleneck, and the library lives on a PC where it is easy to manage, back up, and reorganise.

The cost is dependence. The sharing computer must be on and reachable whenever you play, and network changes at home, such as a new router, can break a setup that worked yesterday. SMB suits people who already leave a PC on, and Slim owners especially well, because it gives fast loading without buying a drive or an adapter.

Internal hard drive: the Fat advantage

Internal drive loading is only for Fat consoles, because only Fat consoles have the drive bay and the network adapter connection it needs. The drive sits inside the console, the library travels with the console, and no PC needs to be on. Paired with FHDB, the drive can even hold the boot files themselves, so the console boots from the drive rather than from a card, as compared in FMCB vs FHDB.

The setup cost is higher than USB or SMB. You need the adapter, a compatible drive, and the patience to prepare the drive for the PS2. There is also a capacity caveat: FHDB-related drive setups support up to 2TB only where the drive operating system has been updated; otherwise the supported size is much smaller, around 137GB. Check that situation before buying a large drive. A hard drive for a Fat PS2 and a network adapter should be chosen together, because the adapter determines the drive interface, and second-hand original adapters can also be found through eBay network adapter listings with condition to check.

MX4SIO: the card-slot route

MX4SIO is an adapter that plugs into a PS2 memory card slot and reads from a microSD card, giving OPL a loading route that is faster than USB and does not need a network or an internal drive. It works on Fat and Slim consoles alike, which makes it attractive for Slim owners who want better-than-USB loading without a network setup, and for anyone who likes a compact, self-contained library on a card.

The trade-offs are compatibility and familiarity. Adapter quality and microSD compatibility vary, and MX4SIO setup is less widely documented than USB setup, so troubleshooting relies more on community notes for the specific adapter and card combination. Buy the adapter and card as a pair to test, rather than assuming any microSD card will behave identically. A microSD card and an MX4SIO adapter are the two components, and there are also MX4SIO options through AliExpress MX4SIO listings, where the same advice applies: test the combination, do not assume it.

Choosing a route

• Simplest first test: USB, with an older, smaller drive if a modern drive misbehaves.
• Fast loading without new console hardware (Slim): SMB, if a PC can stay on and share reliably.
• Largest self-contained library (Fat): Internal hard drive, with the adapter and capacity caveat settled first.
• Compact and faster than USB, without a network (either family): MX4SIO, tested as an adapter-and-card pair.

Whichever route you choose, use only your own dumps, keep the FMCB card dedicated to the softmod, and back up your own saves and dumps separately. For backups of your own files, a cloud option such as pCloud or Backblaze can hold copies of your personal library and saves, which is a different job from loading games on the console and should not be confused with a game source.

FAQ

Which OPL route is fastest? In general, internal hard drive and network share loading outperform USB loading, because they avoid the PS2’s USB 1.1 ports. MX4SIO sits between USB and the faster routes for most users, but exact behaviour depends on the adapter and card.

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

Is exFAT an FMCB feature or an OPL feature? An OPL feature. Modern OPL builds handle exFAT loading where the route supports it. FMCB itself does not add exFAT support to the console.

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 FreeDVDBoot: Permanent Softmod vs Disc Entry Point

FreeMCBoot (FMCB) and FreeDVDBoot are often mentioned in the same breath, and they are often used together, but they are not alternatives to each other. The direct answer is this: FMCB is the persistent softmod that lives on a memory card and gives you a homebrew menu every time you power on a supported console, while FreeDVDBoot is a disc-based entry point that you boot once in order to run something, most usefully the FMCB installer, on a console that has no other way to run homebrew yet. Think of FreeDVDBoot as the key and FMCB as the lock it opens permanently. You need the key only until the lock is fitted; after that, the card does the work on its own.

That relationship explains why guides pair them so often. A completely unmodified PS2 cannot run the FMCB installer by itself, because running the installer is itself a homebrew action. Something has to run first. That something can be an already-modified console, a cheat disc, a PC adapter, or a FreeDVDBoot disc. FreeDVDBoot is popular as that first step because it needs no second console and no special hardware beyond a disc the console can read, provided the console’s disc drive works and the disc is prepared for the console’s DVD player behaviour.

What each one is

FMCB was created by Neme and jimmikaelkael and maintained by SP193, with v1.966 (2019-04-13) as the latest stable release. FreeDVDBoot is a separate project for the PS2’s DVD player, and it should be understood on its own terms rather than as a version of FMCB. The two projects solve different halves of the same problem: getting in the first time, and staying in afterwards.

The typical combined workflow

The most common workflow that uses both looks like this, in outline rather than as a step-by-step burning guide.

1. Prepare a FreeDVDBoot disc for your console and a USB drive or other medium holding the FMCB installer files.
2. Boot the console from the FreeDVDBoot disc, which gives you a homebrew environment for that session.
3. Run the FMCB installer from that environment and install to a dedicated memory card, choosing the install type for the console you will actually use.
4. Power off, remove the disc, and power on with the card inserted. On a supported console, the FMCB menu appears without the disc.
5. From the FMCB menu, launch the loaders and tools you have added separately, such as Open PS2 Loader (OPL) and uLaunchELF, since the v1.966 package itself contains no apps.

Step 5 is worth repeating, because it is where expectations go wrong. Installing FMCB does not install OPL, uLaunchELF, or ESR. Those are separate homebrew programs. FreeDVDBoot does not change that either; it only gets you into the installer. The loaders are compared in OPL vs ESR vs HDLoader, and the loading routes in OPL Loading Compared: USB vs SMB vs HDD vs MX4SIO.

When FreeDVDBoot is the right entry point, and when it is not

FreeDVDBoot is a good entry point when you have one unmodified console, a working disc drive, and no friend with a modified console nearby. It is a poor entry point when the disc drive is failing, because the whole method depends on reading the disc, and it is unnecessary when you already have another route, such as a PC adapter or an already-modified console. In that case, adding a disc step only adds a variable.

FreeDVDBoot also does not solve the late-model problem on its own. A late SCPH-90000 Slim that cannot auto-boot FMCB will not be fixed by entering through FreeDVDBoot and then installing standard FMCB, because the installed FMCB still will not auto-boot on that console. Late consoles need the Fortuna or FunTuna route, compared in FMCB vs Fortuna, FunTuna, and OpenTuna. Entry point and boot route are different questions, and confusing them leads to repeated installs that were never going to change the outcome.

Disc dependence after installation

Once FMCB is installed on a supported console, daily use does not need a disc at all. Loaders can run your own dumps from USB, a network share, a hard drive, or an MX4SIO card, and the FMCB menu itself needs only the card. That is one of the main reasons people install FMCB in the first place: it frees the console from dependence on a disc drive that is, on many surviving PS2s, the oldest and most failure-prone part.

FreeDVDBoot, by contrast, remains disc-dependent by design. Every use requires booting the disc. That is fine for a one-time install, but it would be a poor daily routine, which is exactly why the two are combined rather than used as substitutes. If you find yourself booting a disc every time to reach homebrew, you have an entry point but not yet a persistent softmod, and the next step is to complete the FMCB install rather than to get better at booting discs.

Checklist

1. Decide whether you need an entry point at all; an already-modified console or a PC adapter may already provide one.
2. If you use FreeDVDBoot, treat it as the first step, not the destination.
3. Install FMCB to a dedicated card for the console you will actually use.
4. After installation, test power-on without the disc; the menu should appear from the card alone on a supported console.
5. Add loaders separately, and get the v1.966 package from /download/.

FAQ

Is FreeDVDBoot a replacement for FreeMCBoot? No. FreeDVDBoot is a disc entry point. FMCB is the persistent card softmod. They are complementary, and FreeDVDBoot is most often used to install FMCB.

Do I still need the FreeDVDBoot disc after installing FMCB? No, not for daily use on a supported console. The card provides the menu on its own. Keep the disc as a fallback entry point if you ever need to reinstall.

Can FreeDVDBoot install FMCB on a late Slim? It can run the installer, but the resulting standard FMCB install still will not auto-boot on a late Slim. Late consoles need a Fortuna or FunTuna trigger instead.

Does using FreeDVDBoot require a working disc drive? Yes. The entry point is a disc, so a failing drive blocks this route even though disc-free loading afterwards does not need the drive.

If I already have a modified console, do I need FreeDVDBoot? No. An already-modified console can run the installer directly, which is simpler than adding a disc step you do not need.

FreeMCBoot vs Modchip: Software Exploit vs Hardware Mod

FreeMCBoot (FMCB) and a modchip both change what a PlayStation 2 will run, but they do it in opposite ways. The direct answer is this: FMCB is a software exploit that lives on a memory card and needs no soldering, no console disassembly, and no permanent change to the console, while a modchip is a hardware modification soldered inside the console that changes how the console reads and boots. For most people on a supported console, FMCB is the simpler, lower-risk, and reversible choice. A modchip still has a place, mainly for late consoles where FMCB cannot auto-boot and for users who specifically want hardware-level behaviour, but it should be chosen knowingly, not as a default.

FMCB v1.966, created by Neme and jimmikaelkael and maintained by SP193, works through the console’s browser and update behaviour. A modchip works by altering signals inside the console, typically around the drive and boot process. That architectural difference drives every practical difference below, from installation risk to what happens when you change your mind.

Installation: external versus internal

FMCB installation is external to the console’s internals. You prepare a memory card using an entry point, such as an already-modified console, a cheat disc, FreeDVDBoot, or a PC adapter, and then the card itself carries the softmod. The console is never opened for FMCB itself. The main risks are to the card’s contents, for example formatting the wrong card, and those risks are recoverable by reinstalling.

Modchip installation is internal. It requires opening the console, soldering small points on the board, and reassembling everything correctly. The risks are to the console itself: a lifted trace, a bridged connection, or heat damage can leave a console worse than before, and the quality of the result depends heavily on the installer’s skill and on the specific chip and console revision. A good install can last for years, but a bad install is not fixed by reformatting a card. This is also why modchip advice varies so much by console revision: the board layout and the available chips differ across Fat and Slim families, and a chip that fits one revision may not fit another.

Reversibility and daily use

Reversibility is often the deciding factor for people who care about preserving a console. FMCB can be tried, removed, and retried without touching the hardware. A modchip is a commitment to that console in its modified state, and it affects resale, repair, and future troubleshooting in ways a card does not.

What each one does and does not change

A modchip is sometimes described as if it simply did everything FMCB does, plus more. That is too simple. A modchip changes boot and drive behaviour at the hardware level, which can matter for disc-based use cases and for late consoles where card auto-boot is unavailable. FMCB changes the menu and launcher behaviour from the card, which matters for homebrew, loaders, and disc-free loading through OPL. The overlap is real, but the two approaches are not identical in scope, and neither is a superset of the other in every respect.

Both approaches share the limits described in What FreeMCBoot Cannot Do in the sense that no single claim covers every use case. FMCB alone does not add import-disc support, and a modchip’s behaviour depends on the specific chip, its firmware, and the console revision. Anyone promising that either approach “unlocks everything” is selling a slogan, not a specification. Research the specific chip and revision if hardware modification is genuinely what you want, and do not assume a chip marketed for one PS2 family applies to yours.

Cost and skill, honestly stated

FMCB’s cost is mainly the card and, depending on your entry point, an accessory you may already own or can borrow, such as a cheat disc or a PC adapter. The skill required is following an installer carefully and checking the console’s model and install type. The modchip’s cost is the chip plus installation, whether you pay someone or invest the time and tools to learn soldering on a board where mistakes are costly. The skill required is electronics work, not software configuration. Comparing only the price of a chip with the price of a card therefore understates the modchip route, because the installation labour and risk are part of its real cost.

There is also a maintenance difference. An FMCB setup is maintained by keeping a spare card and a copy of the installer package. A modchip setup is maintained as hardware: if the console is opened again for another repair, the chip and its wiring become part of that repair’s complexity.

When a modchip still makes sense

A modchip is not obsolete in every case, and saying so would repeat the exaggeration this site corrects elsewhere. It makes sense to consider hardware modification when the console is a late model where FMCB cannot auto-boot and you do not want a manual trigger every time, when you specifically want hardware-level disc behaviour that a card route does not provide, or when you already own a console with a well-installed chip and have no reason to change it. In those cases, research the chip for your exact console revision, use an installer whose work you can check, and keep the original behaviour in mind: you are modifying hardware, and that decision should be deliberate.

For everyone else, and especially for first-time softmodding on a supported console, the card route is the place to start. Confirm compatibility in FreeMCBoot Compatibility List, prepare a dedicated card, as described in PS2 Memory Card Compatibility for FreeMCBoot, and get the v1.966 package from /download/. If that route meets your needs, there is no reason to open the console at all.

FAQ

Is a modchip more powerful than FreeMCBoot? Not in a general sense. A modchip changes hardware-level behaviour, while FMCB changes menu and launcher behaviour from a card. They overlap but are not identical, and “more powerful” depends on the specific use case and chip.

Can I remove a modchip as easily as removing an FMCB card? No. Removing an FMCB card returns the console to standard behaviour immediately. Removing a modchip requires opening the console and desoldering, which is repair work, not a menu choice.

Does FreeMCBoot make modchips pointless? No. FMCB is the simpler choice on supported consoles, but hardware modification remains relevant for late consoles and for specific hardware-level uses. The claim that it makes modchips pointless overstates the case.

Do I need soldering skills for FreeMCBoot? No. FMCB installation involves preparing a memory card through an entry point. No soldering and no console disassembly are involved in FMCB itself.

If my console already has a modchip, should I also install FMCB? You can, and some owners do, because the card menu is convenient even on a chipped console. But it is optional, not required, and a chipped console already has a route into homebrew through its hardware.

FMCB vs Fortuna, FunTuna, and OpenTuna for Late PS2 Slims

Standard FreeMCBoot (FMCB) does not boot on its own on late PlayStation 2 Slims. That single fact is the reason Fortuna, FunTuna, and OpenTuna exist, and the direct comparison is this: FMCB is an automatic boot from a memory card on supported consoles, while Fortuna, FunTuna, and OpenTuna are manual triggers for consoles that cannot auto-boot FMCB, launched by opening the on-screen browser, selecting the memory card, and backing out to the main menu. They are not newer versions of FMCB, they are not interchangeable labels for the same file, and they do not turn a late Slim into an auto-boot console. They give a late Slim a working homebrew menu with one extra step, every time.

FMCB v1.966, created by Neme and jimmikaelkael and maintained by SP193, relies on update behaviour that Sony removed from late Slim consoles, starting with boot ROM 2.30. Because the console BIOS is read-only memory, that behaviour cannot be restored by a card alone. Fortuna, created by krat0s in 2019, takes a different path into the same destination: a vulnerability in how the browser handles the memory card display, triggered by the user’s own navigation. FunTuna is a package built around that Fortuna approach for late Slims, and OpenTuna is an open-source implementation of the same idea. The names describe a family of triggers, not a single download, and the package you obtain may bundle the trigger with a launcher and configuration in ways that vary. Check what a given package actually contains before assuming it matches another package with a similar name.

The core difference: auto-boot versus manual trigger

The daily-experience row is the one people underestimate. A manual trigger sounds trivial, and it is, once. But it is a step you repeat every time you power on, and it changes how the console feels to use, especially for other people in the household who did not set it up. If you are choosing a late Slim deliberately, accept the trigger as part of the console. If you are choosing between a late Slim and an earlier console, weigh the trigger against the other factors in Fat vs Slim PS2 for FreeMCBoot.

Fortuna, FunTuna, and OpenTuna: how they relate

Think of Fortuna as the original trigger concept and implementation. FunTuna is a package that applies that concept for late Slims, combining the trigger data with a launcher setup so that the end result feels like a working homebrew menu. OpenTuna is an open-source version of the trigger, developed so the community has an implementation that can be inspected and adapted. In practice, a user rarely chooses between these names in the abstract; they obtain a package, and that package embodies one of these approaches plus whatever launcher and configuration its maker included.

That is why this post does not describe the contents of any specific FunTuna archive in detail. Package contents vary, and describing one archive as if it described all of them would mislead. Before you use a package, check its own documentation for what it contains, which consoles it targets, and how the trigger is performed on your console. If that documentation is missing or vague, treat the package as unconfirmed for your purposes, whatever its filename suggests.

Coverage and limits

Coverage is where the Fortuna family is strongest. Where FMCB auto-boot stops, at late Slims, the Fortuna family starts, covering consoles from ROMVER 1.90 onwards through the last production models, including the PS2 TV. That breadth is the reason the family matters: without it, the newest PS2 hardware would have no card-based homebrew route at all.

Limits are equally clear. First, the Fortuna family was not ported to the earliest SCPH-10000 and SCPH-15000 models. Those consoles are covered by FMCB direct boot, so the gap only matters if you are comparing triggers rather than choosing a route for a console you own. Second, a trigger is not auto-boot, and no package in this family changes that. Third, the same FMCB limits apply once you are in the menu: a Fortuna or FunTuna trigger does not add import-disc support or change disc authentication on its own, as explained in What FreeMCBoot Cannot Do. The trigger gets you to homebrew; what homebrew can do from there is a separate question.

Choosing between them

• Your console boots FMCB directly: Use FMCB. There is no reason to add a manual trigger to a console that already auto-boots, and doing so only adds a step.
• Your console is a late Slim or PS2 TV: Use a Fortuna-family trigger. Choose the package based on its documentation for your exact model, not on its name alone, and test the trigger on your console before relying on it.
• You are unsure which group your console is in: Check model, datecode, and ROM version against FreeMCBoot Compatibility List before choosing. Guessing between FMCB and a trigger wastes more time than the check takes.
• You need a card for the trigger: The card requirements are similar in spirit to FMCB: a reliable card matters, and a dedicated card is simpler than a card shared with saves. A blank PS2 memory card is a reasonable starting point for preparing a trigger card you can test and, if needed, redo.

Checklist

1. Confirm whether your console is in the FMCB direct-boot group or the late group.
2. If late, expect a manual trigger every time, and choose a package with documentation for your model.
3. Do not assume packages with similar names contain the same files.
4. Test the trigger on your own console before treating the setup as finished.
5. Remember that the trigger only reaches homebrew; loaders and their limits are separate, as in OPL vs ESR vs HDLoader.

FAQ

Is FunTuna just a newer FMCB? No. FunTuna is a package built around the Fortuna trigger approach for late Slims. It is not a version of FMCB, and it does not auto-boot.

What is the difference between Fortuna and OpenTuna? Fortuna is the original trigger implementation. OpenTuna is an open-source implementation of the same trigger idea. They share the concept and the manual trigger behaviour, but they are distinct implementations.

Does a Fortuna trigger make my late Slim behave exactly like an FMCB console? Almost, except for the trigger step itself. Once the menu is up, you launch homebrew in the same way, but you must perform the browser step on every power-on.

Why does the Fortuna family not cover the earliest Fat consoles? It was not ported to SCPH-10000 and SCPH-15000 models. Those consoles boot FMCB directly, so the gap does not leave them without a route.

Can I use FMCB and a Fortuna trigger on the same console? On a console that boots FMCB directly, a trigger adds nothing. On a late console, the trigger is the route, and FMCB auto-boot is not available to combine with it.

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

FMCB vs FHDB: Memory Card Boot vs Hard Drive Boot

FreeMCBoot (FMCB) and Free Hard Drive Boot (FHDB) are the same softmod idea in two different homes. The direct answer is this: FMCB lives on a memory card and boots from that card, while FHDB lives on an internal hard drive in a Fat PlayStation 2 and boots from that drive. FHDB is only an option for Fat consoles with a network adapter, because Slim consoles have no internal drive bay. If you have a Fat console and a large library, FHDB is worth considering; if you have a Slim, or you want the simplest setup, FMCB on a card is the route, and FHDB is not available to you at all.

Both are part of the same project lineage. FMCB was created by Neme and jimmikaelkael and maintained by SP193 through the 1.9 series, with v1.966 (2019-04-13) as the latest stable release. FHDB is not a different exploit or a competing product. It is FMCB installed to a hard drive instead of a card, using the same installer family, for consoles that can connect a drive. Understanding that relationship prevents a common confusion: you do not choose between two unrelated softmods, you choose where the softmod lives.

How each one boots

With FMCB, the console reads the custom menu from the memory card at power-on. Remove the card and the console returns to its standard browser. The card is small, portable between consoles where the install type allows it, and easy to replace. The limitation is that the card is also the thing you must protect: lose it, corrupt it, or fill it carelessly, and the softmod menu goes with it.

With FHDB, the console boots from the internal hard drive through the network adapter. The drive holds both the boot files and, typically, the game library loaded through Open PS2 Loader (OPL). The advantage is integration: one drive holds the system and the games, and you do not occupy a memory card slot with system files. The limitation is that the setup is tied to that console and that drive. Move the drive to another console without planning and the result is not assured, and a drive failure affects both the softmod and the library at once.

Requirements compared

The network adapter deserves a note. Fat consoles need it for FHDB, and it is also the part that connects the drive physically. Original adapters and modern SATA-conversion adapters both exist, and the choice affects which drives you can use comfortably. If you need an adapter for a Fat setup, a PS2 network adapter is the component to research first, before buying a drive, because the adapter determines the drive interface. Second-hand original adapters are also commonly found through eBay network adapter listings, where condition and included parts vary and should be checked.

Capacity and the caveat to know

FHDB supports drives up to 2TB, but with an important qualification: if the hard drive operating system on the console has not been updated with a replacement module, the supported size is much smaller, around 137GB. That caveat is easy to miss in summaries that simply say “up to 2TB”, and it is the reason some FHDB setups see only part of a large drive. Before buying a large drive for FHDB, confirm which situation your setup is in, because the answer changes what you should buy. A hard drive for a Fat PS2 setup should be chosen after the adapter and the drive-system situation are settled, not before.

FMCB has no equivalent capacity question, because the card holds only the system files and the library lives elsewhere. USB drives, network shares, and MX4SIO cards each have their own practical limits, compared in OPL Loading Compared: USB vs SMB vs HDD vs MX4SIO. In that sense FMCB is more modular: you can change the library storage without touching the softmod, and change the softmod card without touching the library.

Which should you choose?

Choose FMCB on a card if: you have a Slim, you want the simplest install, you want to move the softmod between consoles, or you want library storage that can change independently of the softmod. This is the default recommendation for most people, and it is the only option of the two for Slim owners.

Choose FHDB if: you have a Fat console, you already have or plan to buy a network adapter and a drive, and you want a single-drive setup where the console boots from the drive and the library lives on the same drive. FHDB is at its best as a dedicated Fat-console library machine, not as a casual experiment.

Consider both if: you have a Fat console and want a fallback. An FMCB card plus an FHDB drive gives you two ways into homebrew on the same console, so a problem with one does not leave you without the other. This is more setup work, but for a console you use regularly, the redundancy is genuinely useful.

One caution applies to both routes: neither FMCB nor FHDB alone adds import-disc support or changes how the console treats original discs from other regions. That limit is explained in What FreeMCBoot Cannot Do, and it is unaffected by where the softmod lives.

Checklist

1. Confirm the console is a Fat if you are considering FHDB; Slim consoles cannot use it.
2. For FHDB, settle the network adapter first, then the drive, then the capacity caveat.
3. For FMCB, use a dedicated Sony 8MB card and keep saves on a second card.
4. Decide where the library will live, because that choice matters more day to day than where the softmod lives.
5. Get the v1.966 package from /download/ and install for the console you will actually use.

FAQ

Is FHDB a newer or better version of FMCB? No. FHDB is FMCB installed to a hard drive instead of a card. It is a different home for the same softmod idea, not a successor version.

Can I use FHDB on a Slim PS2? No. Slim consoles have no internal drive bay, so FHDB is a Fat-only option.

Do I still need a memory card if I use FHDB? Not for booting, since the drive holds the boot files. You will still want a card for game saves, which is a separate job from booting.

What happens if my FHDB drive fails? You lose both the boot files and the library on that drive until you restore them. That is why backups of your own dumps and saves matter, and why some Fat owners keep an FMCB card as a fallback.

Can I switch from FMCB to FHDB later? Yes, on a Fat console. The two routes are not exclusive, and many Fat owners run an FMCB card alongside an FHDB drive so that either route can reach homebrew.

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

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.