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

Dark Souls III Souls Editor

Raise the two documented name-relative soul fields for the lowest-numbered occupied character slot in a verified Dark Souls III PC SL2 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 Souls 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

Raise the two documented name-relative soul fields for the lowest-numbered occupied character slot in a verified Dark Souls III PC SL2 save.

Verified input boundary

The file must be a bounded 12-entry BND4, every entry MD5 must already validate, AES-128-CBC decryption must succeed, entry 10 must identify an occupied ASCII-name slot, and that encoded character name must occur exactly once in the corresponding character payload.

What is deliberately not claimed

No slot selection, soul reduction, stats/inventory, name edits, checksum repair from an invalid base, console saves, ambiguous name matches, or arbitrary SL2 editing is claimed.

Output

A separate .sl2 copy in which only the selected encrypted character entry changes: two name-relative fields are raised monotonically, the original IV and encrypted length are preserved, and MD5 is rebuilt.

Instructions

Close the game, back up DS30000.sl2, select it locally, verify the read-only character name/slot, enter a souls floor from 1 to 999,999,999, and retain the original.

Verification

Verified against the upstream name-relative algorithm with two deterministic AES fixtures, native-crypto differential checks, unique-name matching, exact entry-only writes, monotonic no-lower tests, immutable-original and reopen checks.

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 BND4/AES-128-CBC/MD5 family, restricted to the first occupied slot and unique ASCII-name subset.

Input constraints

The file must be a bounded 12-entry BND4, every entry MD5 must already validate, AES-128-CBC decryption must succeed, entry 10 must identify an occupied ASCII-name slot, and that encoded character name must occur exactly once in the corresponding character payload.

Known limitations

No slot selection, soul reduction, stats/inventory, name edits, checksum repair from an invalid base, console saves, ambiguous name matches, or arbitrary SL2 editing is claimed.

Output / result

A separate .sl2 copy in which only the selected encrypted character entry changes: two name-relative fields are raised monotonically, the original IV and encrypted length are preserved, and MD5 is rebuilt.

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, verify the read-only character name/slot, enter a souls floor from 1 to 999,999,999, and retain the original.

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 45 profile/codec scripts contain no fetch, XMLHttpRequest, WebSocket, or sendBeacon calls. The original bytes remain immutable; a separate output is produced only after an exact profile match and successful post-write reopen.

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

Bad MD5, wrong entry count, no occupied slot, unsupported/ambiguous character name, malformed encryption framing, or out-of-range target fails closed.

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

Method notes

Verified against the upstream name-relative algorithm with two deterministic AES fixtures, native-crypto differential checks, unique-name matching, exact entry-only writes, monotonic no-lower tests, immutable-original and reopen checks.

Public references

  1. https://github.com/jtesta/souls_givifier/blob/master/souls_givifier.pynhttps://github.com/jtesta/souls_givifier/blob/master/sl2_editor.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 Souls 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.