How-to · Web

How to create a URL slug from a title

Case Converter2 min read

The short answer

Paste the title into Case Converter and click Slugify. You get a lowercase, hyphen-separated, ASCII-only slug — accents are transliterated (café → cafe), and the tool tells you when characters had to be dropped. All local, nothing uploaded.

  1. 1

    Click the Case Converter icon and paste your title.

  2. 2

    Pick your separator — hyphen (recommended) or underscore.

  3. 3

    Click Slugify to get a lowercase, ASCII-only slug.

  4. 4

    Review the note if accents were transliterated or characters dropped.

  5. 5

    Copy the slug into your CMS or route before publishing.

A URL slug looks trivial to make — lowercase the title, swap spaces for hyphens — until real titles show up. What happens to "Café & Résumé: A How-To"? Naive find-and-replace leaves you with stray punctuation, double hyphens, or percent-encoded accents that look broken in the address bar. A good slug is lowercase, ASCII-only, single-separator, with no leading or trailing separators. Here is how to get one reliably.

Paste the title and click Slugify

Open the Case Converter popup, paste your title, and click Slugify. The transformation lowercases everything, collapses every run of non-alphanumeric characters — spaces, punctuation, symbols — into a single separator, and trims separators from both ends. "Café & Résumé: A How-To" comes out as cafe-resume-a-how-to: one clean token per word, nothing dangling.

Accents become plain ASCII, honestly

Accented characters are not dropped — they are transliterated by stripping the accent from the base letter, so café becomes cafe and naïve becomes naive. And rather than doing this silently, the tool reports that transliteration happened, so you know the slug differs from the title in a specific, predictable way.

Know when characters can't survive

Some characters have no meaningful ASCII form. Chinese, Japanese and Korean text cannot be transliterated without a pronunciation dictionary, so those characters are dropped — and Case Converter says so explicitly instead of leaving you to notice a suspiciously short slug. That honesty is the difference between a tool you can trust for production URLs and one you have to double-check.

Choose hyphens or underscores

Hyphens are the safe default: search engines treat a hyphen as a word separator, while underscores can join words together, and readers parse hyphenated slugs more easily. Google's own URL guidance has recommended hyphens for years, and virtually every modern CMS follows suit. But if your system's convention is underscores — some legacy platforms and internal routing schemes insist on them — switch the separator and Slugify uses _ throughout, with the same collapsing of repeated separators and the same trimming at both ends.

Keep slugs stable and local

Because a slug is part of a permanent URL, generate it once, before publishing — changing it later breaks links and splits analytics. Everything here runs inside the popup on your device: no account, no server, and the only permission the extension holds is local storage for your preferences. Your unpublished headlines stay private until you decide to ship them.

Clean slugs from any title

Lowercase, ASCII, single-separator slugs with honest transliteration notes — fully local.

See Case Converter →