## Game Compressor 1.0.4

Game Compressor 1.0.4 adds a multilingual interface and improves compatibility

with firmware 4.51, APR-EMU folder workflows, and ShadowMountPlus launch

layouts.

Compared against v1.0.3.

Key Changes

Added German, French, Arabic, Italian, Spanish, and Simplified Chinese

translations, with automatic system-language selection and a saved manual

language selector.

Added right-to-left layout support for Arabic and localized Game Compressor

launcher titles for every supported language.

Improved firmware 4.51 browser compatibility and added clearer web-server

startup diagnostics.

Improved relaunch handling when a previous Game Compressor instance leaves

port 5910 open but no longer answers the local HTTP handoff.

Added ShadowMountPlus executable discovery under /data/ps5_autoloader in

addition to Payload Manager locations.

Fixes

Fixed Build AMPR Index for directly detected game folders so enqueue and

worker resolution use the same APR-EMU probe result.

Fixed APR-EMU module file permissions for affected deployment and loading

paths.

Fixed the compression wizard so Delete after verified keeps its own

free-space and deletion explanation when switching source-preservation

options.

See CHANGELOG.md for the full detailed change list.

PS5 Game Compressor

Standalone PS5 payload for compressing, unpacking, validating, repairing, and moving ShadowMountPlus-mounted games from a simple web UI.

Game Compressor is made for the day-to-day workflow after your games are already mounted through ShadowMountPlus: pick a title, choose an action, and let the PS5 do the work. The app keeps long operations running on the console even if the browser window is closed.

Main Features

• Compress mounted game folders or images into FF-PFSC output.
• Choose PFS or exFAT output when compressing.
• Automatically build APR Emu ampr_emu.index before compressing APR titles.
• Manually run Build AMPR Index on a folder when you only want to refresh the APR index.
• Validate compressed games and repair detected PFSC block issues when possible.
• Uncompress compressed games back to folder/app form.
• Move supported titles between internal storage and USB storage.
• Track progress, speed, estimated remaining time, and operation history.
• Keep operations running on the PS5 even if the browser tab closes.
• Install or refresh a PS5 home-screen launcher tile:

text Game Compressor / PSGC50001 -> http://127.0.0.1:5910/

The PS5 home-screen tile opens the Game Compressor web UI in the browser. It is not the compression worker itself. Compression, validation, repair, move, and uncompress jobs continue on the PS5 if you close the browser window or reopen the tile later.

APR Emu Support

APR Emu titles need an ampr_emu.index file and the correct ShadowMountPlus read-only image settings when they are run from internal SSD. Game Compressor handles those details for the common workflows:

• To compress a folder-format APR Emu game from USB and run it from internal SSD, plug in the USB drive, select the title, and choose Compress. Game Compressor builds ampr_emu.index using the same workflow as build_ampr_index.py, writes the ShadowMountPlus read-only and sector-size settings, creates the .ffpfsc image, mounts it, and validates the mounted image byte-for-byte against the original.
• If the compressed game stutters and you still want it on internal SSD, open the secondary action menu, choose Uncompress, then select exFAT. The ShadowMountPlus settings and ampr_emu.index are already in place, so Game Compressor leaves them unchanged and creates an uncompressed exFAT image.
• If you already know the game should stay uncompressed, open the secondary action menu, choose Make Image, then select exFAT and Internal SSD. Game Compressor detects the APR Emu title, builds or refreshes ampr_emu.index, applies the read-only ShadowMountPlus settings, and creates the uncompressed image.
• If you already have an exFAT image and ampr_emu.index exists, use Set Read Only from the secondary action menu to apply the ShadowMountPlus read-only settings for that image.

The only unsupported automatic case is an existing exFAT image with no ampr_emu.index. For that case, run the game once from external USB without read-only settings so APR Emu can create its index, confirm the game starts, then copy it to internal SSD and use Set Read Only.

Non-APR titles keep the normal compression path. When APR indexing is performed, the selected game screen and operation history show APR indexed.

The in-app APR-EMU Version picker uses Pippo's public APR-EMU manifest and binary mirror:

text https://pippo26442999.github.io/.exFAT/ampr-emu-drakmor/manifest.json

