How to Back Up Dark Souls II Saves and Avoid Online Bans When Testing Mods

Back up the save while Dark Souls II is closed, test mods only offline, and remove every mod component before reconnecting. On Windows, Scholar of the First Sin stores its active save at %APPDATA%DarkSoulsII<your account id>DS2SOFS0000.sl2. Keep an untouched copy of that file on separate storage, create dated copies for experiments, and verify that at least one copy can be restored. A clean save by itself is not proven to make modified game files safe for online play, and no official source promises a ban-proof mod workflow.

What you need to protect

Dark Souls II stores character progress in a single save container rather than in a normal Steam game-file folder. For Scholar of the First Sin on Windows, the published location is:

#	Preview	Product	Price
1		Dark Souls II: Scholar of the First Sin - PlayStation 4	$21.39	Buy on Amazon
2		Dark Souls II Game Guide: Complete Walkthrough, Secrets, and Strategies to Master Every Boss, Build,...	$17.99	Buy on Amazon
3		Dark Souls II: Design Works	$28.34	Buy on Amazon

As an Amazon Associate I earn from qualifying purchases.

%APPDATA%DarkSoulsII<your account id>DS2SOFS0000.sl2

%APPDATA% normally resolves to your Windows user profile’s roaming application-data directory. The folder represented by <your account id> is specific to the Windows account or profile in use. Do not assume that a Steam installation backup contains this file: Steam Support says third-party save files may need to be copied separately from a Steam installation backup.

The file belongs to the Scholar/Windows DX11 save family. Original Dark Souls II, Scholar of the First Sin, DLC state, and platform/server family are not interchangeable in every direction. Confirm the edition before you copy or restore anything.

#1 Best Overall

Dark Souls II: Scholar of the First Sin - PlayStation 4

• All 3 DLC Pack Contents: Crown of the Sunken King, Crown of the Old Iron King, Crown of the Ivory King
• Additional NPCs Added For Enhanced Story Experience To Assist Guiding Players Through Level
• Parameter Setting Adjustments for Improved Balance
• Augmented Item Descriptions
• Increase in Maximum Online Players

$21.39

Buy on Amazon

Before copying: close every game process

A save copied while the game is still running may be incomplete or immediately overwritten. Exit to the desktop, then make sure Steam has also finished the game’s process before touching the file.

1. Save normally and quit Dark Souls II to Windows.
2. Open Task Manager with Ctrl + Shift + Esc.
3. In the process list, check that no Dark Souls II process remains. If one is still present, select it and choose End task only after the game has visibly closed.
4. Wait for Steam to stop showing the game as running. Do not begin a backup during a cloud-synchronization prompt or while Steam is still closing the session.

Closing the game is also required before a restore. Otherwise, the running process can replace your restored file with the newer in-memory state when it exits.

How to make a reliable Windows backup

1. Open the save directory

1. Press Win + R to open the Run dialog.
2. Enter %APPDATA%DarkSoulsII and press Enter.
3. Open the folder matching your account ID.
4. Locate DS2SOFS0000.sl2. If several profiles or account-ID folders exist, use the one whose modified time changes after you make a harmless in-game save and quit.

Do not rename or edit the original file in place. The safest operation is a copy, leaving the active file untouched.

2. Create an untouched baseline

On a separate drive or removable storage, create a folder with a descriptive name such as DS2-backups. Copy the file into a subfolder that identifies the edition and date, for example Scholar-Windows-DX112026-10-19-clean-baseline. Retain the original .sl2 extension.

A USB flash drive is sufficient for the small save file, provided it is disconnected or otherwise protected from accidental overwrites after the copy. An external drive or another offline storage location gives you a second failure boundary if the computer’s drive is damaged or a mod corrupts the active profile.

3. Keep experiment copies separate

Never overwrite the clean baseline. Before each significant mod test, make another copy in a dated folder such as 2026-10-19-mod-name-before-test. After a test that changes character progress, keep a second copy labeled with the result, for example 2026-10-19-mod-name-after-test. Use names that record the game edition, date, and purpose rather than generic names such as “backup2.”

• Baseline: the untouched pre-mod save that you will preserve indefinitely.
• Pre-test copy: the state immediately before a particular mod or tool is launched.
• Recovery copy: a known-good file that you have actually restored and checked.

