Quick Answer: A PS5 game mounter is a homebrew payload that scans your internal SSD and USB drives, then mounts debug FPKG
.pkgfiles and game folders so they appear as launchable games. Kraken Mount does this as a single ELF file. You send it through elfldr on port 9021, and it adds a home-screen tile and a web interface on port 8097. It handles plain folders and folders packed with zstd or LZ4.
Most PS5 homebrew guides stop at "load the payload and you're done." The harder part comes after that: keeping games visible, rebuilding caches, and knowing where things live when something breaks. Kraken Mount is a minimalist PS5 game mounter that handles those steps. It's a small tool, but it has enough moving parts that a few details matter. Here's what it does, how to set it up, and where people usually get stuck.
What Kraken Mount Actually Does
Kraken Mount is a PS5 ELF payload. It scans for games on the internal SSD and on USB or extended drives, then mounts them. It accepts three kinds of input: debug FPKG .pkg files, plain game folders, and game folders packed with zstd or LZ4 compression.
The format rules are strict, and they're the first place setups fail. A .pkg must be a plaintext debug FPKG, as the project's README specifies. A folder must contain eboot.bin and sce_sys/param.json. If either file is missing, the game won't register, and no error will tell you why unless you check the log.
Compression is where the popular advice goes wrong. Most people assume packing everything with zstd or LZ4 is a free space saving. It saves disk space, but it also adds a cache layer. Kraken Mount stores its per-game work in /data/krakenmount/caches/<TITLE_ID>. That means a packed game leaves a second footprint on the console that you need to track when you rebuild or delete titles. Plan for it before you compress your whole library.
Setting Up Scan Roots and Folder Layout
Kraken Mount only looks in specific places. Put each game in one of these scan roots:
/data/homebrew/data/etaHEN/gameshomebreworetaHEN/gameson a USB drive- The root of a USB drive
If your game sits in a subfolder the scanner doesn't check, it won't appear. This is the most common reason someone thinks the tool is broken when it isn't.
Backports need their own location. Put them in <scan root>/backports/<TITLE_ID>*, where the title ID matches the game they patch. The project borrowed backports from ShadowMountPlus, so the same folder convention will look familiar if you've used that tool. Here's where it gets practical: a backport in the wrong folder doesn't throw an error. It just does nothing, so check the path first.
Loading the ELF Over the Network
Kraken Mount runs through elfldr, the ELF loader that listens on port 9021. You download kraken-mount.elf from the project's Releases page and send it once from your computer:
nc -w 3 <ps5-ip> 9021 < kraken-mount.elf
The payload saves a copy on the console. After that first send, the Kraken Mount tile on the home screen starts it, but only if elfldr is running. That dependency is easy to miss. If the tile does nothing, check that elfldr is active before you reinstall anything.
Once it starts, each game gets a "<name> registered" notification and its own home-screen tile. The registration system and the fakelib sandbox overlay are ported from drakmor/ShadowMountPlus, which the project credits directly.
Managing Games: The Tile Versus the Web Interface
You have two ways to manage your library. The home-screen tile opens the interface on the console. From a computer, you can open http://<ps5-ip>:8097/ to see your games, rebuild or delete them, change settings, and read the log. The web interface is the better choice when you're troubleshooting, because reading a log on a TV screen is slow.
| Access method | Requires | Best for | Limitation |
|---|---|---|---|
| Home-screen tile | elfldr running, payload saved on console | Launching the mounter directly | Dead if elfldr isn't running |
| Web UI on port 8097 | Computer on the same network | Rebuilds, deletes, settings, log reading | Needs the console's IP and a browser |
Manual nc send on port 9021 | Computer, netcat, the ELF file | Reloading after an update | Must be repeated after each reboot if elfldr doesn't auto-start |
The last row is an inference from the README's setup steps rather than a documented behaviour, so verify it on your own setup before relying on it.
Know where the data lives, too. Settings are in /data/krakenmount/config.toml, the log is in /data/krakenmount/kraken.log, and the bundled ampr-emu-ng is installed into /data/krakenmount/ampr/ at startup. The log is your first stop when something fails. Most people skip it and go straight to reinstalling, which wastes time.
Swapping the Bundled Emulation Library
Kraken Mount ships with ampr-emu-ng already installed. If you want to run a different build, place its libSceAmpr.sprx in /data/krakenmount/ampr/. The file stays there until you delete it.
This is a useful feature, and it carries a real caveat. A swapped library changes behaviour across every game the tool mounts, not just one title. If a game starts failing after a swap, the library is the first suspect. Keep a copy of the working bundled file before you replace it. Then you can roll back by deleting the new file and letting the known-good one return on the next start, or by restoring your copy yourself.
Where Mounts Break and How to Diagnose Them
Most failures follow a predictable pattern. Here's the cause and effect for the four I see most often:
- A
.pkgthat isn't a plaintext debug FPKG won't mount. The file looks right in your library, but the mounter rejects it because the format doesn't match what the tool expects. - A folder missing
sce_sys/param.jsonwon't register. The game folder is present, but without the metadata file there's no tile to create. - A game in an unscanned subfolder won't appear at all. The scanner checks specific roots, not your whole drive.
- A stale cache after a rebuild can show old data. Rebuilding from the web UI is the fix, and if that fails, clear
/data/krakenmount/caches/<TITLE_ID>and try again.
When something fails, read kraken.log before changing anything else. One log entry usually tells you which of these four cases you're in.
Legal Boundaries, Firmware Risk, and Building From Source
Kraken Mount is homebrew. It requires a console that already runs a payload loader, and it's not a product from Sony or any retailer. Use it only with content you own or have the rights to use. The project is licensed under GPL-3.0-or-later, and third-party notices are in THIRD_PARTY_NOTICES.
Firmware compatibility is a separate question, and the README doesn't document a full support matrix. Treat any console update as a reason to recheck that elfldr, the payload, and your games still work together. Keep copies of anything you can't easily reacquire.
If you'd rather not trust a prebuilt binary, you can build it yourself. Run ps5/build.sh with Docker installed, and the output lands at target/ps5/kraken-mount.elf. The build pulls in the ps5-payload-sdk, which the project credits as its toolchain. Building from source takes longer, but you know exactly what you're loading onto your console.
Frequently Asked Questions
What is a PS5 game mounter?
A PS5 game mounter is a homebrew payload that scans storage for games and mounts them so they appear as launchable titles on the home screen. Kraken Mount is one example. It runs as an ELF file loaded through elfldr, and it supports debug FPKG .pkg files plus plain or zstd/LZ4-packed game folders.
How do I mount a PS5 game folder with Kraken Mount?
Place the folder in a scan root such as /data/homebrew or homebrew on a USB drive. Make sure it contains eboot.bin and sce_sys/param.json, then start Kraken Mount. A "registered" notification and a home-screen tile confirm success. If it doesn't appear, check the log at /data/krakenmount/kraken.log.
Why doesn't my game show up after I copy it?
The most common causes are a missing param.json, a folder placed outside a scan root, or a .pkg that isn't a plaintext debug FPKG. Each one fails silently at the registration step. Check the folder layout first, then rebuild from the web interface on port 8097.
Where does Kraken Mount store its settings and cache?
Settings live in /data/krakenmount/config.toml, and the log is in /data/krakenmount/kraken.log. Per-game caches are in /data/krakenmount/caches/<TITLE_ID>. Clearing a title's cache folder forces a clean rebuild the next time it's processed.
Most people who get a PS5 game mounter working on the first try do one thing differently: they check the folder layout and the log before they reinstall. Try checking your scan roots this week, then open kraken.log after the next start and note what it says. Pass this guide to anyone stuck on a game that won't register, because the fix is usually one missing file.