Where Does SANE Store Scanner Config?
SANE backend configs live in /etc/sane.d per driver, with per-user settings in home config. Scans save in the frontend folder.
Last updated
SANE splits scanning into backends and frontends. Backend drivers configure per model in the system sane.d directory, with network discovery and option defaults in named conf files. Frontends then expose whatever the backends offer.
Per-user tweaks live in the home config tree and override system defaults. Scanned output never lands near the configs; each frontend points at its own folder. When a scanner vanishes after an update, check backend package names first, since renames orphan old conf files.
Where SANE Scanners stores this, by platform
/etc/sane.d/
Per-driver backend files plus network discovery config. Needs root to edit; user overrides in home config. Frontends save scans to their own output folders.
Frequently asked questions
How do I add a network scanner?
Edit the matching backend file under /etc/sane.d, such as the network backend for shared scanners. Restart the frontend after changes. USB scanners usually need no config beyond permissions for the scanner group.
Scanner found but permission denied. Why?
Add your user to the scanner or lp group, then log out and back in. Permission errors that survive correct backend files are group membership issues nine times out of ten. Frontends like NAPS2 read the same backends underneath.
Notice an outdated path? Let us know.