PasteCleanly

PasteCleanly / Text tools

Change the case of your text

Switch between uppercase, lowercase, sentence case and title case without retyping your text.

Your pasted text stays in this tab. How privacy works

Example: turn a rough heading into title case

Original
a guide through the archive: notes from nasa
General Title Case
A Guide Through the Archive: Notes From NASA

Choose Title Case and leave Keep common acronyms on to preserve NASA.

Choose the kind of capitalization you need

Uppercase and lowercase

Use these for a label, a heading, or a list of plain words. Check before changing a case-sensitive URL, filename, or identifier. These two modes do not preserve acronyms or preferred spellings, because they are meant to change the case of every letter.

Sentence case

Use Capitalize Each Word when even short words should start with a capital. Swap Case flips letter case; it can expand some Unicode letters, so running it twice is not a reliable undo.

Use this for prose or labels written as sentences. It lowercases the text and capitalizes the detected starts. Abbreviations and names may still need a second look.

English title case

  • General: a simple headline convention that leaves common short words such as of and the lowercase in the middle.
  • APA-inspired: applies a basic major-word rule and uses a shorter cutoff for common minor words. See the APA title case guide.
  • Chicago 18-inspired: uses a different cutoff for common prepositions, as described in the Chicago 18th edition updates.

These are starting points, not full style checks. The converter does not reliably distinguish a preposition from a particle in a phrasal verb. Review unusual names, hyphenated terms and publication-specific rules before submitting.

Protect names and abbreviations

For sentence and title case, keep the built-in acronyms, preserve existing all-capital words, or enter preferred single-word spellings separated by commas. For example, iPhone, JavaScript restores those spellings in the result.

Choose and check the capitalization your text actually needs

Choose a case style based on where the text will appear

A button label, a report title and an identifier do not all follow the same rules. Sentence case is a good starting point for labels and prose where only sentence starts and proper names need capitals. Title Case is meant for English headings with an editorial convention. Capitalize Each Word uses a simpler rule and can put a capital on a short connecting word that a title style would leave lowercase. Pick the mode based on the destination, not just the appearance of a two-word example.

Uppercase and lowercase are more mechanical. They are useful when the target explicitly expects every letter to change, such as an all-capital label. They are not safe defaults for a list of identifiers, filenames, or URLs. A single letter can be significant in a file path or machine-readable key. Work on a copy if the text contains both reader-facing labels and machine values; isolate the visible copy rather than converting everything together.

If you are updating an existing publication, compare two recent headings from the same section before making a choice. A single headline that uses a different convention can look like a mistake even if its capitalization is defensible in isolation. Use the title and slug guide when the same wording also needs a public URL, but decide the visible heading first.

Compare modes on the same heading before choosing

Paste the words notes from the archive in a new copy. Sentence case can produce Notes from the archive. A common English title convention can produce Notes from the Archive. Capitalize Each Word makes the short connecting words stand out too. The wording is the same, but the result fits different kinds of page. The editor helps you make the mechanical part of that choice visible.

Now try a heading with a subtitle, such as archive notes: a guide to PDF forms. Look at the first word after the colon and the acronym PDF. A publication may capitalize a subtitle's first word even if the same word would be lowercase within the main title. Verify the result against the publication's rule instead of assuming that the automatic preset knows which punctuation begins a subtitle in your context.

For a batch of headings, test a short one, a heading with punctuation and one that contains an acronym or brand. If they follow the expected pattern, apply the setting to the rest. Then read through the changed headings once without looking at the originals. This helps catch a result that mechanically follows a setting but reads awkwardly. Keep a record of the mode and any manual exceptions for future titles in the same section.

Compare the casing modes in the editor

Protect acronyms, brands and proper names

Capitalization carries meaning in names such as iPhone, GitHub and NASA. A converter cannot infer every preferred spelling from ordinary context. For sentence and title case, enable the acronym settings you need and enter preferred single-word spellings as a comma-separated list. Treat this as a set of explicit exceptions for the current job, not a substitute for checking names after the conversion.

Preserving existing all-capital words is helpful when a draft contains abbreviations that are not in the built-in list. It is less useful when someone pasted the entire title in uppercase: nearly every word could be preserved when your intention was to make most of them lowercase. Check one normal word and one genuine acronym with the chosen settings. If an acronym also appears as an ordinary word in a different sentence, review those occurrences individually.

Possessives, plurals and words attached to punctuation deserve a second look. The preferred spelling you type may describe a base form rather than all variants that appear in the text. Keep a separate list of names you must preserve and compare the output with that list. For person names in an unfamiliar language, use the spelling supplied by the person or source document rather than guessing from an English casing convention.

Use title case presets as starting points, not style certification

English headline conventions often capitalize the first and last words and leave certain short words lowercase in the middle. They differ in how they handle prepositions, hyphenated words and text after punctuation. The General, APA-inspired and Chicago-inspired choices represent different practical starting points. They do not validate a document against every rule in a style guide. If the publication requires exact conformity, check its reference and apply any exceptions manually.

Context matters even for a very short word. The same letters can be an ordinary preposition in one phrase and part of a phrasal verb in another. Automatic handling does not reliably infer that grammatical role. Instead of testing whether a preset always makes a particular word uppercase, read the whole expression. Look at the headline, surrounding context and examples from the same publisher before editing a marginal case.

Hyphenated names or terms require a similar check. A style may capitalize the first part but not the second in some compounds; a product may have its own spelling independent of the surrounding style. Do not remove hyphens simply to get the casing you want. Keep punctuation as supplied, run the selected preset and verify the full term. Use the text comparison tool for a long batch if you need to distinguish intended capitalization from accidentally changed wording.

Check punctuation and languages with different casing behavior

Sentence case depends on identifying where a new sentence begins. An abbreviation such as Dr. or an initial can resemble a full stop without ending a sentence. Some quoted sentences begin after punctuation that a simple converter cannot interpret as a reader would. Test a paragraph containing the punctuation you actually use, not only a line that begins with a lowercase word and ends with a period.

Unicode also makes it unsafe to assume that case conversion is reversible. A letter can expand into more than one character when uppercased. Characters from different languages may have context-sensitive or locale-specific behavior. English title presets are not rules for other languages. If a local convention controls a title, check the output with a fluent reader. Copy the original before using Swap Case or a mechanical uppercase conversion so you can restore it without relying on a second transformation.

For a passage that combines multiple languages, format each part according to its destination. If one segment is a quoted title, preserve its original spelling when required. Accents that look broken may be an encoding issue, not a casing issue. Use Fix broken accents to diagnose a possible decoding problem, or Normalize Unicode when two spellings look the same but contain different underlying sequences.

Keep the display title, slug and key separate

A reader-facing title can contain punctuation, acronyms and accents that are useful to a person. A slug normally uses a shorter naming convention and may intentionally remove punctuation or transliterate some accented Latin letters. Do not convert a complete URL to lowercase just because you want the heading lowercase. Work from the label and generate the destination value separately with the slug and identifier converter. Keep the actual existing URL if the page has already been published and there is no reason to change it.

For a QA handoff, preserve three values when relevant: the original wording, the approved visible heading and the resulting identifier or route. Check capitalization and spelling in the heading, then check uniqueness and destination rules for the identifier. A case converter has no access to your published routes and cannot tell whether a new key conflicts with an existing one.

Read the final title in its actual destination before sharing. A title that looks fine in a text area can wrap poorly in a narrow card. Read it aloud, compare important names with the original and check a mobile preview if it will be a page heading. Save the preset and any manual corrections you would want a colleague to repeat. The goal is a consistent, readable set of headings, not merely proof that every word passed through the same automatic operation.