URL Slug Generator

Turn blog post titles into clean URL slugs. Korean is auto-romanized to RR (Revised Romanization) before slugification, with full control over separator, case, length, and digits.

Separator
Case
Hangul handling
Options
Title
Slug
https://yoursite.com/posts/-

How to Use

1
Type the title

Enter your title — any mix of Korean, English, numbers, emoji, or punctuation. Hangul auto-romanizes (e.g. 한국 → hanguk).

2
Pick options

Choose separator (- or _), casing (lowercase / preserve), max length, and whether digits are allowed.

3
Copy & paste

The slug updates live on the right. Copy in one click. Use it for blog URLs, permalinks, or filenames.

FAQ

What is a slug?

It's the human-readable last segment of a URL (e.g. blog.com/posts/<slug>). Slugs help SEO and let users guess content from the URL alone. By convention they only use URL-safe characters: lowercase letters, digits, and hyphens.

How is Hangul handled?

It's converted via the official Revised Romanization (RR). e.g. "한국어 가이드" → "hangugeo-gaideu". The result is search-engine friendly and safe across browsers and tools.

Can I keep Hangul in the URL?

Modern browsers do support Hangul URLs, but they can break in some tools, share scenarios, and legacy systems — so romanized slugs are the standard. The tool also offers a "Keep original (percent-encoded)" option if you really want a Hangul URL.

Why lowercase by default?

URLs are case-sensitive, so /About and /about can be two different pages. Slugs are conventionally all lowercase to avoid confusion. WordPress, Hugo, Jekyll, and Gatsby all default to lowercase.

Is anything sent to a server?

No. All conversion runs in your browser; titles never leave the page.