File names from a Mac break into separated Korean letters

Built!

Jamo Restore turns separated Korean letters in file names and text back into normal Korean, and bundles renamed files into a ZIP.

Current workflow

Files created on a Mac often arrive on Windows with names like a Korean report file split into separate consonants and vowels — unreadable and unsearchable. People usually fix this by retyping each file name by hand, running a Python unicodedata snippet, or installing a converter program. The file itself isn't damaged: it's a Unicode normalization difference. macOS stores Korean text decomposed into individual jamo (NFD), while Windows uses composed syllables (NFC). Only the name's representation differs, so fixing the name is enough.

Solution

Fix Split Korean Letters

How to use

1. Upload the files with broken names. You can upload several at once. 2. Check the restored names in the preview. 3. Download the renamed files as a ZIP. If the text content itself is broken, you can also paste it in to restore it.

Example

- Input: a batch of files transferred from a Mac, with names decomposed into separate jamo characters - Result: names normalized into composed, readable Korean (a decomposed "report_final.pdf" becomes the proper composed file name) — searchable again. Broken names inside ZIP folder paths are fixed too.

Open tool
View details
Limits
- If a restored name matches an existing file, you'll get a name collision. Check the preview first. - Broken characters inside a file's content can be attempted with the paste-in text restore, but results vary depending on how the text was damaged.
Cost type
Free

If the problem isn't jamo decomposition but the encoding itself is broken — characters replaced by completely different symbols or question marks — restoration is limited, because there's no way to know what the original was. A quick way to tell: if you can still see the Korean jamo separated, it's a normalization issue and can be fixed; if the jamo aren't visible at all, it's encoding damage and re-downloading the original is faster. Decomposition can also reappear when files pass through cloud services (Google Drive, Notion, Slack) or ZIP archives, so normalizing important files right after receiving them is the safe habit.

Support

I have this problem too · 0 people

Sign in to support or ask a question

Comments

Be the first to comment.

Additional information

Delete a post made without signing in