Word Counter
Count words, characters, sentences, paragraphs, reading and speaking time, and keyword frequency while keeping text in your browser.
Share
The inputted text is too long to include in a share link.
List Diff Checker
Compare two text lists to find shared and unmatched entries, duplicates, and differences with case and whitespace normalization.
Results
How to use this list diff checker
Use this checker when two exports, lists, or pasted columns should mostly match and you need to find what changed.
- Paste one line-by-line list into List A and the other into List B.
- Choose whether to ignore case, punctuation, symbols, numbers, or extra spaces.
- Review common entries, entries only in List A, and entries only in List B as the results update.
List Diff Checker features
- Compare two line-by-line lists side by side.
- Find entries common to both lists.
- Find entries that only appear in List A.
- Find entries that only appear in List B.
- Ignore case differences while comparing.
- Ignore punctuation, symbols, numbers, or extra spaces when needed.
- Keep readable original values in the displayed output.
- Update results automatically as lists or comparison options change.
What list comparison is useful for
Use this list diff checker to compare two sets of text, names, IDs, keywords, URLs, product SKUs, email addresses, or other line-by-line values. It helps find matching items, missing entries, removed entries, and newly added values.
It is especially useful after exporting data from two systems that should agree: a CRM list and an email platform, a product catalog and marketplace upload, a keyword plan and an ad group, or two versions of a spreadsheet column. The normalization options help when values differ only because of capitalization, spacing, punctuation, or symbols.
For audit work, keep a copy of the original lists before changing normalization settings. Ignoring punctuation or numbers can be helpful for messy names, but it can hide meaningful differences in SKUs, URLs, invoice numbers, or IDs.
Common list checks
- Find duplicate values across two lists
- Compare keyword, URL, or SKU exports
- Check customer, lead, or email lists
Difference checks
- See what is missing from either list
- Spot removed or newly added entries
- Normalize inconsistent formatting before comparing
How list differences are calculated
The tool splits each list into non-empty lines, normalizes each line according to the selected options, and compares unique normalized values. The displayed output keeps the first original version of each matching value so the result stays readable.
Because comparison is based on unique normalized values, the result answers "which values appear?" rather than "how many times does each value appear?" That makes it useful for membership checks, but not for duplicate-count audits.
List diff checker FAQ
Does this show duplicate counts?
No. The comparison uses unique normalized values, so it is best for finding shared and missing entries rather than counting duplicates.
What does trim spaces do?
It removes leading and trailing spaces and collapses repeated internal whitespace before comparing values.
Can I compare IDs, SKUs, or URLs?
Yes. Any line-by-line values can be compared, including IDs, SKUs, URLs, emails, names, and keywords.
When should I avoid ignoring numbers?
Keep numbers enabled when comparing IDs, SKUs, invoice numbers, zip codes, versions, or URLs where digits are meaningful.
Does this upload my lists?
No. The comparison runs in your browser.
Define when two list entries should count as the same
Start by naming the unit represented by one line. It might be an email address, product code, filename, domain, full record, or free-text label. The correct comparison rules depend on that unit. Trimming or changing case can be useful for one list and destructive for another.
Case sensitivity is not universally cosmetic. Some identifiers are case-insensitive by specification or local policy, while passwords, tokens, paths, and product codes may be case-sensitive. Domain names and the local part of an email address also have different rules and real-world handling. Use a domain-aware validator when the distinction matters.
Whitespace can include spaces, tabs, carriage returns, nonbreaking spaces, and other Unicode characters that look similar. Trimming ends is often safe for labels but not for fixed-width values or intentional leading content. Replacing all internal whitespace can merge entries that were meaningfully different.
Decide how duplicates should behave. A set comparison asks whether a value appears at least once, while an inventory or transaction reconciliation may need occurrence counts. If one list contains a value three times and the other once, a unique-only comparison hides two unmatched occurrences. Preserve duplicates until the business rule is clear.
Normalization can also affect punctuation, accents, composed Unicode forms, and locale-specific letters. Two strings can look identical but use different code-point sequences, or look similar while representing different names. Do not strip accents or transliterate personal names merely to force a match. Keep the original value beside any normalized comparison key.
For large reconciliations, compare counts as well as values. Record input lines, blank lines, unique entries, duplicates, common entries, and each side's differences. A total that does not reconcile can reveal a parsing or normalization mistake. Spot-check entries from every output group before acting on the result.
The comparison happens in the browser, but source and copied output may still contain confidential identifiers. Replace production data with synthetic samples when testing rules. Store reconciliation exports in approved locations, limit access, and remove temporary files after the decision when policy requires it.
Before deleting, emailing, merging, or updating records from a difference list, validate the result against the system of record. A text match cannot see aliases, retired identifiers, linked accounts, or business status. Use the output as a candidate list and keep a rollback or review step for consequential changes.
Review checklist
- Define the entry type, comparison key, case rule, whitespace rule, Unicode treatment, blank-line policy, and duplicate behavior.
- Keep original values beside normalized keys and never erase accents or meaningful punctuation merely to increase matches.
- Reconcile input, blank, unique, duplicate, common, and unmatched counts and inspect samples from every output group.
- Protect identifiers and exports as confidential data when their source or business context requires it.
- Validate candidates against the system of record before deletion, outreach, account merging, or another consequential action.
- Check whether order matters and use a sequence-aware method when moved lines should count as a change.
- Document approved aliases and replacements separately instead of repeatedly editing the raw source lists.
- Keep evidence of reviewed exceptions so the same legitimate mismatch is not investigated in every reconciliation.
Built and maintained by utilkit. Updated . Found an issue? Send corrections to contact@utilkit.com
Related Utilities
Collections featuring this utility
Content Cleanup
Content cleanup is the last mile before publishing, importing, or sending work. Catch messy text, mismatched lists, broken formatting, and file issues before they reach someone else.