This page contains common problems people have with Krita. Note that we assume that you are using the latest version of Krita. Please verify that to make sure.
This is our vision for the development of Krita:
Krita is a free and open source cross-platform application that offers an end-to-end solution for creating digital art files from scratch. Krita is optimized for frequent, prolonged and focused use. Explicitly supported fields of painting are illustrations, concept art, matte painting, textures, comics and animations. Developed together with users, Krita is an application that supports their actual needs and workflow. Krita supports open standards and interoperates with other applications.
Krita should automatically use the system language. If that is not the case, please follow these steps:
. A small window will appear.
Click Primary language and select your language.
Click OK to close the window.
Restart krita and it will be displayed in your selected language!
If this doesn’t work, you might have to add a fall-back language as well. This is a bug, but we haven’t found the solution yet.
Krita has no clipping mask, but it has a clipping feature called inherit alpha. Let’s see this page and learn how to do clipping in Krita!
These are stored at the following places for the following operating systems:
- MacOS X
The kritarc file is the configuration file. Krita does not store settings in the Windows registry.
You can reset the Krita configuration in following way:
For Krita 3.0 and later: Delete/rename the kritarc file, found here:
- MacOS X
There can be two other files you might want to remove: kritaopenglrc and kritadisplayrc.
If the configuration was causing a crash, don’t delete the mentioned file, but instead rename and send it to us in order for us to figure what caused the crash.
If you have installed Krita through the Windows store, the kritarc file will be in another location
The random string depends on your installation.
Windows users have a habit of uninstalling and reinstalling applications to solve problems. Unless the problem is that the installation was corrupted by a virus scanner or drive failure, that will NOT work. Uninstalling Krita then reinstalling replaces the bytes on your drive with exactly the same bytes that were there before. It doesn’t reset anything, least of all Krita’s settings.
- Mac OS X
- If you installed Krita in the Windows Store, your custom resources will be in a location like:
Causes for this could be the following:
It might be that your download got corrupted and is missing files (common with bad wifi and bad internet connection in general), in that case, try to find a better internet connection before trying to download again. Krita should be around 80 to 100 MB in size when downloading.
It might be that something went wrong during installation. Check whether your harddrive is full and reinstall Krita with at least 120 MB of empty space. If not, and the problem still occurs, there might be something odd going on with your device and it’s recommended to find a computer expert to diagnose what is the problem.
Some unzippers don’t unpack our zipfiles correctly. The native ones on Windows, OSX and most Linux distributions should be just fine, and we recommend using them.
You manually, using a file manager deleted or moved resources around, and thus Krita cannot find them anymore.
Krita can use OpenGL to accelerate painting and canvas zooming, rotation and panning. Nvidia and recent Intel GPUs give the best results. Make sure your OpenGL drivers support OpenGL 3.2 as the minimum. AMD/ATI GPU’s are known to be troublesome, especially with the proprietary drivers on Linux. However, it works perfectly with the Radeon free driver on Linux for supported AMD GPU. Try to get a graphics card that can support OpenGL 3.2 or above for the best results, some examples:
Intel 3rd Generation HD Graphics, IvyBridge or Bay-Trail microarchitecture, released in 2012. Commonly available products: Celeron J1x00, N2x00, Celeron (G)1xx0, Pentium J2x00, N3500, Pentium (G)2xx0, Core i3/5/7-3xx0.
Radeon HD 2000 family, TeraScale 1 microarchitecture, Released in 2007. Commonly available products: Radeon HD 2400 PRO, Radeon HD 2600 PRO, etc.
GeForce 8 family, Tesla microarchitecture, released in 2006. Commonly available products: GeForce 8400 GS, GeForce 8800 GTS, 9800 GTX, GTS 250, etc.
For Krita 3.3 or later: Krita on Windows can use Direct3D 11 for graphics acceleration (through ANGLE). This is enabled automatically on systems with an Intel GPU.
There is no text support for psd file yet. The text will appear rasterized and converted into a paint layer.
For simple images, its easy to calculate: you multiply width * height * channels * size of the channels (so, for a 1000×1000 16 bit integer rgba image: 1000 x 1000 x 4 x 2). You multiply this by the number of layers plus two (one for the image, one for the display). If you add masks, filter layers or clone layers, it gets more complicated.
You’re probably used to Gimp or Photoshop. The default background or first layer in these applications doesn’t have an alpha channel by default. Thus, on their background layer, the eraser paints in the background color.
In Krita, all layers have an alpha channel, if you want to paint in the background color, you should simply do it in a layer above the first one (Layer 1), that would prevent you from erasing the white background color, making the checkerboard visible. You get the same effect in, say, gimp, if you create new image, add an alpha channel and then use the eraser tool. Most Krita users will actually start a sketch in Krita by adding a new blank layer first before doing anything else. (The Ins key is a useful shortcut here). That doesn’t use extra memory, since a blank layer or a layer with a default color just takes one pixel worth of memory.
No. Krita has been designed from the ground up to use real colors, not indexed palettes. There are no plans to support indexed color images, although Krita can export to some indexed color image formats, such as GIF. However, it does not offer detailed control over pixel values.
All the older versions of Krita that are still available can be found here:
If you’re using Windows, you can set the display scaling to 150% or 200%. Krita comes with HiDPI enabled by default, so if you do that, the Krita UI might be too big for your screen. You can turn it off using the following steps:
On the menu, select
On General page, switch to Window tab.
Uncheck Enable Hi-DPI support (or check if you wish to enable it)
Press OK, if the settings screen is too big, Alt + O will trigger the OK button too.
You can also change the toolbox icon size by right-clicking on the toolbox and selecting a size.
The possible workarounds for this is to do either of the following:
Turn off OpenGL in.
Or don’t use the hardware accelerated mode (game recording mode) in OBS, thus capturing the whole desktop instead of attempting to capture only Krita.
You might also be able to work around the problem by using the ANGLE renderer instead of native OpenGL.
No, this is not recommended. Sandboxie causes stuttering and freezes due to the way it intercepts calls for resources on disk.
If the message is “File not found. Check the file name and try again.”, you probably have Controlled Folder Access enabled.
Select Open Windows Defender Security Center.
Select Virus & threat protection, and then choose Virus & threat protection settings.
Under Controlled folder access, turn it on or off.
You can also whitelist Krita, following these instructions.
Your file got corrupted. There are several things that might cause this:
Windows was shutdown improperly, like by holding the power button. This prevents your harddrive from finishing up the things it is doing and file away your files incorrectly. Please always try to shutdown your computer via the proper shutdown procedure, and if you are in a situation where this is not possible (like frequent blackouts), make daily backups! This may lead to the file being filled with zeroes, so it cannot be recovered from.
Changed in version 4.2.8: Krita version 4.2.8 introduced special safety measure for Windows that should help avoiding this situation. But in any case, unless something makes it impossible, always make sure to shutdown your system using the standard approach. On Windows that means going to Start menu and selecting “Shutdown”.
Badly programmed security software may attempt to rewrite kra files, or prevent Krita from writing to the folder you wish to save to. These cases can be checked by trying to save in that location, and then, without shutting down Krita, checking in the folder to see if the file saved. Files lost due this cannot be recovered.
Cloud services like dropbox and onedrive have been known to prevent Krita from saving. We’ve implemented fixes for this, but much like the above point it is worth checking that this isn’t the cause of the issue. Files lost due this cannot be recovered.
Occasionally the zips that kra files comprise of will have the last few bytes missing. We’re doing everything in our power to prevent this kind of corruption, but it might be a file system issue. This particular bug can be fixed by renaming the extension (in windows you will need to enable the file extensions, which this FAQ will not cover) to zip, and then using a zip repairing utility to fix the zip file. Then rename it back to kra.
If Krita doesn’t give an error message, but rather crashes, your file is too big, and Krita is not so much crashing as that the operating system is shutting it down. Try shutting down some other programs like webbrowsers or streaming services to free up working memory. You should be able to open the file in question. At this point the recommended course of action is to try and reduce the file size in some manner, such as merging layers, splitting up an animation or scaling the image down.
Check whether you have any backup file or autosave left: Saving, AutoSave and Backup Files .
- Check whether you can open the file as zip archive.
Rename the extension of the file from .kra to .zip.
Try to open (your system should automatically select an archive opener tool).
There is file called mergedimage.png inside that represents all layers merged that you can use for reference in case you can’t restore anything else.
- Check whether zip repairer tool helps.
Copy the file so you have a backup just in case.
Rename the extension of the file from .kra to .zip.
Use zip repairer tool on the .zip file.
# On Linux: mv file.kra file_copy.zip zip -F file_copy.zip --out file_new1.zip unzip file_new1.zip # if it still doesn't work: zip -FF file_copy.zip --out file_new2.zip unzip file_new2.zip # if it still doesn't work, try to run it again on file_new2.zip file, or try on file_new1.zip file # On Windows: Copy the file, rename the extension. Use any graphical zip repairer on the new file. (Follow the instructions for that specific program).
Try to open in Krita.
If it cannot be opened in Krita, try the trick from 2.: open the archive and find mergedimage.png file.
Open your file in Notepad or any other text editor. If the the content of the file is only a repeated NUL symbol, it means the file is most probably unrecoverable using the standard method. If it’s of a very high importance for you, you can try to recover the previous save using methods that checks the hard drive directly.
Starting with Krita 4.2.0, Krita uses version 5.12 of the Qt toolkit. This needs to have access to Direct3D 11 or OpenGL ES 2.0 or higher. You might need to install drivers appropriate to your GPU (Nvidia, AMD/ATI, Intel). This also makes it hard to run Krita in a virtual environment: in Virtual Box you need to install the guest addition in safe mode, and enable the experimental Direct3D support.
If you experience a crash on Windows, and can reproduce the crash, the bug report will be much more valuable if you can create a backtrace. A backtrace is somewhat akin to an airplane’s blackbox, in that they tell what set of instructions your computer was running when it was crashing (where the crash happened), making it very useful to figure out why the crash happened.
Chances are you are using an NVidia GPU. Due to a bug in Nvidia’s driver that we haven’t been able to workaround yet, sometimes Krita’s window will be transparent or semi-transparent. The solution is to enable the Angle renderer in Krita’s Settings dialog. Open the Configure Krita dialog. In the dialog window select the Display page and select the Angle renderer in the Preferred Renderer combobox. Restart Krita.menu (Press Alt-N if the menubar is not visible and your system is in English), then open the
Krita isn’t much fun without a pressure sensitive tablet. If the tablet has been properly configured, Krita should work out of the box.
On Windows, you need to either install the Wintab drivers for your tablet, or enable the Windows 8+ Pointer Input option in Krita’s settings.
You can find a community curated list of tablets supported by krita here.
If you’re looking for information about tablets like the iPad or Android tablets, look here.
First, check if you have installed drivers and the like. The Drawing Tablets page has some explanations and descriptions of common issues. If none of those work, we would like to have a bug report at bugs.kde.org, with a tablet log. Here’s how you make a tablet log:
You need to have something to output the log to. On 4.2 you can use the Log Viewer docker for this. Just open the log viewer, and enable logging.
Changed in version 4.2: The log viewer got added to Krita in 4.2, so for older versions of Krita, you will need to either run Krita in the terminal if you have Linux or MacOS, or for Windows install DebugView from the official Microsoft site, start DebugView and then start Krita.
When using a terminal, make sure to enable ‘unlimited scrollback’
Press the Ctrl + Shift + T shortcut, you will see a message box telling the logging has started.
Try to reproduce your problem, you will be able to see the log being created in the log viewer as you draw.
Save the output from the log viewer into a txt file, and attach it to the bugreport.
On Linux, it is also useful to have the following information:
xinput list-props(id can be fetched from the item 2)
However, in 100% of the cases where Windows users have reported that their tablet didn’t work over the past five years, the problem has been either a buggy driver or a broken driver installation, but not a bug in Krita.
If you see that your tablet pointer has an offset when working with Krita canvas, it might be highly likely that Krita got an incorrect screen resolution from the system. That problem happens mostly when an external monitor is present and when either a monitor or a tablet was connected after the system booted.
You can configure this by going to the Tablet Settings.
Krita 3.3.0 and later supports the Windows Pointer API (Windows Ink) natively. Your Surface Pro or other N-Trig enabled pen tablet should work out of the box with Krita after you enable Windows Ink in.
Unlike Wacom’s Companion, the Surface line of tablets doesn’t have working hardware buttons. Tablet Pro is a (non-free) utility that puts virtual buttons on screen. Krita 3.1 and above will have predefined shortcut profiles to work with Tablet Pro.
See https://www.youtube.com/watch?v=WKXZgYqC3tI for instructions.
Windows comes with a lot of settings to make it work with a pen. All these settings can be annoying. This tool can help you set the settings correctly when you’re using a tablet:
You might have to disable and enable the touch driver: go to the device manager. (Click the Start button and type device manager). Choose HID (User interface devices or something like that). Choose Intel(R) Precise Touch Device. Right click, Disable it. Right click, Enable it.
You can reset the Workspace by pressing the right most button on the toolbar, the Workspace switcher, and click on a desired Workspace from the list.
Or you can right-click on any docker title bar or open space in any toolbar, and select Toolbox. It’s the first option.
Also, you can check the Settings menu, it has got a lot of interesting stuff, then go to the Dockers menu and select Toolbox.
Is there a way to restore a default brush that I have mistakenly overwritten with new settings to default?¶
Yes. First go to the resource folder, which is in
You can easily do this by going into.
Then go into the paintoppresets folder and remove the latest created file that you made of your preset.
After that go back to the resources folder and edit the blacklist file to remove the previous paintoppreset so Krita will load it. (Yes, it is a bit of a convoluted system, but at the least you don’t lose your brushes)
Right-click a brush in the brush docker and assign it a tag. Then right-click on canvas to call popup palette, click the second right-most icon on the bottom-right of the palette, now you can pick the tag which contains the brush you assigned to it.
Yes, but there are limitations. You can load ABR files by using the Import button in the Predefined brush tab in the brush editor. Since Adobe hasn’t disclosed the file format specification, we depend on reverse-engineering to figure out what to load, and currently that’s limited to basic features.
There is a myriad of reasons why this might be. Below is a short checklist.
Something else is hogging the CPU or the memory: spotify and other electron apps have been known to do this.
You are running Windows, and have 3rdparty security software like Sandboxie or Total Defender installed
You are working on images that are too big for your hardware (dimensions, channel depth or number of layers)
You do not have canvas acceleration enabled
You have (NVidia) Vertical Sync enabled
Please also check this page
You probably have too many resources installed. Deactivate some bundles under.
If you’re using Windows with the portable zip file, Windows will scan all files every time you start Krita. That takes ages. Either use the installer or tell Microsoft Security Essentials to make an exception for Krita.
Check if you accidentally turned on the stabilizer in the tool options docker.
Try another scaling mode like trilinear..
Try a lower channel depth than 16-bit.
For NVidia, try a 16-bit floating point color space.
For older AMD CPU’s (Krita 2.9.10 and above), turn off the vector optimizations that are broken on AMD CPUs.. This isn’t needed if you’ve got an AMD Threadripper™ CPU.
It’s a fairly memory hungry program, so 2GB of RAM is the minimum, and 4GB is the preferable minimum.
Check that nothing else is hogging your CPU
Check that Instant Preview is enabled if you’re using bigger brushes (but for very small brushes, make sure is disabled).
Set brush precision to 3 or auto.
Use a larger value for brush spacing.
If all of this fails, record a video and post a link and description on the Krita forum.
Check whether OpenGL is enabled, and if it isn’t, enable it. If it is enabled, and you are on Windows, try the Angle renderer. Or disable it.
Once you have the slowdown, click on the image-dimensions in the status bar. It will tell you how much RAM Krita is using, if it has hit the limit, or whether it has started swapping. Swapping can slow down a program a lot, so either work on smaller images or turn up the maximum amount of RAM in.
The transform tool makes a preview that you edit before computing the finalized version. As this preview is using the screen resolution rather than the image resolution, it may feel that the result is blurry compared to the preview. See this page for more info.
The Stichting Krita Foundation owns the Krita trademark. The copyright on the source code is owned by everyone who has worked on the source code.
Kiki is a cybersquirrel. She’s our mascot and has been designed by Tyson Tan. We choose a squirrel when we discovered that ‘krita’ is the Albanian word for Squirrel.
Krita is developed as free software within the KDE community. We believe that good tools should be available for all artists. You can also buy Krita on the Windows Store if you want to support Krita’s development or want to have automatic updates to newer versions.
Krita on Steam and in the Windows Store is still Free and Open Source software; the binaries are exactly the ones you can also download from krita.org. We’ve put a price tag on downloading Krita from either store to support Krita’s development. Nobody is getting rich out of it, but the income from Steam and the Windows Store currently pays for the full-time involvement with Krita of four developers. See Krita Available from the Windows Store for more information.
Yes. What you create with Krita is your sole property. You own your work and can license your art however you want. Krita’s GPL license applies to Krita’s source code. Krita can be used commercially by artists for any purpose, by studios to make concept art, textures, or vfx, by game artists to work on commercial games, by scientists for research, and by students in educational institutions.
If you modify Krita itself, and distribute the result, you have to share your modifications with us. Krita’s GNU GPL license guarantees you this freedom. Nobody is ever permitted to take it away.
Not for iOS or iPadOS at this point in time. Android is being worked on, but it will not have a phone or tablet, but the same desktop ui as always.
Krita is a KDE application — and proud of it! That means that Krita’s translations are done by KDE localization teams. If you want to help out, join the team for your language! There is another way you can help out making Krita look good in any language, and that is join the development team and fix issues within the code that make Krita harder to translate.