The short answer: no. Not with D2CE, not with any other save editor, and not with a tool you have not heard of yet. Online Diablo II: Resurrected characters are not files on your computer — they are records stored on Blizzard’s servers. Save editors work by opening a local file, and for an online character there is no local file to open. Everything else in this article follows from that one fact.

Where online characters actually live

When you create a Battle.net character, the character’s data — level, stats, skills, items, progress — is kept server-side, under your account. Your PC downloads what it needs to display and play the character during a session, but it never holds an editable save file for it. Compare the offline mode: an offline character is a .d2s file in C:\Users\<your name>\Saved Games\Diablo II Resurrected, fully under your control — see the save file location guide for what those files look like. That difference in where the data lives is the whole reason offline editing exists and online editing does not.

No transfer in either direction

It is also not possible to route around the limit by moving characters between modes. Offline characters cannot be transferred to Battle.net, and online characters cannot be brought offline into an editable file. The two populations are kept separate by design — which is precisely what keeps edited characters out of the online economy and ladders. Any guide or video claiming a working offline-to-online transfer for D2R is describing something that does not exist, and any tool sold on that promise should be treated as a scam; our editor safety checklist explains the pattern.

Cross-progression does not change this

Cross-progression can confuse the picture, so to be precise: it syncs your online characters between platforms — play the same Battle.net character on PC and console under one account. What it never does is produce an editable file. The character remains a server-side record on every platform, and console saves are equally out of reach of a PC editor. Cross-progression moves access, not data you can open. The FAQ answers the related console-save questions as well.

Blizzard’s rules, stated plainly

Blizzard’s EULA (section C) prohibits cheats and unauthorised third-party software that alters gameplay, and Blizzard has never officially endorsed save editors — for offline play or anything else. We will not tell you any editor is “100% safe” or carries “zero ban risk”, because nobody outside Blizzard can promise that. What can be said factually: save editors like D2CE read and write local offline files and never interact with Battle.net characters at all, because they cannot. Keep your editing to your own offline saves, back them up first, and treat the activity as your own choice under rules Blizzard has written the way it has.

What you can legitimately do instead

• Test builds offline. This is the real use case most “online editing” searches are chasing: duplicate the idea, not the character. Build the character offline, edit and experiment freely there, and use what you learn to plan the online character you level legitimately. The D2CE user guide covers offline editing within the editor’s supported game versions.
• Respec in game. D2R itself offers respecs: Akara offers one after the Den of Evil quest (once per difficulty), a Token of Absolution can be crafted from essences dropped by act bosses for further respecs, and on PC the -enablerespec launch argument enables an in-game respec option for offline play. None of these touches a save file.
• Plan before you spend points. A build planner lets you test skill and stat layouts without committing either an online character or a save edit.

And if a site disagrees with this article and offers you an “online D2R editor” download, remember the shape of the trick: the one thing every such tool needs — your online character’s file — does not exist on your machine for it to edit. What those downloads usually contain instead is covered on our download page, which links only the genuine D2CE release.

The short answer: the classic Hero Editor was never a Diablo II: Resurrected editor. Hero Editor v1.04 (by ZonFire99) was built for classic Lord of Destruction 1.14d saves, and it cannot natively open a D2R .d2s file from any patch — the file formats are different. It also cannot create a character from scratch. There is, however, a documented indirect workflow: edit a classic-format save in Hero Editor, let D2R import it, and use a converter when you need to go back the other way.

Why Hero Editor rejects D2R files

Diablo II save files carry a format version, and the format kept moving after the classic game ended. Classic saves from the later LoD era, D2R launch saves and current D2R saves are all different versions with different internal structures. Hero Editor understands the classic 1.14d format it was written for; a D2R file contains structures it has never seen, so the open fails. This is not a bug, a missing setting or a corrupted download — the tool and the file are simply from different generations of the game. No option inside Hero Editor changes that, which is why the compatibility status page lists it as unable to read D2R saves at all, rather than partially compatible.

What Hero Editor still does well

Within its own format, Hero Editor remains a capable classic editor: it edits existing classic characters, including their items, and generations of classic players know its interface. The two hard limits to plan around are the ones above: it cannot read D2R-format files, and it cannot create a brand-new character from nothing — you always start from an existing classic save, even if it is a freshly made level 1 character created in the classic game.

The workaround, step by step

1. Start with a classic-format save (Lord of Destruction 1.14d) — create the character in classic Diablo II if you need a fresh one.
2. Open that save in Hero Editor and make your edits there, where the format matches the tool.
3. Copy the edited classic save into the D2R save folder, C:\Users\<your name>\Saved Games\Diablo II Resurrected — see the save file location guide for the folder details.
4. Launch D2R and let the game import the character. From this point the game works with it as a D2R character.

