Where Are Steelrising Save Files Located?
Steelrising saves fsav files directly under Documents with a GOG variant folder. Proprietary engine, no Unreal involved.
Last updated
Steelrising files saves flat under Documents with fsav extensions and no subfolders. GOG builds twin the folder with a seller suffix while interiors match. Cloud quotas run generous per account.
Proprietary engine means no Unreal or Unity conventions apply. Mod guides insist on moving files rather than folders into these trees. Epic layouts stay unverified and unquoted.
Where Steelrising stores this, by platform
%USERPROFILE%\Documents\Steelrising
Flat fsav saves with GOG twin folder per seller. Cloud mirrors with large quotas. Move files not folders per mod guides, copied whole with the game closed.
<SteamLibrary>/steamapps/compatdata/1283400/pfx/
Steam Play prefix for App ID 1283400. The Documents tree maps inside the prefix drive. Seller-suffix split applies on every platform.
Frequently asked questions
How do I back up Steelrising saves?
Copy the whole %USERPROFILE%\Documents\Steelrising folder with the game closed, moving files rather than folders per mod guides. GOG builds use the SteelrisingGOG twin instead. Cloud mirrors per store with sizable quotas.
What engine does Steelrising use?
It runs the proprietary Silk engine, not Unreal or Unity. Folder shapes follow Spiders conventions rather than engine defaults. Epic paths stay unverified with the same Documents guess unconfirmed.
Steam versus GOG Steelrising paths?
They split by seller suffix with identical interiors. Steam writes the plain folder while GOG appends its name. Mod installs move files into the matching tree per guide instructions.
Notice an outdated path? Let us know.