Where Does Vimium Store Keymaps and Settings?
Vimium keeps keymaps and settings in synced browser extension storage inside each browser profile folder.
Last updated
Vimium stores its settings in the browser sync area, not in a dotfile. Custom keymaps, exclusions, and CSS live in extension storage under the active profile. Chrome sync carries them between machines on the same account.
There is deliberately no vimiumrc. The options page is the config file, with export and import buttons for manual moves. Firefox keeps the same data under its own profile tree. Sync off means each profile stands alone.
Where Vimium stores this, by platform
%LocalAppData%\Google\Chrome\User Data\Default\Extensions (per profile)
Settings ride with browser sync when signed in. Export from options before reinstalls. Local extension folders carry opaque IDs, so prefer the export file.
~/Library/Application Support/Google/Chrome/Default/Extensions (per profile)
Same sync model on Mac. Firefox data sits under ~/Library/Application Support/Firefox/Profiles. One export file covers keymaps, exclusions, and CSS.
~/.config/google-chrome/Default/Extensions (per profile)
Chromium and Firefox both keep Vimium data under ~/.config or ~/.mozilla profile trees. Sync behaves the same. Manual backup is still the options export.
Frequently asked questions
Do Vimium settings follow my browser sync?
Usually yes, through the browser sync Vimium already uses. Same signed-in profile on the new machine pulls settings down. Exclusions and custom CSS come along with the rest.
Where is the Vimium config file?
There is no vimiumrc file. Everything lives in the extension options page backed by synced storage. Paste shared mappings into the custom keymaps box and save.
What is in the Vimium backup file?
The backup file is plain text with one mapping per line. Keep it in dotfiles for versioning. Restoring is a paste into the same options box.
Notice an outdated path? Let us know.