This is a one-way door, and the next section is about exactly that.

Going back: the converter step

Once D2R has loaded and re-saved your character, the file on disk is a D2R-format save, and Hero Editor cannot open it any more than it could before. To edit that same character in Hero Editor again, the save first has to be converted back to the classic format — that conversion is a documented feature of the dschu012 tooling, whose online editor doubles as a D2R-to-classic converter. Our online save editor guide covers that tool and the conversion direction. Convert, edit in Hero Editor, re-import into D2R — and expect to repeat the conversion every round trip.

A note on item packs

If what you actually want from Hero Editor is its item ecosystem, there is a community resource worth knowing: JeffVanGorp’s Hero-Editor-Assets project collects item packs for use with Hero Editor. Item packs work within the same classic-format workflow above — they do not change the format limits, and items still reach D2R by the import route, not by opening a D2R save directly.

Keep the classic original

The single most important habit in this workflow: once D2R re-saves a character, the file is D2R-format permanently — there is no “save as classic” button in the game. Keep your original classic-format save backed up and untouched, separate from the copy you placed in the D2R folder. That original is your way back into Hero Editor without a conversion step, and your recovery point if an import goes wrong. How to back up D2R saves covers the folder-copy routine, and for most players who simply want to edit a D2R-native character, the D2CE user guide is the more direct route within D2CE’s own supported versions.

The short answer: a character that vanishes from the select screen after editing, or that the game refuses to load, is usually not deleted — the game is skipping a file it cannot parse. Stop editing, do not save anything over the original, and work the recovery steps below in order: close the game properly, restore D2CE’s .bak backup, then fall back to your own backup copy. In most cases the character comes back exactly as it was before the edit.

Step 0: stop, and touch nothing else

Every additional save, edit or “fix” attempt writes files and can overwrite the very backup you are about to need. Close the editor, close the game, and make a copy of the whole Saved Games\Diablo II Resurrected folder as it stands right now before you change anything. Whatever state the character is in, this freezes it. The full reasoning behind this habit is in how to back up D2R saves.

Step 1: rule out the running game

Diablo II: Resurrected builds its character list while it runs, and it holds that list while you play. If you edited a save while the game was open — alt-tabbed out, editor in another window — the game can keep showing its cached list, overwrite your edit when it next saves, or behave as if the character is not there. Editing is only safe with the game fully closed. So: exit the game completely, confirm it is no longer running, then start it again and check the character select screen with fresh eyes before you assume the file itself is broken.

Step 2: restore the .bak through D2CE

1. Open D2CE (with the game closed) and select the affected character.
2. Use Options → Restore Character. D2CE can keep a per-character .bak backup (Options → Backup Character Before Save), and Restore Character rolls the save back to that backup.
3. Close the editor, launch the game, and check whether the character is back in the list and loads.

This is the cleanest recovery because it uses the editor’s own snapshot of the file from before your edit. If you had the backup option off, or the .bak is itself from after the bad edit, move to the next step. Our restoring a corrupted D2R save guide goes deeper on each branch.

Step 3: replace the file with your own backup

If you copied the save folder before editing — manually, or with a cloud backup service keeping versions — close the game, and copy the character’s .d2s file from that backup back into Saved Games\Diablo II Resurrected, replacing the edited file. You lose the edits, but the character returns in its pre-edit state, which is the right trade: a working character with yesterday’s gear beats a broken file with edited stats. Then, if you still want the edit, redo it in smaller steps, launching the game after each change to confirm the character still loads.

Why this happens: values the game rejects

The usual cause of a character that will not load after editing is not the act of editing itself but a value the game cannot accept: a stat, skill level, item property or quantity outside the range the game expects. Editors will happily write numbers the game then refuses to read. When you redo an edit, change one thing at a time, keep values within the ranges the game itself allows, and test-load the character between changes — the step where it stops loading tells you which value was the problem. The D2CE user guide notes the safe ranges approach for common edits.

What the character select screen is telling you

The select screen is a parser report, not a filing cabinet: it lists the files the game can read, and quietly skips the ones it cannot. A current-version game reads its own current saves fine — disappearance is about the file, not the patch. A save that was edited wrongly, truncated, or written in a shape the game does not recognise simply does not appear, which is why the character looks “deleted” while the .d2s file is still sitting in the folder. That is also the hopeful part: because the file is usually still there, the restore steps above usually work. If your save is a current Patch 3.x save, remember the separate limit on the editor side — see the compatibility status before blaming the edit.