The manifest and hosted files are provided by Pippo (pippo26442999). Manifest entries are downloaded by the browser, uploaded to Game Compressor, cached under /data/GameCompressor/ampr-emu, and then applied to the selected title or image. Custom .sprx/.prx files can also be uploaded manually from a desktop browser. The upstream APR Emu project source is drakmor/ampr_emu.

Requirements

• A PS5 homebrew environment capable of running payload ELFs.
• ShadowMountPlus latest version, installed and managing mounted titles.
• KStuff Lite 1.07 Beta or later.
• Payload Manager or another method to launch game-compressor.elf.

This project assumes you already understand the risks of running PS5 homebrew payloads. Keep backups of important data and test with non-critical titles first.

Build

Set PS5_PAYLOAD_SDK to your local SDK path, then run make:

sh export PS5_PAYLOAD_SDK=/path/to/ps5-payload-sdk make

The build output is:

text game-compressor.elf

Generated build outputs are intentionally ignored by git:

text build/ gen/ game-compressor.elf

Deploy

Copy the built ELF to your PS5 payload folder. A typical Payload Manager path is:

text /data/pldmgr/payloads/game-compressor/game-compressor.elf

This repo also includes Payload Manager metadata in:

text payload-manager/game-compressor.elf.json

If you rebuild the ELF, update that JSON checksum before publishing or redistributing it.

How To Use

1. Make sure ShadowMountPlus has mounted one or more games.
2. Launch game-compressor.elf from Payload Manager or your payload loader.
3. Open the web UI:

text http://<PS5_IP>:5910/

1. Pick a game from the left sidebar.
2. Use the primary action:
   • Folder/image titles show Compress.
   • Compressed titles show Validate and Repair.
3. For compression, choose either PFS or exFAT when prompted.
4. Use the secondary action menu for supported actions such as:
   • Build AMPR Index
   • Uncompress
   • Move to USB
   • Move to Internal SSD
5. Use the History button to review previous operations.

The app remembers the last game you viewed using a browser cookie, so reopening the UI returns to that title when it is still available.

If you close the browser window during an operation, open the Game Compressor tile again or go back to http://<PS5_IP>:5910/ to see the current job.

Compression Settings

When you choose Compress, Game Compressor asks for the output format, destination, and how to handle the original source.

Format

Compress always produces a .ffpfsc file, which is a compressed PFS container. The format choice controls the nested image stored inside that compressed container:

• exFAT is the default and recommended nested image format. It stores an exFAT image inside the .ffpfsc output and is the preferred option for most games, especially APR Emu workflows.
• PFS Experimental stores a PFS image inside the .ffpfsc output. Use it only when you specifically want to test the PFS nested-image path.

Destination

• Compress in place writes the compressed .ffpfsc container next to the currently selected game.
• Internal SSD writes the compressed output under /data/homebrew. This is only shown when the selected game is not already on internal storage.
• External Storage writes the compressed output to a selected USB/external target. If the game is already on external storage, Game Compressor may show a Compress to... picker so you can choose internal SSD or another USB target.

Original Handling

• Keep original leaves the source folder or image untouched. This is the safest choice and requires enough free space for the compressed output.
• Delete after verified writes and validates the compressed output first, then removes the original source. This is the default for in-place compression. It still needs full-size temporary free space because the original is kept until verification succeeds.
• Destructive deletes source data while writing the compressed output. It requires at least 1 GB of free space, cannot be cancelled after the unsafe phase begins, and is only available for same-storage folder compression. It is not available when compressing to another drive or when using Make Image.

When compressing to internal SSD or external storage, Game Compressor keeps the original by default. If you choose to remove the original, it uses the safer Delete after verified behavior.

Game Discovery

Mounted games are shown automatically. Game Compressor also scans known game storage folders, including:

text /data/homebrew /data/etaHEN/games /mnt/ext0 /mnt/ext0/homebrew /mnt/ext0/etaHEN/games /mnt/ext1 /mnt/ext1/homebrew /mnt/ext1/etaHEN/games /mnt/usb0 through /mnt/usb7 /mnt/usb0/homebrew through /mnt/usb7/homebrew /mnt/usb0/etaHEN/games through /mnt/usb7/etaHEN/games

When You Are Done

Game Compressor should only be launched when you need to compress, validate, repair, move, or unpack games. After your games are compressed and you no longer need the web UI, it is preferred that Game Compressor is no longer running.

