Local path-segment utility

URL Slug Generator

Turn one title or a bounded list into deterministic slugs, compare them with your own reserved list, and inspect exactly what each path segment looks like when percent-encoded.

Titles and policies

At most 100,000 UTF-16 code units, 200 lines, and 2,000 code units per line. A trailing blank line is ignored.

8–200 Unicode code points, not visual grapheme clusters; suffixes fit inside this limit.

Latin folding: uses NFKD, removes combining marks, and applies a fixed small Latin map such as ß → ss, æ → ae, ø → o, and ł → l. Other scripts are removed and reported.

0UTF-16 code units
0input lines
80code-point limit

Collision check

Optional; one exact slug per line, up to 200. This is your list—not a claim about universal reserved words.

Generated slugs

No result yet. Generate to review every row before publishing.

RowSourceSlugEncoded path segmentDiagnosticAction
No slugs generated yet.

What this generator does

A slug is usually one human-readable segment of a URL path, such as cafe-guide in /articles/cafe-guide. This tool turns each input line into one segment. It does not build, validate, reserve, publish, redirect, or fetch a complete URL.

The raw slug and its encodeURIComponent representation are shown separately. ASCII output normally looks the same in both columns. Readable Unicode output may be displayed directly by browsers, while the encoded column shows the UTF-8 percent-encoded segment typically transmitted in a URL.

Choose a policy deliberately

Portable ASCII — Latin folding

Compatibility normalization decomposes many accented Latin letters, then combining marks are removed. A short fixed table handles letters that do not decompose usefully. Extended mode first recomposes canonically equivalent text and applies its fixed Greek/Cyrillic map, preserving distinctions such as й/ё/ї before the remaining text is decomposed. Unmapped scripts are removed and reported, so a title can produce no slug.

Portable ASCII — extended map

This adds deterministic, practical Greek and Cyrillic character mappings. It is designed for stable identifiers, not pronunciation, language-aware romanization, reversible transliteration, or compliance with ISO, BGN/PCGN, UNGEGN, or another scholarly system. Review names before publishing.

Readable Unicode

NFC normalization preserves letters and decimal digits from any script. Unicode letter-number and other-number categories, such as Roman numerals and superscript numbers, are diagnosed and removed rather than treated as decimal digits. A combining mark is kept only when it is directly attached to a preceding kept letter, decimal digit, or attached mark; punctuation, whitespace, emoji, and other removed characters break that attachment. Filesystems, routers, content systems, and teams can still impose narrower policies, and visually similar Unicode strings can remain distinct.

Collisions, limits, and URL realities

  • Collision checks are exact, case-sensitive string comparisons against this batch and the optional list you provide. The tool cannot inspect your CMS, filesystem, database, redirects, aliases, or remote site.
  • Automatic suffixes are deterministic and remain inside the selected maximum length. They are suggestions; a concurrent publisher could still take the same slug.
  • The complete path segments . and .. have hierarchical meaning in URI processing. A source consisting only of either is rejected rather than presented as a publishable slug.
  • URL paths are generally case-sensitive unless a specific server or application says otherwise. Lowercase is a consistency choice, not a universal syntax requirement.
  • Changing a published slug changes the URL. Plan an appropriate redirect and update internal links in the system that owns the page.

Privacy and operational limits

Generation, comparison, copying, and CSV creation happen in this browser tab. This tool makes no input-bearing request, upload, storage, cookie, or analytics call of its own. Shared site infrastructure may deliver the page and record an ordinary page view, but it cannot read these fields through this tool.

The generator cannot determine search ranking, keyword quality, language meaning, trademark risk, route availability, canonical URLs, redirect correctness, or whether a destination exists. There is no universal ideal slug length or stop-word list, so neither is claimed here.