Dusk save file location
Use this page before updating Dusklight, moving from Dusk to Dusklight, changing the data folder, testing texture packs, or trying to recover a Dusk Twilight Princess save file on Steam Deck, Android, Windows, macOS, Linux, or iOS.
Think in data folders, not random paths
The most important Dusk save file rule is that the app file and the data folder are not the same thing. The app file is the downloaded Dusklight build. The data folder is where saves, settings, texture replacements, and sometimes other user state live. Users lose time when they delete an old app folder, move a portable install, or copy a texture pack into a guessed location without knowing which data folder Dusklight is actually reading.
Dusklight v1.1.1 introduced desktop Change Data Folder support, and v1.2.0 continues to make data-folder awareness important because updates now include autosave safety work and more platform fixes. If the app offers an Open Data Folder or Change Data Folder action on your platform, use it. That route is better than copying a path from a guide that might not match your OS, username, portable mode, or app sandbox.
This page deliberately avoids pretending there is one perfect path for every device. A Windows portable install can store data beside the executable. A macOS user may choose a data folder after moving the app. Steam Deck users often keep games under a custom Games folder or SD card. Android app data visibility can vary by file manager and Android version. The correct answer is to identify your active data folder, then back up that folder before making changes.
Platform notes
| Platform | Where to start | Save risk |
|---|---|---|
| Windows | Use the app's data folder option or the portable data/ folder if portable mode is enabled. | Deleting a portable folder can delete saves if you did not copy data/ first. |
| Steam Deck / Linux | Launch from the AppImage once, then use the current data folder or your chosen custom folder. | Moving the AppImage shortcut does not automatically move old data. |
| macOS | Use the correct Apple silicon or Intel build, then open or set the data folder from the app when available. | Gatekeeper and app bundle moves can distract from the real data-folder location. |
| Android | Use in-app access if available and watch file-manager limitations. | Android app data may be hidden, protected, or hard to reach after reinstalling. |
| iOS | Follow your sideloading tool's backup workflow and avoid deleting app data during resigning or reinstall. | Reinstall flows can remove app containers if not handled carefully. |
Safe backup workflow
- Open Dusklight and confirm the app launches before touching folders.
- Find the active data folder using the app's data-folder tool where possible.
- Close Dusklight completely so save files are not being written while copied.
- Copy saves, config, and any custom user folders into a dated backup folder outside the app directory.
- Do not mix the backup folder with texture pack downloads or mod archives.
- Update Dusklight or change folders only after the backup exists.
- Launch the new build clean before restoring or moving anything back.
A dated backup folder is boring, but it prevents the most common recovery problem: not knowing which folder was the real one. Use a simple name such as dusklight-save-backup-2026-05-23. Keep it outside the app folder so replacing a build or deleting an old portable directory does not remove the backup at the same time.
Android data access warning
Android needs special caution. The official tracker has a current issue around full data folder access on Android. That matters because users often search "Dusk save file location Android" after a file manager hides app data or after a reinstall makes the expected folder disappear. Do not assume that every Android file manager exposes the same paths. Do not assume a folder under Downloads is the live Dusklight data folder just because you created it.
Use this Android order instead: install the official APK, launch once, select your own supported disc image, create or confirm one test save, then inspect data access from inside the app or through a trusted file manager. If you cannot access the folder, record Android version, device model, Dusklight version, file manager name, and what action failed. That is a useful support report. Randomly copying folders into protected Android directories is not.
For texture packs on Android, separate save recovery from texture installation. A large texture pack can create storage pressure and performance symptoms, but it should not be part of the first save-location test. Confirm saves first, then use the texture pack guide.
Steam Deck save workflow
Steam Deck users should keep the app shortcut and the data folder easy to recognize. If you download a newer AppImage, update the non-Steam shortcut, but do not delete the old folder until you know where saves and texture packs live. If you use a custom data folder on the Deck, write the path down in a note. Many Deck issues come from Desktop Mode and Game Mode seeing the same files through different launch habits, not from Dusklight corrupting saves.
Before changing texture packs on Steam Deck, copy saves first. Texture pack testing often involves large folders and repeated restarts. It is not the time to discover that you moved a data folder and left the only save inside an old directory. Use Steam Deck setup for the install path and return here when you need to back up.
Restore and migration rules
Restoring is safer when you move one thing at a time. First prove that the new Dusklight build opens. Then prove that a clean supported disc image reaches gameplay. Then restore one save and test loading it. Only after that should you add texture packs, mods, custom controls, or platform remappers. If you restore everything at once and the app fails, you will not know whether the save, config, texture pack, controller profile, or graphics backend caused it.
Dolphin saves and Dusk or Dusklight saves should not be treated as automatically interchangeable by simple copy-paste. If you are migrating from an emulator workflow, keep the emulator backup separate and test a copy, not your only save. The same rule applies when moving from Windows to Steam Deck or from a desktop build to Android. One clean backup, one test restore, one platform at a time.
Save file FAQ
Should I delete old Dusk folders after installing Dusklight?
Not immediately. First confirm the newest official Dusklight build launches, sees your supported disc image, and loads your save from the intended data folder. Then archive or delete old folders only after your backup is safe.
Can I put texture packs in the same backup folder?
Keep backups and texture pack installs separate. A backup should preserve user state. Texture packs should live in the active texture replacement folder or in a separate archive folder from the original creator.
Where should I go next?
Use the update guide before replacing builds, known issues for current save and Android reports, and not working if the app launches but cannot find files.