Why this tool exists
Slugify Helper turns editorial ideas into URL-safe slugs, audits legacy permalink lists, and shares camel/snake variants so product, marketing, and API teams stay aligned.
Editorial & blog planning
Generate SEO-friendly permalinks for landing pages, docs, and changelogs before publishing.
CMS migrations
Paste existing slugs and spot collisions while rebuilding content hierarchies in new stacks.
Platform integrations
Share camel, studly, or snake variants with API and design system partners from one run.
Quick start
Paste a phrase, pick the slug styles you need, then copy unique outputs with collision context and suffixing rules.
- Launch the Slugify helper, paste or load a preset string, and confirm which slug styles should stay active.
- Optional: paste known slugs (one per line) into the Existing slugs textarea and pick a deduplication strategy.
- Submit the form to refresh the results grid, review collision badges, and copy the slugs you need.
Supported inputs
- Accepts plain text, emoji, punctuation, and numbers — whitespace is trimmed before slugging.
- Existing slug lists support newlines or comma separation; duplicates are normalized for comparisons.
- Handles up to dozens of slugs per submission with deterministic output per style.
Form walkthrough
Input workflow
Every field mirrors the tool UI so you can onboard writers or engineers fast.
- Source input: type or paste the phrase you need to slugify, or click a preset to prefill helper text.
- Style selection: enable styles via checkboxes — each badge includes a helper line so stakeholders know when to use it. At least one style is always active.
- Existing slugs: paste legacy or reserved slugs, one per line or comma-separated, to power collision detection and metrics.
- Deduplication strategy: choose Warn only to leave duplicates untouched or Auto-suffix numbers to append -2, -3, etc. when conflicts arise.
Mode 01
Slug styles
Enable as many styles as you like—the helper returns the same lineup on every submission for consistent reviews.
- Kebab case outputs lowercase, hyphenated slugs ready for SEO-friendly URLs and sitemap entries.
- Snake case uses underscores for file exports, CLI flags, and environment keys.
- camelCase and StudlyCase variants support React components, enums, and API fields without extra tooling.
- Dot case creates dotted namespaces for config scopes or feature flags while still tracking collisions.
- All styles preserve ASCII letters/numbers only, stripping unsupported symbols automatically.
Mode 02
Collision handling
Feed in historical slugs and pick your resolution style to avoid shipping duplicates.
Duplicate checks normalize casing and separators, so `New-Post` and `new_post` count as the same slug.
Warn only highlights collisions without modifying values — perfect for audits where you prefer manual reviews.
Auto-suffix numbers appends `-2`, `-3`, or `_2` based on the style’s separator, and flags any slug it had to adjust.
Metrics panel summarizes how many existing slugs were provided, how many duplicates were found, and how many were resolved by suffixing.
Outputs & copy helpers
The results grid keeps collision context close to the copy buttons so QA never loses track of what changed.
Each result card shows the slug, the original (pre-adjustment) value, collision badges, and contextual notes.
Copy buttons trigger a toast + badge change so you always know which slug already hit your clipboard.
Status labels (“Unique”, “Duplicate”, “Resolved”) mirror the metrics so QA teams can screenshot the run.
Field notes
Keep permalink reviews tight across roadmaps, marketing, and dashboards.
- Use the presets when demonstrating policies — they enable recommended styles and populate existing slugs instantly.
- Pair Slugify helper with the Case Converter guide when you need matching headings and permalinks for docs.
- Export your CMS slugs first, paste them into the Existing field, then rerun after each editorial batch to catch collisions early.
- Bookmark the documentation hub to jump between Slugify, Counting + Stats, and other text helpers while auditing content.