Repository navigation
saves
Launchstation keeps the classic memory-card/save toolbox while making destructive actions and timestamp manipulation more explicit.
Select one or more individual PS1 saves or folders containing files and no subdirectories, then choose Copy or Cut. Browse to the output folder, open Options and choose Create archive.... Both browsers offer formats appropriate to the save in the clipboard:
| Selected save | Archive choices |
|---|---|
| PS2 save folder | PSU - PS2 save backup (EMS/wLE) or PSV - PS3 export |
| Individual PS1 save | MCS - PS1 save backup, PSV - PS3 export or PSX - Action Replay / GameShark |
Choose the archive format once. Launchstation creates a separate archive for each copied or cut save, automatically names each archive from its save and creates it in the folder you are browsing, including an empty folder. There is no filename keyboard. PSU creation respects the settings for game ID/title names, modification-date suffixes and never overwriting existing files. With never overwrite enabled, an existing PSU is skipped and a Cut source is retained. Otherwise, a PSU is written directly over the existing file, following the R3Z overwrite setting. Other archive formats preserve existing files; rename the existing file or choose another output folder. PSU and PS2 PSV retain the save's original folder/file names, attributes and timestamps. PSV exports include a PS3 signature; PS2 PSV also includes the icon.sys and icon references needed by the PS3. The generated PSV filename uses the PS3 naming convention. For PS3 import, put it in PS3/EXPORT/PSV/ on USB storage. MCS stores one PS1 save with its original game filename and directory checksum. PSX stores one PS1 save in Action Replay format: a 54-byte header containing the original game filename, followed by the unchanged save data. PSX is a single-save archive; whole cards use Save card as instead. A PS1 backup folder containing the original save can also be archived.
Copy or Cut records the source path and file metadata immediately. Save contents are read only when Create archive or Extract is chosen. Those operations reuse the R3Z transfer checks to restore compatible source and destination drivers and HDD mounts as needed. An unavailable source or unmounted VMC must be reconnected or mounted again. Incompatible driver pairs, including MMCE with MX4SIO, are rejected before reading or writing save data. Create archive is offered after Copy or Cut of one or more PS1 saves or folders, when the current output folder is writable. Opening Options does not read the source or start its drivers. Choosing Create archive checks the copied folders for subdirectories and identifies their save types before offering formats. Selecting an item alone does not enable it. A flat folder does not need icon.sys for PSU creation; PS2 PSV still requires valid icon.sys and its referenced icons. Folders with subdirectories are refused before any archive is written; ordinary files are ineligible. A mixed selection of PS1 and PS2 saves offers PSV, the format shared by both save types. Each archive is processed separately. If a batch stops, completed Cut items leave the clipboard and failed or unprocessed sources remain. Skipped PSU archives retain their Cut sources. If two saves generate the same filename, the batch stops before overwriting an archive created earlier in that batch. Copy retains the source. Cut removes it only after the archive is created and the source still matches the data read for that archive operation; if the source changed, became unavailable or cannot be removed, the archive is kept and a message explains that the source remains. Canceling or a failed archive write retains the source and clipboard. Archive creation and extraction write the requested files directly, without depending on temporary-file renames. Failed new exports and incomplete new extraction folders are removed. A failed PSU overwrite can leave an incomplete file; Cut retains its source on failure. A PS1 card receives extracted PS1 saves rather than archive files.
Creating and extracting archives use the same progress popup as Paste. It shows the current save in the batch, the current file, transferred bytes, average speed and estimated time remaining for that file. The bar advances as source data is read or destination data is written. Preparation, opening an archive and Cut source verification are named stages; preparation counts completed saves until byte sizes are known. Copy/Cut and opening Options still use listing metadata only.
Archive creation streams PSU, MCS, PSX and PS1/PS2 PSV output through the same device-specific buffer policy as file transfers. Each transfer buffer is at most 1 MiB; fast transfers can use a second buffer, with fallback to one if it cannot be allocated. Save payloads and complete output archives are not held in RAM. Cut verifies the source data and metadata with an incremental fingerprint before deleting it. The dashboard continues drawing while serialized device requests are in progress.
Select one or more supported archives and choose Copy or Cut. Browse to the destination folder or compatible memory card, open Options and choose Extract PSU..., Extract PSV..., Extract MCS... or the corresponding clipboard extension. Archives of the same format share that extension label; a mixture of formats uses Extract saves.... Extraction writes directly into the current folder with no destination-picker popup. The save counter shows which save is being extracted. One progress bar, byte total and speed/time estimate cover all files in the current save, without restarting for each file. Completion is shown after file closes and save metadata restoration succeed. Selecting an archive alone does not enable extraction. A native save copied from a PS1 card is already extracted: use Paste to transfer it or Create archive to export it. Native PS1 saves and other files without a recognized save-format extension do not enable Extract. Mount a VMC first to extract into it. PS1 saves restore directly at a PS1 card's root using their original game filename; no directory is created there.
Copy retains the original archives. Cut removes each unchanged source only after its save has been successfully extracted; failed or unverifiable removals retain the source and report it. If a batch stops, completed Cut items are removed from the clipboard and unprocessed items remain. Ordinary Paste copies or moves the original archive files.
| Save type | Accepted formats | Destination |
|---|---|---|
| PS2 | PSU, CodeBreaker CBS, Action Replay MAX, X-Port/SharkPort XPS/SPS, PS3 PSV | PS2 memory card, mounted PS2 VMC, or storage folder |
| PS1 | MCS, Action Replay PSX, PS1 PSV, raw SC saves with PS1/MCB/PDA extensions | PS1 memory card or mounted PS1 VMC; PS2 cards and storage folders receive a backup folder containing the save |
Imports retain the game filename. Existing saves require overwrite confirmation; batch extraction offers Continue, Skip and Cancel. Memory-card and VMC space checks round each file to the card allocation unit, include directory storage and credit the space reclaimed from the existing save. Replacement reuses the parent directory entry. If an existing save cannot be measured reliably when its space is needed, extraction stops before removing it. Approved overwrites remove the old save before writing its replacement; a failed write does not restore the old save. Invalid paths, incomplete archives and duplicate filenames are rejected before writing. Compressed and uncompressed save data are limited to 16 MiB per input; allocation failures are reported. Save metadata and timestamps are restored on PS2 cards and VMCs; ordinary storage folders keep the decoded files.
Copy/paste and PSU workflows retain the specialized handling required by memory-card folders. Avoid treating a PS2 save as an arbitrary PC directory when preserving icon metadata, attributes and timestamps matters.
Both browsers show Mount as vmc0: and Mount as vmc1: for whole-card image filenames ending in VMC, MCD, MC2, BIN, MCR, MC, SRM, VM1, DDF, PS, PSM, SAV, PS2, VM2, RAW, GME, VGS, MEM or VMP, regardless of case. Other files do not show these actions. The extension selects which filenames offer mounting; mounting still validates the contents and geometry and distinguishes PS1 from PS2 when the same suffix is used. Supported raw and headered card images can be mounted directly.
| PS1 image layout | File size | Header before card data |
|---|---|---|
| Raw MC card (supported raw-image suffixes) | 131,072 bytes | None |
| VGS | 131,136 bytes | 64 bytes |
| PSP VMP | 131,200 bytes | 128 bytes |
| DexDrive GME | 134,976 bytes | 3,904 bytes |
Every supported PS1 layout contains one 128 KiB card payload beginning with MC. Wrapped files are larger than 128 KiB and can be mounted directly. Changes retain the wrapper, update the VMP signature or GME directory tables as needed, and preserve unrelated header data.
PS2 images support both 512-byte data pages without ECC and 528-byte pages containing 512 bytes of data plus 16 spare bytes. For example, an 8 MiB card is 8,388,608 bytes without ECC or 8,650,752 bytes with ECC. ECC is stored per page, rather than in a separate image header. Writes regenerate the twelve ECC bytes from each changed page and retain its remaining spare bytes. Image length and superblock geometry must agree.
A PS1 card has sixteen 8 KiB blocks. One contains the directory; fifteen are available for saves. Both browsers show X of 15 blocks free for physical PS1 cards and mounted PS1 VMCs. A multi-block save consumes every block in its chain.
Real PS1 memory cards work in either PS2 memory-card slot through mc0:/ and mc1:/. Their contents are a flat list of saves, each using one or more blocks. Import writes the original game save filename directly at the card root, without a directory. Folder creation, folder pasting, PS2 icon/date tools, text editing and launch-argument actions are disabled on PS1 cards and PS1 VMCs.
Select a PS1 image, or browse a physical PS1 card or mounted PS1 VMC, and choose Save card as.... Both browsers offer Raw image... for a custom filename and these emulator presets, followed by a destination folder picker:
| Emulator | Card 1 | Card 2 | Folder |
|---|---|---|---|
| Ember | MC1.vmc |
MC2.vmc |
games/<game>/ beside that game's disc files |
| POPStarter | SLOT0.VMC |
SLOT1.VMC |
The game's VMC folder, normally POPS/<game>/
|
The Raw image option lets you enter the output filename after choosing a folder; emulator presets use their required names. Each output is a raw 128 KiB card, suitable for mounting and save imports. Raw, DexDrive GME, VGS and PSP VMP images can all be exported this way for emulators that require raw cards. Exporting a mounted VMC preserves the complete image, including deleted slots. Exporting a physical PS1 card rebuilds an image containing its active saves. Existing output files are preserved; choose another folder or back them up and rename them first.
References: PS1 memory card format, Ember memory cards, POPStarter VMC naming and folders.
Launchstation can edit and organize directory timestamps. This is especially useful for OSDSYS/HOSDSYS ordering and icon-based exploit folders whose position is influenced by timestamps.
The organizer supports memory-card roots and hdd0:/__common/. Sorting modes include manual ordering, A–Z and SAS-style timestamps; game-save handling is kept distinct where appropriate. The native updater preserves an existing SAS date on its own app folder after updating the ELF and metadata, so its position does not need to be organized again.
Dangerous modifications/deletions of known exploit-style memory-card folders trigger warnings. That guard exists because a routine rename/delete can turn a bootable exploit card into an unbootable one.
LAUNCHSTATION repository · Live documentation · Release downloads
Maintained from documentation sources. Do not edit generated pages directly; propose changes in the source repository.