Where Does Micro-Manager Store Config?
Micro-Manager keeps hardware configs as .cfg files you save, plus ImageJ plugin data. Match device names on the new PC.
Last updated
Micro-Manager stores microscope setups as hardware config files you save by hand. Device adapters load from the install tree. Images go wherever your acquisition saves them.
Treat .cfg files as the portable unit. Plugin data rides with the ImageJ install. Copy configs plus plugins with stable paths, since device names must resolve on the new machine.
Where Micro-Manager stores this, by platform
Hardware .cfg files wherever saved (adapters in install dir)
Hardware configs as .cfg files wherever saved. Adapters in install tree. Copy configs plus plugins with matching paths.
Hardware .cfg files wherever saved (adapters in install dir)
Same .cfg workflow on every OS. Keep ImageJ plugin sets aligned.
Hardware .cfg files wherever saved (adapters in install dir)
Same .cfg workflow. Confirm adapter paths when installs differ.
Frequently asked questions
How do I move a Micro-Manager setup?
Copy your .cfg hardware files plus plugins to matching paths. Configs reference devices by name. Keep ImageJ versions aligned between installs.
Devices missing after restart. Why?
Save the hardware configuration explicitly from the setup wizard. Unsaved device lists vanish on close. Keep .cfg files with their calibration data.
Notice an outdated path? Let us know.