How to use this tool
- Enter the title or short phrase that describes the page.
- Choose ASCII for a restricted Latin-letter output or Unicode to retain letters from other writing systems.
- Generate and review the slug, then check its availability and any reserved path rules in your website system.
Understanding the output
The result is a single path segment, not a complete URL. Spaces and punctuation become hyphens, repeated separators collapse, and leading or trailing hyphens are removed. Review the result before assigning it to a page because different titles can generate the same slug.
When a path component or query value needs percent escapes, use URL Encoder and Decoder rather than treating this slug transformation as URL encoding.
A title with an accent and punctuation
Café & Summer Guide! becomes cafe-summer-guide in ASCII mode. Unicode mode produces café-summer-guide. The ampersand is treated as a separator; the tool does not insert the word and.
ASCII conversion is not universal transliteration
ASCII mode applies compatibility decomposition and removes combining marks before keeping a–z and 0–9. This converts many accented Latin letters, such as é to e, but does not translate words or reliably transliterate every alphabet. A title containing only Chinese characters has no ASCII letters left and produces an error rather than an invented name. Unicode mode is appropriate when those characters should remain.
Changing a slug changes a page address
Check whether a generated slug already belongs to another page. This tool has no access to your website’s route registry and cannot append a guaranteed unique suffix. For an existing published page, replacing its address requires a deliberate redirect and canonical-link update. Descriptive paths help readers understand a URL, but generating a slug alone does not promise a search ranking improvement.
Method and supported input
The input limit is 100,000 UTF-16 code units. ASCII mode uses NFKD normalization, removes Unicode marks, lowercases text, and replaces runs outside a–z and 0–9 with a hyphen.
Unicode mode uses NFC normalization and lowercase conversion, retaining Unicode letters, numbers, and combining marks. Other runs become hyphens. An output without letters or numbers is rejected.
- The generated text will be reviewed as one path segment in an existing site.
- Lowercasing and punctuation removal are acceptable for the intended label.
Limitations
- The output is not percent-encoded, checked for uniqueness, or checked against reserved routes.
- ASCII mode can discard meaningful characters and does not implement language-specific transliteration.
- No stop words are removed, and no target length or ranking score is assigned.
Common questions
Will this encode an entire URL?
No. It produces one readable slug. It does not preserve a URL’s scheme, query, fragment, or slash structure.
Why did two titles create the same result?
Case, punctuation, and some accents are removed or normalized. A CMS or route registry must resolve collisions before publication.
Should every slug use English characters?
Not necessarily. Unicode mode retains other writing systems. Choose a policy your site and audience support, and keep published addresses stable.