Stardew Valley Save Clinic — Read-Only Backup Comparison
Stardew Valley Save Clinic: Read-Only Backup Comparison
Safety boundary: this tool never rewrites or downloads a modified save. Recipe dictionaries require nested
key/string and value/int serializer nodes; inventory stacking requires the game’s full canStackWith and maximum-stack logic; normal quality tiers are 0, 1, 2, and 4. This read-only tool therefore does not edit recipes, merge stacks, set arbitrary quantities, or change quality.
Choose related save files
Select the main save plus any matching _old, _STARDEWVALLEYSAVETMP, or SaveGameInfo files. Files stay in your browser and are not uploaded.
No files selected.
XML and metadata summary
| File | Role | XML | Farmer / farm | Date | Money | Recipes | Inventory entries | Bytes / fingerprint |
|---|---|---|---|---|---|---|---|---|
| Load files to inspect them. | ||||||||
Main versus backup differences
Load at least two related parseable files to compare their metadata.
What this report can and cannot diagnose
- It can: identify XML parse failures; classify main, old, temporary, and info files; compare farmer name, farm name, save ID, date, money, recipe counts, inventory entry counts, file size, and a content fingerprint.
- It can: warn when supposedly related backups have different save IDs or identity fields.
- It cannot: round-trip the file through Stardew Valley’s serializer, prove every gameplay invariant, or certify a save as corruption-free.
- It does not: merge items, unlock or forget recipes, normalize quality, or mutate XML.
If a main file fails to parse and a matching _old file parses with the same save ID and expected identity, preserve copies of both before manually restoring anything. Let the game create no new save until your originals are backed up.