Why Does Krita Keep Crashing? 6 Causes and How to Fix Each

A painting program that quits without warning is worse than one that never opens, because it takes work with it. Krita is stable for most people, but when it does misbehave, the cause is almost always in the layer between Krita and your hardware: drivers, display settings, or a configuration file that has gone sideways. This troubleshooting guide walks through the causes in the order they are most likely, with the fix for each, and finishes with how to recover unsaved work.

Plugins are one possible culprit, but they are also how most people get the extra brushes, reference tools, and workflow shortcuts that make Krita worth using. If a stable setup is your goal, stick to well-maintained extensions. Our rundown of dependable Krita plugins for digital painting flags which ones are actively updated for current releases.

Why Does Krita Keep Crashing? The Main Causes

Before changing anything, note what you were doing when Krita closed. The timing points to the cause.

Cause 1: Graphics Driver Problems

Krita draws its canvas through the GPU. A driver that is out of date, half-updated, or generic (the default Windows one) can crash Krita the moment it tries to render a canvas.

Fix

1. Identify your GPU. On Windows, open Task Manager, pick the Performance tab, and look at the GPU entry. On macOS, use About This Mac. On Linux, run lspci | grep VGA in a terminal.
2. Download the current driver directly from NVIDIA, AMD, or Intel, not from Windows Update, which often ships older versions.
3. Choose a clean install if the installer offers it, which removes leftover files from the previous driver.
4. Restart, then open Krita and go to Settings > Configure Krita > Display. Check that the renderer is set to a hardware option and that the preferred renderer actually reports your GPU.

Laptops with two graphics chips, typically an Intel integrated GPU and an NVIDIA or AMD discrete one, add a twist. Krita may be running on the weaker chip. In the NVIDIA Control Panel or AMD software, add Krita and force it to the high-performance GPU. Some crashes stop simply because the program is no longer bouncing between two drivers.

Cause 2: Canvas Renderer Conflicts

Krita can draw the canvas with OpenGL, with Direct3D through a translation layer called ANGLE (Windows only), or with plain software rendering. Each path depends on different driver code, and one of them often works where another fails.

Fix

1. Open Settings > Configure Krita > Display.
2. Under Canvas Graphics Acceleration, change the Preferred Renderer. On Windows, try Direct3D 11 via ANGLE first if OpenGL is crashing, or the reverse.
3. Restart Krita. The renderer change does not apply until you do.
4. If both hardware options crash, uncheck Canvas Graphics Acceleration entirely to fall back to software rendering. Painting will feel less smooth on large canvases, but it isolates whether the GPU is the problem.

If Krita will not stay open long enough to reach Settings, you can edit the renderer setting directly in the configuration file. In the kritarc file (location below), find or add the line OpenGLRenderer=angle or OpenGLRenderer=none under the [General] section and save it before launching.

Cause 3: Corrupted Configuration or Resources

Krita stores its preferences in a file called kritarc and its brushes, bundles, and other assets in a resource folder. A crash during a save, a broken bundle download, or a sync service like OneDrive touching the folder can corrupt either. The symptom is Krita crashing on launch or when opening the brush preset docker.

Where the files live

• Windows: %APPDATA%\krita\ for resources and %LOCALAPPDATA%\kritarc for the config file.
• macOS: ~/Library/Application Support/krita/ and ~/Library/Preferences/kritarc.
• Linux: ~/.local/share/krita/ and ~/.config/kritarc.

Fix

1. Close Krita completely. Check Task Manager or Activity Monitor for a lingering krita process.
2. Rename kritarc to kritarc.old. Do not delete it; you may want to copy settings back later.
3. Launch Krita. If it opens normally, the config was the problem. Reapply your preferences manually.
4. If it still crashes, rename the whole resource folder (for example krita to krita_old) and launch again. A fresh folder is created with default brushes.
5. Once Krita is stable, move your custom brushes and bundles back into the new resource folder a few at a time. If a crash returns after a specific bundle, that file is corrupt.

If you keep your resource folder inside a cloud-synced directory, move it out. Sync clients can lock files while Krita is writing to them, which is a reliable way to corrupt the resource database.

