ShadowMountPlus: A PS5 Auto-Mounter That Warns of Data Corruption

By Indie Kings | October 21, 2026

Updated October 21, 2026: ShadowMountPlus is a background auto-mounter for jailbroken PlayStation 5 consoles. It finds game dumps on internal or external storage, mounts them, and registers them in the system library without opening a separate payload for each title. Its own README opens with a warning that mounting images can cause shutdown problems and data corruption on internal drives.

That warning is the story. ShadowMountPlus is not a game loader with a friendly front end. It is a low-level storage tool that attaches disk images to a console the user has already modified, and it changes what the system sees at boot. The project is popular, with 1,066 stars and 92 forks at the time of check, but it is still publishing beta builds. The latest tag, 1.7beta7, arrived on October 21, 2026.

ShadowMountPlus GitHub repository social preview

Image: GitHub social preview for the ShadowMountPlus repository. Image credit: drakmor/ShadowMountPlus, via GitHub.

What ShadowMountPlus does

The project describes itself as a fully automated background auto-mounter payload for jailbroken PS5 consoles. It detects, mounts, and installs game dumps from internal and external storage. The point is to remove manual steps that otherwise require tools such as DumpRunner or Itemzflow for every title.

It works by watching configured scan paths. When it finds a supported image or a folder game, it attaches the image through the console's storage layers, reads the title metadata, and registers the game so it appears in the library. The README says the first scan can take a few seconds on a large library, and games of 100 GB or more may need extra time for the system to verify integrity before the installed notification appears.

The tool also handles backport overlays, per-game fakelib overlays, emulator updates, and a small web interface with an HTTP and JSON API. Those features make it more than a mount script. It is closer to a storage service that runs alongside the console shell and reacts to games starting and stopping.

GitHub records the repository as a fork of RDX-Sci01's ShadowMount1.3GBT, which in turn descends from ShadowMount. The README's credits section names Drakmor for the evolution of ShadowMount into ShadowMountPlus, VoidWhisper for ShadowMount itself, and BestPig for BackPort.

ItemDetail from the repository
ProjectShadowMountPlus for jailbroken PlayStation 5
LanguageC
LicenceGPL-3.0
Stars and forks1,066 stars, 92 forks, 15 open issues at check
Repository createdFebruary 13, 2026
Latest tag1.7beta7 on October 21, 2026
CompatibilityJailbroken PS5 with kstuff-lite v1.07 or newer, including firmware 2.00
Default API bind127.0.0.1 on port 10101

The data corruption warning

The README's first paragraph after the repository links is a warning, not a feature list: mounting images can cause shutdown problems and data corruption on internal drives. It says the risk depends on many factors and is more common with older firmware versions.

That is not a generic disclaimer. Attaching disk images to a modified console asks the storage stack to do something it was not designed to do in that configuration. A badly formed image, an interrupted write, a power loss, or a firmware mismatch can leave the backing file or the console's internal storage in a bad state. The warning is not scoped to one mount mode. The project defaults to read-only mounts, which reduces one class of risk, but it does not remove the warning.

The README also documents a recovery trap. If a mounted game does not start, one troubleshooting step is to remove the game data from system settings and retry. The README notes that this will delete game saves. That is the kind of instruction that should be read before touching a library, not after.

Two defaults are worth knowing. Read-only mode is on by default, and automatic removal of missing games is off by default. If a user turns on auto_remove_missing_games, the tool will remove a game from the system library after its source has been unavailable for a configured delay, 300 seconds by default. The delay exists to avoid removing a game during a temporary USB disconnect, but it is still an automated delete from the library.

Supported image formats

ShadowMountPlus supports four image families. The README recommends UFS for normal use and treats the other formats as compatibility or experimental paths. The distinction matters because the mount backend and the filesystem are not the same thing.

ExtensionFilesystemStatus in the README
.ffpkgUFSRecommended for normal use
.exfatexFATCompatibility path, mainly for titles that need external-drive-style handling
.ffpfsPFSExperimental
.ffpfscPFS containerExperimental container for nested images

For manually built exFAT images, the README asks for a 64 KB cluster size and warns that smaller clusters can reduce performance. It also documents a fast path for images stored on the internal BFS volume, with a 512-byte logical sector and a 64 KiB secondary unit. Those are storage-tuning details, and getting them wrong is one reason the project ships builder scripts for Linux, macOS, and Windows.

Folder games are also supported. The layout rule is strict: game files must sit at the image root, with sce_sys/param.json directly inside. An extra top-level folder inside the image produces a missing or invalid parameter file error. That single rule explains many of the troubleshooting entries in the README.

Installation and autoload

There are two installation paths. The manual path sends shadowmountplus.elf to port 9021 with a payload sender. The recommended path adds the ELF to autoload.txt for plk-autoloader so it starts on every boot. The sample order loads ShadowMountPlus, waits 3,000 milliseconds, then loads kstuff.

The project depends on kstuff-lite v1.07 or newer. Without that layer, the payload has nothing to hook. The README lists firmware 2.00 as supported, but it does not claim support for every firmware. Users should check their own version against the compatibility note before installing anything.

