Is my file uploaded?
No. A browser Worker reads selected byte ranges from your File. There is no upload API, analytics or third-party runtime script. JSON reports and supported SFO/icon resources are saved through local browser downloads.
Can it extract a protected PS4 game?
No. You can extract readable param.sfo and icon0.png header resources, but not complete game folders or protected payloads. This tool does not decrypt protected game data, validate package signatures, or establish gameplay compatibility.
Are PS4 and macOS PKG the same?
No. PS4 packages commonly start with the CNT signature. Flat macOS installers use an XAR container. XAR may also contain other data, so detection alone is not proof of an installer.
Why is my Title ID unavailable?
TITLE_ID must be read from a plaintext param.sfo. If SFO is absent, encrypted, invalid or over the read limit, the field stays unavailable. Renaming the file does not supply this metadata.
How large can a file be?
There is no arbitrary full-file size cap, but the browser and operating system must expose it as a local File. Header-only inspection reads 1,444 bytes. Entry-table and SFO reads are each limited to 1 MiB. Icon extraction reads up to 8 MiB separately, with PNG dimensions limited to 2048 × 2048. Huge-file read volume is tested; browser memory and device limits vary.
Does a readable package mean compatibility?
No. Readable metadata does not establish successful extraction, installation or gameplay. Public project requirements and this site’s own tests are kept separate.