Cause 4: Running Out of Memory

A 4000 by 6000 pixel canvas at 16-bit color with twenty layers and a long undo history can consume many gigabytes. When Krita hits the memory ceiling it has been given, or the system runs out of physical RAM and swap, it can freeze and then close.

Why is my Krita lagging before it crashes?

Lag is the warning sign. When each stroke takes a moment to appear, or the layer thumbnails stop updating, Krita is swapping data to disk. If you see this, save immediately and then adjust the settings below rather than pushing on.

Fix

1. Go to Settings > Configure Krita > Performance.
2. Set the Memory Limit to around 70 to 80 percent of your installed RAM. Leaving the default can starve Krita on machines with lots of memory, while setting it too high starves the operating system.
3. Lower Undo Stack Size from the default to 20 or 30 if you work on very large files. Each undo step stores a copy of the changed area.
4. Point the Swap File Location to your fastest drive, ideally an SSD with plenty of free space.
5. Work at 8-bit color depth unless you specifically need 16-bit for printing or heavy gradient work. Sixteen-bit doubles memory use per layer.
6. Merge finished layers or group and collapse them. Flattened reference layers cost far less than a dozen live ones.

On a machine with 8 GB of RAM, a practical ceiling for comfortable work is roughly a 3000 by 4000 pixel canvas at 8-bit with a modest layer count. Beyond that, expect lag and occasional crashes regardless of settings.

Cause 5: Tablet Driver Conflicts

Crashes that happen only when the pen touches the screen point to the tablet. Windows has two input paths, WinTab (the classic Wacom-style API) and Windows Ink, and Krita can use either. Some tablet drivers behave badly on one of them.

Fix

1. Update the tablet driver from the manufacturer’s site, uninstalling the old one first. Leftover drivers from a previous tablet brand are a known source of conflicts; remove any you no longer use.
2. In Krita, open Settings > Configure Krita > Tablet Settings and switch between WinTab and Windows 8+ Pointer Input (Windows Ink). Restart Krita after changing it.
3. Disable Windows Ink features like Press and Hold in the Pen and Windows Ink settings, which can intercept input and freeze the canvas.
4. Unplug the tablet and paint with a mouse for a few minutes. If Krita stays open, the tablet driver is confirmed as the trigger.

Cause 6: Plugins and Scripts

Krita’s Python plugins run inside the main process. A plugin written for an older Krita version, or one with a bug, can take the whole program down, often at startup or when you open the docker that belongs to it.

Fix

1. Open Settings > Configure Krita > Python Plugin Manager.
2. Uncheck every plugin you installed yourself, leaving the ones that shipped with Krita.
3. Restart. If the crashes stop, re-enable plugins one at a time, restarting after each, until the culprit appears.
4. Check whether the plugin has an update for your Krita version. If it has not been touched in a year or more, look for a maintained alternative.

If Krita will not open at all, you can disable plugins without the interface by deleting or moving the plugin’s folder out of pykrita inside the resource folder. For installation and removal steps, see our walkthrough on how to install plugins in Krita, which covers the folder structure.

Why Is Krita Not Opening at All?

If the program never shows a window, work through this short list in order.

• Check for a hidden process. A previous instance may still be running. End it in Task Manager or Activity Monitor and try again.
• Rename kritarc. A bad window geometry or renderer setting can stop the window from drawing.
• Launch from a terminal or command prompt. Error messages print there. On Windows, run krita.exe from its install folder in Command Prompt; on macOS and Linux, run krita from a terminal.
• Try the portable or AppImage version. A self-contained build sidesteps installation problems and shared library conflicts.
• Check antivirus quarantine. Some security software flags Krita’s Python components. Add an exception.

Why Is Krita Not Responding?

A frozen window is different from a crash. Krita may be busy rather than broken. Filters on large layers, opening a heavy file, or saving a multi-gigabyte document can lock the interface for a minute or more. Wait at least two minutes before force-closing, especially during a save, because killing Krita mid-write corrupts the file.

