Skip to content
Game save workbench
Local-first tools No installation Support status shown

Platform directory / Save ecosystems

Find save tools by platform.

Browse PC, console, emulator, retro, and engine-specific hubs. Each Platform page separates useful save documentation from real Tool availability so a category link never implies unsupported functionality.

01 / How to read the directory

Platform coverage is evidence-based.

A Platform Hub can organize save paths, file formats, emulator workflows, limitations, Game Hubs, and active Tools. Verified Tool status is derived separately from the taxonomy itself.

Documentation first

Save paths and formats can be useful even before a custom editor exists.

Tool state is separate

Verified and in-development tools are counted explicitly; planned work is excluded.

Limits stay visible

Protected console saves and server-side workflows are not presented as browser-local when they are not.

02 / Browse platforms

Choose the save ecosystem.

Empty platform terms remain discoverable for navigation but are automatically kept out of the search index until real published Game Hubs or active Tools are assigned.

Desktop & local workflows

PC save paths, launcher differences, browser-local tools, and file-format references.

PlayStation

Generation-specific save references with protection and signing limits stated clearly.

Nintendo

Handheld, home-console, memory-card, and emulator-oriented save workflows.

Sega & retro

Older save-memory formats, emulator files, inspection, and conversion references.

Emulator ecosystems

Named emulator hubs appear only when a specific save/container workflow is already verified.

Engine ecosystems

Save formats organized around game engines where one reusable parser can support many titles.

Additional platforms

Administrator-added platform hubs appear here without being hidden by the curated default set.

03 / Platform differences

A save file is not the same problem on every system.

PC saves are often ordinary files in user folders, while emulator saves can use emulator-specific containers or byte order. Console saves may live on memory cards, virtual memory cards, account-bound containers, or signed formats. The platform layer exists so those differences are explained before a user reaches an editor or converter.

01

Locate the save

Start with the correct device, launcher, memory-card, or emulator location.

02

Identify the format

Check whether the file is raw, containerized, compressed, signed, or emulator-specific.

03

Use compatible tools

Only use a Tool whose platform and support state match the save workflow.