Variable Naming Converter
Convert text between camelCase, snake_case, PascalCase, kebab-case, and more. One item per line.
How It Works
The Variable Naming Converter rewrites identifiers between every common programming-style convention: camelCase, PascalCase, snake_case, kebab-case, SCREAMING_SNAKE_CASE, and dot.notation. Paste any number of identifiers — one per line — into the input field, choose the target convention, and the tool splits each identifier on word boundaries (transitions between case, digits, and the separators _, -, ., space), normalises the case of each word, and rejoins them with the appropriate separator for the chosen output convention. The splitter understands acronyms heuristically: HTTPSConnection becomes https connection, then can be rendered as httpsConnection (camelCase), HttpsConnection (PascalCase), https_connection (snake_case), and so on. Lines are processed independently so you can paste a column copied from a spreadsheet or a list of database columns and convert all of them in one click, ready to drop into source code or a configuration file. Conversion is instant and runs entirely in the browser, with output staying in sync as you adjust either the input or the target convention.
Use Cases
- Renaming variables when migrating code between languages with different conventions
- Converting database column names to JSON field names
- Generating CSS class names from programmatic identifiers
- Batch-renaming a list of API fields to match a style guide
Frequently Asked Questions
- How does the converter handle acronyms like HTTPS or URL?
- It uses a heuristic: a run of consecutive uppercase letters is treated as a single word, so HTTPSConnection splits to https connection. This matches what most style guides recommend.
- Can I convert hundreds of identifiers at once?
- Yes. Each non-empty line is processed independently — paste a column of database column names or API field names and convert the entire batch in one click.
- What separators are recognised in the input?
- Underscores, hyphens, dots, spaces, and case transitions all act as word boundaries. Mixed inputs like camelCase_with-underscores are handled correctly.
- Why does the dot.notation output use lowercase?
- Dot notation is conventionally all-lowercase (used in feature flag keys and config namespaces). Use PascalCase if you want capitalised dotted segments.
- Is my list sent anywhere?
- No. The conversion runs entirely in your browser, so identifiers from internal codebases stay private.