Where Does SonarLint Store Bindings and Server Data?
SonarLint (now SonarQube for IDE) keeps server data in ~/.sonarlint, bindings in .sonarlint, and settings in the IDE.
Last updated
SonarLint splits state three ways. Connection tokens live in IDE settings (VSCode settings.json or the JetBrains equivalent). The project binding (server URI plus project key) sits in a .sonarlint folder in the repo, meant to be shared. Downloaded analyzers and synced profiles cache under ~/.sonarlint in your home dir.
Note the rename: the VSCode extension is now called SonarQube for IDE. Docs and menus use the new name while the folders and settings keys still say sonarlint.
Where SonarLint stores this, by platform
%USERPROFILE%\.sonarlint\storage
Server storage: analyzers, quality profiles and suppressions. Safe to delete; it rebuilds on next sync. Project bindings live in [RepoDir]/.sonarlint/ instead.
~/.sonarlint/storage
Same storage role. SSL truststores default under ~/.sonarlint/ssl/ (truststore.p12, keystore.p12) for servers behind custom CAs.
~/.sonarlint/storage
Same layout on Linux. Connection setup moved into the IDE's Connected Mode view (v3.8+); older setups used raw sonarlint.connectedMode keys in settings.json.
Frequently asked questions
Can I safely delete the SonarLint storage folder?
Delete the storage folder while the IDE is closed. It holds downloaded analyzers and synced quality profiles, all of which re-download on the next server sync.
Should the .sonarlint folder be committed to git?
That folder is the shared team binding: server URI plus project key. Tokens stay in your personal IDE settings, so committing the folder is the intended workflow.
Notice an outdated path? Let us know.