List Intersection Tool

Paste two lists, choose matching rules, then get the shared lines plus quick stats.

Compare your lists

Enter two lists below. Each item should be on a separate line.

Comparison Options

Common Items

Items that appear in both lists.

Before you trust the overlap, check your rules

List intersection feels simple. Paste two lists, click one button, copy the overlap.

Yet most wrong results come from one of two things. Formatting drift. Matching rules you did not mean to apply.

This list intersection tool gives you four switches, so the output matches your intent. Case sensitivity, whitespace trimming, empty line removal, sorting.

Pick rules first. Then trust the overlap.

Common mistake: If your list items contain extra spaces or mixed case, leave trimming on and case sensitivity off for a first pass. Then rerun with stricter rules when you need exact matches.

Intersection means one thing. A line appears in list 1. The same line appears in list 2. The output keeps one copy.

Everything else stays out.

If you need a combined list, use a union workflow instead. Try the List Union Tool when you want one de-duplicated list from two inputs.

If you need what is missing, take the opposite path. The List Difference Tool highlights items present in one list, absent from the other.

Those three operations solve different questions. Overlap. Combined set. Unique remainder.

Mixing them up wastes time.

Here is a fast way to choose the right one.

OperationWhat you getGood for
IntersectionLines present in both listsOverlap checks, access audits, list cleanup
UnionAll unique lines from both listsBuilding a master list without repeats
DifferenceLines present in one list, missing from the otherFinding gaps, missing items, drift over time

Need lines that show up once across a bigger merged list. Use Find Unique Lines after you combine sources.

When list intersection pays off

Real work rarely arrives as neat data.

You paste usernames from a ticket. You export emails from a CRM. You copy product SKUs from a spreadsheet cell range. Then you need the common subset between two sources.

Some examples.

  • Audit access. Compare a role list to a list of active accounts, then pull the accounts with permissions.
  • Content cleanup. Compare two keyword lists, then keep only shared terms before you rewrite a page outline.
  • Ops checks. Compare two server host lists from two tools, then isolate the machines seen by both.
  • Study planning. Compare two reading lists from two courses, then identify shared titles.

In each case, the best output depends on normalization. A trailing space should not break a match. Unless you want it to.

One realistic example. A vendor exports “ACME-1042 ” with a trailing space. Your internal list stores “ACME-1042”. With trimming on, you get a match. With trimming off, you get a miss. Neither output is wrong. Only one matches your goal.

The matching pipeline, in plain language

The tool splits each input into lines. One line becomes one item.

Then it applies your rules.

Trimming removes leading and trailing spaces. Empty line removal drops blank entries. Case handling turns matching into either exact case matching or lowercased matching.

After normalization, the tool checks which normalized items appear in both lists. That part uses a set lookup, so it stays fast even when you paste long lists.

Finally, it formats the output. Sorting is optional. Stats show counts plus a match rate.

The match rate uses the larger list as the baseline. This is a practical signal, not a math proof of similarity.

If you want a quick sanity check, turn sorting on, copy the result, then spot-check three random items in each original list. This catches the most common paste mistakes fast.

Why your output looks “wrong” sometimes

Most “wrong” intersections are correct given the rules. The surprise comes from hidden differences in input.

Examples.

  • Invisible spaces. A pasted cell often carries a trailing space. Trimming fixes it.
  • Mixed case. “ACME” versus “Acme” fails with case sensitivity on.
  • Duplicate lines. The result lists each match once, even if one list repeats the same line.
  • Multi-field lines. If a line contains commas, tabs, or extra labels, the tool still treats the whole line as the item.

If you need field-level matching, first clean your input. A quick way is to convert structured text into one value per line, then rerun the intersection.

For a visual diff view, the Text Line Comparison tool helps when you need to see what differs inside a line.

Limits you should know up front

This tool compares whole lines. It does not parse CSV columns. It does not detect synonyms. It does not fix typos.

If two items match only after heavy normalization, you need a different approach. Try a fuzzy matching workflow in your data tool, then validate results manually.

Also, treat case rules with care for IDs. Many identifiers are case-sensitive by design. API keys, coupon codes, file names on some systems.

When in doubt, run two passes. One forgiving pass for a quick scan, one strict pass for your final output.

Small workflow tips

Paste list 1 from the source you trust most. The tool preserves that side’s original line in the result.

Turn sorting off when you want the output to follow list 1 order. Turn sorting on when you want a clean scan list.

Need overlap across more than two lists. Run intersection iteratively. Output becomes list 1 for the next run.

For multi-list overlap, the Find Common Lines tool fits better when you have more than two sources.

1
Data analysis

Find overlapping customer segments, shared product features, or common data points across datasets.

2
Research work

Identify common factors, shared references, or overlapping findings across multiple research sources.

3
Access control

Match user permissions, find shared roles, or identify common access rights across different groups.

Input processing

The tool splits each list by line breaks, applies your selected options for trimming and case handling, then removes empty entries.

Set creation

Normalized items from both lists convert into sets. This structure enables fast lookup operations for comparison.

Intersection calculation

The algorithm checks each item from the first list against the second set, collecting matches into the result collection.

Result formatting

Common items sort alphabetically if requested, then display with statistics showing match rates and item counts.

Performance scales well for typical paste sizes. Thousands of lines stay responsive because lookup uses a set. If your browser tab slows down, split the job into smaller batches.

Privacy stays simple. Processing runs in your browser. Your lists do not get uploaded by this page logic.

Questions people ask after one “weird” result

Short, practical answers about matching rules, limits, and privacy.

Why did a line not match when it looks identical?

Hidden whitespace is the usual cause. Keep “Trim Whitespace” enabled, then rerun. If you copied from a spreadsheet, trailing spaces are common.

Should I enable case sensitivity for IDs?

Often yes. Codes, usernames, file names, and many identifiers treat case as meaningful. Use a strict pass for final checks, then store the output.

Does the tool compare whole lines or parts of a line?

Whole lines. If you paste CSV rows, the full row becomes the item. For column-based matching, extract the column first, then run intersection.

Why does the output remove duplicates?

Intersection is set-based. One match appears once. If you need counts of repeats, keep the raw lists elsewhere and treat this output as a unique overlap list.

Is my list uploaded to a server?

No. The intersection logic runs in your browser on this page. Use the copy buttons to move results where you need them.

What is a good next step after intersection?

If you need the non-overlap, run the List Difference Tool. If you need one combined list, run the List Union Tool. Use the overlap as a clean input for the next step.