Where Does GlazeWM Store Its Config?
Where GlazeWM generates its config.yaml file on Windows, and the flag and variable that relocate it..
Last updated
GlazeWM keeps one YAML file describing binds, rules, and gaps, generated under a .glzr folder in your profile on first run. A CLI flag or environment variable points the app at any other path when dotfile setups demand it. Reloading happens live through a keybind.
The file validates on load with readable errors, which beats silent misbehavior. Samples ship in the repo for new setups. State like layouts never touches disk, so the YAML is the entire backup story. Keep it with your other dotfiles.
Where GlazeWM stores this, by platform
%USERPROFILE%\.glzr\glazewm\config.yaml
Auto-generated YAML with binds, rules, and gaps on first run. Override with --config flag or GLAZEWM_CONFIG_PATH variable. Reload live via keybind after edits. The whole backup is this one file.
Frequently asked questions
how do I change GlazeWM settings
Edit config.yaml in the .glzr tree and reload with the documented keybind instead of restarting. Validation errors print on load, so keep a known-good copy. The app generates a sample file on first run when none exists.
how do I move the GlazeWM config
Start with --config pointing at the file, or set GLAZEWM_CONFIG_PATH persistently. Custom paths allow friendlier names than config.yaml. Dotfile managers symlink either location with equal ease.
is the config portable
Yes for the config file itself, which is plain YAML describing binds and rules. Window state stays in memory and never persists. Back up the YAML; nothing else needs saving.
Notice an outdated path? Let us know.