This browser-local viewer is for standard PlayStation 1 memory-card images. A PS1 card contains directory information and game save blocks; it is not interchangeable with an emulator save state. SaveEditor validates the raw card header before showing entries, reports directory checksum and chain status, and keeps the original selected file untouched. Wrapper handling is intentionally strict: truncated or malformed containers are rejected rather than padded or guessed. Use exported files only with software that explicitly supports the target format, and keep a backup of the original card image.
Emulator & Retro Tools
PS1 Memory Card Viewer
Inspect standard PlayStation 1 memory-card images locally, including directory entries, block chains, file sizes, titles, checksums, and free-block counts.
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
.mcd.mcr.mc.srm.psm.ps.ddf.bin.gme.vgs.mem.psx
Platforms
DuckStation / PS1
Supported versions / editions
Standard PS1 raw memory-card images plus complete DexDrive GME, VGS/MEM, and PSX wrapper images whose embedded 128 KiB card validates as a standard PS1 memory card.
Input constraints
The embedded raw card must be exactly 128 KiB and contain the standard MC header. Complete GME, VGS/MEM, and PSX wrapper images are normalized only when their full expected wrapper and card payload are present.
Known limitations
This viewer interprets standard PS1 memory-card directory structures. It does not emulate a console, decrypt unrelated formats, repair filesystem corruption, or infer game meaning from arbitrary save payload bytes.
Output / result
Read-only card summary and save-directory table. Individual valid save chains can be exported as MCS files without changing the selected card.
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 a memory-card image. Review the detected wrapper, card-header checksum, directory checksums, used/free blocks, filenames, titles, and block chains. Export an MCS copy only from an entry whose chain is reported valid.
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 the card is rejected, confirm that it is a complete PS1 memory-card image rather than an emulator save state or a single game save. Damaged directory checksums and invalid block chains are reported instead of silently repaired.
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
Profileps1-memory-card-viewer
Method notes
Verified against the standard 128 KiB PS1 card geometry, MC header/checksum rules, directory allocation states and linked blocks, plus DuckStation-compatible raw/GME/VGS/PSX wrapper normalization and MCS export semantics.
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 PS1 Memory Card 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.
Related guides
Read the guidance connected to this tool.
Only reviewed, index-ready Guides that explicitly reference this Tool are included.
Beginner
Save File Formats
PlayStation 1 Memory Card Image Integrity & Troubleshooting Guide
A fail-closed PlayStation 1 Memory Card Image troubleshooting guide for distinguishing representation problems from unsupported semantics and for selecting read-only integrity checks before any repair attempt.
Beginner
Backups & Safety
PlayStation 1 Memory Card Image Backup & Identification Guide
A safety-first PlayStation 1 Memory Card Image guide for identifying the intended representation, preserving an untouched source copy, and choosing only a verified compatible Tool.
Beginner
Backups & Safety
PlayStation MCS Save Backup & Identification Guide
A safety-first PlayStation MCS Save guide for identifying the intended representation, preserving an untouched source copy, and choosing only a verified compatible Tool.