Where Does Dialpad Store Local Data?
Dialpad user data and app binaries split across Roaming and Local AppData, per official deployment docs.
Last updated
Dialpad documents its own data split unusually well. User data such as config.json, auth sessions, logs and cookies lives in a Dialpad folder under Roaming AppData. Application binaries, the updater and Electron cache live in a separate Dialpad folder under Local AppData.
That split tells you what to touch. Troubleshooting sign in or corruption means clearing the Roaming side with the app fully quit. The Local side is just program files that reinstall cleanly, so deleting it only forces a re download on next launch.
Where Dialpad stores this, by platform
%APPDATA%\Dialpad
Holds config.json, auth session data, logs and cookies. Quit Dialpad fully before deleting anything here. The Local AppData namesake at %LOCALAPPDATA%\Dialpad holds binaries and Electron cache instead, safe to leave alone.
Frequently asked questions
how do i back up dialpad settings
Back up %APPDATA%\Dialpad with Dialpad signed out and closed. That folder holds config.json, auth session data and settings. The Local AppData copy holds reinstallable binaries, so it needs no backup.
does dialpad slow down windows roaming profiles
Yes. Dialpad documents excluding the Cache and Logs subfolders under %APPDATA%\Dialpad from roaming capture to keep logins fast. The main config still roams, so settings follow you while bulkier cache stays local.
Notice an outdated path? Let us know.