Keep at least one baseline and several dated experiment copies. A long list of unverified copies is less useful than a small set whose contents and restoration procedure you understand.

4. Record the context

Put a text note beside each backup stating whether it is original Dark Souls II or Scholar, whether DLC was installed, the Windows edition in use, and which mod files were active. This prevents an apparently valid file from being restored into an incompatible game state months later.

Choose a backup location with the right failure protection

Whatever medium you choose, follow Steam Support’s advice: “To avoid problems in the future, make sure to test any backups that you create.” A file that merely exists in a folder has not yet proved that it can restore your character.

Test a backup without risking your baseline

Testing should be done before installing a mod, not after the original save has already been damaged.

Rank #2

Dark Souls II Game Guide: Complete Walkthrough, Secrets, and Strategies to Master Every Boss, Build, and Area in Drangleic

$17.99

Buy on Amazon

1. Close Dark Souls II and confirm that its process has ended.
2. Copy the current active DS2SOFS0000.sl2 to a temporary safety folder. This gives you a way back if the test itself goes wrong.
3. Copy a dated backup into the active account-ID folder and allow Windows to replace the existing DS2SOFS0000.sl2.
4. Launch the game while still offline. Confirm the expected character name, level, inventory, world progress, and other identifying state.
5. Quit normally, close Steam’s game process, and restore the latest active file from the temporary safety folder if you do not intend to continue from the test copy.

Do not test by connecting to online multiplayer. The test is intended to establish that the file can be read and that the expected character state is present, not to validate a mod for matchmaking.

How to restore a known-good save

1. Disconnect the computer from the internet or block the game before launching it. This is a precaution while you verify the restored state.
2. Exit Dark Souls II and confirm in Task Manager that no game process remains.
3. Open %APPDATA%DarkSoulsII<your account id>.
4. Copy the current DS2SOFS0000.sl2 to a temporary folder instead of deleting it. That copy is your emergency fallback if you selected the wrong backup.
5. Copy the known-good dated .sl2 into the account-ID folder and choose to replace the active file.
6. Launch the game while offline and verify the exact character and progression you expected.
7. Quit again before changing network status or removing any further files.

If the expected character is not present, close the game without saving, restore the temporary fallback, and try a different dated copy. Do not keep launching different files while online; first establish which save is valid offline.

What is known about mod-related ban risk

No official source establishes a universal, ban-proof procedure for Dark Souls II mods, and no trustworthy topic-specific statistic shows how often mod users are banned. Treat any online use of modified code, assets, input tools, or save data as a risk decision rather than as a guaranteed-safe setup.

Community modding guidance advises checking the individual mod author’s instructions and comments, testing offline, and removing mod components before returning online. That is community advice, not an official guarantee. The same guidance recommends removing all mod files, not merely restoring a clean save.

A concrete anti-cheat warning

PCGamingWiki records a specific warning that using Durazno to reduce controller deadzone can trigger anti-cheat and permanently ban an account from online matchmaking. This is a reported risk for that tool and configuration; it is not evidence that every mod has the same effect. It does show why a mod that appears unrelated to game balance can still be detected by anti-cheat.

Why a clean save is not enough

Replacing DS2SOFS0000.sl2 does not automatically restore original executables, DLLs, injectors, loaders, texture archives, configuration files, or controller utilities. The available sources do not establish that a clean save makes modified program or asset files safe for online play. Treat the game installation as modified until every component introduced by the test has been removed or replaced with an official copy.

A conservative offline mod-testing workflow

Prepare the rollback point

• Create and test the untouched baseline before installing anything.
• Make a dated pre-test save copy.
• Write down the mod’s file names and installation locations so you can remove them completely.
• Read the mod author’s online-use instructions and recent comments before deciding whether any online use is supported.

Keep the test offline

1. Disconnect from the network before launching the modded game.
2. Use only the offline features needed for the test. Do not enter co-op, versus play, messages, or bloodstains.
3. Do not allow a mod manager, injector, controller tool, or loader to remain running in the background when you finish.
4. Save the resulting state only as a dated experiment copy, never over the clean baseline.

FromSoftware’s FAQ describes online multiplayer as including co-op, versus play, messages, and bloodstains. Those features should be treated as online activity even if you are only checking one of them briefly.

Remove the mod before any online session

