D2R Online Save Editor: Edit .d2s Files in Your Browser (dschu012)

Not every edit needs a Windows program. The community editor built on dschu012’s d2s library runs entirely in a web browser: you open a .d2s file from your own computer, edit it, and download the result — the file is processed locally in the browser, never uploaded to a server. That design is why it became the community’s default online editor, and it doubles as the converter that moves saves between D2R and classic LoD formats. This guide explains what it does, where its code actually lives, and its honest limits.

Why a browser editor can be private

“Online editor” sounds like your save gets sent somewhere. This one is architected the other way: it is a client-side web application. The page’s code runs in your browser, reads the file you select from your disk into the browser’s memory, lets you edit it there, and writes the edited file back as a download. No account, no upload queue, no server-side copy. You can verify the claim the way you verify any open-source tool — the library code is public on GitHub — and the safety habits in how to check an editor is safe apply to web tools exactly as they do to downloads.

What it edits

Per the project’s own documentation, the editor built on the d2s library covers the standard offline editing surface:

• Character stats — level, experience, attributes, life/mana and gold.
• Skills — viewing and adjusting skill points.
• Quests and waypoints — progression state per difficulty.
• Items — inventory and item handling supported by the library’s item parser.
• Format conversion — converting saves between D2R and classic LoD formats (see below).

Exact screens change as the project changes, so treat the list above as the documented scope rather than a promise about a specific button layout — another reason the GitHub repository, not a screenshot on a fan site, is the reference. Your saves themselves live in the usual place: the save file location guide shows the folder.

Its second job: the D2R ↔ LoD converter

For many players the converter role matters more than the editing. Classic Hero Editor cannot open D2R saves — it predates the format. The documented workaround chain is: convert the D2R save down to classic format with dschu012’s tooling, edit the classic-format file in Hero Editor or another 1.14d tool, then let D2R import the result as described in importing LoD saves into D2R. The d2s library’s version handling is what makes that round trip possible, and it is also why developers build other tools on top of it.

Browser editor or D2CE?

• Choose the browser editor if it is available and you want a quick edit or a format conversion with nothing to install — and you value that the file never leaves your machine.
• Choose D2CE if you want a documented, downloadable program with a written UserGuide, built-in .bak backups and restore, bulk Upgrade tools and a mercenary dialog. The complete walkthrough is our D2CE user guide, and the file itself is on the download page with verified checksums.
• Either way, back up first and respect the version limits below. The side-by-side view is in best D2R save editors.

Honest limits

• 2.x-era formats. The library and editor were built for the save formats of the D2R 2.x era. There is no verified support for Patch 3.x or Warlock saves — the same limit that applies to every classic editor. The current status for all tools is tracked on the Patch 3.x & Warlock compatibility page.
• Offline only. Online characters have no local file, so no browser tool can open them either.
• Availability is not guaranteed. A community-hosted page can be down, moved or rebuilt without notice — as our check above shows. Bookmark the GitHub project, not just the hosted page.
• Backups are on you. A browser editor cannot keep a .bak in your save folder the way D2CE does; download the edited file under a new name or copy the folder first.