Difftastic

Last reviewed Aug 26, 2026 · 788 words

Two lines of git config change how you read every diff from now on:

git config --global diff.external difft
git config --global difftool.difftastic.cmd 'difft "$LOCAL" "$REMOTE"'

After the first line, git diff, git show, and git log -p all route through Difftastic, and a reformatted function that a line diff shows as 40 red lines and 40 green ones shows up as what it is: nothing changed. The difft binary is Rust, single-file, 25,819 stars, and reads about 50 languages with tree-sitter parsers. It sits on your laptop, not on a server, which is why this page is about where it fits in a self-hoster's workflow rather than how to deploy it.

What "structural" buys you on a normal Tuesday

Line diffs treat a moved closing brace, a re-indented block, and a real logic change identically. Difftastic parses both versions into syntax trees and diffs the trees, so it knows that wrapping a function body in an if moved everything one level in without changing it, and it highlights only the new if. Renamed variables show as the identifier changing, not the line. JSON and YAML that were reordered by a tool show as reorderings. The practical effect is that reviewing a commit that touched formatting and logic at the same time, which is most commits, takes a fraction of the time. Side-by-side is the default when the terminal is wide enough; DFT_DISPLAY=inline switches to one column.

It cannot make a patch, and that decides where you use it

Difftastic's output is for eyes only. There is no unified-diff mode, nothing you can pipe into git apply or patch, and it makes no attempt to be one. So it belongs on the reading side of your workflow and nowhere on the writing side. git diff > fix.patch still needs the built-in differ, which is one reason to prefer the difftool wiring over diff.external if you script around git: git difftool -t difftastic opts in per invocation, and git diff stays a patch generator. Reviews on your Gitea or Forgejo instance are unaffected either way; those render their own diffs server-side, and the web view stays line-based whatever your laptop does.

Where it falls back, and how to tell

Unsupported languages, files above a size threshold, and files where parsing fails all fall back to a plain line diff, and Difftastic says so in the header. Huge minified files and generated code are the ones that trip the memory limit the catalogue mentions: the tree-matching algorithm grows with the number of nodes, and a 5 MB bundle can push it past a gigabyte before it gives up. DFT_GRAPH_LIMIT caps that, and I set it lower rather than higher on machines with 8 GB or less. It is also blind to semantics that are not in the syntax: two functions with identical bodies but different names are a rename, and it will show exactly that, which is correct and occasionally unhelpful.

Difftastic or delta

They are not rivals. Delta is a pager that makes line diffs beautiful, with syntax highlighting, side-by-side, and line numbers, and it keeps the output patchable in spirit because the underlying diff is still git's. Difftastic changes what the diff is. I run both: Difftastic as the difftool for reading a commit I am about to review, delta as the default pager for everything else. Lazygit users can point its custom pager at either. If you only want one, and you read more diffs than you write patches, take Difftastic.

Installing it across a homelab

Cargo (cargo install difftastic), Homebrew, and most Linux package managers carry it, and the GitHub releases page has static binaries for the machines where you do not want a Rust toolchain. On a jump host or a Proxmox node where you occasionally inspect config drift, difft /etc/nginx/nginx.conf /backup/etc/nginx/nginx.conf is a better first look than diff -u because a reordered block reads as a reorder. The whole binary is a few tens of megabytes and the 64 MB catalogue figure is the idle footprint; peak use depends entirely on the files you throw at it. Other tools of this shape live in dev tools.

What I'd do

Wire it in as difftool rather than diff.external, keep delta as the pager, set DFT_GRAPH_LIMIT conservatively on small machines, and reach for git difftool -t difftastic HEAD~1 whenever a commit mixes formatting with logic. It will not change how your forge shows pull requests, and it will change how quickly you understand them.