Naming Convention Tools
Map a phrase or identifier into the naming style your layer expects — JavaScript camelCase, React PascalCase, Python/SQL snake_case, URL kebab-case, or a CMS slug.
Pick one convention per layer and stay consistent. Public URLs and CSS classes usually want hyphens; JSON APIs in JS ecosystems usually want camelCase; databases often want snake_case. The slug generator is stricter about punctuation than a plain kebab-case pass.
These converters split on spaces, underscores, hyphens, dots, and camel boundaries. They do not refactor call sites — convert the name, then rename in your IDE.
Tools in this hub
camelCase Converter
Migrating SQL columns to a Node API, turning spreadsheet headers into TypeScript property names, renaming CSS modules that a linter wants in camelCase, and converting a design-doc phrase into a variable name. Paste a list, one identifier per line, for bulk work, then review acronyms before you commit.
PascalCase Converter
Naming React components and matching file names to their default export, generating TypeScript interfaces from a design-doc phrase list, turning SQL or API field labels into C# or Java class names, and converting a kebab-case or snake_case token into a type name. Paste one identifier per line for bulk work, then review acronyms before you commit.
snake_case Converter
Aligning a Node or TypeScript mapper with PostgreSQL column names, generating Python method names from a product spec, turning spreadsheet headers into database fields, and preparing keys that will later become environment-style constants (then uppercasing). Paste one identifier per line for bulk work.
kebab-case Converter
CSS class names and BEM blocks, REST path segments, data-testid values, design-token names that a style guide wants dashed, and a first-pass convert from camelCase props into a URL-ish token. Paste one name per line for bulk work.
dot.case Converter
Building i18n keys, namespacing telemetry events, matching a config schema that already uses dotted paths, and turning spreadsheet headers into lodash-style accessor strings. Paste one identifier per line for bulk work, then shorten overly deep keys by hand.
Slug Generator
Blog posts, documentation pages, product listing URLs, knowledge-base articles, and CMS permalink fields when you have a working title and need a path before publish. Also useful for turning a noisy marketing headline into a short candidate slug you can still edit by hand.
Related developer hubs
Frequently asked questions
Which style should I use for URLs?+
Prefer kebab-case or the Slug Generator for public paths. Hyphens are the conventional choice for readable URLs and make words easier for people and search engines to distinguish than underscores.
camelCase vs PascalCase?+
Same word splits; PascalCase capitalizes the first letter (UserProfile) and is the React component / type convention. camelCase keeps the first letter lower (userProfile).