Turn a heading, a product name or a whole list of them into clean URL slugs. Accents are folded, punctuation becomes separators, and nothing is uploaded.
Waiting for a title
Paste a heading, a product name or a list of them — everything runs on your device.
The slug appears here
Punctuation becomes separators, runs collapse, and the edges are trimmed.
Slug Generator runs entirely on your device — nothing is uploaded.
You’re on the Free plan. Compare plans
A slug is the readable part of a URL — the how-to-read-a-cron-expression at the end of a path. Getting it right matters more than it looks: it is what people see in search results and in a pasted link, it is what a shared URL has to survive, and it is usually permanent, because changing it either breaks every existing link or commits you to a redirect you will maintain forever.
The rules are mechanical. Lowercase, because URLs are case-sensitive on most servers and a capital letter turns one address into two. Separate words with hyphens, which search engines read as word boundaries while underscores are read as part of a word. Strip anything that would need percent-encoding, since an encoded character in a slug is unreadable in a search result and fragile when pasted into chat applications and email clients that guess at where a URL ends.
Accented Latin characters are folded to their base letters by default, so café becomes cafe and Müller becomes muller. That is a deliberate default rather than a universal good: it keeps the slug typeable on any keyboard, and for a Latin-script language it loses very little.
What this tool will not do is pretend to transliterate scripts it cannot. Chinese, Japanese, Arabic, Hebrew, Thai and the rest have no mechanical mapping to Latin letters, and the honest options are to keep the original characters — which modern browsers and search engines handle correctly, encoding them in the address bar while displaying them as written — or to write a slug by hand. Many tools silently return an empty string here. This one keeps your characters and tells you what it did.
There is a mode for a list, because the real job is rarely one slug. Paste forty headings, one per line, and get forty slugs back in the same order, ready to paste into a spreadsheet or a migration script.
Hyphens. Search engines treat a hyphen as a word separator and an underscore as part of a word, so cron-expression-explainer reads as three words and cron_expression_explainer reads as one. Hyphens are also what every major CMS defaults to.
Because paths are case-sensitive on most web servers, so /About and /about are two different URLs. Lowercasing removes a whole class of duplicate-content and broken-link problems before it can start.
By default they are folded to their base Latin letter — é to e, ü to u, ñ to n — which keeps the slug typeable anywhere. Turn that off and the original characters are kept, which modern browsers and search engines handle correctly.
The characters are kept and a note explains why. There is no mechanical transliteration to Latin letters for these scripts, so the alternatives are keeping them — which works fine in practice — or writing the slug by hand. Returning an empty string, as some tools do, is the one wrong answer.
Usually not. Shorter slugs read slightly better, but removing filler words can make a title ambiguous, and the ranking benefit is negligible. The option is off by default for that reason.
Long enough to describe the page and short enough to read in a search result — roughly three to six words. There is no technical limit worth worrying about, but a slug that wraps in a result listing is doing nothing for anyone.
You can, but every existing link to the old one breaks unless you add a permanent redirect. Treat a published slug as close to immutable, and spend the extra ten seconds getting it right the first time.