تبدیل حروف

What the Case Converter does

The WriteWithin Case Converter reshapes letter casing in a block of text you paste into the input area. Choose uppercase, lowercase, title case, sentence case, or toggle case, and the output updates as you type. Nothing leaves your browser — there is no server round trip and no account required. That privacy model matches the rest of the writing toolkit on WriteWithin, where sensitive lists and drafts stay on your device.

People reach for a case converter after PDF copy-paste turns headings into ALL CAPS, after a spreadsheet export shouts product names, or after you held Shift too long in a chat box. Retyping a long block to fix casing wastes time and introduces new typos. One mode click applies a consistent rule to every character the mode affects.

The tool is intentionally small: input, mode buttons, output, copy, and clear. It is not a grammar checker or style guide enforcer. Understanding when each mode helps — and where Unicode and code identifiers need caution — saves frustration later.

Why letter case still matters

Case carries meaning even when readers do not consciously notice it. ALL CAPS reads as shouting in prose. Title Case signals headings in slide decks and blog CMS fields. lowercase domains and paths appear in developer docs and DNS examples. Sentence case matches body copy in newsletters and support articles.

Systems are picky. A CSV import may expect sku-1042 in lowercase while marketing wants SKU-1042 on the label line. JSON keys and environment variables often require exact casing; changing them breaks builds. A converter speeds bulk reshaping when the underlying words are right but the caps are wrong.

Accessibility matters too. Screen readers sometimes spell ALL CAPS letter by letter. Fixing case is a quick pass before publishing public-facing text copied from legacy PDFs or scanned documents.

How to use the Case Converter

Paste your source text into the input textarea. The output pane mirrors conversions live. Click a mode button along the top — uppercase, lowercase, title case, sentence case, or toggle — and the active mode highlights. Every keystroke in input re-runs the selected transformation on the full block.

Review the output before copying. Title and sentence modes apply English-oriented rules, not a full locale-aware title dictionary. They will not know that “iPhone” stays lowercase or that Chicago style lowercases “and” in some titles. For mixed lists, convert chunks separately: names in title case, product codes in upper or lower as required.

Click Copy to send the result to the clipboard, or Clear to reset both panes. There is no undo stack; keep the original in source until you are satisfied. If the paste includes odd spacing from Word or the web, run the Whitespace Cleaner first so line breaks do not split words mid-conversion.

When to use each mode

UPPERCASE

Use uppercase for acronyms expanded from messy source, form fields that literally require ALL CAPS, and legacy mainframe-style codes. It is also a quick way to compare two strings case-insensitively by eye after both are uppercased — though deduplication belongs in Line Tools, not here.

Avoid uppercasing long prose meant for humans to read. Convert headings back from PDF shout-case to something gentler using title or sentence mode instead.

lowercase

Lowercase suits email local parts you are normalizing for comparison, slug previews, hostname lists before sorting, and CSS class names when your style guide demands it. Developers paste enum-like constants here when refactoring naming convention across a pasted excerpt.

Do not lowercase passwords, base64, or mixed-case API keys where casing is significant. The tool does not know which lines are secrets versus labels.

Title Case

Title case capitalizes the first letter of each word as defined by a simple word-boundary rule: lowercasing everything, then uppercasing characters that follow word boundaries. It works well on plain English names and headings when you need speed over publishing-house nuance.

It will capitalize short prepositions and articles mid-title. Proper nouns with internal capitals — McDonald, WriteWithin — may flatten incorrectly. Fix those manually after bulk conversion.

Sentence case

Sentence case lowercases the block, then uppercases the first letter of the string and the first letter after sentence-ending punctuation (., ?, !, and ellipsis). Body paragraphs, release notes, and email intros map naturally to this mode.

Abbreviations with periods can trigger extra “sentences.” URLs and decimal numbers may behave unexpectedly. Proofread output when the source is technical.

tOGGLE cASE

Toggle inverts each letter’s case — upper becomes lower and lower becomes upper. It helps recover text typed with Caps Lock on, or playfully fix shift-key accidents. It is rarely a publishing finish step; it is a recovery tool.

Non-letters pass through unchanged. Numbers, punctuation, and spaces stay put.

Publishing vs code: different rules

For publishing workflows — blog posts, handouts, slide titles — title or sentence case plus manual proper-noun fixes is usually enough. Pair with the Line Counter to hit word limits after casing is settled, and with the Character Cleaner if smart quotes from Word survived the paste.

For code and data workflows, never bulk-convert a mixed file containing identifiers, base64, regex, or URLs unless you mean to break things. Convert only the columns or lines that are purely human labels. Keep JSON keys, camelCase variables, and hash strings out of the input entirely.

When preparing CSV names for mail merge, convert a column copied alone rather than the whole sheet. When normalizing link text, remember the URL Cleaner handles URLs; case converter handles words around them.

Unicode and special characters (light caveats)

JavaScript’s toUpperCase and toLowerCase follow Unicode rules for many scripts, but they are not a substitute for linguistically correct casing in Turkish, German sharp s, or Greek sigma variants. English-centric publishing modes — title and sentence — use regex word boundaries that align with ASCII letters and digits. Words in other scripts may not title-case the way a native editor would.

Combining characters and emoji generally pass through or change case in ways that may look odd. A flag emoji does not have a meaningful upper variant; the tool leaves symbols alone in toggle mode except for letters. If you work heavily in multilingual copy, treat output as a first pass and review with a native speaker or locale-aware editor.

This is not a limitation unique to WriteWithin; lightweight converters trade locale tables for speed and zero upload. Knowing the boundary prevents blaming the tool for Chicago Manual rules it never claimed to implement.

Benefits

• Fast bulk fixes — one mode replaces hundreds of manual shift-key edits
• Live preview — compare input and output side by side before copying
• Private — client names, employee lists, and unreleased copy stay in the tab
• No install — works anywhere you have a browser, including shared machines
• Pairs with cleaners — fix invisible junk first, then casing, then count lines

Common mistakes

Running title case on product SKUs and passwords. SKUs often mix digits and case by design. Lowercasing a password changes it. Separate human prose from machine identifiers before converting.

Expecting dictionary-aware title rules. “The Lord of the Rings” will become “The Lord Of The Rings.” That is correct for the algorithm, not for every style guide. Hand-fix small proper nouns after bulk work.

Converting code in place. camelCase and PascalCase collapse to wrong shapes in every mode except toggle, which makes a mess. Use editor-aware refactors for source code; use this tool for pasted plain labels.

Ignoring locale. Turkish dotted and dotless I issues appear in any basic converter. For Turkish public text, verify in a locale-aware word processor after conversion.

Skipping whitespace cleanup. Hard line breaks mid-word from PDF paste produce title case on each fragment. Clean lines first with whitespace or line tools.

Related WriteWithin tools

Casing is usually mid-pipeline. Start with the Character Cleaner when curly quotes and zero-width characters ride along from Word. Normalize spaces in the Whitespace Cleaner. Dedupe or sort name lists in Line Tools before mail merge. Measure final length in the Line Counter. Shorten ugly links in the URL Cleaner when bios and footers need character room. Practice typing mixed-case passwords and prose faster with the Typing Test on the same private platform.

Explore WriteWithin for the full toolkit and language keyboards when your case-fixing session turns into writing in another script entirely.