Drop any file to identify it
No upload. No signup. No sending your file halfway across the internet.
We tell you what it is, right here in your browser.
Drop it!
Let go to identify this file.
Couldn't identify this file
Need to convert it? fwip it →
The .conf extension is the Unix world's equivalent of .cfg — a plain text configuration file with no single standard format. Apache uses .conf files. Nginx uses .conf files. systemd uses .conf files. They all use different syntaxes, because Unix respects your freedom to be confused.
Apache config uses a pseudo-HTML tag syntax. Nginx uses a C-like block syntax. systemd uses INI-style sections. sshd_config uses space-separated key-value pairs. The .conf extension tells you nothing about the format — you need to know which application created it.
All .conf files are plain text, editable in any text editor. On Linux servers, configuration files typically live in /etc/ and its subdirectories. Editing them usually requires root/sudo access. The golden rule: always make a backup before editing a conf file, and test the configuration before restarting the service (`nginx -t`, `apachectl configtest`, `sshd -t`).