Keep an untouched copy before conversion, editing, repair, or checksum work.
PlayStation / Save hub
PSP save files & tools
PSP save-file documentation, format notes, emulator workflows, and compatible save utilities where technically appropriate.
01 / Platform context
Match the save workflow before choosing a tool.
SaveEditor.com treats the platform as part of compatibility. File locations, containers, byte order, memory-card formats, emulator behavior, account binding, and signing can change what is safe or technically possible.
Verified and in-development Tools are clearly separated. Planned records do not appear here.
Browser-local, server, hybrid, and informational workflows are labeled at Tool level.
02 / Game hubs
Published PSP game-save hubs
A Game Hub is useful documentation. It does not imply a game-specific Save Editor exists; each card shows linked Tool state separately.
No published Game Hubs are assigned yet.
The platform page does not create placeholder game records merely to look populated.
03 / Active tools
PSP tools with explicit support state
Only published Verified and In Development Tool records are shown. Planned and deprecated Tools are excluded from this hub.
Verified
File Analysis
PSP PARAM.SFO Key Inventory
List every key in a strictly parsed PARAM.SFO table with no game-payload interpretation.
Verified
File Analysis
PSP PARAM.SFO Type Inspector
Classify strictly parsed PARAM.SFO entries by encoded value type and format identifier.
Verified
File Analysis
PSP PARAM.SFO Capacity Auditor
Compare each PARAM.SFO entry’s used length and declared maximum capacity without rewriting metadata.
Verified
File Analysis
PSP PARAM.SFO Title Metadata Viewer
Expose only present common title/save identifiers from a strictly parsed PARAM.SFO table.
Verified
File Analysis
PSP PARAM.SFO Fingerprint
Prove a high-confidence PSP PARAM.SFO Fingerprint match from strict local content/structure checks without trusting filename extension or byte length alone.
Verified
Emulator & Retro Tools
PSP Save Viewer
Inspect metadata from a PSP PARAM.SFO file locally, including title/category fields and numeric or UTF-8 entries, without decrypting or rewriting the associated savedata payload.