If freezes are frequent and short, the usual causes are the undo stack filling up, a swap file on a slow hard drive, or an animation timeline with the cache set too high. Each has a setting under Performance. If the freeze always happens with one brush, that brush may use a texture or pattern that is too large; try a smaller version of the texture file.

Why Is My Krita Not Working After an Update?

Updates occasionally change the resource database format or how plugins are loaded. If Krita worked yesterday and crashes today, after an update, do the following.

1. Rename the resource folder so Krita rebuilds its database with the new format, then copy your brushes back in.
2. Check each third-party plugin against the new version. Plugin authors sometimes need weeks to catch up to a major release.
3. If the new version is unusable, install the previous release alongside it. Krita versions can coexist, and the portable build makes this painless.

Reading the Crash Log

Guesswork goes faster with evidence. Krita writes a log you can read from inside the program.

• Open Help > Show Krita Log for Bug Reports. The window lists recent sessions, including the one that crashed.
• Look near the end of the previous session for lines mentioning OpenGL, a plugin name, a file path, or “out of memory.”
• Help > Show System Information for Bug Reports lists your GPU, driver version, and renderer, which tells you whether Krita is actually using the chip you think it is.
• On Windows, a crash often leaves a file called kritacrash.log in %LOCALAPPDATA%. Its last lines name the component that failed.

If you decide to report a bug, that log plus the exact steps that trigger the crash is what the developers need. Vague reports rarely get fixed.

Recovering Unsaved Work

Krita autosaves by default. The interval is set under Settings > Configure Krita > General > File Handling, and the default is every few minutes. After a crash, the next launch of Krita offers to restore the autosaved document. Say yes, then save it immediately under a new name.

If no prompt appears, look for files beginning with a period or named like .krita-autosave in your home folder (Linux and macOS) or %LOCALAPPDATA% (Windows). Krita also keeps backup copies of saved files, ending in ~, in the same folder as the original unless you turned that off. Shorten the autosave interval to two or three minutes while you troubleshoot a crashing setup.

Preventive Habits

• Keep the GPU driver current, but wait a week or two after a new driver release before installing it, so early bugs are caught by others.
• Store the Krita resource folder on a local drive, outside any cloud sync.
• Match the memory limit to your RAM and keep undo steps modest on big files.
• Install plugins from maintained sources and remove ones you stop using.
• Save in incremental versions (Ctrl+Alt+S in Krita) so a corrupt file costs you minutes, not days.
• New to the program? Our beginner’s guide to using Krita covers the Performance and Display settings that most often need adjusting on a fresh install.

FAQs

Why does Krita keep crashing when I open a file?

Most often the canvas renderer conflicts with your graphics driver. Switch between OpenGL, ANGLE, and software rendering under Settings > Display, and update the GPU driver from the manufacturer.

Why is my Krita lagging so much?

Krita is probably short on memory. Raise the memory limit under Performance, reduce the undo stack, move the swap file to an SSD, work at 8-bit color depth, and merge layers you no longer need to edit.

Why is Krita not responding during save?

Large files take time to compress and write. Wait several minutes before force-closing, because interrupting a save can corrupt the document. Saving in .kra with compression off speeds this up.

Can a plugin make Krita crash?

Yes. Python plugins run inside Krita, so a buggy or outdated one can crash the whole program. Disable plugins in the Python Plugin Manager and re-enable them one at a time to find the cause.

Does Krita autosave?

Yes, at an interval set under General > File Handling. After a crash, Krita offers to restore the autosaved file on the next launch. Save the recovered file under a new name right away.

Why is Krita not opening after I installed a brush bundle?

The bundle may be corrupt or built for a different version. Rename the resource folder so Krita starts fresh, then add bundles back one at a time.

Next Step

Work the list from the top: driver, renderer, config reset, memory, tablet, plugins. Nearly every persistent Krita crash falls to one of those six, and the log tells you which when the timing does not. Once the program is stable, be selective about what you add back. Extensions that are kept current with each Krita release are far less likely to send you back to this page, and our list of top Krita plugins worth installing is a good place to find them.