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.

Checksum Fixers

Dark Souls III Checksum Fixer

Rebuild only per-entry MD5 fields in a verified Dark Souls III PC DS30000.sl2 BND4 save.

Dark Souls III 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.

Dark Souls III Checksum Fixer
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 checksum tool changes

Rebuild only per-entry MD5 fields in a verified Dark Souls III PC DS30000.sl2 BND4 save.

Verified input boundary

The file must parse as a bounded non-overlapping 12-entry BND4, match the Dark Souls III size discriminator, and successfully decrypt at least one character entry with the documented DS3 AES key to a bounded save-format version. Existing MD5 mismatches are allowed as repair targets.

What is deliberately not claimed

No Steam account transfer, stat/inventory editing, decryption export, payload recovery, Elden Ring support, console saves, or arbitrary 12-entry BND4 promotion is claimed.

Output

A separate .sl2 copy with each entry's first 16 bytes replaced by MD5(IV + encrypted payload). IVs, ciphertext, BND4 metadata, offsets and sizes are preserved.

How to use it safely

Close the game, back up DS30000.sl2, select it locally, inspect the invalid-MD5 count, run repair, and retain the original until the repaired copy is confirmed in-game.

Troubleshooting

Malformed/overlapping entry tables, wrong extensions, Elden Ring-sized entry structure, or failure of the DS3-key decryption fingerprint fails closed. A valid checksum cannot prove that damaged encrypted payload is semantically correct.

Verification evidence

Verified with clean and checksum-damaged deterministic AES/BND4 fixtures, native-crypto/reference decryption, independent hashlib checks, wrong-key and overlap negatives, exact-byte repair, immutability, and post-write reopen.

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

.sl2

Platforms

PC

Supported versions / editions

Dark Souls III PC DS30000.sl2 12-entry encrypted BND4 family.

Input constraints

The file must parse as a bounded non-overlapping 12-entry BND4, match the Dark Souls III size discriminator, and successfully decrypt at least one character entry with the documented DS3 AES key to a bounded save-format version. Existing MD5 mismatches are allowed as repair targets.

Known limitations

No Steam account transfer, stat/inventory editing, decryption export, payload recovery, Elden Ring support, console saves, or arbitrary 12-entry BND4 promotion is claimed.

Output / result

A separate .sl2 copy with each entry's first 16 bytes replaced by MD5(IV + encrypted payload). IVs, ciphertext, BND4 metadata, offsets and sizes are preserved.

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

Close the game, back up DS30000.sl2, select it locally, inspect the invalid-MD5 count, run repair, and retain the original until the repaired copy is confirmed in-game.

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 processed entirely in the browser after explicit selection. Phase 39 checksum profiles and codec scripts contain no fetch, XMLHttpRequest, WebSocket, or sendBeacon calls. The original bytes stay immutable; repair produces a separate copy only after game-specific structural identification, and that copy must reopen under the same verified profile.

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

Malformed/overlapping entry tables, wrong extensions, Elden Ring-sized entry structure, or failure of the DS3-key decryption fingerprint fails closed. A valid checksum cannot prove that damaged encrypted payload is semantically correct.

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
Profiledark-souls-3-pc-sl2-checksum-v1

Method notes

Verified with clean and checksum-damaged deterministic AES/BND4 fixtures, native-crypto/reference decryption, independent hashlib checks, wrong-key and overlap negatives, exact-byte repair, immutability, and post-write reopen.

Public references

  1. https://github.com/Hapfel1/er-save-manager/blob/main/src/er_save_manager/games/ds3_steamid.py
  2. https://github.com/darthdemono/sl2-analyzer/blob/main/app/parser.js

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 Dark Souls III Checksum Fixer 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.

Verified

Checksum Fixers

Sekiro Checksum Fixer

Rebuild only the ten documented slot MD5 fields and the settings MD5 in a structurally valid Sekiro PC S0000.sl2 save.

Platform
PC
Processing
Local browser processing
Verified
2026-08-08
Updated August 11, 2026 Open tool

Related guides

Read the guidance connected to this tool.

Only reviewed, index-ready Guides that explicitly reference this Tool are included.