Where Does CLion Store Settings and Toolchains?
CLion keeps settings in ~/.config/JetBrains/CLion<version> on Linux (Preferences on Mac, AppData Roaming on Windows) with toolchains, CMake profiles, and keymaps inside.
Last updated
CLion follows JetBrains conventions with versioned config folders per platform. Settings, keymaps, plugins, CMake profiles, and toolchain definitions live together in that tree. Caches and indexes sit in system folders beside it, safe to delete.
Toolchains deserve attention because compilers move between machines. Profiles reference absolute paths that break on transfer, so re point them after migration. Export settings through the IDE for version tolerant moves.
Where CLion stores this, by platform
~/.config/JetBrains/CLion2024.3
Settings, keymaps, plugins, and CMake toolchains together. Versioned folders coexist across upgrades. Export from IDE for safer moves.
~/Library/Application Support/JetBrains/CLion2024.3
Preferences tree mirrors Linux config for settings and toolchains. Caches live in Caches folder beside it. Re point toolchains after moves.
%APPDATA%\JetBrains\CLion2024.3
Roaming tree holds the same settings and profiles on Windows. Version folders keep upgrades isolated. Copy with IDE closed.
Frequently asked questions
How do I back up CLion settings?
Copy the config folder for your version with CLion closed, since settings, keymaps, and toolchains travel together. Major versions keep separate folders that do not migrate automatically. Export settings from the IDE for safer transfers.
Where are CLion toolchains stored?
Open settings and point toolchains at compilers, CMake, and debuggers, stored per profile in the config tree. Remote toolchains add deployment mappings beside them. Test each toolchain after moves.
Notice an outdated path? Let us know.