Text workspace
Case Converter
Convert text between upper, lower, title, sentence, camel, Pascal, snake, kebab, and more in one panel.
Casing runs entirely in your browser. Paste is not uploaded.
What this panel does
Convert the same paste through common casing styles in one panel so you can compare title case, sentence case, camelCase, PascalCase, snake_case, and kebab-case without bouncing between editors. Spider_Case is not a single industry standard: GetToWork means Capitalized_Words with underscores (Hello_World_Example). Use snake_case when you need lowercase_words. Digits and punctuation stay put unless a mode splits on word boundaries, so check identifiers that contain numbers before you commit. Remote writers and developers use it to normalize ticket titles, variable names, and headings before they land in shared docs. Pair with Slug Generator when the destination needs a hyphenated URL path instead of a code identifier.
How to use it
Paste the text, pick a casing mode, and copy the result. Flip modes on the same paste when you need to compare camelCase against snake_case or Title Case against sentence case. For URL paths, finish in Slug Generator rather than forcing kebab-case by hand when accents or punctuation remain.
Assumptions
Modes transform the full input box. Word boundaries follow common letter/digit splits; punctuation may become separators. Spider_Case on GetToWork means Capitalized_Words with underscores.
Worked example
Input
due date reminder
Output
camelCase → dueDateReminder PascalCase → DueDateReminder snake_case → due_date_reminder kebab-case → due-date-reminder Title Case → Due Date Reminder Spider_Case (GetToWork) → Due_Date_Reminder
Quick comparison
| Option | Detail |
|---|---|
| Title / sentence | Human headings and prose-facing labels. |
| camel / Pascal | Identifiers in many JS and C-family codebases. |
| snake / kebab | Python-style names, flags, and path-ish stems. |
| Slug Generator | When you need a URL-safe hyphenated path with accent folding. |
More typical paste jobs
- due date reminder → dueDateReminder in camelCase before a commit.
- Try title case and sentence case on the same paste without leaving the page.
- Normalize a feature-flag name into PascalCase and kebab-case side by side.
Practical use cases
- A ticket title needs Title Case before it goes into Linear or Jira.
- A slug or identifier must become snake_case or camelCase before a pull request.
- You pasted mixed case from chat and need one consistent style for a status note.
- You are renaming a feature flag and want PascalCase and kebab-case side by side.
- You need sentence case for a doc heading after someone pasted Title Case everywhere.
Limitations
Not a rename refactor across a codebase. Word-boundary splits can surprise IDs that contain numbers or unusual punctuation. Spider_Case here is GetToWork’s Capitalized_Words definition, not a universal standard. Entire input box is transformed; there is no selection-only mode.
Text tool questions
- What does Spider_Case mean here?
- GetToWork uses Capitalized_Words with underscores (Hello_World_Example). Prefer snake_case when you need lowercase_words_with_underscores.
- Will numbers stay in place?
- Digits usually stay attached to neighboring words. Modes that split on word boundaries may still reshuffle separators around them, so review IDs with numbers before committing.
- Is title case the same as sentence case?
- No. Title Case capitalizes major words; sentence case capitalizes the first letter of the sentence. Pick the style your doc or ticket system expects.
- Can I convert only part of a long paste?
- Paste the segment you care about, convert it, then merge the result back. The tool always transforms the full input box.
Text tools on GetToWork process paste locally. Assumptions belong on the page. How our tools work · Editorial policy · Contact