Anki Keeps Crashing | Fixes That Stop Random Exits

If anki keeps crashing during reviews, on startup, or right after syncing, don’t start by reinstalling. That’s the move that feels productive, yet it often leaves the real cause untouched. A better plan is a short set of tests that isolates one variable at a time, so you can stop the crash without risking your collection.

This article targets Anki on desktop (Windows, macOS, Linux). Mobile apps can crash too, but file locations and settings differ.

Quick Triage Before You Change Anything

Start with two habits that protect your data: make sure you have a current sync and keep a local copy of your Anki data folder. You can do both in a couple of minutes, and it removes a lot of stress from the rest of the steps.

1. Sync once if Anki stays open — Open Anki, wait until it settles, then click Sync so your latest cards reach AnkiWeb.
2. Quit Anki fully — Close the window, then confirm it’s not running in the tray or dock.
3. Copy your Anki data folder — Make a backup copy of the whole Anki2 folder to a second location on your drive.

Default data paths (use these only as a starting point, since custom setups exist):

• Open it on Windows — Press Win + R, type %APPDATA%\Anki2, then press Enter.
• Open it on macOS — In Finder, use Go to Folder and enter ~/Library/Application Support/Anki2.
• Open it on Linux — Check ~/.local/share/Anki2.

Once that copy exists, you can test fixes without feeling like one wrong click will wipe your work.

Anki Keeps Crashing On Startup Or During Review

This section is the “get one stable run” path. The goal is to make Anki open and stay open long enough to identify the trigger.

What You See	Most Likely Cause	Best First Step
Anki won’t open, or freezes on “Starting…”	Rendering or driver issue	Switch video driver to Software
Anki opens, then closes when reviews begin	Add-on conflict	Start in safe mode
Crash happens after sync	Collection file needs repair	Run Tools → Check Database
Window flickers or turns black	GPU driver mismatch	Change video driver setting

Start In Safe Mode

Safe mode runs Anki without add-ons and without automatic syncing. If Anki stays stable in safe mode, you’ve learned a lot in seconds: the crash is likely tied to an add-on or to something that runs at startup.

• Hold Shift while opening Anki — Keep Shift pressed until you see a prompt, then confirm safe mode.
• Launch from a terminal when needed — On Linux, some desktop setups don’t pass the Shift state to apps in the same way; launching with anki --safemode can work when Shift doesn’t.
• Skip syncing for one test run — If your crash happens right after launch, keep sync off until Anki is stable.

Run A Short Repro Test

Once Anki is open, keep the test small and repeatable. You want a crash you can trigger on demand, since that makes the fix obvious.

1. Open a small deck — Pick something light on audio and images for the first pass.
2. Review 10 cards — Stop on purpose so you can repeat the same test after each change.
3. Write down the moment — “Crashes when I flip a card with audio” is useful. “Crashes sometimes” is harder to act on.

Grab A Clue From The Console

If Anki closes instantly, the last line printed to a terminal can point at the cause. You don’t need a full debug session. You just need the final lines before the app exits.

• Run Anki from Terminal on macOS/Linux — Start it with anki, reproduce the crash, then copy the last lines shown.
• Note your version string — When Anki stays open long enough, open Help → About and save the version details.

Add-on Checks That Fix Most Review Crashes

After updates, add-ons are the most common reason anki keeps crashing when you hit Review. The clean way to solve it is to isolate the one add-on that breaks your current setup.

Disable Add-ons In Batches

If safe mode is stable, do this in a normal run, then restart between changes. The batch method is fast and keeps you from deleting everything at once.

1. Open Manage Add-ons — Go to Tools → Add-ons in a stable session.
2. Disable half the list — Restart Anki and run your same 10-card test.
3. Halve again based on results — If the crash stops, the culprit is in the half you just disabled. If the crash continues, it’s in the half still enabled.
4. Update or remove the culprit — Install its update if one exists, then test again.

Prioritize Reviewer And UI Add-ons

Add-ons that touch the reviewer screen, card rendering, audio playback, or custom buttons are more likely to crash than simple helper add-ons. If your add-on list is long, start by disabling anything that changes reviewer visuals, adds overlays, or hooks into scheduling screens.

Check For A Single Bad Note Or Template

Some crashes only happen on one card type. That often points to a template issue, a font problem, or a script you added to card styling.

• Find the last reviewed note — Open Browse and locate the note tied to the moment the crash happens.
• Strip custom scripts first — If you added JavaScript to a template, remove it, then test again.
• Test a plain template — Duplicate the note type and try a plain front/back layout to see if stability returns.

If you need to study right now, safe mode is a solid short-term fallback while you isolate the add-on or template that causes the exit.

Repair Your Collection And Stop Sync-Triggered Crashes

