Create one bounded URL path slug locally with an explicit Unicode or ASCII policy. Choose hyphens or underscores, lowercase handling, Latin camelCase splitting, and an optional maximum length. The result is one candidate path segment: processing stays local, unsupported transliteration and removed characters are reported, and no CMS, router, duplicate namespace, reserved word, redirect, canonical tag, or search result is checked. Review percent-encoded length and verify uniqueness and redirects in the real publishing system.
Continue with a related workflow or open the next tool that usually follows this task.
A slug generator can produce a consistent path-segment candidate, but it cannot own the route or protect a published address. This workflow records the target platform and current URLs, chooses an explicit Unicode or ASCII convention, reviews transliteration and encoded length, checks duplicates and reserved names in the real namespace, and treats redirects, canonical metadata, internal references, sitemap updates, monitoring, and rollback as required parts of any live URL change.
OpenRelated toolConvert every line into 10 exact case styles and review identifier risks locally.
OpenRelated toolCompare bounded text locally with exact line hunks, code-point highlights, and unified patch export.
OpenRelated toolConvert one IDN between Unicode and Punycode with strict validation and label review.
OpenIdentify the exact CMS, router, path namespace, existing URL convention, and whether the page is new or already published.
Remove confidential draft names, customer identifiers, tokens, and private project terms, then paste one title or route label within the documented limits.
Keep Unicode for scripts that should remain readable, or choose ASCII transliteration only when the engine supports the source language and a reviewer confirms the spelling.
Choose a hyphen or underscore, lowercase behavior, Latin camelCase splitting, and an optional maximum visible length.
Generate in Manual mode and review removed punctuation, transliteration warnings, truncation, percent-encoded length, meaning, and reserved words before copying or downloading.
Check uniqueness in the real platform; for an existing page, configure and test redirects, canonical tags, internal links, sitemap entries, analytics, and rollback before release.
Create a candidate path for a new article, help page, release note, or documentation section, then check it against the real CMS namespace.
Keep Korean, Japanese, accented, or other international titles readable instead of deleting every non-ASCII letter.
Create a supported ASCII transliteration for a legacy route policy and review any characters that the engine could not represent.
Compare separator, case, camelCase, and length settings before pinning one convention in a repository or CMS integration.
Generate the proposed replacement while keeping redirects, canonical metadata, links, sitemap changes, monitoring, and rollback as explicit release gates.
Transliteration is not available for every writing system. Korean, Japanese, and Chinese characters can disappear in ASCII mode, so the tool reports dropped letters and fails when nothing remains. Keep Unicode or supply a spelling reviewed by a speaker.
A locally generated string is not reserved in a CMS, router, database, or static-site build. Query the real content store and test case-folding rules before publishing a route that must be unique.
Changing a live path can break inbound links, bookmarks, analytics continuity, and search signals. Keep the old URL mapped with the correct permanent redirect and update canonical tags, internal links, hreflang, sitemap entries, and tests.
Visible Unicode length and the transmitted percent-encoded path length differ. Review the encoded-length warning and verify limits in the exact CMS, framework, proxy, CDN, database column, and downstream API.
A readable path can help people understand a link, but no separator, keyword, or length setting guarantees rankings. Match the page subject, avoid misleading wording, and judge results with crawl, index, and legitimate user evidence.
The default Unicode policy keeps Korean letters readable, lowercases applicable scripts, replaces boundaries with hyphens, and leaves one path segment.
2026 여름 여행 가이드2026-여름-여행-가이드ASCII mode transliterates supported accented Latin letters. Review any warning before using it with another writing system.
Déjà Vu: Café Launchdeja-vu-cafe-launchWith lowercase disabled, camelCase splitting enabled, and underscore selected, Latin word boundaries and capitals remain visible.
ReleaseAPIClient v2Release_API_Client_v2The 50-character setting cuts at a nearby word boundary, trims the final separator, and emits a truncation warning for review.
A practical guide to changing a published URL without breaking old linksa-practical-guide-to-changing-a-published-urlThe engine uses @sindresorhus/slugify 3.0.0. Source text is normalized to NFC, apostrophes are removed inside words, and punctuation, symbols, controls, and invisible formatting characters become word boundaries before slugification.
Unicode mode preserves Unicode letters, numbers, and required combining marks. ASCII mode invokes the package transliterator and counts non-ASCII letters or numbers it cannot represent, rather than silently claiming complete romanization.
The selectable separators are hyphen and underscore, both in the RFC 3986 unreserved set. Repeated boundaries collapse, and leading or trailing separators are removed. The output is one candidate path segment, not a complete URL.
Lowercase conversion is optional. Latin camelCase splitting can turn ReleaseAPIClient into Release-API-Client before case conversion; it is not a general word-segmentation system for every language.
Maximum visible length can be unlimited, 50, 80, 120, or 200 Unicode code points. When shortening is needed, the engine prefers a nearby separator boundary and reports the original and selected lengths. It also reports percent-encoded path length above a conservative review threshold, which is not a universal platform limit.
Input is bounded to 10,000 UTF-8 bytes, 20 lines, and 5,000 UTF-8 bytes on any line. Processing and file creation stay in the browser; the engine does not fetch a URL, reserve a route, query duplicates, configure redirects, or measure search performance.
Unicode mode preserves letters and numbers from scripts such as Korean, Japanese, and Devanagari and returns a readable IRI-style segment. Browsers normally percent-encode non-ASCII bytes when sending a URL. Confirm that your CMS, router, proxy, database, and analytics pipeline accept the same form.
ASCII mode transliterates many Latin, Cyrillic, Arabic, Greek, and other supported characters, but not every writing system. Unsupported non-ASCII letters are counted in a warning, and an all-unsupported title returns an error instead of a blank success.
Hyphens and underscores are both RFC 3986 unreserved characters. Many publishing conventions prefer hyphens for visible word boundaries, but the correct choice is the one your existing routes, framework, and migration policy use consistently.
No universal slug length produces better search results. The optional 50, 80, 120, and 200-character limits are review controls, not standards. Check the visible and percent-encoded lengths against every system that stores or forwards the path.
No. The browser does not query your CMS, database, repository, or router. Search the real route namespace, account for case and Unicode normalization, and test create and update behavior before publishing.
Keep the existing URL live, add the platform-appropriate permanent redirect to the new URL, update canonical and hreflang tags, internal links, sitemap entries, feeds, structured data, and campaign references, then test redirect chains and monitor crawl and traffic evidence.
Generation, copy, and download occur in the current browser. Operational analytics can record mode, selected settings, byte counts, duration, warnings, and stable error class, but not the title or generated slug. Still avoid pasting confidential draft names on a shared or extension-heavy device.
Maintained and tested by SimpleWebUtilsReviewed
Method: We replayed “Keep a Korean title readable, then verify the route in the CMS” in Slug Generator, keeping the guide's input unchanged. “Preserve the source and remove confidential draft data” and “Check ownership, duplicates, and reserved behavior in the real system” defined the normal path; “Letting unsupported ASCII transliteration erase the title” and “Optimizing for a mythical perfect slug length” defined the boundary review before the output was accepted.
Expected result: The slug retained the Korean words, normalized URL to lowercase, and produced 2026-여름-여행-준비와-안전한-url-가이드 for a CMS route and redirect check.
Sources and standards
Use these focused guides when you need a practical workflow before opening the tool.
Continue with another maintained workflow
Convert every line into 10 exact case styles and review identifier risks locally.
Compare bounded text locally with exact line hunks, code-point highlights, and unified patch export.
Convert one IDN between Unicode and Punycode with strict validation and label review.
Encode or decode exact URL components, full URLs, and form values locally.
Parse absolute URLs or resolve references with raw, decoded, normalized, and duplicate-query views.