Follow the author’s uninstall instructions and remove every added component: loaders, DLLs, patched executables, replacement archives, scripts, configuration files, and controller utilities. If the installation method changed original files, use Steam’s file-verification or a clean reinstall as appropriate, then confirm that the files are back to the official version. A save-file swap alone is not a substitute for restoring the installation.

Use the clean save for the online return

After the installation is clean, close the game, replace the active save with the verified baseline or another known-good online-era copy, and launch once while still offline to confirm the character. Only then should you restore network access. This sequence reduces accidental exposure, but it is still not an official promise that an account cannot be flagged.

Returning online: a preflight checklist

• Edition confirmed: You are launching the same Dark Souls II edition and platform family that created the save.
• Processes stopped: The previous offline session has fully closed.
• Mod files removed: No injector, loader, patched executable, replacement asset, script, or controller utility from the test remains active.
• Installation checked: Official files have been restored where the mod altered them.
• Save selected: The active DS2SOFS0000.sl2 is the verified clean or appropriate online copy, not an experimental state.
• Offline launch checked: The expected character loads before networking is enabled.
• Author guidance followed: Any mod-specific warning overrides this general checklist.

If any item is uncertain, stay offline and resolve it first. Do not rely on a last-minute save replacement while leaving modified files in the installation.

Rank #3

Sale

Dark Souls II: Design Works

• Dark Souls II Design Works

$28.34

Buy on Amazon

Edition, DLC, and platform compatibility

FromSoftware’s FAQ sets boundaries that matter when restoring a backup:

Scholar of the First Sin released on Steam on April 1, 2015. The release date does not make its save compatible with every older or console edition; the platform and server-family distinction remains the deciding factor.

Troubleshooting common backup failures

The folder is missing

Launch the correct Windows edition once, create or load a character, save, and quit normally. Then check %APPDATA%DarkSoulsII again. If more than one account-ID folder exists, compare modified times and preserve copies from each folder rather than guessing.

The game ignores the restored file

Confirm that the file is named exactly DS2SOFS0000.sl2, that it is in the correct account-ID directory, and that the game process was closed before replacement. Also check edition, DLC state, and Windows DX9/DX11 compatibility. A file from a different platform family cannot be made compatible by renaming it.

The save appears corrupted

Stop launching it repeatedly. Close the game, preserve the questionable file in a separate folder, and restore the last dated copy that was successfully test-loaded. If no copy has ever been test-restored, treat the archive as unverified and try older copies one at a time while offline.

Steam restores the wrong state

Do not assume Steam’s game backup or synchronization contains the third-party save you need. Keep the manually copied .sl2 files separately and disable or pause synchronization only long enough to prevent an unwanted cloud state from replacing the file you are testing.

You removed the save but left the mod installed

Restoring the baseline does not undo executable or asset changes. Remove the mod according to its instructions, restore official game files where needed, and complete the offline preflight checklist before considering an online launch.

A practical backup naming plan

A consistent naming scheme makes the correct rollback obvious:

• Scholar-Windows-DX11-clean-baseline-2026-10-19
• Scholar-Windows-DX11-before-modname-2026-10-19
• Scholar-Windows-DX11-after-offline-test-modname-2026-10-19
• Scholar-Windows-DX11-online-ready-clean-2026-10-19

Store a short note with each file identifying the DLC state, the character it contains, and whether it was successfully loaded during an offline test. Never edit the baseline name to describe a later experiment; create a new copy instead.

What this workflow can and cannot guarantee

It can give you a recoverable rollback point, distinguish a verified save from an untested copy, and reduce the chance that modified files are exposed to online services. It cannot guarantee that an account will never be flagged, prove that every mod is detectable or undetectable, or make a cross-platform save compatible. The safest boundary is simple: preserve the clean file, test modifications offline, remove all mod components, verify the matching edition, and only then decide whether the remaining online risk is acceptable.

Quick Recap

Bestseller No. 1

Dark Souls II: Scholar of the First Sin - PlayStation 4

Parameter Setting Adjustments for Improved Balance; Augmented Item Descriptions; Increase in Maximum Online Players

$21.39

Bestseller No. 2

Dark Souls II Game Guide: Complete Walkthrough, Secrets, and Strategies to Master Every Boss, Build, and Area in Drangleic

$17.99

SaleBestseller No. 3

Dark Souls II: Design Works

Dark Souls II Design Works

$28.34

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.