Where Does NAPS2 Store Profiles and Scans?
NAPS2 keeps scan profiles in profiles.xml and settings in config.xml under the Roaming app data folder on Windows or ~/.config on Mac and Linux.
Last updated
NAPS2 stores scanning profiles as plain XML you can copy. The user-level profiles.xml plus config.xml sit in the Roaming app data folder on installed Windows builds. Device choice, paper size, resolution, and save defaults all live there in readable form.
Portable builds flip the layout: the same two files sit in a Data folder beside the executable so the stick carries its profiles. Mac and Linux builds use the standard config home instead. Finished scans go wherever each profile points, usually Documents or a chosen folder, far from the settings themselves.
Where NAPS2 stores this, by platform
%appdata%\NAPS2\profiles.xml
Copy profiles.xml and config.xml to migrate. Installed builds use Roaming; portable builds use the Data folder next to the EXE. Scanned PDFs land in each profile output folder.
~/.config/naps2/profiles.xml
Same XML pair as Windows under the config home. Reach it in Finder with Go > Go to Folder, since .config is hidden.
~/.config/naps2/profiles.xml
Same layout as macOS. Profiles and app settings migrate by copying the two XML files to the same path on the new machine.
Frequently asked questions
How do I move NAPS2 profiles to a new PC?
Copy profiles.xml and config.xml from the old machine to the same folder on the new one. Portable builds keep them in the Data folder next to the EXE instead. Restart NAPS2 after copying so it picks up the moved profiles.
Can I deploy default profiles to many PCs?
Yes via the organization files in the install directory. Place a profiles.xml with defaults next to the program files and new users inherit those profiles. Once a user edits any profile, the shipped defaults stop applying to them unless locking is configured.
Notice an outdated path? Let us know.