Find byte-identical duplicates with different filenames
Files with different names can belong to one duplicate group when their bytes are identical. This does not judge visual similarity, so edited or recompressed copies of the same photograph may remain separate.

How to use this tool
- Add the files to compare for duplicates.
- Confirm the list and run inspection.
- Review group names, sizes and hashes.
- Download the inspection CSV.
Choose the right settings
Add every file you want compared and check that no suspected copy is missing. The tool calculates SHA-256 without a similarity threshold, making actual file content rather than filenames the comparison basis.
- Supported input
- *
Before you start
Choose content or file organization
Decide whether the task concerns wording, document structure, hidden information or filenames. Keep an original copy and check the supported input. Extracted plain text is useful for reviewing words, but it does not reproduce every picture, font, equation or page arrangement in the source.
Where separators, normalization or text cleanup are available, try a short passage with headings, unusual characters and meaningful line breaks. For inspection or file comparison, include all relevant source files instead of assuming the visible page tells the whole story. For renaming copies, confirm the selected order and keep the mapping between old and new names.
Before text cleanup, decide which spaces, repeated lines or characters carry meaning; a spelling difference may be intentional. Where the task is file inspection or organization, record the files included and the literal naming or comparison choices instead. To diagnose a problem, compare a short source passage or a known file pair with the result. Check an intermediate copy separately: a previous extraction, normalization or rename may explain the difference before this tool is involved.
Check meaning as well as appearance
Read the result’s beginning, ending and transitions between sections. Compare names, table values and special characters with the source. If the tool produces a report, locate sample findings in the original file; an inspection result is a review aid, not automatic removal of the identified information.
For downloadable file copies, verify names, extensions and correspondence to the originals before using them elsewhere. If wording is missing or jumbled, distinguish unsupported embedded content from an encoding or ordering issue. A filename change does not change the underlying format, and a matching appearance does not prove two files have identical bytes.
Example input and output
identical bytes with different names → duplicate-group CSVExamples describe the workflow. Results depend on the source file and settings.
Check the saved result before using it
Compare names, byte counts and hashes within each reported duplicate group before deciding what to retain. Unique files remain in the report too, allowing you to confirm that all selected files were inspected.
If the result is different from what you expected
Apparently identical photos can differ in metadata or compression and therefore have different file hashes. Results do not choose or delete files automatically, so inspect locations and backups before any subsequent cleanup.
Limits to keep in mind
- Finds exact byte duplicates, not visually similar images. Deletes nothing. Up to 100 files, 250 MB total, 60 MB each.
Continue with a related tool
This guide explains the public browser tool. Keep a copy of the original and inspect the result before sharing it.