The human-readable part of a URL that identifies a page — in example.com/blog/how-to-bake-bread, the slug is how-to-bake-bread. Good slugs are short, lowercase, hyphen-separated and descriptive: readers can guess the topic and search engines can, too.

Hyphens or underscores?

Hyphens. Google has stated for years that hyphens are treated as word separators while underscores are not — red-shoes reads as “red shoes”, red_shoes risks reading as “redshoes”. The underscore option exists for legacy systems that require it, but hyphens are the safe default.

What happens to accents and special letters?

They’re transliterated, not deleted: café → cafe, Straße → strasse, Søren → soren, Łukasz → lukasz. Apostrophes vanish cleanly (don’t → dont, not don-t). Scripts that don’t map to Latin letters — Chinese, Devanagari — are dropped, so check the preview when slugging non-Latin titles.

How long should a slug be?

Short enough to read at a glance — 3 to 6 meaningful words is a common sweet spot. Drop filler words (a, the, of) when they add nothing. The max-length option cuts at your limit without leaving half a word or a trailing hyphen behind.

Should slugs always be lowercase?

Yes, in practice. URL paths are case-sensitive, so /My-Post and /my-post can be two different pages — a recipe for duplicate-content problems and broken links. Lowercase-only eliminates the whole class of errors, which is why it’s on by default.

Does changing a published URL slug hurt SEO?

Changing a slug changes the URL, so the old address 404s unless you add a 301 redirect — links and ranking signals then transfer to the new URL. Pick slugs you can live with; when you must change one, always redirect the old URL.

Is my text sent to a server?

No — slugs are generated instantly in your browser as you type. Draft titles for unpublished posts stay on your device; nothing is transmitted or stored, and the tool works offline once the page has loaded.

URL Slug Generator

Turn any title into a clean, SEO-friendly URL slug — accents handled, separator and length options included.

Files never leave your device Instant — no upload waitFree, no sign-up

Title or phrase

Separator

LowercaseLimit length

Turn any title into a clean, SEO-friendly URL slug

Paste a headline — punctuation, accents, emoji and all — and get a publication-readyURL slug as you type: lowercase, hyphen-separated, with every unsafe character handled. “10 Café Recipes You Can’t Miss!” becomes10-cafe-recipes-you-cant-miss — no manual find-and-replace, no stray hyphens.

Accents handled properly, not deleted

Cheap slug tools simply strip anything non-ASCII, mangling names and words. This onetransliterates: é → e, ü → u, ß → ss, ø → o, ł → l. Apostrophes collapse the right way (don’t → dont, not don-t), and repeated separators are squeezed to one. Your slugs stay readable in every language that maps to Latin letters.

Options for real publishing workflows

Hyphen or underscore separator, lowercase toggle, and a max-length limit that cuts at a word boundary — never mid-word, never leaving a trailing hyphen. A live character count helps you keep slugs comfortably short. Copy with one click when it looks right.

Why slugs matter

The slug is one of the few URL parts humans actually read — in search results, in chat previews, in the address bar. Descriptive, hyphenated, lowercase slugs are easier to share, harder to mistype and clearer to search engines. Set them once, well, and never touch them again.

Related free tools

Encoding a query string rather than naming a page? That’s theURL encoder / decoder. Fixing capitalization in bulk? Thecase converter handles Title Case, UPPER and more. Cleaning a list of titles first? Try remove duplicate lines.

Frequently Asked Questions

What is a URL slug?
The human-readable part of a URL that identifies a page — in example.com/blog/how-to-bake-bread, the slug is how-to-bake-bread. Good slugs are short, lowercase, hyphen-separated and descriptive: readers can guess the topic and search engines can, too.
Hyphens or underscores?
Hyphens. Google has stated for years that hyphens are treated as word separators while underscores are not — red-shoes reads as “red shoes”, red_shoes risks reading as “redshoes”. The underscore option exists for legacy systems that require it, but hyphens are the safe default.
What happens to accents and special letters?
They’re transliterated, not deleted: café → cafe, Straße → strasse, Søren → soren, Łukasz → lukasz. Apostrophes vanish cleanly (don’t → dont, not don-t). Scripts that don’t map to Latin letters — Chinese, Devanagari — are dropped, so check the preview when slugging non-Latin titles.
How long should a slug be?
Short enough to read at a glance — 3 to 6 meaningful words is a common sweet spot. Drop filler words (a, the, of) when they add nothing. The max-length option cuts at your limit without leaving half a word or a trailing hyphen behind.
Should slugs always be lowercase?
Yes, in practice. URL paths are case-sensitive, so /My-Post and /my-post can be two different pages — a recipe for duplicate-content problems and broken links. Lowercase-only eliminates the whole class of errors, which is why it’s on by default.
Does changing a published URL slug hurt SEO?
Changing a slug changes the URL, so the old address 404s unless you add a 301 redirect — links and ranking signals then transfer to the new URL. Pick slugs you can live with; when you must change one, always redirect the old URL.
Is my text sent to a server?
No — slugs are generated instantly in your browser as you type. Draft titles for unpublished posts stay on your device; nothing is transmitted or stored, and the tool works offline once the page has loaded.