Compare two local files
Last updated: 2026-04-13
This use case covers the most common workflow: compare two local exports (text lists, IDs, usernames, or CSV-like records) without sending raw rows to a remote compare backend.
- Open the home tool.
- Import or paste your first source into List A.
- Import or paste your second source into List B.
- Click Compare lists and review the tabs.
TXT workflow vs CSV workflow
- TXT: each line is usually one item.
- CSV: import first, then adjust CSV mode (row or first-column) if needed.
- If CSV headers should be ignored, enable header skipping before applying parsing again.
Privacy note
Comparison runs entirely in your browser. Local file content is only what you paste into the input boxes and is not uploaded for server-side processing. See Privacy.
High-confidence checklist
- Verify case sensitivity based on your identifier rules.
- Enable trim if data may contain accidental leading/trailing spaces.
- Review duplicates tabs to detect upstream export quality issues.
Input -> option -> output example
Input A: id-001, id-002
Input B: id-002, id-003
Options: Trim ON, Ignore empty ON
Output: A only = id-001, B only = id-003, Intersection = id-002.
Typical production scenarios
- Comparing CRM exports before and after dedupe operations.
- Reconciling inventory identifiers across procurement and warehouse systems.
- Checking entitlement lists between expected and deployed states.
FAQ
Is CSV better than TXT for compare quality?
Neither is inherently better. Quality depends on how consistently each row maps to one logical compare item.
Should I compare full rows or one column only?
Use full rows for record-level diff, first-column extraction for identifier-only reconciliation.