Where Are PlanetSide 2 Settings Located?
PlanetSide 2 keeps UserOptions.ini and keybinds next to the game exe, not in Documents. Install path plus Proton notes.
Last updated
PlanetSide 2 breaks the usual pattern. Its settings live next to the game executable, not in Documents or LocalAppData. UserOptions.ini holds graphics options and InputProfile_User.xml holds keybinds, both in the install folder beside PlanetSide2.exe.
That placement surprises people who check Documents first and find nothing. It also means reinstalls wipe settings unless you copy the two files out first. Characters and unlocks live on the Daybreak servers, so the local files carry options only. Running from Program Files without rights can redirect writes to VirtualStore.
Where PlanetSide 2 stores this, by platform
C:\Program Files (x86)\Steam\steamapps\common\PlanetSide 2\UserOptions.ini
Graphics live in UserOptions.ini with keybinds in InputProfile_User.xml beside it. Replace the Steam root with your own library path. Non-Steam installs use their own folder with the same two filenames. Back both up before reinstalling.
<SteamLibrary>/steamapps/compatdata/218230/pfx/
Steam Play prefix for app ID 218230. The install-folder layout above is mirrored inside the prefix. Copy UserOptions.ini and InputProfile_User.xml out before verifying files, since validation can reset them.
Frequently asked questions
Where is the PlanetSide 2 config file?
Next to the game exe at UserOptions.ini in the PlanetSide 2 install folder. Graphics, render distance and smoothing options live there. Edit with the game closed, since the client overwrites the file on exit.
How do I back up PlanetSide 2 keybinds?
Copy InputProfile_User.xml from the install folder beside UserOptions.ini. Restore both files to the same folder on the new install before launching. Characters, certs and unlocks follow your Daybreak account regardless.
Why do my settings reset after every patch?
Validation and reinstalls rewrite the install folder, which is also the settings folder here. Keep copies of both files elsewhere and restore after patching. Running as admin once can also clear VirtualStore confusion.
Notice an outdated path? Let us know.