Konverter
Slugify
The Slugify tool converts any text into a clean, URL-safe slug by lowercasing letters, replacing spaces with hyphens, removing accents and diacritics, and stripping all characters that are not alphanumeric or hyphens. It produces the SEO-friendly URL segments used in blog posts, product pages, and routes in web applications. The tool handles Unicode normalization to correctly convert accented characters from many languages.
What is a URL slug?
A URL slug is the human-readable part of a URL that identifies a specific page, typically derived from the page title. For example, the slug for 'How to Deploy a Node.js App' would be 'how-to-deploy-a-node-js-app'. Good slugs are lowercase, use hyphens as word separators, contain only alphanumeric characters and hyphens, and are descriptive and concise. SEO best practices recommend that slugs reflect the main keywords of the page. Slugs should avoid stop words (a, the, of) when possible and must not contain special characters that would need URL percent-encoding.
How does the tool work?
The tool processes the input text through several normalization steps. First, Unicode NFC normalization is applied. Accented and diacritic characters are then decomposed using Unicode NFD normalization and the combining diacritical mark characters are stripped, leaving the base ASCII letter (e.g. é → e, ü → u, ñ → n). The text is converted to lowercase. Non-alphanumeric characters (punctuation, symbols) are replaced with hyphens. Consecutive hyphens are collapsed to a single hyphen. Leading and trailing hyphens are removed. The result is a clean, URL-safe slug that works correctly in all browsers and web frameworks.
Typical Use Cases
- Generating URL slugs for blog posts, documentation pages, and product listings
- Creating file names or directory names from document titles
- Producing route segments for web application paths (React Router, Next.js, etc.)
- Generating database keys or identifiers from human-readable labels
Step-by-step Guide
- Step 1: Type or paste the title or text you want to slugify into the input field.
- Step 2: The URL slug appears instantly in the output field.
- Step 3: Optionally configure options such as max length or separator character.
- Step 4: Copy the slug with the copy button or use it directly in your project.
Example
Input
Héllo Wörld! This is a Test.
Output
hello-world-this-is-a-test
Tips & Notes
- Keep slugs concise and keyword-focused – Google recommends URLs under 60 characters for best SEO.
- Avoid changing a slug after it is published; URLs are indexed by search engines and changing them without a 301 redirect loses link equity.
- For multilingual sites, transliterate non-Latin scripts (Cyrillic, Arabic, CJK) to ASCII rather than percent-encoding them for cleaner URLs.
Frequently Asked Questions
Should I include stop words (a, the, of) in slugs?
SEO guidance has evolved – modern consensus is to include them if they are part of the natural keyword phrase and removing them would make the URL look unnatural. Short stop words in the middle of a phrase are generally fine to keep.
Can I use underscores instead of hyphens in slugs?
Hyphens are strongly preferred for web URLs. Google's John Mueller has confirmed that Google treats hyphens as word separators but underscores as part of the word, meaning 'hello_world' is seen as one word rather than 'hello' and 'world'.
How are Chinese, Japanese, or Arabic characters handled?
Non-Latin scripts that cannot be directly transliterated to ASCII characters are typically removed from the slug. For multilingual sites, it is better to use transliteration libraries (e.g. pinyin for Chinese) before slugifying.
Slugify
Convert any string into URL-safe, filename-safe, and ID-safe slugs — with umlaut transliteration and configurable options.
Open Tool