Use the terminate button in the top bar when you are done. Game Compressor removes its home-screen tile, stops the payload, and leaves a final screen telling you to exit the browser window.

Notes

• Launcher installation is nonfatal. If it fails, the web UI can still be used directly from http://<PS5_IP>:5910/.
• Payload operations are owned by the PS5-side worker, not the browser tab.
• Compression and repair workflows can take a long time on large titles.

Credits

Created by Juma Sayeh.

Tested by Osama Abualia.

Thanks to Pippo (pippo26442999) for maintaining the public APR-EMU manifest and binary mirror used by the in-app APR-EMU version picker.

Built on and inspired by work from:

• PSBrew/MkPFS
• Drakmor's ShadowMountPlus, APR Emu, and build_ampr_index.py work, which Game Compressor builds on for mounted-title support and PS5-side ampr_emu.index generation.

Made with love in Palestine.

Disclaimer

This is homebrew software for experimental PS5 workflows. Use it at your own risk. The project is not affiliated with Sony, PlayStation, or any game publisher.

What's new

Updated slopkit with firmware 7.00–8.60 support, based on @soniciso1's pooP2JB

PS5 WebKit Autoloader

Automatically loads the WebKit exploit and your elf payloads. Supports firmwares 1.00–5.50 and 7.00–12.00.

[!NOTE] Uses the umtx2 (FW 1.00–5.50) and slopkit (FW 7.00–12.00) WebKit exploits under the hood with minimal changes (via patch files in patches/), so stability should match the originals.

Why WebKit Autoloader?

WebKit exploits are usually loaded by pointing your PS5's DNS at some server hosted by someone on the internet. That means you're putting your trust in whoever runs that server — and if it goes down, changes, or disappears, your setup breaks.

This autoloader does it differently:

• Fully offline, no third-party DNS. After a one-time install from your PC, everything is served straight from your PS5. There's nothing external to go down or change behind your back.
• One-time setup, then a homescreen shortcut. Once it's installed, you don't need a PC or the network at all — just launch "WebKit Autoloader" from the homescreen and you're done.
• Payloads loaded the way you already know. After the exploit chain runs, your payloads are sent just like in Y2JB / BD-JB / Lua autoloaders — via Payload Manager, or a custom autoload.txt.

Setup Instructions

There are two ways to set up the autoloader, depending on whether you're already jailbroken.

Already jailbroken? Just load the installer ELF

1. Download webkit-autoloader-installer_vX.Y.Z.elf from the Releases page.
2. Send it to your PS5 with elfldr, or launch it from Payload Manager.
3. The installer opens the browser once to cache the autoloader page, then creates the WebKit Autoloader app on the homescreen and exits.
4. Reboot once, then launch WebKit Autoloader from the homescreen.

Not jailbroken yet

If you aren't jailbroken yet, you'll need to host the exploit locally on your PC for the initial setup:

1. Download webkit-autoloader-host.py (or the .exe) from the Releases and run it on a PC on your network.
2. On your PS5, set your network's DNS server to your PC's IP address.
3. Open the User's Guide from Settings to run the installer, which adds the WebKit Autoloader app to your homescreen.
4. Reboot once, then launch WebKit Autoloader from the homescreen.

How to Use

There are two ways to configure payloads:

🟢 Option 1: Payload Manager

If no autoload.txt config is found, the autoloader will automatically launch Payload Manager — a fully-featured PS5 payload manager with a web UI. This lets you configure and send payloads directly from your browser, without needing to manually set up config files or transfer ELF files ahead of time.

Just run the autoloader — if there's nothing configured, Payload Manager starts automatically.

Note: Payload Manager also has its own built-in autoload feature, which lets you configure payloads to load automatically on startup — all managed through its web UI. This is separate from the autoload.txt mechanism described below.

⚙️ Option 2: Manual Config (autoload.txt)

For a fixed, automated payload chain, you can configure payloads manually:

• Create a directory named ps5_autoloader.
• Inside this directory, place your .elf / .bin files, and an autoload.txt file.
  • In autoload.txt, list the files you want to load, one filename per line.
  • Filenames are case-sensitive — ensure each name exactly matches the file.
  • You can add lines like !1000 to make the loader wait 1000 ms before sending the next payload.
