Automatically Switch Profiles for Different Apps
Automatic profile switching watches the application in the foreground and loads the profile assigned to that application's process. It is useful when different games or programs need different control layouts.
Prerequisites
- Create every profile you want to switch between before adding rules.
- Open each target application at least once so it is easy to find under Open windows.
- Use a regular game profile as the target. The Global profile already runs alongside regular profiles and normally does not need an app rule.
Add an app-to-profile rule
- Open Settings.
- Select Advanced.
- Under Focused app, find Find apps.
- Select Profile form.
- In Browse apps, select Open windows.
- Select Refresh list if the application is not already shown.
- Search for the application, then select its row.
- Under Add app → profile, confirm that Process name was filled.
- Choose the matching Profile.
- Select Add.
- Turn on Auto-switch profile by focused app.
The new rule appears under Profile per app. Process names are stored in lowercase without a trailing .exe.
If the application is not open, try All processes or Installed in the app browser. You can also type or paste its process name directly into Process name.
Add rules for more applications
Repeat the procedure for each application and select a different profile where needed. Each listed rule contains:
- The normalized process name
- The profile PlayAbility will load
- A Remove button
To change the profile for an existing rule, use its Profile list. To change its process name, remove the row and create it again.
Verify automatic switching
- Keep Auto-switch profile by focused app on.
- Open two applications that have different rules.
- Bring the first application to the foreground.
- Wait briefly, then confirm its assigned profile becomes current.
- Bring the second application to the foreground and confirm the profile changes again.
At the top of Focused app, Active window now shows the process PlayAbility currently detects. Use this value to diagnose a rule that does not match.
PlayAbility ignores its own window while checking rules, so opening Settings does not replace your game profile.
Tune foreground detection
The default polling interval is suitable for most people. If switching is noticeably delayed:
- Expand Advanced at the bottom of Focused app.
- Adjust How often to detect the active app (ms).
- Test the switch again.
The allowed range is 200 to 10,000 ms. A shorter interval detects changes faster but checks the foreground application more often.
Troubleshooting and limitations
The app is missing from Open windows
Start the application and make sure it has a visible window, then select Refresh list. If it still does not appear, search All processes or Installed, or copy the value from Active window now.
The wrong executable was selected
Some games use a launcher and a separate game process. Bring the actual game window to the foreground and use the process shown under Active window now, not the launcher name.
The rule exists, but the profile does not change
- Confirm Auto-switch profile by focused app is on.
- Confirm the target profile still exists.
- Compare the rule's process name with Active window now.
- Expand Advanced and review Last error if one is shown.
A broad process name matches the wrong application
Foreground rules support exact and partial process-name matching. Use the most distinctive full process name available. Avoid short fragments that can also appear in another application's process name.
Switching happens when a launcher opens
Remove the launcher rule and create a rule for the game's actual process instead.
The profile changes, but no output reaches the app
Profile switching and output filtering are separate. Confirm Main Output is on and check whether Limit remapped output using the lists below is blocking the foreground application.
A deleted or renamed profile was used by a rule
Update the rule's Profile selection after a rename. Remove stale rules whose profile no longer exists.
Checking Settings appears to stop detection
PlayAbility deliberately ignores its own process so you can configure the feature safely. Return focus to the target application to test its rule.
Updated on: 29/07/2026
