Converter · SOTA Unicode NFKD + IRI-safe
Slugify (URL Slug Generator)
Generate URL-safe slugs from any text. Unicode NFKD decomposition handles accented characters (café → cafe), multi-language transliteration (北京 → bei-jing), custom separator, and safe truncation.
How to Use Slugify in 3 Steps
- Configure. Paste any text: multi-byte, accented, CJK, emoji, mixed. The tool handles everything.
- Process. Configure: separator (dash, underscore, dot), max length, lowercase toggle, keep-dots toggle.
- Export. Copy the slug. Unicode NFKD decomposes accented characters (é → e), curated maps handle non-Latin scripts (日本 → ri-ben, Привет → privet).
Why Slugify on Pixlane
Slugs are URL-safe versions of titles used for blog posts, product pages, documentation, filenames, and permalinks. A good slug is human-readable, SEO-friendly, and safe across URL constraints (RFC 3986 unreserved). Pixlane uses Unicode NFKD normalization to strip accents, curated transliteration maps for non-Latin scripts, and emits strict URL-safe output.
- Unicode NFKD Normalization: Uses String.prototype.normalize('NFKD') to decompose accented characters (café → cafe, Ångström → angstrom), the correct Unicode way, not a lossy hex-escape.
- Multi-Script Transliteration: Built-in maps for Cyrillic (Привет → privet), Greek (Ελλάδα → ellada), Arabic, Japanese romaji, Chinese pinyin. CJK characters get readable romanized output.
- RFC 3986 Compliant: Output uses only unreserved URL characters (A-Z, a-z, 0-9, -, _, ., ~), guaranteed safe in every path segment without additional percent-encoding.
- Smart Truncation: Truncate at word boundaries to preserve readability. A 500-char title becomes a clean 80-char slug without mid-word cuts.
Frequently Asked Questions
Why use NFKD instead of regex replacement?
NFKD is Unicode's Normalization Form Compatibility Decomposition. It formally separates a character like é into 'e' + combining acute. This is the standardized, locale-correct way to strip accents. Regex-only approaches miss characters and produce inconsistent results across Unicode versions.
Can slugs include uppercase letters?
Technically yes (RFC 3986 allows them), but URL case-sensitivity varies: Apache/Linux paths are case-sensitive, Windows/IIS are not. Google treats differently-cased URLs as separate pages. Best practice is lowercase slugs, the tool enforces this by default.
How does it handle emoji and symbols?
Emoji and symbols are stripped by default (they have no URL-safe representation). An option to keep them as percent-encoded UTF-8 is available, but not recommended for SEO.
Is this tool free?
Yes. Slugify on Pixlane currently requires no signup for core use; tool-specific limits may apply.