Where Does Rabby Store Wallet Data on Desktop?
Rabby keeps its keyrings in Chrome local storage, but copied files can never restore on a new machine.
Last updated
Rabby stores keyrings, passwords and preferences in Chrome local storage under Local Extension Settings\acmacodkjbdgmoleebolmdjonilkdbch. The folder looks like any Chromium wallet's LevelDB set, and its README says so outright. Copying it feels like a backup.
It is not a portable one. Rabby's encryption ties to the local environment, so the same folder on a new machine opens as a stranger. A GitHub recovery thread confirms it: files plus password still meant starting over. Treat the seed phrase as the backup and the folder as a convenience copy at best.
Where Rabby stores this, by platform
%LOCALAPPDATA%\Google\Chrome\User Data\Default\Local Extension Settings\acmacodkjbdgmoleebolmdjonilkdbch
Keyrings in Chrome local storage under the Rabby store ID. Copies do NOT restore on new machines by design; the seed phrase is the migration path. Copy with the browser closed.
~/Library/Application Support/Google/Chrome/Default/Local Extension Settings/acmacodkjbdgmoleebolmdjonilkdbch
Same extension-ID folder on macOS. Same non-portability: files plus password still open as a fresh wallet elsewhere.
~/.config/google-chrome/Default/Local Extension Settings/acmacodkjbdgmoleebolmdjonilkdbch
Same extension-ID folder under the Chrome config root. Brave and Edge follow with their own vendor profile roots.
Frequently asked questions
Can I migrate Rabby by copying the extension folder?
No. Rabby binds its encryption to the local environment, so transplanted LevelDB files open as a fresh wallet. The seed phrase is the only migration path; the files are a dead end for moves.
How do I move Rabby to a new computer properly?
Reinstall, import the phrase, reconnect the hardware device. Rabby re-derives the same accounts from the phrase alone. Local preferences like allowlists rebuild by hand.
Notice an outdated path? Let us know.