Free Tools /Development
Case Converter for Field Names
Convert any text or field name to camelCase, snake_case, kebab-case, PascalCase, CONSTANT_CASE and more.
- Free, no signup
- Runs in your browser
- Nothing stored
Calculating…
Who uses it, and for what
Map "First Name" from a form to first_name in your database without typos.
Rename a field consistently across API, code and database conventions.
Fix headings to Title Case or Sentence case in one paste.
How this tool works
Splits into words
Spaces, underscores, dashes, dots and camelCase boundaries are all treated as word breaks.
Rebuilds in 10 styles
Every common naming convention at once, so you can copy the one you need.
Instant
Updates as you type.
Guide
What are camelCase, snake_case and kebab-case?
They are naming conventions for writing several words as one identifier. camelCase joins the words and capitalises every word after the first (firstName). PascalCase capitalises every word (FirstName). snake_case joins lower-case words with underscores (first_name), CONSTANT_CASE does the same in capitals (FIRST_NAME), and kebab-case joins them with hyphens (first-name).
None of them is more correct than the others. What matters is using the convention the system expects and sticking to it, because a field called firstName and one called first_name are two different fields to a database or an API.
Which convention does each tool expect?
JavaScript and JSON APIs usually use camelCase for properties and PascalCase for classes. Python uses snake_case for variables and functions. SQL databases such as PostgreSQL usually use snake_case for tables and columns, because unquoted identifiers are folded to lower case. URLs, CSS classes and file names usually use kebab-case. Environment variables and constants use CONSTANT_CASE.
Why does case matter in automation workflows?
In n8n, Make or Zapier you map fields from one app to another. A form may send "First Name", a CRM may expect firstname and a database first_name. One wrong character and the value is silently dropped or a new empty field is created. Converting names once, and pasting the exact key, avoids that whole class of bug.
Frequently asked questions
Which case should I use for database columns?
snake_case is the most common for SQL databases; camelCase for JSON APIs in JavaScript ecosystems.
Does it keep numbers?
Yes, digits stay attached to their word.
Is anything stored?
No.
What is the difference between camelCase and PascalCase?
camelCase starts with a lower-case letter (customerId); PascalCase starts with a capital (CustomerId). The rest of the words are capitalised in both.
Should JSON keys be camelCase or snake_case?
Either works; follow the API you are talking to. Many JavaScript APIs use camelCase and many Python or Ruby APIs use snake_case. Consistency inside one API matters more than the choice.
Related free tools
All tools →Webhook Sample Payload Generator
Generate realistic sample payloads for Stripe, Shopify, HubSpot, and Typeform events, no live trigger needed.
JSON ⇄ CSV Converter
Paste either format, get a clean conversion in the other, ready for the next node.
CSV Column Mapper
Paste two CSV headers, get instant field-mapping suggestions for a migration or integration.
Regex Tester for Automation
Test a pattern against real sample text and get a plain-English explanation of what it matches.
JWT Decoder
Paste a JWT to instantly see its header, payload, and expiry, decoded and formatted.
Base64 & URL Encoder / Decoder
Encode or decode Base64 and URL-encoded strings instantly, both directions, auto-detected.
Done for you
Want this running inside your business, automatically?
We build the workflow behind tools like this one, wired to your CRM, inbox and apps, and keep it running. Fixed price, from $390 a month.