PS5 UltraPack builds installable PS5 packages on macOS, no Wine needed
A new macOS app builds PS5 .pkg files without Wine or Sony DLLs, and its author says they launch on retail firmware 11.60.
A new macOS app called PS5 UltraPack, from knutwurst, can turn a game folder, archive or disk image into a PS5 .pkg that installs on a jailbroken console. The author says a homebrew test package launches on a retail PS5 running firmware 11.60 with kstuff-lite 1.13-dr-test3. If you work on a Mac and have been fighting Wine for PS5 packaging, the key line is simple: no Wine, no Sony DLL.
The core is a bundled ffpfsc-pkg-tool, a self-contained .NET 9 build of drakmor’s LibProsperoPkg 1.2.0 (GPL-3). The app also packs, unpacks, browses and patches .ffpfs, .ffpfsc and .pkg files, and it can fake-sign them. Auto-organize names the output <Title> [TITLEID] [vXX.YYY] [fwN.NN].pkg, reading the identity from the game’s own param.json. A validate checklist runs after every build, and if the console rejects a package, the log names the check that failed.
The more interesting part is the history. The README says earlier builds hit an “11.40 at most” ceiling. The author traces that to one wrong outer-PFS wrap mode in this builder, not to a Sony patch. A byte diff against a libScePubTools.dll reference build shows the inner PFS is identical; only timestamp and ICV bytes in the outer wrap differ. Retail titles also reportedly launch since 1.1.12, with saves kept.
My take: fixing a format bug by diffing against a reference build is how this scene should work, and it’s rare to see a mistake described this plainly. Mac users have needed a native path for a long time. Still, 16 stars and a test log in the README mean this is early. “Verified” here means one console and the author’s own tests.
Limits to know before you start. You need a jailbreak on the console, and package behavior depends on that jailbreak, not on the builder. Backport targets are 7.61 (the documented path), 6.02 (experimental, only some titles run) and 10.xx (SDK values only). No system library ships with the app; you extract them from your own firmware. Encrypted executables stop the job with a message.