The right tool for the right task

Kompare is a graphical difference viewer that allows you to visualize changes to a file. Whether you're a developer comparing source code, or you just want to see the difference between that research paper draft and the final document, Kompare is the tool you need.

What Kompare can do

  • Compare two text files
  • Recursively compare directories
  • View patches generated by diff
  • Merge a patch into an existing directory
  • Entertain you during that boring compile


If you have the KDE Software Development Kit (SDK, included with many distributions), you already have Kompare. Just look for it in your K Menu. If you don't find Kompare there, go ahead and get a fresh copy from the KDE project. Enjoy!

Helping out with Kompare

If you have some C++ programming experience, along with a little knowledge of Qt/KDE, you could help out with Kompare. First, you might want to check out the Kompare Junior Jobs, open bugs that beginners can tackle. Normally, the developers have made helpful comments in the bug reports to help you get started. If you find a bug in Kompare, we'd be delighted if you would file a report at the KDE bug tracker.

If you're interested in actual development work, you'll also want to get Kompare from the KDE code repository. You can find the kompare git repository details and browse the source here. For an anonymous git checkout, use:

git clone git://

Contacting the Kompare team

We appreciate feedback. Your input helps us to make Kompare a more useful tool, so if you have questions regarding helping out with the project, want to notify us of a bug, or have a suggestion, please contact one of us, or send a mail to the list:

The list address is kompare-devel at and you can subscribe to kompare-devel by following the instructions on the list information page.


Kompare was originally written by Otto Bruggeman, but since Otto is no longer active, Kompare is now maintained for the most part by Kevin Kofler. It started out by the name of KDiff2, but was renamed when the code became part of the KDE SDK package, where it still resides today, a testament to the strength of the KDE community.