The short answer: D2CE does not search your PC for characters. It opens the folder you point it at and lists the save files inside that folder — nothing else. Most “my character is missing” problems come down to one of five things: the editor is looking at the wrong folder, the save folder has been moved, the file is not a .d2s file, the character has no local file at all, or the save is in the newer format the editor cannot read.

Point the editor at the real save folder

On Windows, Diablo II: Resurrected keeps offline saves in C:\Users\<your name>\Saved Games\Diablo II Resurrected. That is the folder D2CE needs to open — not the game’s install folder, which contains program files and no characters. If you pointed the editor at the install directory, a shortcut, or a folder you copied “Diablo II” files into by hand, it will legitimately show nothing. The full breakdown of what lives in the save folder, file by file, is in our D2R save file location guide. Once the editor is aimed at the right folder, each offline character should appear by name.

If the folder looks empty

• Check the extension. A character file is a .d2s file named after the character. The .d2i file in the same folder is the shared stash, not a character, and .bak files are D2CE backups — neither will open as a character.
• Check you are in your Saved Games. PCs with several Windows user accounts have several Saved Games folders. The game writes to the account you play on.
• Look for folder redirection. OneDrive backup and Windows folder redirection can move Saved Games out from under the usual path, so the folder you remember may no longer be the folder the game writes to. If your characters exist in the game but not in the folder, check whether Saved Games is being redirected — for example under your OneDrive folder — and point D2CE at the location the game actually uses. Treat this as something to check on your machine, not a certainty: it only applies where redirection is turned on.

Characters with no file to find

If the character was created on Battle.net, there is nothing to point the editor at: online characters are stored on Blizzard’s servers and no .d2s file exists on your PC for them. That is by design, not a bug in the editor, and no setting changes it — the FAQ covers the online/offline divide in full. Only offline characters ever appear in the save folder.

The file is there, but the editor cannot read it

A .d2s file that shows up but fails to open is a different problem from a missing file. The current version of the game writes saves in a newer format (versions 100–105) that D2CE, whose final release was author-tested up to D2R PTR 2.6, cannot parse. A save written by the current game will not become readable by moving or renaming it. See the Patch 3.x and Warlock compatibility status for exactly which saves are affected, and the online editor guide for the other tool whose format support you can check.

Mod saves live somewhere else

If you play with a mod, do not look for your characters in the standard folder and conclude they are gone. D2CE documents support for mod saves such as BTDiablo and Rebirth, and mods keep their characters in the mod’s own save location rather than the vanilla Saved Games folder. Point the editor at the mod’s save folder instead. The same applies in reverse: a mod save opened from the wrong folder context may not behave like a vanilla save, so keep mod and vanilla folders separate and back each up separately, as described in how to back up D2R saves.

A quick checklist

1. Open C:\Users\<your name>\Saved Games\Diablo II Resurrected in Explorer and confirm the .d2s file is really there.
2. Point D2CE at that exact folder — not the install folder, not a shortcut.
3. Confirm the character is an offline character, not a Battle.net character.
4. Check for OneDrive or Windows redirection if the folder is empty but the game sees the character.
5. If the file is present and current-version, accept the format verdict and check the compatibility status page rather than renaming or converting files at random.

The short answer: D2CE is a single portable program — D2Editor.exe — with nothing to install and no setup wizard. When it will not open at all, or opens and then throws an unhandled exception, the cause is almost always outside the editor itself: security software has taken the file, the editor has been handed a save it cannot parse, the save is damaged, or the program is sitting somewhere it cannot write to. Work through the causes below in order before you download anything else.

First, check the file itself

Start by confirming you still have the genuine, complete file. The real D2Editor.exe from the D2CE project’s GitHub releases is 21,064,192 bytes, with MD5 99131b19e4f337c333a81d6f46afbe44 and SHA-256 eef13d429d764296c844d7a146516d5a2fe500bec4fb273aa96b8a8f2dd4195c. If your copy is a different size, or its checksum does not match, it is incomplete or it is not the project’s file at all — delete it and get a fresh copy through our download page, which links the official GitHub release. Our guide to checking an editor is safe walks through checksum verification step by step.

Cause 1: antivirus quarantined the executable

Save editors are a classic false-positive target: a small, unsigned program whose whole job is reading and rewriting game files looks suspicious to heuristic scanners. If D2CE opened yesterday and the shortcut is dead today, or the .exe has vanished from its folder, check your antivirus quarantine or Windows Security protection history first. If the file is there, restore it only after you have verified the checksum above — never whitelist a copy you cannot verify, because repacked “editor” downloads from random mirrors are a real malware lure. If the checksum matches the GitHub release values, the file is the genuine article and restoring it is reasonable.

