Contact

Contact and support

Use the right channel and you will get an answer faster: this site’s authors can fix pages on fastfetch.dev, but fastfetch bugs and feature requests belong to the upstream project.

Corrections and site questions

Wrong or outdated information on a page, a broken link, or a question about this site.

support@fastfetch.dev

Report a fastfetch bug

The program prints wrong data, crashes, or misses a package manager. Search existing issues first.

GitHub Issues →

Ask for usage help

Configuration questions, sharing your setup, or ideas for new features.

GitHub Discussions →

Before you ask for help

Most questions are answered in the FAQ or the troubleshooting guide. If not, include these details so the problem can be reproduced:

  • The output of fastfetch --version and your operating system, desktop or window manager, and terminal.
  • What you expected and what you got, plus the config snippet involved (or fastfetch -c none output to rule your config out).
  • The output of fastfetch --show-errors; it names the module that failed. For a data problem, fastfetch -s <module> --format json shows the raw values.
Check before you post: fastfetch output can include your username, hostname, IP addresses, serial numbers and Wi-Fi name. Remove anything you do not want to be public from logs and screenshots.

Security reports

Problems with this website (for example a vulnerability in its pages or headers): email security@fastfetch.dev and describe how to reproduce it. Please give us reasonable time to fix it before disclosing it publicly. Our machine-readable contact details are in security.txt (RFC 9116).

Vulnerabilities in the fastfetch program itself belong with its maintainers, not with this site: see the Security tab of the upstream repository.

Who answers

fastfetch.dev is an independent guide (about us). We are not the fastfetch developers and cannot change the program, but we will correct this site quickly when it is wrong. We do not publish a response-time guarantee.