Text
Slugify
Convert text to a URL-safe "slug": Cyrillic (uk/ru) transliteration following the official standard, diacritic and punctuation stripping, lowercase.
A slug is a URL-safe version of a title or name: lowercase Latin letters, digits, and hyphens instead of spaces. This tool transliterates Cyrillic text using the official standard and strips diacritics and characters that aren't valid in a URL.
How to use it
- Paste an article title, product name, or any text — the slug is generated instantly as you type.
- Multiple spaces, punctuation, and special characters are automatically collapsed into a single hyphen.
- Copy the result and use it as part of a page or file URL.
Common uses
- Generating URLs for blog posts or products in a CMS from a Cyrillic or Latin title.
- Creating safe file names from arbitrary text with no spaces or special characters.
- Building anchor IDs (#section-name) on a page from section headings.
Things to keep in mind
Cyrillic transliteration isn't unique — different systems (e.g. passport vs. scholarly) transliterate the same letters differently; this tool follows the official transliteration standard.
Keep slugs short and meaningful — long slugs are harder to remember and look worse in search results.
Article about this tool: Slugify: turning arbitrary text into a URL
Frequently asked questions
How is text turned into a URL-friendly slug?
The text is lowercased, Cyrillic characters (Ukrainian, Russian) are transliterated per the official standard, diacritics and URL-incompatible characters are stripped, then words are joined with the chosen separator.
Can I choose the separator used in the slug?
Yes, the separator option lets you choose the character that joins the slug's words, typically a hyphen or underscore.
Is the entered text sent to a server?
No, all slug generation runs locally in your browser in JavaScript, nothing is transmitted online.
What if two different titles produce the same slug?
The titles "Hello, World!" and "hello world" normalize to the same slug, even though the texts differ. If the slug is used as a unique identifier (in an article's URL, say), this kind of collision needs extra handling — typically a numeric suffix or ID.
Why doesn't plain URL encoding work instead of a slug?
Percent-encoding of Cyrillic text is technically valid in a URL but unreadable to a human and looks untrustworthy in an address bar or when copied. A slug solves the readability problem, not just technical character validity.