{{ summaryTitle }}
{{ summaryValue }}

{{ summaryLine }}

{{ badge.label }}{{ badge.value }}
Use a page title, heading, route label, product name, or filename.
{{ sourceActionStatus || sourceHelperLine }}
Keep this off for one title; turn it on for a line-delimited list.
{{ batch_mode ? 'Each line' : 'First line only' }}
Use stable suffixes such as -2 and -3 for colliding batch items.
{{ dedupe_batch ? 'Suffix duplicates' : 'Keep duplicates' }}
The choice updates the primary slug and path artifact.
Technical variants in the ledger keep their conventional lowercase form.
Choose Unicode only when the target accepts and displays encoded paths reliably.
Use 8–160 characters; 64 is the default.
characters
Optional SEO-oriented compression; the neutral default keeps every token.
{{ remove_stop_words ? 'Remove connectors' : 'Keep all tokens' }}
The neutral default uses the exact cap and removes only a trailing separator.
{{ smart_trim ? 'Prefer whole words' : 'Use exact cap' }}
Blank is neutral. Example: section creates section-quarterly-launch-plan-apac-beta.
{{ computation.values.output_text }}

The chart renderer is unavailable. Exact character counts remain in the variant ledger.

SourceTargetValueCharactersBest fitCopy
{{ row.source_label }}{{ row.target }}{{ row.value }}{{ row.character_count }}{{ row.fit }}
Case Converter Convert headings and identifiers into 13 case styles with per-line scope, acronym rules and accent folding for filenames or slugs before reuse.
URL Encode and Decode Tool Encode or decode URL text by context, handle form-style plus signs and nested escapes, and check round-trip or double-encoding risks locally.
Unicode Character Lookup Inspect a character or escape and compare its U+ value with UTF encodings and normalization forms while revealing invisible text and grapheme structure.
HTML Entity Lookup Look up an HTML entity or Unicode value, then compare named and numeric forms with context-safe escapes for copying into markup and code.

An identifier often outlives the title that created it. Once a path is bookmarked, a heading is linked, or a filename enters a build process, changing its spelling can break redirects, selectors, analytics, caches, and external references. A slug turns descriptive text into a stable identifier before those dependencies form.

The best slug preserves enough meaning to recognize the resource while removing characters that have structural or compatibility concerns. Spaces need a separator, punctuation may have a special role, accented letters may be folded or kept, and several different titles can collapse to the same final text.

ASCII-safe
Folds many accented or compatibility characters to basic Latin forms before keeping letters and digits.
Unicode
Keeps letters and numbers from other scripts after compatibility normalization.
Strict ASCII
Drops non-ASCII text instead of transliterating it, while also treating symbols as separators rather than words.

URL slugs and code identifiers overlap, but they are not interchangeable. Hyphens are readable and valid unreserved URI characters, while underscores and dots suit some technical naming conventions. HTML ids and CSS classes also need a safe starting character, so a derived identifier may require a prefix even when the URL segment does not.

Readable output is not proof that the destination is available. Check existing routes, filenames, anchors, and selector conventions before publishing. When replacing a live slug, keep a redirect or update every reference that still points to the old value.

How to Use This Tool:

Match the transformation rules to the place where the identifier will be stored or published.

  1. Enter a title, heading, route label, product name, or filename in Source text.
  2. Turn on Batch mode when each nonblank line should become a separate slug. Leave Resolve duplicate slugs on if normalized collisions should receive numeric suffixes.
  3. Choose the separator, letter case, and Character handling. Lowercase ASCII-safe text with hyphens is a conservative public-URL starting point; Unicode is appropriate only when the destination supports and displays it correctly.
  4. Set Maximum length from 8 to 160 characters. Enable Trim at a word boundary when backing up to the preceding separator is preferable to cutting the final token.
  5. Check the generated text and notices. In batch mode, confirm any duplicate suffix; for anchors and selectors, use the appropriate derived row and test it in the destination.

Interpreting Results:

The primary slug is the direct result of the selected separator, case, character policy, stop-word rule, and length cap. A warning about ignored lines means batch mode is off; a duplicate adjustment means a later batch row normalized to an earlier value and received a suffix such as -2.

Derived URL, path, filename, anchor, HTML id, CSS class, snake_case, and dot-path values are paste-ready variants, not universal validation. Test the chosen value where it will be used, especially when case, Unicode encoding, framework routing, or CSS escaping rules matter.

Technical Details:

Slug generation is an ordered normalization and mapping process. Changing the order would change the result: word boundaries must be found before punctuation is removed, character normalization occurs before token matching, and length enforcement happens before duplicate suffixes are added.

Transformation Core

OrderRuleExample effect
1Insert boundaries between camel-case words and between letters and digits.ReleasePlan2026 becomes three tokens.
2Remove straight and curly apostrophes. In non-strict modes, map &, +, @, and % to words.R&D contributes r-and-d.
3Apply ASCII compatibility decomposition and accent folding, Unicode NFKC normalization, or strict ASCII token selection.Café becomes cafe in ASCII-safe mode and remains café in Unicode mode.
4Keep letter-and-number tokens, apply the selected case, optionally remove the fixed English stop-word set, and join with the separator.Repeated separators and surrounding separators disappear.
5Limit by Unicode code points. Smart trim backs up to the previous separator only when at least eight characters remain.An empty result falls back to item.
6For batch collisions, append separator plus 2, 3, and later numbers while preserving the maximum length.Matching rows become launch, launch-2, and launch-3.

Batch mode accepts up to 50 nonblank lines from source text of at most 10,000 characters. When batch mode is off, only the first nonblank line is processed and the remaining count is reported. Duplicate comparison is case-insensitive even when case preservation or uppercase output is selected.

The optional stop-word list contains common English connectors such as a, and, for, of, the, and with. If removal would discard every token, all original tokens are retained. This prevents a source such as The Of from collapsing to the fallback.

Identifier variants always use lowercase ASCII-derived words. If a value begins with a digit or another disallowed starting form, the anchor and CSS forms receive a normalized prefix, using section when no custom prefix is supplied. These safeguards do not replace destination-specific identifier or selector testing.

Privacy Notes:

Source text is transformed in the browser. Avoid pasting confidential project names when the resulting slug itself would reveal information in a public URL, log, filename, or analytics record.

Worked Examples:

Accented public title

Café Partner Roadmap becomes cafe-partner-roadmap in ASCII-safe lowercase mode. Unicode mode keeps café-partner-roadmap, which should be tested in the publishing system because its transported URL may appear percent-encoded.

Colliding batch titles

R&D Plan and R and D Plan both normalize to r-and-d-plan outside strict mode. With duplicate resolution enabled, the second result becomes r-and-d-plan-2.

References: