Text to slug

Empty input and punctuation-only strings fail with a clear invalid_input error so a blank form cannot look like a successful conversion. Use it free in the browser for content prep, SEO checks, and data cleanup, or call the API at $0.002 per successful request when CI, CMS pipelines, or teaching demos need the same slug every time.

What text-to-slug conversion means and what the response contains

Text-to-slug conversion turns a multi-word title into one path-safe identifier where every letter is lowercase, accents are gone, and words are separated by single hyphens, with no spaces or other punctuation between them. In practice Hello World becomes hello-world, a Spanish headline such as Cómo Añadir un Título becomes como-anadir-un-titulo, Café Ñandú 2024 becomes cafe-nandu-2024, and noisy marketing copy with exclamation marks collapses into a clean hyphen chain. There is no partial mode that only lowercases without stripping accents, no locale-specific transliteration tables beyond Unicode NFD decomposition of combining marks, and no silent coercion of null into an empty success. The transform is not camelCase, not CONSTANT_CASE, not PascalCase, and not a title-case display string: only the SEO-friendly lowercase slug remains. This calculator returns five stable fields: slug holds the URL-friendly result you will paste into a CMS, sitemap, or route table; original echoes the exact input string so you can audit what was transformed; length reports the character count of the slug; words counts how many hyphen-separated tokens were produced; and method is the fixed tag slugify for logs and multi-tool pipelines. The engine either builds a complete slug inside the supported length or rejects the request with invalid_input. Rejected cases include a missing text field, a null value, an empty string, whitespace-only or punctuation-only payloads that leave no letter or digit tokens, objects and arrays that are not plain text, and any payload longer than the documented maximum character count.

How the text field is read and how the result stays reproducible

The value must be a non-empty string; finite numbers and bigints are stringified first so a bare numeric code still becomes a slug token after conversion to decimal digits. Leading and trailing whitespace are absorbed during the non-alphanumeric replacement step; internal runs of spaces, underscores, hyphens, dots, em-dashes, and other non-alphanumeric characters act as word breaks and become single hyphens in the output only between tokens. Diacritics are removed with Unicode NFD normalization followed by a strip of combining marks in the standard range, so á, é, í, ó, ú, ñ (as n plus tilde after decomposition where applicable), ü, and similar Latin letters fold to their ASCII bases before lowercasing completes. Each remaining letter is lowercased with the default JavaScript case mapping, which keeps Hello, HELLO, and hello on the same hello token after processing. The preferred field is text, but aliases input, string, value, content, s, title, and phrase are accepted so query strings, spreadsheets, and typed forms can reuse the same contract without renaming columns. Booleans, plain objects, and arrays are rejected with a clear message so a mistaken JSON body does not become the word true or an unhelpful object dump. Empty string is always invalid_input: the product promise is convert a title, not invent a blank success. Length is capped at one hundred thousand characters so a runaway paste cannot monopolize a Worker; longer payloads fail with an explicit limit message rather than a truncated silent cut. Pair the free browser run on this page with the priced API when you need the identical slug inside an automated pipeline without shipping your own string helpers.

Where text-to-slug conversion fits in publishing, SEO, and software

On this page the work runs entirely in your browser; through the API each successful conversion costs $0.002, failed validation is not charged, and nothing is stored after the response returns. That split—free interactive exploration and a priced, identical API—matches the rest of the KIT tier-A catalog and lets you move from a classroom demo to an automated pipeline without changing the string result.