What is Naming Style Converter?
Naming Style Converter standardizes API fields, database columns, configuration keys, and code identifiers. It detects spaces, hyphens, underscores, case boundaries, and common initialisms before producing camelCase, PascalCase, snake_case, kebab-case, or CONSTANT_CASE. Multiline input is handled one item per line for practical batch cleanup. Common workflows include the following. Convert backend snake_case fields to frontend camelCase. Standardize environment variables, database columns, and API parameters. Clean identifiers copied from documentation or spreadsheets before review. The page also documents input boundaries, output behavior, and practical cautions so you can review the result before putting it into an application, configuration, test, or production workflow.
When to use it
- Convert backend snake_case fields to frontend camelCase.
- Standardize environment variables, database columns, and API parameters.
- Clean identifiers copied from documentation or spreadsheets before review.
How to use it
- Enter one or more identifiers, one per line.
- Choose the target naming style.
- Convert and review acronym and digit boundaries.
- Load one of the realistic examples first to verify the selected options and processing direction before replacing it with your own data.
- Review the output, status message, and documented limits; copy, download, or continue only after the result matches your expectation.
Runnable examples
The “Example 1” and “Example 2” buttons load the matching inputs. They cover different structures, directions, or boundaries and can be run directly in the workspace.
Example 1
HTTP response_code-2026
user profile URL
JSONLane tool statusExample 2
apiResponseTime
MAX_retry-count
user profile IDInput rules
- Each line is processed as one identifier and blank lines remain blank.
- Spaces, underscores, hyphens, and most punctuation act as word boundaries.
- Initialisms, numbers, and Unicode letters are detected where practical but still require style-guide review.
- Text input is counted before processing and is limited to 200,000 characters on this page; file modes apply the separate file limit shown in the workspace.
- Punctuation becomes a word boundary.
Output rules
- Line order and line count remain aligned with the input.
- camelCase lowers the first word and PascalCase capitalizes every word.
- Snake, kebab, and constant modes join words with underscores, hyphens, or uppercase underscores.
- Output reflects only the current input, direction, and options; rerun after changing a mode or value instead of treating an earlier result as current.
- Acronym policies vary between codebases.
Limitations and cautions
- Punctuation becomes a word boundary.
- Acronym policies vary between codebases.
- The result is not validated as an identifier in a specific language.
How your data is handled
Word splitting and recomposition run entirely in the current browser. Identifiers, output, and options are not uploaded or stored.