Toolrack

Text Case Converter

Convert text between sentence case, title case, upper, lower, camelCase, PascalCase, snake_case, kebab-case and CONSTANT_CASE — with correct handling of accented and non-Latin scripts.

The conventions, and where each belongs

StyleExampleUsed for
camelCaseuserAccountIdJS, Java, C# variables
PascalCaseUserAccountIdClass and type names
snake_caseuser_account_idPython, Rust, SQL columns
kebab-caseuser-account-idURLs, CSS classes, filenames
CONSTANT_CASEUSER_ACCOUNT_IDConstants, env variables

Title case rules used here

The first and last words are always capitalised. Articles (a, an, the), coordinating conjunctions (and, but, or, nor, for, yet, so) and short prepositions (in, on, at, to, of, by, up and similar) stay lowercase when they fall in the middle. This is the AP and Chicago convention for headlines, and it is what most style guides expect.

Frequently asked questions

What is the difference between title case and capitalised words?

Title case follows editorial rules: capitalise the first and last word plus everything significant, but leave short articles, conjunctions and prepositions lowercase in the middle. Capitalising every word instead gives you "The Rise Of The Machines" where correct title case gives "The Rise of the Machines".

Which naming convention should I use in code?

Follow the language, not your preference. JavaScript and Java use camelCase for variables and PascalCase for classes; Python and Rust use snake_case; CSS classes and URLs use kebab-case; environment variables and constants use CONSTANT_CASE. Consistency inside a codebase matters far more than which convention is objectively better.

Does this work with accented and non-Latin characters?

Yes, including the dotted and dotless i. Generic uppercasing turns Azerbaijani "yüksəlişi" into "YÜKSƏLIŞI", which is wrong — the correct result is "YÜKSƏLİŞİ". The prose conversions here use locale-aware case mapping, so switching the page to Azerbaijani gives the right letters. Code conventions such as camelCase deliberately stay invariant, because applying the Turkish-i rule to identifiers is a classic source of bugs.

Why did my acronyms get mangled?

Converting "NASA report" to title case gives "Nasa Report", because the converter cannot tell an acronym from an ordinary word. Fix acronyms by hand afterwards — any tool that tried to guess would break more text than it fixed.

Related tools