Cause 2: a save the editor cannot parse

An unhandled exception as soon as you open a character usually means the editor met a save format it does not understand, which is not the same as a broken install. D2CE’s final release (2.22, April 2023) was author-tested up to D2R PTR 2.6; the current game writes a newer format the editor was never updated for. Test this by pointing D2CE at a folder containing an older save, or at an empty folder: if the program itself opens calmly and only fails on one character, the program is fine and that save is the problem. The Patch 3.x and Warlock compatibility status explains which saves fall into this category.

Cause 3: a damaged save file

A save that was interrupted mid-write, copied while the game was running, or already edited badly can fail to parse even if it comes from a supported game version. Try opening a different character from the same folder. If only one character fails, that file is the damaged one — work from its backup instead of retrying the same file. Our guide to restoring a corrupted D2R save covers the recovery order, including D2CE’s own per-character backups.

Cause 4: running from a read-only location

D2CE writes backups and settings next to its own files and works on the save folder you point it at. If the program is still inside the downloaded zip, sitting in a folder you cannot write to, or pointed at a save folder that is locked down, expect it to fail in ways that look like crashes. Extract the .exe to an ordinary folder you own — a folder on your desktop or in Documents is fine — and keep your saves in their normal location. Note what this fix is not: D2CE works on files in your own user folders and does not need to be run as administrator.

The “.NET Desktop Runtime” myth

Many download sites tell you to fix D2CE crashes by installing a .NET Desktop Runtime, reinstalling Visual C++ redistributables, or similar. That advice is copied from generic crash-fix templates and does not apply here: D2CE is a native portable executable, and its UserGuide documents no runtime requirements — there is nothing to install before it, and no installer for it. Installing runtimes will not hurt your PC, but it will not fix D2CE either, and time spent on it is time not spent on the four real causes above. The same applies to “compatibility mode” rituals: the editor runs as an ordinary Windows program.

If it still will not open

Re-download a verified copy, extract it to a fresh folder, and open it with no save folder selected. If the clean copy opens, reintroduce your saves one folder at a time until the failing file identifies itself. If even a verified copy in a fresh folder will not start, the problem is on the machine side — most often security software blocking it silently, which the quarantine check above will show. The D2CE user guide covers normal startup and first-open steps once the program itself is running again.

The short answer: as of October 2026, no established Diablo II: Resurrected save editor has verified support for saves written by Patch 3.x or for Warlock characters from the Reign of the Warlock DLC (February 2026). D2CE, the dschu012 online editor, Hero Editor and GoMule all predate the current save format. Any site claiming its editor is “fully compatible with the 2026 Warlock expansion” is claiming something the tools themselves do not. This page tracks the real status, editor by editor.

Why current saves are different

Diablo II save files carry a format version in their header. Classic Lord of Destruction saves from patch 1.10 onward are version 96; D2R launch saves are version 97, and the format moved through the high 90s during the 2.x era. The Reign of the Warlock update pushed save files to versions 100-105, adding structures the older editors have never seen: additional stash tab types, the Chronicle, a “DemonSection” (v103) and a new 833-byte header (v104). Blizzard has never published an official patch-to-format mapping, so treat any precise conversion table you find on other sites as guesswork.

The game itself is now on Patch 3.3 (August 2026, Ladder Season 15). If your game is up to date, every save it writes is a current-format save.

Editor-by-editor status

What still works today

• Editing older saves with D2CE: characters created and kept on the save formats of its era (D2R up to the PTR 2.6 period, and classic 1.14d) remain fully editable — stats, skills, quests, waypoints, items and the shared stash. The D2CE user guide covers the workflow.
• Classic Diablo II: 1.14d saves work with D2CE and with the original Hero Editor.
• Planning builds: build planners (such as Maxroll’s D2 planner) are not save editors, but they are the safe way to test a Warlock build today without touching a save file.

If all your saves are Patch 3.x

1. Back them up now anyway. When a maintained editor adds v100-105 support, it will work on the saves you have — if you still have them. See how to back up D2R saves.
2. Do not download “D2CE 2.23”, “D2CE 2026 Edition” or similar. No such official release exists; the project’s last release is 2.22 (April 2023) on GitHub. Files using those names on random mirrors are a classic malware lure — see how to check an editor is safe.
3. Check the actively maintained options in the table above, starting with D2RuneWizard, and read their changelogs for explicit Patch 3.x / format v105 statements before trusting a save to them.
4. Ignore “Warlock read-only mode” claims. A 2023 binary has no partial or read-only Warlock mode; that phrase was invented by download sites, including, until our October 2026 cleanup, this one.