Text Case Converter & String Formatter

Convert text and code variables between camelCase, PascalCase, snake_case, kebab-case, CONSTANT_CASE, Title Case, and Sentence case in real time. Features line-by-line batch transformation, word statistics, and naming convention presets for programmers.

How to use

1

Enter or paste your text, variable names, or multi-line list into the input box.

2

View instant transformations across 14 programming naming conventions and natural language casing formats.

3

Click Copy on any individual case card to immediately copy that formatted string to your clipboard.

4

Toggle Line-by-Line Batch Mode when converting column lists, database schemas, or code variables.

5

Inspect the real-time text statistics bar showing character, word, sentence, and line counts.

Programming naming conventions and casing styles

In software engineering, casing conventions dictate how multi-word identifiers (variables, class names, database tables, and URL paths) are formatted without using whitespace. Different programming languages and runtime frameworks enforce strict casing standards to ensure readability and maintain code style consistency.

Comparison of software casing conventions

Casing StyleExampleTypical Language Standards & Ecosystems
camelCaseuserProfileIdJavaScript, TypeScript, Java, and Kotlin variable and method names.
PascalCaseUserProfileIdC#, .NET, Java class names, React component identifiers, and TypeScript types/interfaces.
snake_caseuser_profile_idPython (PEP 8), Rust, Ruby, and relational database table/column naming (PostgreSQL, MySQL).
CONSTANT_CASEUSER_PROFILE_IDGlobal constants, C preprocessor macros, and environment variables (POSIX/Unix standards).
kebab-caseuser-profile-idRESTful API URLs, CSS class names (BEM syntax), HTML attributes, and Linux CLI flags.
COBOL-CASEUSER-PROFILE-IDLegacy COBOL programs and specialized mainframe transaction definitions.
dot.caseuser.profile.idConfiguration property hierarchies, Java package declarations, and logging scopes.
path/caseuser/profile/idFilesystem directory paths and routing path segments.
Header-CaseUser-Profile-IdHTTP request and response header fields (RFC 7230 / RFC 9110).
Title CaseUser Profile IdHeadlines, user interface navigation labels, and document titles.

Word boundary detection algorithm

Accurately converting between cases requires robust word segmentation. Our conversion engine splits strings across mixed delimiters (spaces, underscores, hyphens, dots, and slashes) and identifies transition boundaries between lowercase and uppercase letters (e.g., userProfile β†’ user, Profile) and between consecutive acronyms and words (e.g., parseXMLData β†’ parse, XML, Data).

Zero server transmission guarantee

Proprietary database schemas, internal API endpoint names, source code variables, and confidential notes are processed 100% locally in your web browser using client-side JavaScript. No text is transmitted to or stored on external servers.

Frequently asked questions

What is the difference between camelCase and PascalCase?

Both capitalize the first letter of each subsequent word without spaces. camelCase begins with a lowercase letter (e.g., userProfile), whereas PascalCase begins with an uppercase letter (e.g., UserProfile).

Why is snake_case standard for database columns?

Many SQL database engines (such as PostgreSQL) fold unquoted identifiers to lowercase by default. snake_case uses underscores to maintain word separation regardless of SQL case folding.

How does Title Case handle articles and prepositions?

Our Title Case converter capitalizes major words while optionally keeping minor grammatical particles (a, an, the, and, but, or, for, in, on, at, to) lowercase according to the Chicago Manual of Style guidelines.

Can I convert lists of database columns line-by-line?

Yes. Toggle the 'Line-by-Line Mode' to transform each line independently, allowing you to convert entire SQL table definitions or JSON schemas in a single operation.

Is my text data stored or tracked on a server?

No. All case conversions and text statistics run client-side in your web browser. No inputs or converted texts are sent to any remote server.