Introduction to User Support

Tablet Support

The majority of help requests are about pen pressure and tablet support in general.

Quick solutions

  1. On Windows: reinstall your driver (Windows Update often breaks tablet driver settings, reinstallation helps).

  2. Change API in Settings ‣ Configure Krita ‣ Tablet Settings (for some devices, especially N-trig ones, Windows Ink work better, for some it’s Wintab).

  3. On Windows, Wacom tablets: if you get straight lines at the beginnings of the strokes, disable/minimize “double-click distance” in Wacom settings.

Gathering information

  1. Which OS do you use?

  2. Which tablet do you have?

  3. What is the version of the tablet driver?

  4. Please collect Tablet Tester (Settings ‣ Configure Krita ‣ Tablet Settings) output, paste it to Pastebin or similar website and give us a link.

Additional information for supporters

  1. Except for the issue with beginnings of the strokes, Wacom tablets usually work no matter the OS.

  2. Huion tablets should work on Windows and on Linux, on Mac there might be issues.

  3. XP-Pen tablets and other brands can have issues everywhere.

  4. If someone asks about a tablet to buy, generally a cheaper Wacom or a Huion are the best options as of 2019, if they want to work with Krita. The List of Supported Tablets

  5. Possibly useful instruction in case of XP-Pen tablet issues.


Issues with rendering animation can be of various shapes and colors. First thing to find out is whether the issue happens on Krita’s or FFmpeg’s side (Krita saves all the frames, then FFmpeg is used to render a video using this sequence of images). To learn that, instruct the user to render as “Image Sequence”. If the image sequence is correct, FFmpeg (or more often: render options) are at fault. If the image sequence is incorrect, either the options are wrong (if for example not every frame got rendered), or it’s a bug in Krita.


If the user opens the Log Viewer docker, turns on logging and then tries to render a video, Krita will print out the whole ffmpeg command to Log Viewer so it can be easily investigated.

There is a log file in the directory that user tries to render to. It can contain information useful to investigation of the issue.

Onion skin issues

The great majority of issues with onion skin are just user errors, not bugs. Nonetheless, you need to find out why it happens and direct the user how to use onion skin properly.


In case of crash try to determine if the problem is known, if not, instruct user to create a bug report (or create it yourself) with following information:

  1. What happened, what was being done just before the crash.

  2. Is it possible to reproduce (repeat)? If yes, provide a step-by-step instruction to get the crash.

  3. Backtrace (crashlog) – the instruction is here: Dr. MinW Debugger, and the debug symbols can be found in the annoucement of the version of Krita that the user has. But it could be easier to just point the user to

Other possible questions with quick solutions

  1. When the user has trouble with anything related to preview or display, ask them to change Canvas Graphics Acceleration in Settings ‣ Configure Krita ‣ Display.

  2. When the user has any weird issue, something you’ve never heard about, ask them to reset the configuration: Resetting Krita configuration.

Advices for supporters

  1. If you don’t understand the question, ask for clarification – asking for a screen recording or a screenshot is perfectly fine.

  2. If you don’t know the solution but you know what information will be needed to investigate the issue further, don’t hesitate to ask. Other supporters may know the answer, but have too little time to move the user through the whole process, so you’re helping a lot just by asking for additional information. This is very much true in case of tablet issues, for example.

  3. If you don’t know the answer/solution and the question looks abandoned by other supporters, you can always ask for help on Krita IRC channel. It’s #krita on The Krita Community.

  4. Explain steps the user needs to make clearly, for example if you need them to change something in settings, clearly state the whole path of buttons and tabs to get there.

  5. Instead of Settings ‣ Configure Krita use just Configure Krita – it’s easy enough to find and Mac users (where you need to select Krita ‣ Settings) won’t get confused.

  6. If you ask for an image, mention usage of Imgur or Pasteboard, otherwise Reddit users might create a new post with this image instead of including it to the old conversation.

  7. If you want to quickly answer someone, just link to the appropriate place in this manual page – you can click on the little link icon next to the section or subsection title and give the link to the user so they for example know what information about their tablet issue you need.

  8. If the user access the internet from the country or a workplace with some of the websites blocked (like or, here is a list of alternatives that works:


If you ask user to store their log or other data on a website, make sure it stays there long enough for you to get it – for example stores files by default only for a day! And you can extend it only to one week.

Make sure they don’t post their personal data. Tablet Tester log is safe, log from the Help -> Show system information for bug reports might not be that safe. Maybe you could ask them to send it to you by mail?