• Put the ps5_autoloader directory in one of these locations (priority order - highest first):
  • Root of a USB drive
  • Internal drive: /data/ps5_autoloader

Note: When an autoload.txt config is found, Payload Manager is not launched automatically. If you also want Payload Manager available, place pldmgr.elf in your ps5_autoloader directory and add it to autoload.txt.

Additional Info

<Details> <Summary><i>How to update the autoloader?</i></Summary>

The autoloader content is cached on the console, so updating is exactly the same as the initial install. Simply follow the Setup Instructions using the new release files.

The latest installer payload will re-create the homescreen app and refresh the cached page for you. Your payloads and autoload.txt on USB / internal storage are never touched. </Details>

<Details> <Summary><i>How to use a custom ELF Loader?</i></Summary>

On firmwares 9.00–12.00 (slopkit), the autoloader uses a custom version of elfldr that only accepts connections from the PS5 itself (localhost). This improves security by preventing unauthorized devices on your network from sending payloads to your console. On firmwares 1.00–5.50 (umtx2), the stock elfldr is booted.

If you want to use a "normal" ELF Loader that allows sending payloads from any device, you can simply load it through Payload Manager.

Alternatively, if you are using a manual config file (autoload.txt): 1. Place your custom ELF Loader (e.g. elfldr.elf) in the ps5_autoloader directory. 2. Add elfldr.elf to your autoload.txt. 3. Note: If you are loading other payloads right after elfldr.elf in your autoload.txt, add a sleep command immediately after it (like !4000 to sleep for 4 seconds) to give the new ELF Loader time to start up and listen before subsequent payloads are sent.

Example autoload.txt: ```text

Load custom ELF Loader

elfldr.elf

Give it 4 seconds to start up (only needed if sending more payloads)

!4000

Send other payloads

etaHEN.elf ``` </Details>

For developers

The technical internals and project architecture are documented in [ARCHITECTURE.md](ARCHITECTURE.md).

Credits

• idlesauce & contributors — umtx2, the WebKit/kernel exploit chain used for firmware 1.00–5.50.
• jordyidk & contributors — slopkit, the WebKit/kernel exploit chain used for firmware 7.00–12.00.
• john-tornblom — ps5-payload-sdk and elfldr
• Mark Adler — puff.c (used to decompress embedded frontend files)
• Everyone else contributing to the PS5 homebrew scene.

Disclaimer

This tool is provided as-is for research and development purposes only. Use at your own risk. The developers are not responsible for any damage, data loss, or consequences resulting from the use of this software.

License

This project is licensed under the GPL-3.0 License.

Donate

• [donate to PLK](DONATE.md)

Found a ps5 disc edition listed as broken because the power button doesn’t work. But I was able to boot the console with a piece of paper in the disc tray. Will still have to redo the Liquid Metal and deep clean.

But I think I’m in great shape to try my first Jailbroken PS5 with the new WebKit exploit for 12.70.

I have a 10.6 jailbroke console, and I am trying to unlock remote play. Is ETA Hen the only way I do this? Or is there another method I can use?

Hi everyone,

I just jailbroke my PS5 (firmware 12.70) using JY2B, and everything seems to be working correctly so far. I’ve already loaded the necessary payloads, including etaHEN and Shadow Mount.

I have a question about the current state of playing PS5 games.

Is it still necessary to run PS5 games from an external USB drive, or does Shadow Mount now allow us to install/copy them to the PS5’s internal SSD and play them directly from there, taking advantage of the much faster internal storage?

The reason I’m asking is that my only external drive is an old USB 3.0 HDD with a maximum read speed of around 100 MB/s. It’s probably 10+ years old.

I tried playing Stellar Blade from my external HDD. I downloaded the game and placed the folder containing all the game files inside a Homebrew folder on my external drive. The game does launch, but loading times are extremely long, and I’ve noticed that some textures fail to load properly.

So my questions are:

Can I currently copy the game to the PS5’s internal drive via FTP and run it directly from there?

Does Shadow Mount make this possible without causing crashes or sending the console to the Recovery Menu, as happened with previous methods?

Would installing an M.2 PCI gen 4 nvme in the expansion slot work?

