Where Does Mbed Store Config and Libraries?
Mbed CLI keeps global config in ~/.mbed with libraries cached per project in .lib references.
Last updated
Mbed CLI stores compiler paths and global settings in a .mbed folder in your home, while each project pins its library versions in .lib files beside the code.
Build outputs land in a per project build directory that regenerates freely. Migrating machines means copying projects plus the global config; libraries redeploy from their recorded revisions.
Where Mbed stores this, by platform
~/.mbed
Global config with toolchain paths. Projects hold .lib references and a build folder each. Online compiler users keep nothing local beyond exports.
%USERPROFILE%\.mbed
Same layout on Windows. The Mbed Studio IDE adds its own settings in AppData while sharing the project structure.
~/.mbed
Same arrangement on Mac. Library versions pin in project .lib files, so fresh checkouts rebuild identically.
Frequently asked questions
where are mbed build outputs
In the build folder inside each project, with .hex and .bin at its root on success. Delete it for a clean rebuild.
how do i move mbed to a new computer
Copy project folders plus ~/.mbed for toolchain paths. Run mbed deploy in each project to refetch libraries at pinned revisions.
Notice an outdated path? Let us know.