Have you ever sent a file from a Mac to Windows and seen "résumé.pdf" turn into "re´sume´.pdf"? You can fix that problem with this tool!
This happens because Windows/Linux store Unicode filenames using NFC (composed form), while macOS stores them using NFD (decomposed form).
Upload a file to check whether its filename is normalized as NFC, NFD, NFKC, or NFKD. You can also download the file with your preferred normalization. Downloading in NFC ensures filenames created on Mac won’t break on Windows.
🔒 Don’t worry! Files are never uploaded to a server. All filename transformations happen locally in your browser. If you don’t believe it, open Developer Tools (F12) and verify it yourself!
| # | Original filename | Detected normalization | Actions |
|---|---|---|---|
| No files yet. | |||
⚠️ It has been confirmed that when uploading files in Chrome and Firefox on macOS, filenames are always sent in NFD form. As a result, even NFC files may be detected as NFD. This issue only affects normalization detection and does not impact the downloaded files. Safari does not appear to have this issue. If you would like to verify the normalization form on macOS, we recommend using Safari.
⚠️ Older Macs (before macOS High Sierra, 2017) using HFS/HFS+ always store filenames in NFD format. In such cases, please use a filesystem that supports NFC.