Where Does Star Citizen Store Keybinds and Config?
Star Citizen keeps mappings, profiles, screenshots, and user.cfg inside the install folder under each build USER directory.
Last updated
Star Citizen stores almost everything next to the game install, not in Documents or AppData. Each build (LIVE, PTU, and test channels) has its own USER tree. Exported control profiles land in USER Client 0 Controls Mappings as XML files. Live settings sit in USER Client 0 Profiles. Screenshots collect in a Screenshots folder at the build root.
The USER folder is also the standard fix for patch trouble. Deleting it forces a clean rebuild of shaders and cached settings. Back up Mappings and any custom user.cfg first, since those two hold work you actually want to keep.
Where Star Citizen stores this, by platform
<InstallDrive>\Program Files\Roberts Space Industries\StarCitizen\LIVE\USER
Install relative path, so the drive letter varies. Mappings holds exported XML profiles, Profiles holds live settings, Screenshots holds captures, and user.cfg sits at the LIVE root.
Frequently asked questions
How do I carry keybinds from LIVE to the PTU build?
Copy the Mappings folder plus the Profiles default folder to the same path in the new build. Exported XML files carry keybinds, while the profile folder carries peripheral links.
The game breaks after every patch. What folder do I delete?
Delete the USER folder for that build and let the launcher rebuild it. Shaders recompile on next launch, which fixes most post patch glitches and stale binding errors.
Where do Star Citizen screenshots go?
They land in the Screenshots folder inside the build directory. The folder appears after your first capture, so take one shot before hunting for it.
Notice an outdated path? Let us know.