AaCaseConvertly

kebab-case Converter

Convert text to kebab-case — lowercase words joined by hyphens, for URLs, CSS and file names.

0 characters0 words0 lines0 sentences
kebab-case
Your kebab-case result will appear here…

All cases — live preview (click any result to copy it)

UPPERCASE
Start typing to see UPPERCASE…
lowercase
Start typing to see lowercase…
Title Case
Start typing to see Title Case…
Sentence case
Start typing to see Sentence case…
Capitalized Case
Start typing to see Capitalized Case…
aLtErNaTiNg CaSe
Start typing to see aLtErNaTiNg CaSe…
RaNdOm CaSe
Start typing to see RaNdOm CaSe…
iNVERSE cASE
Start typing to see iNVERSE cASE…
snake_case
Start typing to see snake_case…
camelCase
Start typing to see camelCase…
PascalCase
Start typing to see PascalCase…
kebab-case
Start typing to see kebab-case…
CONSTANT_CASE
Start typing to see CONSTANT_CASE…
Train-Case
Start typing to see Train-Case…
dot.case
Start typing to see dot.case…
slugify
Start typing to see slugify…

Private by design — every conversion runs locally in your browser. Your text is never uploaded, stored or tracked.

kebab-case is a naming convention where words are written in lowercase and joined by hyphens: my-first-post, main-navigation, checkout-button. The words look like pieces of food skewered on a kebab stick, which is where the name comes from. It is the standard for URL paths, CSS class names, HTML attributes and command-line flags.

Hyphens are the one separator search engines treat as a word break in URLs, which is why every major SEO guideline recommends kebab-case for slugs. This converter splits your text into real words first — including camelCase and PascalCase identifiers — then joins them with hyphens and strips punctuation.

When to use it

  • Building readable, SEO-friendly URL paths and file names
  • Naming CSS classes and IDs in a consistent convention
  • Creating command-line flags and configuration keys (--dry-run, --output-dir)
  • Converting class names or headings into URL-safe strings
  • Standardizing asset names before uploading to a CMS or static site

How it works

  1. The input is split into words by the identifier-aware splitter — camel humps, PascalCase boundaries, underscores, spaces and numbers are all word edges.
  2. Every word is lowercased in full.
  3. The words are joined with single hyphens, and punctuation is removed rather than turned into stray hyphens.
  4. Accents are not stripped here — for a publish-ready URL, use the slug generator, which also transliterates accented letters.

Examples

Input
Hello World Example
Output
hello-world-example
Input
My First Blog Post!
Output
my-first-blog-post

Punctuation is removed, not converted into stray hyphens.

Input
UserProfileCard component
Output
user-profile-card-component

PascalCase identifiers are split at their word boundaries.

Good to know

kebab-case won the URL because of a search-engine rule of thumb that has held for two decades: hyphens separate words, underscores join them. A URL like /choosing-a-mortgage reads to a search engine as the words “choosing a mortgage”; the underscored version reads as one invented word. The same logic made kebab-case the standard for CSS classes, where it has a second advantage — it cannot be confused with the camelCase and snake_case names used in the JavaScript and backend code that the CSS sits alongside, so each layer of a web project speaks its own visible dialect.

Naming a thing well in kebab-case is mostly about restraint. Use the words a reader would search for, skip filler where the meaning survives (“best-running-shoes”, not “the-best-running-shoes-for-you”), and never put information in a URL that will change — dates, prices and version numbers in slugs are future redirects waiting to happen. Convert the finished title here, or use the slug generator when you also need accents removed and full URL cleaning.

Frequently asked questions

Why are hyphens better than underscores in URLs?

Google has stated for years that hyphens are treated as word separators in URLs, while underscores are treated as joining the words into one. “my-first-post” reads as three words; “my_first_post” reads as one long word. That is why URL slugs use kebab-case.

What is the difference between kebab-case and a slug?

They overlap heavily. A slug is the finished URL segment, which is usually kebab-case plus extra cleaning: accents removed (é → e), stop words sometimes dropped, and a length limit applied. The slug generator on this site does that extra cleaning; this converter focuses on the case itself.

Can kebab-case be used for programming variables?

In most languages, no — a hyphen is read as a minus sign, so my-variable would be parsed as subtraction. Use kebab-case for URLs, CSS, file names and flags, and snake_case or camelCase inside code.

Is my text uploaded or stored?

No. The conversion runs entirely in your browser. Nothing you type is sent to a server, stored or logged.

Is kebab-case the same as a URL slug?

Very close, but a slug is the finished product: kebab-case plus extra cleaning such as removing accents, dropping some filler words and enforcing a sensible length. Every slug is kebab-case; not every kebab-case string has had the slug treatment. The slug generator on this site does the extra steps.

Why is it called kebab-case?

Because the lowercase words strung along a hyphen look like pieces of food on a skewer. The name is part of a family of food-and-animal case names — snake_case, camelCase — that developers coined because the shapes are easier to remember than formal terms.

Related tools