When crashes feel tied to syncing, importing, or bulk edits, the collection file is the next thing to test. Anki includes built-in repair steps that are worth running before deeper changes.

Run Tools → Check Database

This is the primary built-in repair step recommended in the Anki manual. It checks the collection file and rebuilds internal structures that can get out of shape after interruptions or corruption.

1. Quit and reopen Anki — Start fresh so the repair runs cleanly.
2. Run Check Database — Go to Tools → Check Database and let it finish.
3. Repeat your repro test — Run the same 10-card review that used to crash.

Handle The Full Sync Prompt Carefully

After a database check, Anki can prompt for a full sync. If this computer holds your newest edits, uploading the local collection is usually the safer move, since downloading would overwrite local changes with the server copy. If you’re unsure which device is newest, stop and verify by checking the last sync times on each device before you pick a direction.

Check Media When Crashes Follow Audio Or Images

Media problems can present like a “random” crash when you hit a card that loads a broken file. A media pass can remove bad references and help you find the card that triggers the crash.

• Run Check Media — Use Tools → Check Media and follow prompts to remove missing references.
• Remove the failing media link — If one card triggers the crash, open that note and delete the media reference, then re-add a fresh file.
• Retest on a plain card — If plain text cards never crash, the trigger often sits in media or styling.

Create A Fresh Profile As A Clean Test

A profile can break in ways that look like collection damage, since it stores settings and add-on state. Creating a test profile helps you separate “data issue” from “settings issue.”

1. Open Profile Manager — Start Anki with Shift held, then open Profile Manager.
2. Create a new profile — Name it “Test” and open it.
3. Import a backup copy — If the test profile runs cleanly, import a recent backup or copy your collection into the new profile.

Graphics Fixes For Flicker, Black Windows, And Launch Hangs

If Anki flickers, shows a black window, or won’t launch after a driver update, treat rendering as the likely cause. Anki’s interface uses Qt, and Qt can trip over GPU driver issues on some systems. You don’t need to fight your GPU to keep studying. You just need a stable render mode.

Switch Anki’s Video Driver Setting

Anki includes a setting that can force software rendering. If your crash looks like a display problem, this often restores stability fast.

1. Open Preferences — Go to Tools → Preferences.
2. Set Video Driver to Software — In Appearance, choose Software, then restart Anki.
3. Retest reviews and Browse — If stability returns, rendering was the trigger.

Update GPU Drivers With A Clean Install

If software rendering fixes the crash, you can either stay on it or repair the driver stack. A clean driver install can clear odd Qt crashes after OS updates.

• Get the driver from the GPU vendor — Use the official NVIDIA/AMD/Intel site for your model.
• Choose the clean install option — Pick the install mode that resets prior settings.
• Test default rendering again — Switch video driver back to the default mode and see if it stays stable.

Force Software OpenGL On Windows When Anki Won’t Start

If Anki won’t open at all on Windows, a known workaround is forcing Qt to use software OpenGL through a user variable. This can get Anki running long enough to change settings or update drivers.

• Add a user variable named QT_OPENGL — In Windows System Properties, add QT_OPENGL with the value software, then restart your PC.
• Launch Anki and change the video driver — Once Anki opens, set Video Driver to Software inside Preferences.
• Remove the variable after the driver fix — After your GPU driver is stable, delete the variable and test the default mode again.

Habits That Keep Anki Stable After You Fix It

Once you’ve stopped the crashes, a few habits make repeat failures less likely. None of these require extra apps or complex routines.

Update In A Controlled Order

Updates can fix bugs, but add-ons can lag behind your Anki version. A controlled update order reduces the chance of a broken reviewer.

1. Sync before updates — Push your newest changes to AnkiWeb while your setup still works.
2. Update Anki and run a short test — Do a 10-card review before enabling every add-on.
3. Update add-ons one at a time — If an add-on update breaks stability, you’ll spot it fast.

Keep Add-ons Lean

Each add-on adds code that runs inside Anki. If you only use an add-on once in a while, leave it disabled until you need it. Fewer moving parts usually means fewer crash paths.

Run Check Database After Big Imports

Large imports, bulk edits, or interrupted sync sessions can leave small inconsistencies behind. Running Tools → Check Database after those events is a quick way to keep the collection file clean.

Use Official Reference Pages When The Crash Persists

If you’ve tried safe mode, database repair, add-on isolation, and video driver changes and Anki still exits, use the official manual pages as your next step. They stay current and outline what Anki’s maintainers expect you to test.

Anki Manual: Troubleshooting
Anki Manual: Managing Files

Work through the sections in order, and you’ll usually find the trigger in one sitting. You’ll also end up with a safer setup: a clean data copy, a stable render mode, and an add-on list that matches your Anki version.