A line-by-line diff tells you which characters moved. sdffy tells you what that means: a value changed, a section was removed, a list was only reordered. Reviewers who don't read YAML all day can finally sign off on a change with confidence.
Why sdffy
Classic diffs were built for code. Most of what teams review isn't code.
Forty red and green lines
Indentation shifts, reordered keys and moved paragraphs all look like real changes. The one line that matters hides in the noise.
Four sentences
Changes are matched by structure and meaning. Pure moves and formatting are folded away, and every real change is described in a short sentence.
- Ignores formatting-only noise: whitespace, key order, line wrapping.
- Groups related edits, so “renamed a service everywhere” is one item, not twenty.
- Shareable summaries for people who approve changes but don't read raw files.
How it works
Three steps, all on your machine.
# compare two files sdffy old.yaml new.yaml # compare a file with its previous git revision sdffy config/app.json@HEAD~1 config/app.json
What it reads
Structured formats first; more on the way.
YAML, JSON, TOML, INI and .env files.
Compared as trees, not as text.
Markdown and DOCX.
Compared by section and paragraph.
CSV and TSV.
Rows matched by key column, not by position.
Privacy
Your files never leave your device.
Status
sdffy is in private beta.
- 1NowPrivate beta of the desktop app and command-line tool.
- 2NextPublic desktop release for macOS, Windows and Linux.
- 3LaterMobile apps for reviewing summaries on the go.
The site is being rebuilt; documentation and downloads will appear here when the public release is ready.