Is the text uploaded?

No. The slug is generated entirely in your browser via JavaScript. Use it for drafts, internal titles, and unpublished work without worry.

How are diacritics handled?

We Unicode-normalise the input to NFD (separating base letters from combining marks), drop the combining marks, and keep the ASCII base. That turns é into e, ñ into n, ü into u, and so on automatically.

Are kanji and kana romanised?

Not by this tool. If you want to keep them as-is in the slug, turn off Strip non-ASCII — the browser will percent-encode them in URLs. If you need romanisation, run the Kanji-to-rōmaji converter first and paste the result here.

How long should a slug be?

Search engines prefer slugs that are 3-5 words long (roughly 50-70 characters). We default to a maximum of 80, but you can adjust it to suit your CMS or platform constraints.

Back to Developer

Slug generator — URL-safe string from any title

Turn titles and headings into URL-safe slugs (kebab-case or snake_case). Diacritics (é → e) are normalised to ASCII, emoji and punctuation are stripped, and whitespace is collapsed into the separator. Configurable length cap, case preservation, and non-ASCII handling — all in your browser.

developerURLgenerate

How to use

Choose a separator (kebab / snake / dot) and type a title or heading into the input box. The slug is generated live: diacritics (é → e) are normalised to ASCII, emoji and punctuation are stripped, and whitespace is collapsed into the separator. Turn off Lowercase to preserve the original case; turn off Strip non-ASCII to keep characters like Japanese kanji (the browser will percent-encode them in URLs). The Max length cap trims the slug. To romanise kanji first, run the Kanji-to-rōmaji tool and paste the result here.

FAQ

Is the text uploaded?: No. The slug is generated entirely in your browser via JavaScript. Use it for drafts, internal titles, and unpublished work without worry.
How are diacritics handled?: We Unicode-normalise the input to NFD (separating base letters from combining marks), drop the combining marks, and keep the ASCII base. That turns é into e, ñ into n, ü into u, and so on automatically.
Are kanji and kana romanised?: Not by this tool. If you want to keep them as-is in the slug, turn off Strip non-ASCII — the browser will percent-encode them in URLs. If you need romanisation, run the Kanji-to-rōmaji converter first and paste the result here.
How long should a slug be?: Search engines prefer slugs that are 3-5 words long (roughly 50-70 characters). We default to a maximum of 80, but you can adjust it to suit your CMS or platform constraints.

Related tools

URL encode / decode — safe query strings

Convert between plain text and %XX percent-encoded URL strings. Toggle between encodeURIComponent / encodeURI (and their decode counterparts). UTF-8 based, runs entirely in your browser.

developerURLencodedecode

Text case — UPPERCASE / lowercase toggle

Convert text to all UPPERCASE or all lowercase, with a mode toggle. Unicode-aware so non-Latin scripts (Greek, Cyrillic, etc.) are handled correctly. Japanese, symbols, and digits pass through unchanged. Runs entirely in your browser.

developertextconversion

UTM URL Builder

Build campaign-tracking URLs for Google Analytics / GA4 with utm_source / utm_medium / utm_campaign / utm_term / utm_content / utm_id parameters. Existing query strings and `#fragment` are preserved, blank fields are omitted. Runs entirely in your browser — your URL is never uploaded.

developerURLgenerate

Barcode generator — JAN / EAN / UPC / CODE128 / CODE39

Turn numbers or text into 1D barcodes (JAN-13 / EAN-13, JAN-8 / EAN-8, UPC-A, CODE128, CODE39, ITF, Codabar/NW-7, MSI) and export them as PNG or SVG. Fine-tune bar width, height, colors, margin, and whether the human-readable value is printed below. Check digits are validated automatically. Everything is generated inside your browser — the value you enter never leaves your device.

developergenerateimage