Slug Generator
Build lowercase hyphenated URL slugs with Unicode-preserving or ASCII-only output.
Punctuation becomes separators, repeated separators collapse, and the result is lowercased.
Slug Style
Generated Slug
Generated slug will appear here.
Encoded Path Segment
Percent-encoded form will appear here.
A slug becomes part of an address people and crawlers may keep
Lowercase words and hyphen separators can make a path easier to read, but a generated slug is not an SEO score and it does not decide whether a page should rank. Google recommends descriptive URLs, words in the audience's language, and hyphens between words. Those are naming principles, not a reason to stuff keywords into a path or rewrite a stable URL only to make it look cleaner.
The safest time to choose a slug is before publication. Once bookmarks, internal links, backlinks, analytics, caches, and search indexes know an address, the slug is part of the page's public identity.
Reference: Google Search Central URL structure guidance.
The two character modes make different compromises
Unicode mode keeps letters and numbers from the original language after normalization and lowercasing. ASCII mode is deliberately lossy: it removes combining marks when decomposition provides them, then keeps only a-z and 0-9. It is not a general transliteration engine.
Café APIs
Unicode: café-apis · ASCII: cafe-apis
日本語 API
Unicode: 日本語-api · ASCII: api
The Japanese text disappears in ASCII mode because this page does not transliterate it into Latin characters.
C++ & C#
Both modes produce c-c because punctuation is treated as a separator. Technical names where symbols carry meaning need a manual decision.
Readable Unicode and a serialized URL are two views of the same path
A slug such as café-apis can stay readable in an editor while its non-ASCII bytes appear percent-encoded when serialized into a URL. The encoded preview uses encodeURIComponent(), which UTF-8 percent-encodes characters that need escaping in a URL component. A framework may perform its own URL serialization, so avoid encoding the same path segment twice.
Reference: WHATWG URL Standard.
Treat a published slug change as a URL migration
Renaming a live slug can break bookmarks, inbound links, cached addresses, and references inside your own site. When a published route must move, update internal links and configure the redirect that matches the migration rather than treating regeneration as harmless text cleanup.
Your CMS or router still owns the rules this page cannot know
- Uniqueness: two different titles can collapse to the same slug, so collision handling belongs in the application or database.
- Reserved names: routes such as
admin,api, or framework-specific paths may be unavailable even when the string looks valid. - Length and hierarchy: a CMS may cap segment length, scope uniqueness under a parent, append an ID, or derive the final route from more than the title.
- Meaningful punctuation: apostrophes are removed and other punctuation becomes separators here. Product names, programming languages, model numbers, and trademarks may need an intentional override.