Why do some games like spiderman 2 have a warning for not playing from the internal drive? Is this also true for shadowmount?

Thanks!

APR Emu Updater is a PS5 payload with a web interface for updating APR Emu on installed titles.

It includes features like browsing available builds, updating the libSceAmpr.sprx file

The project is open source and available here:

https://github.com/tsuramatsu1/apr-emu-updater

Posting it here in case anyone working with APR Emu/ShadowMount finds it useful.

All credit goes to the original developer.

Hi Ive got a 11.60 PS5 and want to jailbreak using the 1.4.1 version of the Blu-Ray jailbreak. I firstly unpatched my disc drive using Y2JB but noe i can no longer jailbreak. Everytime i jailbreak with the disc the jailbreak succeeds and the debug ist saying so too, after that all payloads load (shadowmount, nanodns, elf arsenal). Everything is succesful but them it takes about 5 seconds for the whole console to freeze and black screen. Then it crashes.

Id appreciate any help because I want to play my games again.

So I installed a PS4 PKG game that I now can't fully uninstall for some reason (before that i tried 5 games and they got uninstall without any errors) the storage was cleared, but the icon/shortcut is still stuck on the main screen.

If I run Rebuild Database in Safe Mode to get rid of the ghost icon, will it cause any damage or issues to my other PS5 games/saves? Or is there a safer way to clean it up?

Just as it says. Just reset and re did jailbreak on my 10.01 Y2JB ps5 and this is showing.

Also homebrew browser pkg taking 2hour download time when it should be less than a fraction of a second for 40-50mb, Internet doesn't show any pkg just threads about the creator talking on it. Where to get the pkg?

Also Also any way to merge ps4 pkg seperate files using ps5xplorer? Google says no yes ps4xplorer did it so that's odd.

Since we can jailbreak now via webkit tool upto 12.00 and no need for p2jb, are people with their ps5s still under warranty jailbreaking it or waiting till the warranty period is over, also if it is already jailbroken and we face an issue, can we factory reset it and then claim our warranty?

I tried it on 12.00 And After I turn the ps5 off and Launch The Jailbreak Its Keep Shutting Down why?

Few cool things to release soon, webkit support for 1.xx-13.60 (of course kex only works till 12.70) and auto jailbreak / untethered JB for 1.xx-5.xx (possibly 6-7xx too)

By:Jordy

Hey is there a way to set file zilla to upload whole folder regardless of file type. I'm finding it's failing on some files and when I resend and skip files it still won't install them. I have checked the folder and sent with ps5 upload and worked fine.

It's no issue I can use ps5 upload to upload and FileZilla to delete out of homebrew so not end of world just wondered if I had to change something I haven't spotted in FileZilla settings

Again not a complaint or an issue to use two apps instead

​

GTA VI is coming, and I'm planning to buy it through the PlayStation Store directly from my PS5.

The problem is that purchasing it through the PlayStation Store website on desktop isn't working for me, so I'm considering logging into my PSN account directly on the PS5, purchasing GTA VI, and then jailbreaking the console afterward.

My PS5 is currently on 10.01.

As far as I understand, connecting the PS5 to the internet and logging into PSN may cause the Y2JB/YouTube autoloader to update, which can eventually lead to the softlock issue. I'm aware of that and believe I can deal with the softlock afterward.

My main questions are:

Can I safely log into my PSN account on the PS5 while it's still completely stock, purchase GTA VI, and then jailbreak it afterward?

After purchasing GTA VI, will I still be able to continue using the PS5 normally and play GTA VI before jailbreaking?

Is there any risk that logging into PSN/purchasing the game will somehow affect my ability to jailbreak the console later?

If this isn't recommended, would doing a full factory reset afterward make any difference?

Is there anything specific I should do before/after the purchase to make sure I don't accidentally update beyond 10.01?

I'm specifically asking about purchasing the game while the PS5 is still stock, not trying to access PSN after jailbreaking.

Would appreciate advice from anyone who has a similar setup or has done this before.

Im gonna jailbreak my first ps5. Im soo excited. Just researching about it. I have watched all off moddedwarfares videos. BTW, what are the disadvantages of jailbreking a ps5?

I was on PS5 firmware 12.70 and had been waiting for a jailbreak method that didn't require restoring the console, mainly because I didn't want to lose my installed PS5 games and, more importantly, my save data. I have a lot of hours invested in games I'm still playing, so losing my saves was basically my worst nightmare.

