Where Are The Last Caretaker Save Files Located?
The Last Caretaker saves under a Voyage folder in LocalAppData, including an automatic SaveGameBackups folder worth knowing.
Last updated
The Last Caretaker is another Unreal game whose folders do not match its store name. Everything lives under %LOCALAPPDATA%\Voyage\Saved: SaveGames for progress, Config\Windows for settings, and a third folder called SaveGameBackups that the game maintains itself. A search for The Last Caretaker in AppData finds nothing, because Voyage is the internal project name.
Steam and Epic builds use the same local path (Steam App ID 1783560), and both clients run their own cloud sync for the game. The built-in backup folder is the detail worth remembering: if a save ever fails to load, check SaveGameBackups before resigning yourself to a fresh start.
Where The Last Caretaker stores this, by platform
%LOCALAPPDATA%\Voyage\Saved\SaveGames
Live save data. The folder is named Voyage, not The Last Caretaker. Copy it with the game closed for a manual backup.
%LOCALAPPDATA%\Voyage\Saved\SaveGameBackups
Automatic backups the game rotates on its own. A corrupted or missing save can often be restored from here without touching cloud sync.
%LOCALAPPDATA%\Voyage\Saved\Config\Windows
Graphics, audio and gameplay settings in Unreal's standard layout, separate from the save folders next door.
Frequently asked questions
Why is there no The Last Caretaker folder in LocalAppData?
The game uses the internal project name Voyage for its user folders. Search for Voyage instead and the whole Saved tree, saves included, is right there.
Does the Epic version use a different save path?
No. Epic and Steam builds share the same Voyage folder on disk. Swapping stores on one PC keeps your save; on a second PC copy the folder manually, since the two clouds do not talk to each other.
What is the SaveGameBackups folder?
It is the game's own rolling backup of your saves, kept next to the live folder under Voyage\Saved. Prefer restoring from it over starting fresh when a save will not load.
Notice an outdated path? Let us know.