Configuration lives in /data/shadowmount/config.ini. If the file is missing, the payload creates it from a bundled example and uses built-in defaults. The web interface is optional, and the API binds to localhost by default. Changing api_bind_address to 0.0.0.0 exposes it to the network, which the README presents as an option rather than a recommendation.

Debug logging is on by default and writes to both the console and /data/shadowmount/debug.log. That is helpful during setup, but it also means a log file grows until the user sets debug=0 or cleans it up.

The configuration surface

The configuration file is large because the tool touches several layers at once. The most important settings are the ones that change what happens to a library without a user watching.

  • mount_read_only defaults to 1, so images are mounted read-only unless changed.
  • scan_interval_seconds defaults to 15, so the tool keeps looking for new sources.
  • stability_wait_seconds defaults to 10, so a file being copied is not processed immediately.
  • auto_remove_missing_games defaults to 0, but can be enabled with a delay.
  • persistent_image_mounts defaults to 0, so images are released when a game exits.
  • fan_target_temperature defaults to system control, but can be set to a target in degrees Celsius.

The fan setting is a reminder that this is not only a file manager. It can apply a fan target when a game starts, which changes console behavior beyond mounting. The README documents it, but a user should not enable it without understanding the thermal tradeoff.

The web interface adds another surface. It can show game cards, change fakelib modes, and trigger background work. The API is documented in docs/api.md and an OpenAPI manifest. Binding it to localhost is the safe default. Exposing it on a LAN without authentication would be a bad idea, and the README does not describe an authentication layer for the API.

Jailbreak, backups, and legal risk

ShadowMountPlus requires a jailbroken console. That already places it outside the normal warranty and support path. The README's warning about data corruption is the most concrete risk, but it is not the only one. A jailbroken console may be unstable after firmware changes, and a payload that hooks the shell can fail in ways that are hard to diagnose.

The legal side is separate. The tool mounts game dumps. It does not include a legal opinion or a licence to any game. In most jurisdictions, making a backup of a disc you own may be permitted, but downloading a copy you do not own is not. Users should treat this as a tool for their own backups and check their local law. Nothing in the repository suggests Sony has approved it.

The security posture is also worth a second look. The project is open source under GPL-3.0, which helps inspection, but the release assets are binaries. The latest release ships shadowmountplus.elf and a zip. There is no code-signing chain for a jailbroken console, so users have to trust the repository and the release. That is normal for this scene, but it is still trust.

FAQ

What is ShadowMountPlus?
It is a background payload for jailbroken PS5 consoles that finds, mounts, and registers game dumps from internal or external storage. It can also apply backports, fakelib overlays, and emulator updates.

Does ShadowMountPlus work on an unmodified PS5?
No. The README requires a jailbroken console running kstuff-lite v1.07 or newer. It lists firmware 2.00 as supported but does not claim support for every firmware.

Is it safe to use?
The project's own README warns that mounting images can cause shutdown problems and data corruption on internal drives, especially on older firmware. Read-only mode is the default, but the warning still applies.

Which image format should I use?
The README recommends .ffpkg with UFS for normal use. Use .exfat only for titles that need external-drive-style compatibility, and treat .ffpfs and .ffpfsc as experimental.

Does it delete games automatically?
Not by default. auto_remove_missing_games is off unless the user enables it. If enabled, a game is removed from the system library only after its source stays unavailable for the configured delay.

Is ShadowMountPlus official or endorsed by Sony?
No. It is an independent homebrew project for jailbroken consoles. The repository does not claim Sony approval, and using it can affect warranty, stability, and data.

Our take: ShadowMountPlus is a serious piece of storage engineering, and its README is more honest than most homebrew projects about the risk. The corruption warning, read-only default, and delayed auto-removal are the right instincts. The caution is that the project is still shipping beta tags and the failure mode is data loss, not a crashed app. Anyone testing it should use backups, avoid writable mounts unless necessary, and keep the console's important saves somewhere else.

Bottom Line

ShadowMountPlus is a GPL-3.0 auto-mounter for jailbroken PS5 consoles. It scans internal and external storage, mounts UFS, exFAT, and experimental PFS images, registers games, and can apply backports and fakelib overlays. It had 1,066 stars and 92 forks at the time of check, with 1.7beta7 released on October 21, 2026. The project's own warning about shutdown problems and internal-drive data corruption is the first thing to read. It requires a jailbroken console, works on game dumps the user supplies, and is not endorsed by Sony.

Sources

drakmor/ShadowMountPlus repository README, including the corruption warning, compatibility note, image formats, configuration keys, scan behavior, installation methods, and troubleshooting, verified October 21, 2026.

drakmor/ShadowMountPlus releases, including 1.7beta7 published October 21, 2026 and 1.7beta6-fix2 published the same day.

GitHub repository metadata for drakmor/ShadowMountPlus, verified October 21, 2026: 1,066 stars, 92 forks, 15 open issues, C, GPL-3.0, created February 13, 2026, last push October 21, 2026.

Share