Flow Launcher Settings Not Saving: Locate the Active Profile

Troubleshooting · Published October 30, 2026 · Publisher: flowlauncher.app

At a glance

When settings seem not to save, first confirm that you are reopening the same Flow instance and active UserData folder. Then check write access, duplicate processes, and sync interference. Preserve the current profile before editing or replacing configuration files.

Steps to follow

  1. Locate UserData from the running instance and record the executable path associated with it.
  2. Change one harmless preference, exit Flow normally, and reopen that exact copy to check persistence.
  3. Inspect whether the data folder is writable and whether cloud-sync or backup software is creating conflicts. Avoid running two copies against one profile.
  4. Check your version against release notes. Version 2.1.4 includes a fix for stale content remaining when shorter JSON data was saved.

Check the result

The selected preference survives a normal close and reopen using the same profile. Confirm the expected configuration file was updated without manually overwriting it while Flow ran.

Limits and common pitfalls

Editing live settings files can be undone by the running application. A read-only portable folder can also prevent persistence even when the interface allows a change.

Make the check repeatable

Use a reversible test such as a display preference rather than changing credentials or deleting plugin data. Note whether the problem occurs after a normal exit, forced termination, sign-out, or system shutdown; those paths can produce different evidence.

Questions and answers

Why do settings differ when I open Flow another way?

Different shortcuts may launch different installations or profiles. Compare executable and UserData locations.

Sources and scope

Documentation-based guidance, with source review on October 30, 2026. What was and was not tested.

Related guides