Where Does Cloudflare WARP Store Config and Logs?
Where the Cloudflare WARP client keeps mdm.xml config and logs. Not Warp terminal.
Last updated
The Cloudflare WARP client (Cloudflare One agent) splits data three ways on Windows: binaries under Program Files, service logs and mdm.xml under ProgramData\Cloudflare, and GUI logs under the user LocalAppData. MDM deployment means dropping in mdm.xml.
macOS mirrors the pattern with mdm.xml under /Library/Application Support/Cloudflare. Consumer users rarely touch these files. The paths matter most for fleet admins and for support tickets asking for daemon logs.
Where Cloudflare WARP stores this, by platform
C:\ProgramData\Cloudflare\
Holds warp service logs plus mdm.xml for MDM pushed settings. Binaries live under Program Files\Cloudflare\Cloudflare WARP. GUI logs sit separately under LocalAppData\Cloudflare. This is the VPN client, unrelated to the Warp terminal app.
/Library/Application Support/Cloudflare/
Drop mdm.xml here for scripted macOS deploys as an alternative to plist or mobileconfig profiles. Format matches the Windows mdm.xml documented in the Cloudflare One MDM guides.
Frequently asked questions
Is this the same as the Warp terminal?
They share nothing but a syllable. Warp terminal is a Rust terminal emulator with its own data folder, while Cloudflare WARP is the Zero Trust VPN client documented here. Check the install path before following any guide.
How do admins predeploy WARP settings on Windows?
Place or replace mdm.xml at the ProgramData path with organization and onboarding keys. The client picks it up without reinstalling, which is how Intune and other MDM tools push fleet settings.
Notice an outdated path? Let us know.