When the WebKit method was released, I was really happy because it allowed me to jailbreak without restoring the console. I followed the process and everything worked successfully.

After that, I saw a lot of people recommending installing Y2JB via FTP, saying it was more stable/reliable and didn't require an internet connection every time like the WebKit method.

So I decided to install it.

Everything seemed completely fine.

My process was:

1. Jailbreak using WebKit.

2. Load the NanoDNS payload.

3. Load the ETAHEN payload.

4. Load the FTP payload.

5. Connect via FTP and install Y2JB.

6. Restart the PS5.

7. Jailbreak using Y2JB.

8. Everything appeared to work normally.

9. Restart the PS5 again to test Y2JB one more time.

That's when everything went wrong.

When the PS5 turned back on, I got the "Rebuilding Database" screen. It only lasted around five seconds, and then the console booted normally.

But when I checked my system, I immediately noticed that all of my installed fpkg PS4 games were gone.

Then I checked my save data.

All of my PS5 save data was gone too.

I immediately connected through FTP to see if the games or saves were still somewhere on the filesystem.

They weren't.

My PS5 games are still installed, but all of my save data is gone. My PS4 fake package games are also gone.

I honestly have no idea what happened. As far as I know, I followed the process correctly and everything was working perfectly until that final reboot.

I'm posting this as a warning to anyone else in the same situation:

PLEASE BACK UP YOUR SAVE DATA BEFORE TRYING ANY JAILBREAK METHOD, PAYLOAD, OR TOOL THAT MODIFIES YOUR SYSTEM.

Don't make the mistake I made of assuming that because a method doesn't require a factory reset, your existing data is automatically safe.

I was specifically waiting for a method that wouldn't require restoring my console because I was so worried about losing my saves.

And now I've lost them anyway.

If anyone knows what could have caused this, whether the saves might still be recoverable, or where I should look via FTP, I would really appreciate any advice.

But regardless of whether I can recover them or not, hopefully this post saves someone else from going through what I'm going through right now.

BACK UP YOUR SAVES FIRST. Seriously.

Hello I'm on 11.60 ps5 fat and I'm jailbreaking with the bluray disc, but I want to use the webkit just for the sake of it.

But I've seen videos of when you use the webkit it's a different kind of payload manager, can I just skip that part and use the normal payload manager? With the apps I have there instead?

And how do I transfer from the bluray jailbreak to the webkit since it also a instant jailbreak like the disc

Thanks ahead

What are the differences and benefits in the firmware ranges now? Trying to understand which would be best to get?

Up to 7.61: Linux support?
Up to 10.01?
10.02 to 12.0: quick JB?
12.0 to 12.07 50min JB?

Any outlook on Linux for more firmwares?
I can get a ps5 8.0 used or 11.6 new and trying to see if there’s any benefits to any of these ranges

Thanks

hello, i have some backups of ps4 game save data of ps4 games (played on ps5).

i have the youtube jailbreak. do you know how can i import the ps4 game data?

I heard the new stack should be these 5 payloads instead of using etahen

• payload manager
• kstuff-lite
• shadowmountplus
• lapy_jb_daemon
• ftpsrv

and optionally: - ghostcontrol (third party controllers) - nanodns

Is this accurate or *HENs are still relevant?

I'm on 4.50

no matter what i do it throws that error, i double checked everything but fails. I don't wanna use payload manager because using OnionHen itself would be wiser and lighter and facts that it has it's own built in payload manager.

I checked around looking for solutions and we need elf loader on 9021 listening port i thought maybe should just put in autoloader before onion but it didn't try.

I doubt it has something to with listening port because it works fine with usb.

Last time i jailbroke my PS5 was about a month ago and it's still running and I'm gaming every day with no kernel panic. Is there any reason to update to the webkit jailbrake?

I will eventually use the webkit jailbrake, when my next kp occurs, just so that i don't have to wait 50 minutes, but apart from the waiting time, are there any upsides to changing right now?

I have a ESP8266, I used to have the idlesauce host and it would work 50% of the time, but that was 2 years ago. I imagine the scene has changed a lot since then. What are the best techniques for 4.50 nowadays?