Where Does SANE Store Scanner Config?
SANE keeps per backend .conf files in /etc/sane.d, enabled through dll.conf in the same folder.
Last updated
SANE configures scanners through text files in /etc/sane.d. Each backend owns one .conf file with device URIs and options. The dll.conf file in the same folder decides which backends load at all.
USB scanners usually need no edits beyond the right backend enabled. Network scanners need their host added to the backend file. Frontend apps like Simple Scan read these same files, so terminal and GUI agree.
Where SANE stores this, by platform
/etc/sane.d
Backend .conf files plus dll.conf controlling which load. Add network scanner hosts to the matching backend file. Test with scanimage -L after edits.
Frequently asked questions
My scanner is not detected. Which file do I check?
Confirm its backend is uncommented in dll.conf, then check the backend .conf for the device URI. Run scanimage -L as your user to see what SANE finds. Permissions on USB nodes cause most misses.
How do I add a network scanner?
Put its IP or hostname in the backend .conf file for your model family. Some backends want a full URI instead. Rescan with your frontend after saving.
Notice an outdated path? Let us know.