Find Duplicate Files With Different Names

You know the copy is in there somewhere. The problem is it isn’t called what the original is called. The report you saved twice became report.pdf and report-final.pdf. The photo you dragged off your phone is IMG_2231.jpg in one folder and beach.jpg in another. Sort the folder by name and they sit rows apart, looking like two unrelated files. That’s the exact case people mean when they search for how to find duplicate files with different names — and it’s the case a name-based cleanup can never solve.

The good news is that the name was never the file. It’s just a label you (or an app) stuck on top. Underneath, the bytes are what make a file a copy — and those don’t change when the label does.

Why a renamed copy is invisible to your eyes#

Almost everything that scatters duplicates around your disk also renames them along the way. Save a document a second time and Windows tacks on (1). Import the same photos twice and your phone or import tool numbers them differently. A cloud client drops the original in one folder and a conflicted copy in another. Someone emails you a PDF and you save it under a tidier name than the one they used. In every one of these, the file is identical to something you already have — but the name has drifted, so scanning a folder by eye tells you nothing.

Extensions drift too. The same text can live as notes.txt and notes.bak. An export tool might write .jpeg where the original was .jpg. Different extension, identical content — and, again, your eyes and a name sort will never connect them.

Content matching ignores the name entirely#

The way through is to stop comparing labels and compare the thing itself. Elegant File Explorer’s Find duplicates tool reads the actual content of each file and gives it a fingerprint from those bytes — a SHA-256 hash. Two files with the same fingerprint hold the same content, full stop, no matter what they’re called or what extension they wear. The window says as much right at the top: “Compares file contents (SHA-256), not just the name — finds copies even with different names or extensions.”

That single group in the screenshot is the whole argument. The tool didn’t care that one copy was named after its subject, another after nothing in particular, a third with a “Copia” suffix from a Windows copy-paste. It grouped them because their content is byte-for-byte identical. Rename a file all you like — you can’t rename its way out of a group.

And the reverse guardrail matters just as much: two files that merely share a name are not assumed to match. report.pdf in one folder and report.pdf in another might be an old draft and the final version. Because the tool compares content, it groups them only if the content truly matches, and leaves them apart if a single byte differs. You get real copies, and only real copies.

Different name still doesn’t mean “safe to delete”#

Finding a renamed copy is the easy part. Deciding which one to remove is where care comes in — and the tool is deliberately cautious here. Every group keeps one copy marked with a keep this copy badge that can’t be unchecked, so you can never clear the last survivor. Anything sitting in a Windows or program folder is flagged Protected and can’t be selected at all. And because identical files can legitimately belong to different projects, every group arrives marked Review: the header states plainly that no removal is recommended automatically based on the hash alone — review the groups below carefully. Nothing is ever pre-selected, and nothing leaves your disk until you tick it yourself and confirm a dialog.

I’ve kept this to the “different names” angle on purpose. The full walk-through — adding folders, the scan counters, the two ways to remove, and the Recycle Bin default — lives in find and remove duplicate files safely. If your renamed copies are spread across two specific folders, finding duplicate files in two folders shows how to line them up; if they’re photos your phone renamed on import, find duplicate photos is the one to read.