Overview
Repairs shouting text: it lowercases the body and capitalises the first letter of each sentence, while refusing to destroy the things it can identify — standalone I, acronyms like NASA and API, and words like iPhone whose capitals carry meaning. Periods after abbreviations such as e.g. and Dr. no longer trigger false new sentences.
How It Works
Paste the text into the input box; the corrected version appears live in the output panel. The default sample is a small demonstration: “dr. smith and i compared the GPS figures. the API checked out.” comes back with Dr., I, GPS and API intact and exactly two capitals added — the sentence starts. There is no convert button and no options to configure; the value of the tool is in what it refuses to lower, which is described below the controls.
Step-by-Step Usage Guide
- Paste the shouting or badly-cased text into the input box.
- Read the output; it updates as you type, so fixes are immediate.
- Scan for proper nouns — the tool lowercases ordinary words but deliberately preserves any all-caps token it cannot rule out as an acronym.
- Copy the corrected text when the review passes.
Technical Specifications & Standards
The classic implementation lowercases everything and then capitalises after every period. Feed that chain “see e.g. the report. it works.” and it answers “See e.g. The report. It works.” — capitalising mid-sentence after the abbreviation's period (verified behaviour of the naive regex chain). This tool reorders the problem. First it asks whether the whole input is shouting: if every letter in the text is uppercase, the caps carry no information, so wholesale lowercasing is safe. If the input is mixed, all-caps runs of two or more letters are treated as acronyms and preserved, because in mixed text an all-caps token is far more likely to be NASA or API than residue. Words with internal capitals — iPhone, McDonald, eBay — always survive, since no English word is normally spelled that way. The standalone pronoun i is capitalised to I in any position. Only then are sentence starts capitalised: the beginning of the text and every letter that follows a run of ., ! or ? (optionally closed by a quote mark) and whitespace. Two guards keep that boundary honest: a period preceded by a common non-terminal abbreviation — e.g., i.e., vs., Dr., Mr., Inc., approx. and others — does not start a sentence, and a run of three or more dots is read as an ellipsis, not a sentence end. The documented limit is proper nouns: nothing in a string of text reliably distinguishes the surname Smith from an ordinary word, and the same logic that saves NASA saves an accidental SMITH. The tool lowercases only what it can justify and leaves the rest for you, which is why a ten-second review of names after conversion is part of the workflow, not an optional extra.
Targeted Use Cases
- Rescuing forum comments, spreadsheet cells or emails typed with Caps Lock on.
- Converting ALL-CAPS legal or marketing copy into readable body text without losing API, NASA or similar identifiers.
- Normalising headings pulled from a database that stores them in inconsistent case.
- Fixing the output of an OCR pass that guessed capitalisation badly.
Notes & Gotchas
- Expect to review names after conversion; no text-only tool can know that Smith is a surname.
- Feed mixed-case input when you can — in fully-shouting text the tool cannot tell an acronym from residue, so NASA comes back as Nasa.
- Do not use this on text where uppercase carries legal or technical meaning, such as standards documents that capitalise defined terms.
- For headlines rather than sentences, use the Title Case tool instead — its small-word rules are the wrong shape for body text.
Frequently Asked Questions
Why did NASA survive but AND did not?
In mixed input, tokens of two or more capital letters are treated as possible acronyms and kept. Very common words such as AND, THE and OF are on a short exception list because they are never acronyms, so shouting residue in them is lowercased normally.
Why does “e.g. the report” not come back as “E.g. The report”?
The period after e.g. is on the tool's list of non-terminal abbreviations, along with i.e., vs., Dr., Mr. and others. The guard checks the word before the punctuation, so only genuine sentence ends trigger a capital.
Can it detect proper nouns?
No text-only tool can do that reliably. The tool's compromise is preservation: anything with internal capitals or an all-caps shape survives untouched, and lowercase proper nouns stay lowercase mid-sentence because only sentence starts are capitalised. Review names before publishing.
Why did my fully-uppercase sentence keep some words in caps?
If the whole input is uppercase, the tool lowercases everything, so that case does not apply. It appears in mixed input: an all-caps word there is treated as a possible acronym (NASA) and preserved. That is the price of not destroying acronyms — the tool cannot tell NASA from an accidental SMITH.