How to uninstall Canva on Windows

Save your designs and close Canva first. This guide covers Canva 1.126.0 installed per-user through winget. No account was used and no real design was created in this run.

Remove the app

Find Canva in Settings › Apps › Installed apps, or use this PowerShell command to invoke its own uninstaller.

winget uninstall --id Canva.Canva --exact

Startup and processes

The CanvaAutoLaunchAvailabilityCheckAgent user Run entry appeared as Canva. Its switch was turned off and restored, and the entry disappeared after uninstalling. Seven Canva processes were merged into one row rather than treated as separate installations.

Check the result

winget list --id Canva.Canva --exact
Test-Path "$env:LOCALAPPDATA\Programs\Canva"
Test-Path "$env:LOCALAPPDATA\Canva-updater"
Test-Path "$env:APPDATA\Canva"

A successful winget query with no match means the package registration is absent; a query error leaves it unknown. False from Test-Path only confirms that path is absent. Local data retention depends on your selections.

What Mole lists

The program folder %LOCALAPPDATA%\Programs\Canva, its own %LOCALAPPDATA%\Canva-updater, shortcuts, startup entry and handlers pointing to its program are selected by default. %APPDATA%\Canva is listed but not selected by default; measured disk caches and logs inside it have separate selected rows. Leave “Also remove data” off to retain local state.

All bulk-selectable items in the 31-row review were selected. The program and updater were recycled; other targets were already removed by the vendor or absent. Every outcome was Removed or Missing. The parent extension registrations .key and .pages remained; snapshot differences did not widen the removal scope.

What this test covered

Tested on October 4, 2026, in a Windows 11 ARM64 VM with a Mole development build. The selected program and data were removed. Real designs, sign-in, sync, subscriptions, other installation channels and the released package were not verified.

After a separate winget uninstall, a Mole development build listed no app-owned leftovers immediately. More than ten minutes later it listed the empty program folder, updater and usage records; the first two were not selected by default. This checked detection only, without removing those leftovers.