Where Does the Micro Editor Store Settings?
Micro keeps settings.json and bindings in one config dir. The default path and the env vars that move it.
Last updated
Micro stores all user configuration in one directory, defaulting to ~/.config/micro. Options you set with Ctrl+E land in settings.json there automatically, so the file effectively writes itself as you customize. Keybindings live in bindings.json next door.
Two variables redirect it: $MICRO_CONFIG_HOME wins, else $XDG_CONFIG_HOME/micro. An init.lua in the same folder runs at startup for deeper scripting. Pass -config-dir for a one off alternate location without touching the environment.
Where Micro stores this, by platform
~/.config/micro/settings.json
Auto created on first run. bindings.json and init.lua share the folder. Honors $MICRO_CONFIG_HOME then $XDG_CONFIG_HOME; -config-dir overrides per launch.
~/.config/micro/settings.json
Same XDG style path as Linux, not Application Support. Copy settings.json alone to migrate options; plugins travel separately.
%USERPROFILE%\.config\micro\settings.json
Same relative layout under the user profile. Uninstalling means deleting the binary plus this folder; nothing hides in the registry.
Frequently asked questions
how do i reset micro settings
Quit Micro and delete settings.json from the config dir. It regenerates with defaults next launch. Keep bindings.json if you customized keys, since only settings.json holds option values.
micro set option did not stick, why
You likely used setlocal, which applies to the current buffer only and never writes to settings.json. Use plain set to persist. Per filetype blocks in settings.json cover the rest.
Notice an outdated path? Let us know.