Where Does Balena CLI Store Settings and Keys?
Balena CLI keeps tokens, settings and cached images in ~/.balena, with apps and fleets living in the cloud.
Last updated
The Balena CLI stores login tokens and local settings in a .balena folder in your home. Cached base images and build state accumulate beside them across deploys.
Fleets and devices themselves live in BalenaCloud, so the local folder is replaceable. Logging out or deleting it only forgets the machine's session. Rebuilding the cache costs download time, nothing else.
Where Balena stores this, by platform
~/.balena
Tokens in tokenstore, settings and image cache beside them. Log out with balena logout to clear credentials without touching cached images.
~/.balena
Same layout on Mac. Standalone installs and npm installs share the path, so switching install methods keeps your login.
%USERPROFILE%\.balena
Same tree on Windows. The CLI shells out to Docker or Balena Engine, whose own image stores live separately under Docker's data root.
Frequently asked questions
how do i log out of balena cli
Run balena logout. It clears tokens from ~/.balena while leaving cached images. Delete the folder entirely for a full reset including settings.
where are balena apps stored locally
Nowhere permanent. App source stays in your project folders and devices run in the cloud. The CLI folder holds session state and build cache only.
Notice an outdated path? Let us know.