A Field Guide to Case Conversion: camelCase, snake_case, kebab-case
Jun 30, 2026 · 3 min read
camelCase shows up wherever JavaScript conventions rule: JSON API responses, JS/TS variable names, most frontend config. snake_case shows up wherever Python or SQL conventions rule: database columns, Python variables, a lot of REST API bodies written by backend teams that lead with Python or Ruby.
kebab-case is mostly a URL and CSS convention — file names, route segments, CSS class names, HTML attributes — because hyphens are safe in places underscores and camelCasing sometimes aren't. PascalCase is reserved for types, classes and components across nearly every language.
The friction shows up at the boundary between two systems that pick differently — a Python backend returning snake_case fields into a JavaScript frontend that wants camelCase, or a database column name that needs to become a URL slug. That's the exact conversion the String & ID Formatter here handles, along with Base64 and URL encoding for the adjacent problem of getting a string safely into a header or query string.
More from the blog
What We're Building Next: dont-break-prod
A PR-review training game for payments engineers — read the contract, read the code, decide if it's safe to ship.
5 Habits for Debugging Messy JSON Payloads Faster
The difference between a two-minute payload review and a twenty-minute one usually comes down to a few small habits.
SQL Formatting Conventions That Make Code Review Easier
A query that's easy to review is one where the diff shows the actual change, not a reflow of every line around it.