PKGExtractor.Private by design
HomePS4 WORKSPACE
PS4 WORKSPACE

PS4 PKG Inspector & Extraction Guide

See what the package actually says.

Reviewed October 19, 2026 · Preview
Local workspace/ Package inspector
On-device processing
01 SELECT YOUR FILE
.pkg

A closer look at your PKG.

Drop a package here to read its format
and available metadata.

or drag & drop a file · no upload required

Your file stays yours. Only selected byte ranges are read. Nothing is sent to a server.

02 INSPECTION RESULTS
Waiting for your file

Your package, made clearer.

Select a file to see its signature, header fields and any readable metadata.

File formatContent IDAvailable SFO fields
Source file stays unchanged No account neededHow local processing works

Inspect before you extract

The inspector checks the CNT signature, declared ranges and header entry table. It can read Content ID from the header and TITLE_ID / APP_VER from an unencrypted, valid param.sfo. A recognized signature is not proof of authenticity or installability.

What “extract” means here

The Extract files tab saves original plaintext param.sfo (up to 1 MiB) and icon0.png (up to 8 MiB, 2048 × 2048 pixels) when supported. Encrypted, missing, duplicate, overlapping or invalid resources are refused. General game extraction and internal game filesystem browsing are not implemented. A separate Apollo v2.4.0-only WASM experiment, linked from the homepage, can unpack that exact verified homebrew package to ZIP. Every other package is refused. A JSON report is metadata, not game files.

Compare local extraction tools

Why fields can be unavailable

An SFO can be encrypted, absent, malformed or beyond the bounded read limit. Missing fields remain unavailable. The filename is never used to identify a title or version.

Format reference: LibOrbisPkg PS4PKG.bt (LGPL-3.0, reference only). No authenticity or real-package compatibility certification.