Slug Generator

Generate URL-safe slugs across multiple styles, spot collisions against existing registries, and auto-suffix duplicates before they leak into a CMS or release workflow.

Quick samples

Slug inputs

Paste source text, choose output styles, and optionally compare against an existing slug registry.

We normalize text server-side so punctuation, whitespace, and multibyte input stay consistent.

Canonical lowercase slug with hyphen separators.

Lowercase slug with underscores for filenames or identifiers.

Lower camel casing for JavaScript variables or CSS classes.

Upper camel / Pascal casing for classes or enums.

Lowercase slug separated by dots for config scopes.

Paste one slug per line or comma-separated to flag collisions against known entries.

Append numeric suffixes (-2, -3) when collisions are detected.

Slug outputs

Review each style, copy the final slug, and inspect collision notes before publishing.

Awaiting source text

Paste text on the left, choose your slug styles, then submit to generate outputs and collision insights.

Collision insights

Summary counts for the current registry and any duplicate handling that ran.

Existing slugs

0

Collisions detected

0

Auto-resolved

0

Documentation

Slug Generator

Full Docs

About this tool

Slugify converts titles, headings, and labels into URL-friendly slugs. Use it when creating page paths, route names, anchors, or content identifiers.

Behavior

The generated slug is normalized for URL use. Punctuation and spacing are reduced, and accented characters are converted where possible.

Review the final slug against your routing rules and existing URLs.

info

Gotchas

A valid slug is not automatically unique. Check for collisions before using it in a live route.

Avoid changing published slugs unless redirects are planned.

tips_and_updates

Key use cases

  • -Turn a page title into a clean URL segment.
  • -Normalize accents, spaces, punctuation, and casing.
  • -Compare slug styles before publishing.
  • -Check for possible duplicate paths.

FAQ