ASCII versus Unicode
ASCII mode transliterates many Latin, Greek and Cyrillic characters for widely compatible routes. Unicode mode preserves letters from all scripts and percent-encodes safely when needed.
Create readable, route-safe slugs with Unicode-aware normalization, broad Latin/Greek/Cyrillic transliteration, exact length control, custom replacements, collision-safe bulk generation and a character-level transformation inspector. Free, local and ready for production workflows.
One replacement per line as source=replacement, applied before transliteration.
| Line | Input | Slug | Encoded path | Collision |
|---|
| # | Character | Code point | UTF-8 bytes | Category | ASCII transliteration |
|---|
ASCII mode transliterates many Latin, Greek and Cyrillic characters for widely compatible routes. Unicode mode preserves letters from all scripts and percent-encodes safely when needed.
There is no universal reversible transliteration for every language. Always review names, brands and words where language-specific spelling matters.
The cap is Unicode-code-point aware and prefers the previous word boundary rather than slicing in the middle of a word when practical.
If multiple titles become the same slug, bulk mode can append numeric suffixes while respecting the configured maximum length.
The tool encourages readable lowercase paths but does not claim a particular slug length or stopword rule guarantees search ranking.
All transformation and exports happen locally. No text is sent to OneFreePlace.