OmniDiff: a Rust git difftool that diffs code, PDFs, fonts and images
OmniDiff is an open-source command-line diff tool written in Rust that compares the content of source code, images, fonts, PDFs and archives, not just their text lines.
OmniDiff goes beyond source code. The README says it handles code in 26 languages, plus images, fonts, PDFs and archives. It can run as an interactive viewer, as plain text for scripts and pagers, or as JSON, and it can be set up as a git difftool, a jj diff formatter or a lazygit renderer. A file it has no grammar for is diffed as plain text, line by line.
The author writes that they examined the roughly 7400 repositories listed in Gentoo packages, sampled 2000 diffs, and worked out the right results by hand before building a diff pipeline for each content type. The same corpus is said to form the basis of the CI pipeline. The README says the project uses substantial AI assistance, currently Claude Code, and that most commits carry a Co-Authored-By trailer. The post says the author uses AI but does not vibecode. It does not say how the work was split between the author and the AI, and nothing here says what went wrong along the way.
The README says most diffs finish in under 100 milliseconds on a 2023 T14s laptop. These are the author's figures. The project is at v0.3.0 and still in development. The author says they have used it daily as their git difftool for months. Contributions are not accepted at this time.
In the author's words
This project uses substantial AI assistance, currently Claude Code.
From the README or the author's post. We checked that the sentence is there, not that it is true.
What to take from it
Collecting real changes from many repositories and writing down the expected output by hand gives a test set grounded in actual use, and the same set can then serve as the CI suite. For a tool of your own, starting from real inputs and a narrow set of supported formats, with a plain-text fallback for everything else, is a sensible place to begin.
Built with
See it
AI wrote this entry from the project's own README or its author's post. That AI built the project is the author's statement, quoted here. Nobody at IKANGAI ran or tested it. How this list is made