PSP savedata folders commonly include a PARAM.SFO metadata file alongside game-specific savedata. Phase 34 retains only that structured metadata surface. The parser validates table boundaries before reading values and does not claim that metadata access means the protected game payload is decrypted or editable. This keeps the tool useful for identification and inspection without crossing into unsupported signing or encryption behavior.
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.
01 / Tool workbench
Use the runtime only when it is actually ready.
The application shell fails closed. An input interface is not enabled merely because a WordPress Tool record exists; the declared engine must be registered in the current build.
Session change summary
No output has been built in this session.
02 / Compatibility
Know the supported input before opening a file.
Compatibility fields are intentionally explicit. Missing values stay unclaimed rather than being filled with generic assumptions.
Accepted extensions
.sfo
Platforms
PSP
Supported versions / editions
PSP/PlayStation PARAM.SFO metadata structures using recognized UTF-8 or uint32 value formats.
Input constraints
Phase 34 retains PARAM.SFO metadata parsing up to 2 MiB. The PSF header, index table, key table, data table, entry lengths, and offsets must pass bounds validation.
Known limitations
This is a metadata viewer, not a PSP savedata decrypter, resigning tool, account editor, game-save editor, or arbitrary PARAM.SFO writer. Unknown value types are shown as bounded hexadecimal bytes.
Output / result
Read-only PARAM.SFO metadata table. No modified save or metadata file is generated.
03 / Instructions
Use a reversible workflow.
File-oriented workflows start with an untouched original. Tool-specific instructions add only details documented for this utility.
- 01Keep the original
Preserve an untouched copy before creating or transforming binary output.
- 02Confirm scope
Match the file size, format, platform, and version to the support information on this page.
- 03Process locally
Use the runtime only when the page reports that its declared engine is loaded.
- 04Validate output
Compare or test the result before replacing any working source file.
Tool-specific steps
Choose the PARAM.SFO file from a savedata folder. Review parsed key/value entries and use them as descriptive metadata only.
04 / Privacy and processing
The processing mode is part of the product contract.
SaveEditor.com should state local processing only when the implementation truly keeps file contents in the browser. Server or hybrid processing must be disclosed just as clearly.
Declared mode
Browser local
Runtime state
Operational
Tool-specific privacy notes
Phase 36 reads a selected file only after explicit local file selection. Parsing, inspection, normalization, extraction, and supported conversions run in the browser. The emulator-retro runtime contains no fetch, XMLHttpRequest, WebSocket, or sendBeacon calls. The shared file ceiling is 16 MiB, with stricter format-specific limits where appropriate.
05 / Troubleshooting
When a file is rejected, do not force it.
A rejection can indicate an unsupported size, format, version, platform, or byte sequence. Preserve the original and correct the input instead of bypassing validation.
Re-check the documented input type and browser size limit before retrying.
A generic converter does not imply support for every game-specific container, signing scheme, or serialization format.
Return to the untouched source instead of repeatedly processing a damaged or partially transformed file.
Known Tool issues
If a file begins with the PSF signature but contains invalid table offsets or lengths, it is rejected. Encrypted or game-specific save payload files are outside this profile.
06 / Verification
Support claims should be traceable.
The verification date, method notes, and public references are kept separate from marketing language so compatibility can be reviewed over time.
Last verified2026-08-08
Profilepsp-save-viewer
Method notes
Verified with constructed PARAM.SFO fixtures containing UTF-8 and uint32 entries, table-offset bounds checks, malformed-entry rejection, and a strict 2 MiB parser ceiling.
Public references
07 / FAQ
Questions to answer before editing.
These answers are generated from the Tool record and current runtime state rather than generic compatibility promises.
Is PSP Save Viewer ready to use?
The Tool record is verified and declares an operational runtime. The page enables its input controls only when the declared engine module is loaded in the current build.
Does processing stay in the browser?
Yes for this declared mode. The loaded runtime processes the explicit input in the browser; Tool-specific privacy notes describe the exact scope and limits.
Should I keep the original file?
Yes. Keep an untouched source file until any generated output has been validated.
What if my input is rejected?
Use the validation message to correct the base, encoding, width, timezone, byte alignment, or size. The runtime does not guess through invalid input.
Related tools
Continue with the same tool family.
Only index-ready verified records from the same Tool Family are shown here.