How to use and verify
Select multiple files to compare their original names with NFC names. Unicode NFC combines canonically equivalent sequences. It can compose decomposed Hangul syllables, but does not guess intended text or repair arbitrary spelling. Compatibility characters are not rewritten with NFKC.
When normalized names collide, including case-only differences, a suffix such as (2) is inserted before the extension. Input order determines suffixes. Every selected file keeps a unique archive entry without overwriting another file. Folder hierarchies are not imported. File bytes are copied unchanged into the archive.
The limits are 100 files and 100 MiB total. ZIP creation takes place in memory and does not compress the contents, so the archive can be slightly larger than the files combined. The original disk files are never renamed. Check the proposed names and numbered collisions before downloading. Extract the archive into a separate folder and verify its names before replacing any originals.
2026 example: duplicate.txt → duplicate (2).txt
FAQ
How do I use this tool?
Select multiple files to compare their original names with NFC names. Unicode NFC combines canonically equivalent sequences. It can compose decomposed Hangul syllables, but does not guess intended text or repair arbitrary spelling. Compatibility characters are not rewritten with NFKC.
Are files or names uploaded?
No. Processing happens in browser memory without sending inputs to a server or external API. Close the tab after using a shared device.
What should I check at the end?
The limits are 100 files and 100 MiB total. ZIP creation takes place in memory and does not compress the contents, so the archive can be slightly larger than the files combined. The original disk files are never renamed. Check the proposed names and numbered collisions before downloading. Extract the archive into a separate folder and verify its names before replacing any originals.