Krita VCS

Documentation

New to Krita VCS? Start here. Every chapter below covers a different part of the app: installing and saving your first version, a reference for each feature, the guardrails that keep your work safe, and the optional Krita plugin.

Read the docs on GitHub (opens in a new tab)

How Krita VCS keeps your work safe

  • Won't switch or merge if you have unsaved changes. You'll get a prompt with a shortcut straight to Changes, so nothing you've done gets lost or mixed into the wrong line of work.

  • Never silently overwrites a conflict. If the same artwork changed in two places at once, Krita VCS keeps the incoming version and marks the file for you to review — it never guesses.

  • Can't delete your main line of work, or the one you're currently on. Switch to another branch first if you want to remove the one you're using.

  • Won't undo a save that something else depends on. If a later save or another branch still needs it, undo is blocked so nothing gets orphaned.

  • Nothing happens if there's nothing to do. Saving with no changes, or restoring the version you're already on, simply does nothing.

  • Only one save happens at a time. If you're also using the Krita plugin, the two can never save at once — you'll see a brief "please wait" instead of any risk of a mixed-up save.

  • Removing a project defaults to the safe choice. "Remove from list" just forgets it here — your files and history stay untouched. Deleting the folder for good asks you to type its name first, so it's never one accidental click away.

  • Cleaning up always shows you first. You'll see exactly what would be freed before anything is actually deleted.