Where Does Piper Store Mouse Profiles?
Piper keeps gaming mouse profiles, button maps and LED settings through ratbagd on Linux. Config path and backup routine.
Last updated
Piper edits rodent profiles that ratbagd writes to capable hardware. Button assignments, DPI stages and lighting live in a small config tree. Onboard mice keep the applied copy in flash.
That staging design makes moves one copy with the app quit. Reapply profiles after restore so the device matches the file. Mice without memory need Piper running to hold settings.
Where Piper stores this, by platform
~/.config/piper
Button maps, DPI stages and LED settings as staging config. Back up with Piper quit. Reapply to the device after restore; onboard mice keep the applied copy in flash.
Frequently asked questions
How do I back up Piper profiles?
Copy the piper config with Piper quit, then reapply profiles to the mouse. Button maps, DPI stages and LED choices travel with the file. Hardware pairing may ask for a rescan on the new machine, which leaves profiles intact.
Do profiles live on the mouse?
On the mouse flash itself, written through ratbagd when profiles apply. Piper edits a staging copy in config first. Devices without onboard memory lose settings at unplug, which is a hardware limit rather than missing files.
Notice an outdated path? Let us know.