Krita

Why clean Krita?

• Stale thumbnail and preview cache entries can make recent files show outdated artwork or wrong layer states in Krita's open dialogs until the previews are rebuilt
• Old rendered tile data from previous sessions can cause mismatched canvas regions, delayed redraws, or visual remnants that disappear only after zooming or forcing a refresh
• OpenGL or canvas acceleration cache left over after a graphics driver update can invalidate renderer state and show up as flickering, black canvas areas, or sluggish pan and zoom
• A bloated cache directory from large multilayer projects consumes gigabytes of disk space, which users usually notice as Krita growing in size even when project files were moved or deleted
• Corrupted temporary image cache files can make startup or project switching slower because Krita repeatedly tries to read bad cached data before regenerating it
• Outdated cached previews for brushes, bundles, or patterns can make resource browsers display the wrong icon or delayed updates even though the actual resource files are unchanged
• If Krita stores cache metadata in SQLite, page fragmentation can waste space and slow lookups; VACUUM rewrites the database into a compact file without deleting your actual documents or resources

Common questions about Krita

Download Kudu and reclaim your disk space.

Available on Windows, macOS, and Linux. No account required, no feature gates, no telemetry without consent. All cleaning targets are open source and community-auditable.