transliteration · Japanese (Kanji, Katakana, Hiragana)
Japanese titles and native-script URLs
Japanese titles are better left as native-script URLs or URL-encoded paths. Slugmint focuses on Latin diacritics plus Cyrillic, Greek, Hebrew, Arabic, and German ß.
advanced
Japanese (Kanji, Katakana, Hiragana)
Sample input → output
slugmint "東京2026年のニュース" tokyo-2026-nen-no-nyusu slugmint "猫カフェの食べ物" neko-kafe-no-tabemono slugmint "アクセシビリティ" akushibiriti
Transliteration rules
Hepburn: あ→a, い→i, う→u, え→e, お→o, か→ka, き→ki, く→ku, け→ke, こ→ko, ... し→shi, ち→chi, つ→tsu, ふ→fu (consonant exceptions). Long vowels: drop macron, write doubled vowel or single per modified Hepburn.
Examples
| Input | Result |
|---|---|
| 東京 → tokyo (kanji compound, dictionary lookup) | ✓example |
| ニュース → nyusu (katakana, foreign loanword) | ✓example |
| ねこ → neko (hiragana) | ✓example |
| **WARNING**: 東京 has multiple readings — `tokyo` (place) vs `tōkei` (statistics). Dictionary picks most-common; rare contexts mistransliterate. | ⚠caveat |
| ヴァ → va (KATAKANA-V — sometimes written `wa`, no universal rule) | ⚠caveat |
| Long vowels: トーキョー → tōkyō (with macron) vs tokyo (without). Slugs strip macrons (always). | ⚠caveat |
Edge cases & caveats
Note: see the warning above. Treat this page as a starting point, not a security control.
Common use cases
- Japanese blog URL slugs
- Cross-language SEO (en + jp)
- Migrating from Japanese-character URLs
- International e-commerce product slugs
Transliterate any title to a clean URL slug
slugmint does not transliterate Japanese titles; keep CJK as native-script URLs or encoded paths. It focuses on Latin diacritics plus Cyrillic, Greek, Hebrew, Arabic, and German ß. Lowercase, dash-separated, ASCII-safe.
Open slugmint
Related
Chinese (Simplified / Traditional) · Hebrew (RTL script) · Russian (Cyrillic) · Arabic (RTL script) · ↗ validate output slug format