Where Does Alby Store Wallets and Settings?
Where the Alby extension keeps wallets, allowances and settings across desktop browsers for backup.
Last updated
Alby lives inside the browser profile as an extension: wallet connections, per site allowances and options in extension storage, with account linkage through Alby cloud. There is no standalone vault file to copy between machines.
Browser sync carries extension data when enabled; otherwise export and re-import manually. Allowances cap per site spending, so review them after moves. Mobile Alby Go keeps its own separate app storage on phones.
Where Alby stores this, by platform
%LOCALAPPDATA%\Google\Chrome\User Data\Default
Wallets and allowances in extension storage under the browser profile. Confirm the profile with chrome://version. Sync or export moves settings; seeds move funds.
~/Library/Application Support/Google/Chrome/Default
Same extension storage pattern under per OS browser data. Brave and Edge use their own parent names. Cloud login restores accounts after reinstalls.
~/.config/google-chrome/Default
Same pattern under XDG config for Chromium builds. Check the profile path in each browser. Extension reinstalls wipe unsynced allowances.
Frequently asked questions
How do I move Alby to a new computer?
Back up the seed or nsec plus export settings where offered, then enable browser sync for extensions. Reinstalls wipe local extension storage. Accounts reconnect through the Alby cloud login on the new machine.
Where is Alby data inside my browser profile?
Type chrome://version and read the Profile Path. Extension data lives under that parent in Local Storage and IndexedDB. The path wins over documented defaults across browsers.
Notice an outdated path? Let us know.