01
Two files, one desk
Open the original and the revised Markdown. The comparison stays in this browser.
Markdown diff checker
See what changed in the spec—not just which lines moved.
Drop two Markdown files and read heading-aware changes in this browser. Nothing is uploaded, and the original files stay as they are.
checklist.md
Original vs revised
@@ Before release
- [x] Validate preview
- [ ] Publish notes
+ [x] Publish notes
+ [ ] Record the print proof
@@ Rollback
+ ## Rollback
What the checker shows
A document comparison, not a pile of red lines
Plain line pairing by position misreads a heading that moved down. MD Viewer keeps shared sections lined up and names outline changes separately.
02
Headings first
The outline shows which sections arrived, left, or changed level before you read every line.
03
Same engine as preview
Heading names come from the selected Markdown profile, not from a second parser.
04
Line endings called out
CRLF versus LF is a note, not a rewrite of every line.
05
Originals untouched
Reading a file for comparison does not save over it. Download a .diff if you want a record.
06
No Git required
Specs, READMEs, and notes can be compared without a repository.
This browser
Paste, drop, or type. Then read the outline.
Use Source for the line walk, Outline for heading changes, and Preview to see both documents with the same engine as the editor. Download a unified diff when you need a file to keep.
Open the diff checkerOriginal outline
- Release checklist
- Before release
- Support
Revised outline
- Release checklist
- Before release
- Support
- Rollback
1 heading added
Questions
Before you compare important source
Does the Markdown diff checker upload my files?
No. Both files are read in this browser. MD Viewer does not send the source to a server.
What does heading-aware mean?
The outline names headings that were added, removed, or changed level, using the same Markdown profile as preview. The source view still shows every changed line.
Will comparing files overwrite the originals?
No. Opening a file for comparison does not write back to disk. Download a unified .diff if you want a record to keep.
Is this the same as Git diff?
It is a local two-file comparison, not a repository tool. It does not need Git, and it names Markdown headings instead of only listing line numbers.
Compare the two files on this device.
Nothing is uploaded. The originals stay on disk.