About this tool
Create and review one route segment for a blog post, document, product, or CMS entry without uploading the title.
Slug Generator turns one title into a candidate URL path segment with an explicit character policy. Unicode preserve keeps letters and numbers in the audience's language, while ASCII fold performs limited Latin diacritic cleanup rather than claiming complete transliteration.
- Preserves Unicode letters and numbers or applies limited Latin ASCII folding.
- Keeps complete words within a 1 to 200 grapheme limit when possible.
- Shows both the readable slug and percent-encoded URL segment for review.
How to use Slug Generator
Enter one title, choose Unicode preserve or ASCII fold, select a separator, and set a 1 to 200 grapheme boundary. Review the readable value, encoded path segment, truncation evidence, and collision warning before copying it into a CMS or router.
When this tool is useful
- Preserves Unicode letters and numbers or applies limited Latin ASCII folding.
- Keeps complete words within a 1 to 200 grapheme limit when possible.
- Shows both the readable slug and percent-encoded URL segment for review.
Examples you can test
Load an example, compare the result with the expected output, then replace it with your own input.
Create a blog URL slug
Example input
Title: 10 Ways to Clean CSV Data!
Expected output
10-ways-to-clean-csv-data
A clean slug removes punctuation and uses stable separators that are easy to read.
Normalize repeated separators
Example input
Title: Product Launch --- Checklist
Expected output
product-launch-checklist
Repeated spaces and punctuation should collapse into one predictable separator.
Preserve a Korean audience-language slug
Example input
온라인 도구 품질 점검 가이드
Expected output
온라인-도구-품질-점검-가이드
Copy the percent-encoded form when the destination expects an encoded href segment.
Validation checklist
- Review the slug before publishing because changing URLs later can require redirects.
- Choose Unicode preserve for audience-language words; treat ASCII fold as limited normalization, not transliteration.
- Check duplicate slugs in the CMS or router before assigning the final URL.
- Confirm redirects, canonical tags, and server handling before changing an already published URL.