Create Readable URL Slugs From Titles
Convert a heading into a lowercase ASCII slug and plan for collisions and published redirects.
A URL slug is a short path segment based on a title. This generator lowercases text, decomposes characters, removes combining marks, replaces runs of remaining non-ASCII-letter-or-digit characters with hyphens, and trims edge hyphens. It creates readable slugs for many English and accented Latin titles, but the process loses information.
In this guide
See the transformation
“Hello World!” becomes “hello-world.” The exclamation mark is removed through separator replacement, and the space becomes a hyphen. A title such as “Café Notes” becomes “cafe-notes” after accent decomposition and mark removal. Runs of punctuation collapse to one separator.
The output contains lowercase a–z, digits, and hyphens. Non-Latin letters without ASCII transliteration are omitted as content, though their positions may create separators. Some letters that do not decompose into an ASCII base are also lost. Check the final slug manually for a meaningful path.
InputHello World!Output
hello-world
Expect collisions
Different titles can reduce to the same slug: punctuation, case, and many accents are discarded. For example, “Cafe Notes” and “Café Notes” both become “cafe-notes.” A publishing system therefore needs a collision policy, such as appending a stable identifier. The generator does not check existing routes.
An empty result is possible when the input contains no retained ASCII letters or digits. In that case, choose a meaningful manual slug rather than publishing an empty path segment.
Published slugs become addresses
A slug is part of a URL. Changing it after publication can break saved links, search results, and internal navigation unless the old path redirects to the new one. Update internal links and the sitemap when changing an established route. Keep a stable slug even if an article title receives small editorial changes.
Slug generation and URL percent encoding solve different problems. A slug is a lossy naming convention. Percent encoding represents component characters as bytes so they can travel in a URL and be decoded. Do not expect to recover the original title from a slug.
Review before using it
Generate from the proposed heading, read the result aloud, and check for meaning, duplicates, and route stability. Use Kebab Case Converter when you want a hyphenated word form for identifiers, then inspect its different token rules. For public paths, the final editorial choice should be deliberate.
Avoid generating a new slug each time a heading is revised. A stable published route is often more valuable than perfect agreement with the latest headline. If a route must change, document the old and new paths before adding the redirect, then verify that navigation and search listings point to the intended destination.
- Check for an empty result.
- Check existing routes for collisions.
- Preserve redirects when changing a published slug.
Frequently asked questions
Does the tool transliterate every language?
No. It strips many accents but does not provide general non-Latin transliteration.
Can two titles produce one slug?
Yes. Case, punctuation, and accents can collapse to the same output.
Is a slug reversible?
No. Removed punctuation and letters cannot be reconstructed from the slug.