Dev Case Converter
Convert identifiers and text to any code convention: camelCase, PascalCase, snake_case, SCREAMING_SNAKE, kebab-case, dot.case, or path/case. Auto-detects your input format.
How to use the dev case converter
Paste an identifier or phrase and click a case button. The converter detects your input format automatically and shows a badge confirming what it found. Each button displays a monospace example so you can see the output format before clicking. Use Replace to swap the converted text directly into the editor.
How case conversion works for code
The converter first tokenises the input by splitting on whitespace, hyphens, underscores, dots, slashes, and camelCase boundaries (uppercase letters). This produces a clean list of words which are then reassembled into the target format. This means you can convert freely between any two formats — camelCase to kebab-case, snake_case to PascalCase — without any intermediate step.
Why consistent naming conventions matter
Mixing naming conventions in a codebase is a consistent source of bugs and confusion. A variable called user_id in one file and userId in another forces readers to track which convention applies where. When refactoring across language or framework boundaries — moving a Python snake_case API response into a JavaScript camelCase object — this tool saves the tedious manual renaming.
Frequently asked questions
What is the difference between camelCase and PascalCase?
camelCase starts with a lowercase letter and capitalises each subsequent word: helloWorldFoo. PascalCase (also called UpperCamelCase) capitalises every word including the first: HelloWorldFoo. In most languages, camelCase is used for variable and function names; PascalCase is used for class and component names. React components, TypeScript interfaces, and C# classes typically use PascalCase.
When should I use snake_case vs kebab-case?
snake_case uses underscores and is conventional in Python (variable names, file names), Ruby, SQL (column names), and Rust. kebab-case uses hyphens and is conventional in URLs, HTML attributes, CSS class names, and Lisp-family languages. The practical rule: underscores for code; hyphens for URLs and CSS. Never use hyphens in Python or JavaScript identifiers — they parse as subtraction.
What is SCREAMING_SNAKE_CASE used for?
SCREAMING_SNAKE_CASE (all uppercase with underscores) is the convention for constants in most languages — Python, JavaScript/TypeScript, Java, and C. The convention signals 'this value never changes'. Examples: MAX_RETRY_COUNT, API_BASE_URL, DEFAULT_TIMEOUT_MS. Environment variable names are also conventionally written in SCREAMING_SNAKE_CASE.
What is dot.case used for?
dot.case is less common and mainly appears in configuration files and property access chains. Java package names use it (com.company.package). Some config file key names use it (spring.datasource.url). JavaScript property chains (object.property.subproperty) are technically dot.case. It's not used for identifiers in most languages because the dot is a reserved operator.
How does the tool handle multi-word input?
The converter first splits your input into words by detecting existing casing boundaries and separators. It recognises: spaces, hyphens, underscores, dots, forward slashes, and camelCase/PascalCase word boundaries. So 'hello-world_foo' and 'helloWorldFoo' and 'Hello World Foo' all produce the same word tokens, which are then reassembled in whichever format you select.
Tools you might like
17 tools across three categories — all free, no signup required.
Measure, analyze, and optimize your writing. Count words, estimate reading time, check readability scores, and find which keywords dominate your draft.
Transform and clean text into the format you actually need. Convert case, strip junk whitespace, remove duplicate lines, and generate filler copy in seconds.
Built for code and data work. Convert identifiers between naming conventions, inspect byte counts, strip HTML tags, count lines, and deduplicate with a diff view.