URL Slug Generator

What this tool does

URL Slug Generator converts one title per line into readable, hyphen-separated slugs. It transliterates accented letters, spells out symbols such as & and %, can remove stop words, cuts long slugs at a word boundary and makes duplicates unique with -2, -3 suffixes.

A slug is the readable part of a URL that identifies a page, such as /blog/better-sleep-tips. Good slugs are short, lowercase and descriptive, which helps people judge a link before they click and keeps URLs tidy when they are shared. Producing them by hand from titles full of accents, apostrophes, ampersands and question marks is error-prone, and a CMS’s automatic slugs are often too long.

This tool processes a whole list at once. It decomposes accented letters with Unicode NFKD normalisation (so “Café Crème” becomes cafe-creme), maps letters that do not decompose such as ß and ø, spells out symbols, and optionally keeps non-Latin scripts. All processing happens locally, so it can handle tens of thousands of lines for a site migration.

How to use URL Slug Generator

1. Paste your titles, one per line, or open a text or CSV file.
2. Choose the Word separator; Hyphen is the recommended default.
3. Set Maximum length and decide whether to Remove stop words.
4. Enable German umlauts as ae, oe, ue for German content, or Keep non-Latin letters for other scripts.
5. Add an optional Path prefix and trailing slash, then copy or download the slugs.

Tips for better results

• Google recommends hyphens rather than underscores to separate words in URLs.
• Three to five meaningful words is usually enough; a slug does not need every word of the title.
• Leave dates and numbers like “2026” out of evergreen slugs so the URL still fits after you update the article.
• Keep “Make duplicates unique” on when generating slugs for many products with similar names.

Common use cases

• Creating slugs for a batch of blog posts before importing them into a CMS.
• Planning URL structures for a site migration spreadsheet.
• Normalising product names into handles for an online shop.
• Generating file-system-safe names from document titles.

Common mistakes to avoid

• Changing the slug of a published page without adding a 301 redirect from the old URL.
• Removing stop words that carry meaning, such as “not” or “how”, which changes what the slug says.
• Using mixed case; many servers treat /About and /about as different URLs.
• Keeping non-Latin characters without realising they appear percent-encoded when the URL is copied into some apps.