Where Does Hyfetch Store Its Config?
Hyfetch stores its preset and backend choice in ~/.config/hyfetch.json. Rerun hyfetch -c to rebuild it anytime.
Last updated
Hyfetch keeps one JSON file at ~/.config/hyfetch.json: color preset, brightness, alignment, mode, backend choice, and backend args. First run creates it through an interactive wizard; every later run reads it silently. The -C flag points at an alternate file for multi-personality setups.
Backends matter because hyfetch renders through them. Neofetch, neowofetch, and fastfetch each keep their own configs beside hyfetch.json, and backend quirks (stdout detection stripping color, distro misdetection) live there, not in hyfetch itself. Back up hyfetch.json with dotfiles; regenerate backends from defaults when moving machines.
Where Hyfetch stores this, by platform
~/.config/hyfetch.json
Preset, lightness, alignment, backend selection. Created by hyfetch -c wizard. Override per run with -C. Backend configs (neofetch/fastfetch) sit beside it and own rendering quirks.
~/.config/hyfetch.json
Same JSON layout via Homebrew or pip installs. Backend detection differs slightly (local IP hangs were a known macOS quirk), so keep backend configs in sync when sharing dotfiles across OSes.
Frequently asked questions
how do i change my hyfetch flag colors
Run hyfetch -c and pick a new preset. The wizard rewrites hyfetch.json in place. Use -C with another path if you keep multiple identities (work rainbow versus stealth monochrome).
why are my hyfetch colors wrong when piping
The backend config it wraps. Hyfetch delegates rendering to neofetch, neowofetch, or fastfetch, each reading its own config beside hyfetch.json. Set --stdout=off in hyfetch.json or the backend config when pipes eat your colors.
Notice an outdated path? Let us know.