Krita Problems & Issues
Real user-reported problems, complaints, and limitations for Krita. Based on analysis of 12 signals.
Overall score: 76/100
Issues by Category
Krita pen pressure not working
The most repeated complaint in Krita's bug tracker and forum: the pen draws but pressure is ignored. Most threads trace it to the tablet API (WinTab vs Windows Ink), a broken driver after a Windows update, or vendor settings, and many end without a single confirmed cause.
Krita text tool is hard to use
Reviewers repeatedly call the text tool a weak point, with editing in a popup rather than on the canvas. The developers rebuilt text in 5.2 and 5.3 with text on a path and in shapes, so older complaints may be outdated, though PSD text export is still limited.
Krita is not for photo editing or retouching
Reviews describe Krita as strong for painting but weak for photo retouching compared with Photoshop or GIMP. Learning curve and slow startup also come up.
Why is Krita lagging when I paint?
Users report a delay between pen and stroke, especially at stroke start, with large brush tips, textures or random rotation. Krita's own FAQ lists the stabilizer, scaling mode, bit depth, brush precision and renderer as the usual suspects.
Krita gets slower after a long session or with many layers
The FAQ describes slowdown after long sessions and points to RAM use shown in the status bar and the RAM limit in Performance settings. Forum replies also advise keeping layer count low.
Krita 6.0 (Qt6) is early access
Krita 5.3 and 6.0 shipped together in March 2026. The 6.0 Qt6 build launched with critical issues on Windows and Wayland, and guidance has been to stay on 5.3 for production work.
Krita crashes when opening or saving large files
Bug reports describe crashes on save, on duplicating files and on very large canvases, sometimes with a corrupt .kra afterwards. The FAQ says the OS may kill Krita for memory on big files.
Krita screen flickering or canvas glitches
Flicker, black areas and tearing show up on some GPU and driver combinations, mainly with the Direct3D/ANGLE renderer on Windows and with NVIDIA on Wayland. Switching renderer or disabling canvas acceleration is the usual workaround.
Krita settings reset or won't save
The FAQ documents configuration resetting unexpectedly: the OK button can be hidden on scaled Windows displays, and a power-button shutdown can corrupt the config file.
Krita can't render animation: FFmpeg not found
Animation export depends on FFmpeg. Bug reports cover a wrong or empty path, AppImage and Flatpak path quirks and GIF export errors. FFmpeg is not available on Android.
Krita on Android and tablets is limited
The Android version exists but lacks FFmpeg for animation and timelapse export, and it is not the full desktop experience. Users wanting an iPad-style app are usually pointed to other tools.
Krita support is community-only
Help comes from krita-artists.org, the KDE bug tracker and the docs. Developers note tablet problems are rarely Krita bugs, so users with driver issues can be left troubleshooting alone.
Regret Patterns
Common reasons users regret choosing Krita.
Tablet never feels right
Users spend hours switching tablet APIs and drivers before pressure works.
Heavy brushes lag
Favorite textured brushes or big tips cause stroke lag.
Lost work to a crash
A crash or failed save forces an autosave recovery, and sometimes a corrupt file.
Text and PSD handoff fails
Text layers do not round trip to PSD cleanly for clients using Photoshop.
Expecting a photo editor
Users coming from Photoshop expect retouching tools Krita does not focus on.
When Krita Breaks Down
Specific scenarios where Krita fails or underperforms.
Very large canvases
Large files can exhaust RAM, slow Krita or make the OS close it.
Windows update with a tablet driver
Driver breaks after an update and pen pressure stops.
Complex textured brushes
Large tips, texture and rotation cause stroke-start lag.
Exporting animation to video
FFmpeg path or version problems stop render.
NVIDIA on Wayland or ANGLE on Windows
Flicker and canvas glitches depending on renderer.