Convert API field names between cases

Rename a whole column of identifiers between camelCase, snake_case, kebab-case and CONSTANT_CASE in one paste, with acronyms handled properly.

Open this example in Case Converter

Open the tool, then paste the sample input below. Everything runs locally in your browser.

Open this example in Case Converter →

The problem

A JSON API sends camelCase, the database wants snake_case, and the environment variables want CONSTANT_CASE. Renaming forty fields by hand is where typos enter a mapping layer - and an acronym such as HTTP breaks most naive converters.

Sample input

JSON field names
parseHTTPResponse
userFirstName
orgID

Expected output

snake_case
parse_http_response
user_first_name
org_id

How to do it

  1. Paste one identifier per line.
  2. Choose the target casing - snake_case for Python or SQL, camelCase for JSON, CONSTANT_CASE for environment variables.
  3. Decide whether acronyms stay upper-case (HTTPResponse) or are normalised (HttpResponse).
  4. Copy the converted column straight into your model, migration or mapping file.
  5. Open All variants when you need the same name in several conventions at once.

Common mistakes

  • Splitting an acronym letter by letter, producing parse_h_t_t_p_response.
  • Losing digits at a word boundary, so utf8Decoder becomes utf8decoder.
  • Using a slug with accented characters in it, which breaks some routers.
  • Renaming a field in code but not in the migration that created the column.

Related tools

FAQ

How do I convert camelCase to snake_case?

Paste the identifiers and pick snake_case as the target. Each line is converted independently, so a whole column converts at once.

What happens to acronyms such as HTTP or ID?

They are treated as one word, so parseHTTPResponse becomes parse_http_response. Turn on "keep acronyms" to preserve the original capitalisation instead.

Can I generate a URL slug?

Yes. The slug output lowercases, transliterates accented characters to ASCII, strips punctuation and collapses repeated hyphens.

Is my list uploaded?

No. The conversion runs locally in your browser.

This guide uses browser-local tooling. Avoid pasting production secrets unless you understand what the tool displays and shares.

Explore related tools

Continue with adjacent browser-based tools for the same workflow.

View data cleanup tools →

Convert field names between cases: quick answer

Use this when mapping an API payload onto database columns, generating environment variable names, or producing URL slugs. Paste the whole column, pick the target convention, and copy the result rather than renaming each field by hand.

What to verify

Check the acronym handling, any digit boundaries, and whether the target system has a length limit or a reserved-word list. Diff the old and new names before applying a bulk rename.

Recommended next steps