About SQL Identifier Caser

Convert SQL identifiers between snake, camel, and Pascal case. Part of the DevTools Surf developer suite. Browse more tools in the Data / SQL collection.

Use Cases

• Convert database column names to match application naming conventions
• Map API response fields between snake_case backends and camelCase frontends
• Prepare SQL schema identifiers for ORM model generation
• Standardize inconsistent column naming in legacy databases

Tips

• Paste SQL column names or identifiers — each line is converted independently
• Choose between snake_case, camelCase, and PascalCase output styles
• Handles mixed separators: underscores, hyphens, spaces, and existing camelCase are all detected automatically

Fun Facts

• SQL is case-insensitive for keywords by convention, but identifier casing varies wildly: PostgreSQL folds unquoted names to lowercase, MySQL depends on the OS file system, and Oracle folds to uppercase.
• The snake_case convention became dominant in SQL because early databases were limited to uppercase letters and underscores — camelCase wasn't distinguishable without case sensitivity.
• Ruby on Rails popularized automatic snake-to-camel conversion in 2004 with ActiveRecord, which maps snake_case database columns to camelCase Ruby attributes — a pattern now standard in most ORMs.

FAQ

Which case conventions?

snake_case (Postgres style), camelCase (rare in SQL), PascalCase (some .NET ORMs), SCREAMING_SNAKE_CASE (constants). Mix-and-match cross-conversions.

Why would I convert?

Migrating an ORM that mandates a specific case, or consolidating databases where one uses snake_case and another camelCase. Also: Prisma models vs underlying Postgres tables.

Does it preserve table vs column context?

Yes — common convention: table names plural snake_case, column names singular snake_case. The tool respects both.

Keywords stay uppercase?

Yes — SQL keywords (SELECT, FROM, WHERE) are preserved. Only identifiers are converted.