Memory Cards & Save Backups

The author documents a memory card in slot 1, saved in browser storage for the address you play from. Games format and use that card through their own save menus. This is a summary of the documented feature; our community has not independently verified save creation, imports, or recovery.

Save in the game, then export the card

1. Use the game’s own save menu and allow it to finish.
2. Choose Export card on the project page.
3. Keep the downloaded .ps2 file somewhere outside the browser’s storage.
4. Name your backup so you can identify the game region, date, and project revision later.

The exported file is a memory-card image. The README describes the layout as the one PCSX2 uses. It does not describe a save-state system, automatic cloud sync, or a backup service.

Move a card between setups

The documented Import card action puts a .ps2 image into the slot. The README describes moving cards between browsers and importing cards from PCSX2. Its native runner uses the same card layout.

Before an import, export the destination card as a separate backup. Keep the original source file as well. Then import the intended card and check the game’s own load menu. Matching a file format does not establish that a particular game’s region or revision will accept every save; include both versions in a report if a save is missing or rejected.

Understand the storage boundary

The author says browser saves belong to the address you play from. A card is therefore not a promised account-level save that follows you to another browser or server address. Export it before changing your local hosting setup or clearing browser data.

The reviewed source does not specify a browser-storage quota, retention guarantee, or private-browsing behavior. Treat a downloaded backup as the portable copy and label those unknowns clearly in reports.

Start with an empty slot

Appending ?nocard to the local game page starts it without a card in the slot. That is different from starting with a new, unformatted card. Use it only when the empty-slot behavior is the condition you want to investigate, and record the parameter in your test notes.

The default automated discovery runs described in the README use an empty card in slot 1 so they can follow a typical startup path. That does not verify every later save and load sequence.

Report a save issue precisely

Include the game region and revision, project commit, browser and operating system, whether the card was newly created or imported, and the exact save or load step. State whether the problem survives a reload. Do not upload a memory-card image publicly without first considering what it contains; a screenshot and precise steps may be sufficient to explain the symptom.

The browser check helps identify missing browser features. It does not read or modify your saves. For startup problems, see troubleshooting; for a fresh local build, follow Getting Started.