使用繁體中文瀏覽?切換到繁體中文
使用简体中文浏览?切换到简体中文
日本語で表示しますか?日本語に切り替える
한국어로 보시겠어요?한국어로 전환
ดูหน้านี้เป็นภาษาไทยไหม?เปลี่ยนเป็นภาษาไทย
Lihat halaman ini dalam bahasa Indonesia?Beralih ke bahasa Indonesia
Xem trang này bằng tiếng Việt?Chuyển sang tiếng Việt
यह पेज हिन्दी में देखें?हिन्दी में बदलें
Voir cette page en français ?Passer au français
Diese Seite auf Deutsch ansehen?Zu Deutsch wechseln
¿Ver esta página en español?Cambiar a español
Visualizzare questa pagina in italiano?Passa all'italiano
Deze pagina in het Nederlands bekijken?Overschakelen naar Nederlands
Wyświetlić tę stronę po polsku?Przełącz na polski
Ver esta página em português?Mudar para português
Открыть страницу на русском?Переключить на русский
Bu sayfayı Türkçe görüntülemek ister misiniz?Türkçeye geç
عرض هذه الصفحة بالعربية؟التبديل إلى العربية
Skip to content

Case Converter

Convert pasted text and naming snippets between uppercase, lowercase, title case, sentence case, toggle case, camelCase, PascalCase, snake_case, kebab-case, CONSTANT_CASE, dot.case, and path/case.

Input Text

Case Converter

Quick Start

1
Paste text or a naming snippet.
2
Choose a target case or naming format.
3
Review the editor result, then copy it.
4
To convert the result again, edit or paste it back first.

Common Scenarios

Variable/function naming

convert candidate names to camelCase/PascalCase/snake_case before using them in code

CSS/API paths

prefer kebab-case for class names and path segments to improve readability

Database fields/constants

switch to snake_case or CONSTANT_CASE to match conventions

Path-like segments

turn spaced labels into kebab-case or path/case snippets; this does not validate real file paths

APIs/routes

REST paths in kebab- or snake-case; GraphQL fields in camelCase

Docs formatting

Title Case for headings; Sentence case for paragraph openers

Multi-line name lists

paste several candidate names, convert them together, then copy the current result

Before code review

convert candidate names first, then replace them manually in code or docs

Format Reference

lowercase: hello world example
UPPERCASE: HELLO WORLD EXAMPLE
Capitalize: Hello world example
Title: Hello World Example
Sentence: Hello world example. Next sentence
camelCase: helloWorldExample
PascalCase: HelloWorldExample
snake_case: hello_world_example
kebab-case: hello-world-example
CONSTANT_CASE: HELLO_WORLD_EXAMPLE
dot.case: hello.world.example
path/case: hello/world/example
Toggle case: hello world example -> HELLO WORLD EXAMPLE
aLtErNaTiNg: hElLo WoRlD eXaMpLe

Conversion Boundaries

Format cards convert from the current original baseline; they are not a chained conversion pipeline
The Copy button copies the current editor content. Format cards switch results instead of copying
camelCase, snake_case, kebab-case, dot.case, and path/case tokenize Unicode letters and numbers; punctuation and emoji usually become separators
path/case is a path-like segment style only; it does not check file-name validity, preserve extensions, or create folders
This page does not scan code, rename files, update schemas, apply lint fixes, or generate URL slugs
Copy the current editor content when you need the result. File download, CSV/JSON export, and all-formats export are outside this tool.

Usage Advice

Frontend naming: PascalCase for components/types, kebab-case for CSS classes and URLs
Backend naming: snake_case for Python and database fields, CONSTANT_CASE for constants and env vars, camelCase where your style guide expects it
API design: keep REST paths consistent with kebab- or snake-case; GraphQL fields stay in camelCase

Limitations & Compatibility

To keep the page responsive, split very large texts instead of treating this as an unlimited batch processor
Special symbols: characters like @#$ become separators, matching the chosen naming style
Numerals: numbers stay as-is; separators are added only where digits meet letters to avoid breaking values

Privacy & Security

Case conversion runs locally in your browser. The current editor text may stay as a browser draft, and the selected category tab may be kept in browser storage. If a saved workspace or WebDAV sync is enabled, that editor text and tab preference may be saved through that sync. Converted text replaces the same editor content, and copied values are generated from that editor; this tool does not upload files, create attachments, export files, or save a separate result list.

FAQ

7

Continue with these related tools for the next step.

Community

© CrateX.app · All Rights Reserved