Where Is the picom Config File?
Where the picom compositor looks for picom.conf on Linux, and which fallback paths it checks.
Last updated
picom reads one config file at startup, preferring ~/.config/picom/picom.conf (or $XDG_CONFIG_HOME when set) over system copies. Older guides cite ~/.config/compton.conf from the Compton rename era; that still works on some builds but should not be relied on.
Keep effects in one place and launch flags minimal. Backend choice and vsync live in the file, so moving machines means copying one file plus your autostart line. Test under your real driver; VMs hide tearing bugs.
Where picom stores this, by platform
~/.config/picom/picom.conf
Main user config. Legacy compton.conf paths linger on some builds but the picom.conf name is canonical now. Pair with an autostart entry in your WM config.
Frequently asked questions
How do I start a custom picom config?
Create ~/.config/picom/picom.conf and add backend, vsync, shadows, and opacity rules there. Start picom with --config pointing at a test copy first; a bad backend line is the usual reason for a black or flickering screen.
Can I keep the config somewhere else?
Yes. picom --config /path/to/test.conf overrides every default location. The lookup order is the -c path, then $XDG_CONFIG_HOME, then ~/.config, then system dirs. Use it for A/B testing effects.
Notice an outdated path? Let us know.