Dark Souls Remastered also stores several character slots inside one .sl2 profile container. A reliable backup therefore captures DRAKS0005.sl2 at the profile level and keeps the numeric user folder context. Steam Cloud can help, but it should not be the only copy before a mod, manager, or migration. SaveEditor.com does not describe one character as an independent file because that would misrepresent the container structure.
Which storefront context matters
Documented Dark Souls Remastered PC launchers/storefronts: Steam. The account-specific numeric directory matters. Keep the directory level when moving backups between PCs. The active storefront/account should be identified before any restore because cloud and local storage may not use the same path or container across editions.
Documented cloud behavior
Steam Cloud is documented for Dark Souls Remastered, but a manual dated copy is still recommended before experimentation. Cloud synchronization is useful for continuity, but it can also turn a restore into a conflict-resolution event. Let synchronization settle before making a manual backup, and keep an offline copy outside any folder monitored by the launcher or operating-system sync service.
Local save roots still matter
The researched local save boundary is Windows: %USERPROFILE%DocumentsNBGIDARK SOULS REMASTERED<user-id> | Linux / Steam Play: Steam Play: <SteamLibrary-folder>/steamapps/compatdata/570940/pfx/; the known file or folder pattern is DRAKS0005.sl2. A cloud-enabled game still has concrete local data involved in ordinary play, and that local context is what you need when identifying which copy was modified most recently.
Avoid accidental overwrite loops
Copy DRAKS0005.sl2 and preferably the complete numeric profile folder. When restoring, close the game and launcher, preserve both the current local copy and the backup you want to test, then place the intended data in the matching profile/storefront location. Do not repeatedly open the game between different copies without noting which side the cloud client selected.
Compatibility and conflict checks
File replacement affects the whole profile container. Character-level merging requires a dedicated parser and is not implied by this Game Hub. If progress disappears or rolls back, If an imported profile does not appear, verify that it is inside the correct numeric account folder and that cloud synchronization did not restore another revision. Resolve identity/path/cloud questions first. A cloud conflict is not proof that the save itself is corrupt, and a successful upload is not proof that files from another storefront are compatible.
Verification context: The Documents/NBGI save path and Steam Cloud support were reviewed against current PCGamingWiki coverage. DRAKS0005.sl2 naming is corroborated by current save-manager/community references.