Generate
URL Slug Generator for Clean, SEO URLs
Turn a title into a clean, URL-friendly slug — separator, casing and length options.
Runs entirely in your browser — nothing you paste is uploaded or stored.
What is slug generator?
A slug is the readable part of a URL that identifies one specific page — the `10-best-javascript-frameworks` in `/blog/10-best-javascript-frameworks`. It needs to be lowercase, free of spaces and punctuation, and safe for every browser and server to handle without escaping. Typing one out by hand from a title means manually replacing spaces, stripping punctuation, and remembering to drop accents — easy to get inconsistent across a site. This tool does that conversion for you: paste a title or heading, and it strips accents, substitutes a few common symbols with words, and replaces everything else with a single separator, live as you type.
When to use it
- Turning a blog post or article title into the slug used in its URL.
- Generating a consistent file or folder name from a document title, free of spaces and special characters.
- Building a URL-safe identifier from a product name or category label for an e-commerce site.
- Converting a heading into an anchor-safe ID for in-page navigation or a table of contents.
How to use this tool
- Paste or type the title or text you want to convert.
- Choose a separator — hyphen or underscore. Hyphens are the SEO convention for URLs; underscores are more common for filenames and code identifiers.
- Turn off "Lowercase" if you need to preserve the original casing.
- Optionally set a max length so the slug never exceeds a limit your system enforces — it truncates on a word boundary, never mid-word.
- Copy the result, or copy a link that restores this exact text and settings.
Example
A typical blog post title.
Input
10 Best JavaScript Frameworks to Learn in 2026!Output
10-best-javascript-frameworks-to-learn-in-2026The exclamation mark and every other symbol is dropped, and the whole string is lowercased and hyphen-joined.
Why truncation stops at a word boundary
A slug cut off mid-word — 10-best-javascript-framewo instead of
10-best-javascript-frameworks — reads as broken rather than intentional, and looks worse
in a URL bar or a shared link than a slightly shorter, complete one. When a max length is
set, this tool always backs up to the last full word that fits, so the result is a clean
prefix of the full slug rather than a cut string.
Frequently asked questions
Why does my slug come out empty?
This happens when nothing in the input survives slugifying — most commonly because the text is entirely in a script this tool doesn't transliterate into Latin letters, like Chinese, Japanese, Arabic, or Cyrillic. Accented Latin letters (é, ñ, ü) are converted to their plain equivalent, but non-Latin scripts have no plain-ASCII equivalent to convert to, so the tool reports the problem instead of silently returning nothing.
Should I use a hyphen or an underscore?
Hyphen, for anything URL-facing — Google has stated it treats hyphens as word separators in a URL but generally does not split words on underscores, which can hurt how a page is indexed for the words in its slug. Underscores remain a common convention for filenames, code identifiers, or systems where hyphens have another meaning.
What happens to accented and special characters?
Accented Latin letters are converted to their unaccented equivalent (é → e, ñ → n, ü → u) via Unicode normalization, not simply dropped. A few common symbols are converted to words instead of removed outright — "&" becomes "and", "@" becomes "at", "%" becomes "percent" — since dropping them silently can accidentally merge two unrelated words together.
Why does the max length sometimes produce a shorter slug than I set?
Truncation always stops at a word boundary rather than cutting a word in half, so the result is the longest whole-word prefix that fits within the limit — which is very often a few characters short of the exact number you entered. A slug ending mid-word (like `javascript-framewo`) is harder to read and looks broken in a URL.
Is this the same as what my CMS or static site generator does automatically?
Usually close, but not guaranteed identical — most platforms use their own slugify logic with their own edge-case decisions (whether "&" becomes "and" or is dropped, whether numbers are kept, how they handle a title that's entirely non-Latin). If your slug needs to exactly match one specific platform's behavior, use this as a starting point and verify against that platform for edge cases.
Find these tools useful? A coffee helps keep them free and ad-light.
Buy me a coffee