Skip to content

Slug Generator

Turns a title into a URL-safe slug, with romanisation for Korean and a choice of separator.

Turns a title into a URL-safe slug, romanising Hangul on the way — 한국어 기초 강의 becomes hangugeo-gicho-gangui. Duplicates get a number rather than silently colliding, which is the failure that matters when you are slugging a whole content export.

🔒 Runs entirely in your browserslugurlseo

Titles

One per line. Duplicated slugs get a number rather than silently colliding.

Options

Separator

0 for no limit. Cuts at a separator, never mid-word.

Romanisation follows 국어의 로마자 표기법 including the sound changes, so 신라 becomes silla rather than sinra — the same result the 한글 로마자 tool gives, because it is the same implementation.

Slugs

Slugs

3

Numbered for collision

1

Longest

26

  • Café & Bar: Rock ’n’ Rollcafe-and-bar-rock-n-roll
  • 한국어 기초 강의hangugeo-gicho-gangui
  • Top 10 Cafés in Seoul 2026top-10-cafes-in-seoul-2026

How to use it

  1. Paste the titles, one per line

    A whole column out of a CMS export works. Every line is slugged, and the pairs are shown side by side so you can see which title produced which slug.

  2. Decide about Hangul

    Romanise gives a readable ASCII slug. Keeping Unicode letters is valid in a modern URL and readable in the address bar, but percent-encodes the moment anyone copies it. Doing neither leaves an empty slug.

  3. Cap the length if your CMS does

    The cut falls at a separator, never mid-word, so the slug still reads. Zero means no limit.

  4. Look at the collision count

    Any slug ending in -2 or -3 came from two titles that reduced to the same thing. On a bulk import that is the number to check before you commit the URLs.

Common questions

Why is 신라 romanised as silla and not sinra?

Because the romanisation follows 국어의 로마자 표기법 including the sound-change rules, which is what the government standard specifies. It is the same implementation the 한글 로마자 tool uses, so the two always agree.

Is a Korean slug bad for search?

Search engines handle both. The practical difference is elsewhere: a percent-encoded URL is unreadable when pasted into a chat, an email or a printed document, and some older systems still mangle it. Romanised slugs survive that journey.

A slug came out empty

The title was entirely characters with no ASCII form and romanisation was off — Chinese, Japanese or symbols. Turn on romanisation for Korean, or keep Unicode letters for the rest.

What do the stop words do?

Drops English words like the, a and of, which shortens a slug without losing meaning. It never empties one: a title made entirely of stop words keeps them.

Feed it from

Next

These accept what this tool produces, so the result can go straight in.