Diff two directory snapshots
Paste two tree command outputs and instantly see which paths are only in A, only in B, and present in both. Runs entirely in your browser.
tree, find, or any indented path list (2 spaces per level).Paste two snapshots to see the diff
How to diff two folder snapshots
Run tree or find on two folders, paste each side, and see which paths moved, were added, or removed.
- 01
Capture snapshot A
Run
tree -L 3 ./folderand copy the output.Inputs are treated as UTF-8 throughout the pipeline and validated client-side as you type — nothing dispatches until the value is well-formed.
captureinpututf-8client-sidevalidatedsrc · textbefore · settree -L 3 ./app
loaded · parsedclient-side - 02
Capture snapshot B
Same command in the second folder or after changes.
Each toggle re-computes through a memoised hook, so flipping options never resets your input and the UI stays snappy on large inputs.
captureoptionslivememoisedtogglessrc · memoisedafter · livetree -L 3 ./app2
options set · memoisedlive - 03
Paste both
Tree characters are stripped — indent levels matter.
Randomness — where used — comes from
crypto.getRandomValues, neverMath.random. Heavy work sits inuseMemo.pastecomputeinstantlocaldeterministicinput · instantboth · computedA and B
computed · instantinstant - 04
Read the diff
Red = only in A, green = only in B, neutral = unchanged.
Copy writes through
navigator.clipboardand downloads use aBlob— zero network traffic. Same input plus same options always yield the same bytes.reportcopydownloadzero-networkreproducibleok · copiedready · copieddiff ready
shipped · ready to shipsuccess
Pro tips for everyday utilities
Reach for crypto.getRandomValues
Cryptographically random for IDs, tokens, salts. Math.random is for animation and games, not security.
Mock data with seeds
Faker-style libraries can be seeded so tests are reproducible. Embed the seed in the fixture file.
Reference cards beat memory
Cheatsheets for Vim, Git, Docker, Linux signals are faster than man pages when you’re mid-flow.
Browser APIs vary
Touch events, gamepads, and clipboard differ across vendors. Feature-detect before use.
Persist in the right place
localStorage for user preferences, sessionStorage for transient state, IndexedDB for structured data.
When to diff trees
Refactor audits, release notes, drift detection.
Refactor audits
Spot moved or removed files after a big rename. Random values come from crypto.getRandomValues — cryptographically secure for tokens, salts, and session IDs. Math.random is deterministic enough for animations but predictable enough to be a security bug.
CSPRNG-backedRelease notes
List the new/deleted files between two tags. Pair with hashids, ULID, or UUID v7 when you need both random and sortable — useful for primary keys, public-facing IDs, and event log ordering without a sequence column.
reproducibleServer drift
Compare two deployed snapshots for surprise files. Output is deterministic given the same seed, so fixtures and tests stay reproducible across CI runs and contributor machines. Embed the seed in the fixture file for full replay.
snappyBackup audit
Spot files missing from a restore. Heavy work runs through useMemo so the UI stays snappy on large inputs. Same input + same options yields identical bytes — the kind of stability snapshot tests rely on.
feature-detectedMigration check
Confirm a copy moved every path expected. Storage tools persist to the right backend: localStorage for user preferences, sessionStorage for transient state, IndexedDB for structured data. Pick the right shelf and quota worries disappear.
deterministicDoc structure
Track how a docs folder evolves between versions. Browser feature detection: clipboard, fullscreen, gamepad, and Web Bluetooth APIs gracefully fall back when unavailable. No surprise white screens on Safari or older Firefox.
production-readyFrequently asked questions
Something missing?
Tell us what you need. We ship the top requests every two weeks.