Skip to content
Game save workbench
Local-first tools No installation Support status shown
SAVEEDITOR.COM
Browse tools
DEVICE-LOCAL Favorites and recent pages stay in this browser.

Save Editors

Stardew Valley Save Editor

Edit a narrow set of verified Stardew Valley 1.6.x PC main-save XML fields locally: money, current health, and current stamina, while keeping identity and maximum-stat fields read-only.

Stardew Valley PC

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.

Stardew Valley Save Editor
BROWSER LOCAL

Checking whether the declared runtime module is loaded. No input has been processed.

Session change summary

No output has been built in this session.

What this game-specific editor changes

Edit a narrow set of verified Stardew Valley 1.6.x PC main-save XML fields locally: money, current health, and current stamina, while keeping identity and maximum-stat fields read-only.

Verified save contract

Select the larger main save file inside the Stardew Valley save folder, not SaveGameInfo. The document must be valid UTF-8 XML with a SaveGame root, a direct player record containing the required scalar fields, and a gameVersion tag in the 1.6.x family. File size is limited to 16 MiB.

Supported save family

Stardew Valley PC/main-save XML tagged 1.6.x.

Deliberate limitations

This first profile does not claim support for older 1.5 saves, console-specific extraction workflows, arbitrary mod-added structures, inventory reconstruction, friendship dictionaries, skills, quest state, or SaveGameInfo synchronization.

Safe workflow

Back up the entire save folder, select the larger main save file rather than SaveGameInfo, confirm the farmer name and game version shown by the Tool, change only the exposed fields, and download the edited copy. Replace a game file only while the game is closed and retain the original backup.

Why SaveEditor fails closed

The Tool must match its exact bundled game profile before the workbench will launch. The original selected bytes are preserved, edits occur on an in-memory copy, and the generated output must pass the same profile/version validation after writing.

Verification basis

Verified with two deterministic 1.6.x main-save fixtures, strict root/version/player matching, UTF-8 and unsafe-XML rejection, read-only field protection, numeric bounds, original-byte preservation, and post-write reopen validation. The public Stardew Valley Wiki documents XML save storage, the paired main/SaveGameInfo files, version tagging, backup guidance, and manual XML editing.

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

No extension (the main save file is normally named after its save folder).

Platforms

PC

Supported versions / editions

Stardew Valley PC/main-save XML tagged 1.6.x.

Input constraints

Select the larger main save file inside the Stardew Valley save folder, not SaveGameInfo. The document must be valid UTF-8 XML with a SaveGame root, a direct player record containing the required scalar fields, and a gameVersion tag in the 1.6.x family. File size is limited to 16 MiB.

Known limitations

This first profile does not claim support for older 1.5 saves, console-specific extraction workflows, arbitrary mod-added structures, inventory reconstruction, friendship dictionaries, skills, quest state, or SaveGameInfo synchronization.

Output / result

A separate edited copy of the selected main save. Only money, current health, and current stamina are rewritten; game version, farmer name, maximum health, maximum stamina, and the rest of the XML remain untouched by the profile.

03 / Instructions

Use a reversible workflow.

File-oriented workflows start with an untouched original. Tool-specific instructions add only details documented for this utility.

  1. 01Keep the original

    Preserve an untouched copy before creating or transforming binary output.

  2. 02Confirm scope

    Match the file size, format, platform, and version to the support information on this page.

  3. 03Process locally

    Use the runtime only when the page reports that its declared engine is loaded.

  4. 04Validate output

    Compare or test the result before replacing any working source file.

Tool-specific steps

Back up the entire save folder, select the larger main save file rather than SaveGameInfo, confirm the farmer name and game version shown by the Tool, change only the exposed fields, and download the edited copy. Replace a game file only while the game is closed and retain the original backup.

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

The selected save is read only after explicit file selection and processed entirely in the browser. Phase 26 profile scripts contain no fetch, XMLHttpRequest, WebSocket, or sendBeacon calls. The original bytes remain untouched; successful edits generate a separate downloadable copy after profile/version validation and post-write revalidation.

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.

Wrong file or size

Re-check the documented input type and browser size limit before retrying.

Unsupported format

A generic converter does not imply support for every game-specific container, signing scheme, or serialization format.

Source was modified

Return to the untouched source instead of repeatedly processing a damaged or partially transformed file.

Known Tool issues

If the file is rejected, confirm it is the main SaveGame file from a 1.6.x save and not SaveGameInfo. A modded save can still be rejected if required vanilla scalar fields are missing or no longer match the verified structure. Restore the original folder if the game does not accept the edited copy.

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
Profilestardew-valley-pc-xml-v1

Method notes

Verified with two deterministic 1.6.x main-save fixtures, strict root/version/player matching, UTF-8 and unsafe-XML rejection, read-only field protection, numeric bounds, original-byte preservation, and post-write reopen validation. The public Stardew Valley Wiki documents XML save storage, the paired main/SaveGameInfo files, version tagging, backup guidance, and manual XML editing.

Public references

  1. https://www.stardewvalleywiki.com/Saves
  2. https://www.stardewvalleywiki.com/Version_History
  3. https://github.com/beeradmoore/StardewValleySaveEditor

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 Stardew Valley Save Editor 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 version is not listed?
Treat unlisted versions as unverified. Do not assume two releases use identical save layouts, checksums, signing, or serialization.

Related tools

Continue with the same tool family.

Only index-ready verified records from the same Tool Family are shown here.