Text to Slug

Convert any text or title into a clean, URL-friendly slug. Handles spaces, special characters, diacritics, and unicode.

Input Text
Separator
Slug Output

Frequently Asked Questions

A URL slug is the human-readable part of a URL that identifies a specific page. For example, in https://example.com/blog/how-to-build-rest-api, the slug is how-to-build-rest-api. Good slugs are lowercase, use hyphens, and contain only letters, numbers, and separators.
URLs are technically case-sensitive (RFC 3986), so /Blog/Post and /blog/post are different URLs. Lowercase slugs avoid duplicate content issues and user confusion. Google recommends lowercase URLs.
Diacritics (accented letters like é, ü, ñ) are normalized using Unicode NFD decomposition, which separates base letters from their accent marks. The accent marks are then stripped, leaving the clean base letter — e.g., café becomes cafe.
A slug is the final segment of a URL: in /blog/how-to-bake-bread, the slug is how-to-bake-bread. A permalink is the full, permanent URL including the domain and path: https://example.com/blog/how-to-bake-bread.
Special characters should be removed or replaced. Common replacements: & becomes and; % becomes percent; # is removed. Characters like ?, =, and & are reserved in URLs and will break query string parsing if included literally.
There is no official maximum, but shorter slugs are generally better. Most SEO professionals recommend keeping slugs under 5–6 words and under 75 characters. Remove stop words (a, the, and, of) to shorten slugs without losing meaning.
Yes. Numbers are valid in slugs and are commonly used for years (/blog/2024/my-post), product IDs (/product/42), and version numbers (/docs/v3). This tool preserves all numeric characters in the output.
This tool handles diacritics (é → e, ü → u) via Unicode NFD normalization, but does not transliterate full non-Latin scripts like Arabic, Chinese, or Cyrillic. For those, server-side libraries like PHP's transliterator_transliterate() are needed.
A canonical URL is the preferred URL for a page when multiple URLs could show the same content. Consistent, clean slugs help prevent duplicate content. Always use lowercase slugs and set up 301 redirects from alternate URL formats to the canonical one.
Use hyphens. Google treats hyphens as word separators, so red-wine is indexed as two words. Underscores are treated as connectors — red_wine is indexed as a single word "red_wine". Hyphens improve keyword matching in search.

About This Slug Converter

This free slug converter transforms any heading or title into a URL-friendly slug by converting to lowercase, replacing spaces with hyphens, and removing special characters. Handles accented characters, punctuation removal, and consecutive-hyphen collapsing.

When to use this tool

  • Generating blog post or article URL slugs from their titles
  • Creating clean file names from arbitrary descriptive strings
  • Building URL-safe identifiers for CMS content or API routes
  • Normalising slugs consistently across a site migration

Standards & References

Related Text Tools

Case Converter Find & Replace Whitespace Cleaner URL Encoder

Related Articles

In-depth guides and technical articles.

View all →
Text Aug 2, 2026
Hierarchical vs Flat URL Structure, Taxonomy Collisions, and Multilingual Slug Design — The Slug Decisions That Last Forever
Slug architecture for content series, taxonomies, and multilingual sites involves permanent commitments — a slug embedded in inbound links can never be silently changed. Here's the hierarchical vs flat URL structure trade-off (hierarchy embeds category in URL, making recategorisation cost real), how category/tag slug collisions form when the same term appears in both taxonomies, author slug edge cases at scale (departures, pen names, duplicates), and why path-prefix multilingual URL structure beats subdomains for authority consolidation.
Text Jun 26, 2026
Slug Design Beyond Single Pages — How Hierarchy, Tags, Authors, and Languages Shape Your URL Structure
Flat vs nested slug structures, author page cardinality problems, tag proliferation diluting content quality signals, and when CMS-generated slugs from titles produce wrong results for numbers and acronyms. Here's the slug architecture decisions that affect content series, taxonomies, and international content, plus why the language identifier belongs in the path prefix rather than embedded in the slug itself.
Text Jun 22, 2026
When Changing a Slug Is Worth the SEO Cost — and the Exact Sequence to Follow When It Is
Changing a URL slug after publishing has permanent SEO consequences — but so does keeping a slug that contains a wrong date, a discontinued product name, or a keyword that's shifted. Here's when slug changes are genuinely warranted (vs when they're not worth the disruption), the correct 301-redirect-then-update-internal-links sequence, why CMS auto-slug-regeneration on title edit destroys rankings, and why year-in-slug is almost always a decision you'll regret.
Text Jun 13, 2026
Slug Collisions: What Happens When Two Pages Generate the Same URL, and How CMSs Handle It
Two posts titled "How to Make Sourdough Bread" generate identical slugs by default — and what happens next varies by CMS, from silent numeric suffixes (chocolate-chip-cookies-2) to outright rejection requiring manual resolution. Here's how different collision-handling approaches work, why date/ID-based URL structures avoid most collisions structurally, and the tricky edge case of new content colliding with an old slug's redirect.
Text Jun 10, 2026
International URL Slugs: Transliteration vs Native Characters for Non-Latin Scripts
Chinese, Arabic, and Cyrillic characters in URLs are technically valid and browsers display them readably — but transliteration vs native-language slugs involves real SEO and UX trade-offs. Here's how percent-encoding works, transliteration libraries for different languages, and how major frameworks handle non-ASCII slugs.