Back up and restore DS4Windows profiles

Back up the settings actually used by your running edition, not only the application executable.

Home / Guides

On this page

Set it up

Close DS4Windows to finish writing settings. Identify the active data folder from the app or the storage choice made during setup. Classic installations commonly use a DS4Windows folder under AppData or data beside the executable.

Apply and test

Copy the complete active data folder, including Profiles, auto-profile rules and configuration files, to a dated backup. Keep the backup outside the working application folder so replacing or deleting the app cannot remove both copies.

Fine-tune the behaviour

To restore, close the target app and preserve its current data first. Copy the saved data into the correct location for that edition, then open the app and verify profile selection and auto-profile executable paths. Importing a single profile is safer than overwriting all settings across different forks.

Common pitfalls

A new PC needs its own drivers and HidHide application/device rules. Old game paths, moved executable allowlists and Bluetooth pairings do not become valid simply because the profile XML was copied. Test one controller and one game before restoring complex automation.

Verify before keeping the change

  1. Save a copy of the last working profile.
  2. Select the changed profile on the controller you are testing.
  3. Test in Windows, then in the target game or application.
  4. Compare with the unchanged baseline if behaviour is unexpected.
  5. Back up the working result and change only one further variable at a time.

Sources: Nexus release documentation · Project and screenshot credits. Updated 11 November 2026.