Find the people you both know. Compare two LinkedIn exports without either file leaving its own computer.

Your files and names stay in this browser. Salted profile hashes go directly to the other browser only in connected mode. Room codes use a daily-changing address hash for a short request budget.

Connection details

For room codes, a service holds one connection blob from each side for ten minutes so the two browsers can find each other. It never sees a name or a hash, and the copy and paste route skips it entirely.

Have both exports? Compare them here in seconds. Both files stay in this tab. Only use files you have permission to read.

First connection list

Choose a LinkedIn CSV

Second connection list

Choose a LinkedIn CSV

Choose both files to reveal your overlap.

Can't see

Method and limitations

Second-degree paths. It compares two lists of people you are each already connected to, so somebody you both reach through a third person is invisible to it.
Warmth. A colleague you speak to weekly and a stranger who sent a request in 2019 look exactly the same in an export, and this tool does not read the connected-on date to guess between them.
Anyone who has changed their profile URL since one of the two exports was taken. The slug is the identifier, so an old file and a new one hold two different people as far as the hashing is concerned, and nothing can detect that.
Rows with no profile link. LinkedIn leaves the URL out when a connection has restricted it, and those rows are counted and reported rather than guessed at.
Old style /pub/ links from exports taken years ago. They are a different identifier space from an /in/ slug and comparing the two would invent matches.