Removing text formatting in Pages means stripping every inherited font, color, weight, and link from a selection so only the raw characters remain. In Apple Pages this is a daily chore because Pages, like most modern word processors, treats the clipboard as a layered object: when you paste, the destination app inspects every available format the source supplied and chooses the richest one it can render. A copied snippet from a website, a Word document, or a styled email often arrives with embedded HTML or RTF, and Pages keeps the visible bold, the colored run, and the hyperlink instead of the bare text. The cleanest cross-app workaround is to route the paste through a plain-text converter, copy the resulting string, and paste it back into Pages with Match Style. That workflow preserves every letter, punctuation mark, accent, emoji, tab, and line break you actually want while discarding the styling layer that Pages would otherwise absorb and reapply.
Why Pages Holds Onto Bold, Italic, and Color After You Paste
When text lands in Apple Pages from another application, Pages does not just see a sequence of characters. The macOS clipboard routinely exposes the same content in several formats at once: a plain-text representation, an HTML representation carrying inline styles, an RTF representation, and sometimes the original application's native format. Pages reads these layers in order of richness and, by default, adopts the richest one it supports. That is why a bold run from a web page arrives bold, why a colored phrase keeps its color, and why a hyperlink stays live.
The destination app's behavior is consistent across word processors: when you paste data into Microsoft Word, for example, the destination scans the clipboard and requests the HTML or RTF layer by default. Apple Pages follows the same convention, so the inheritance is automatic unless you intervene. Three standard interventions exist:
- Use the Edit menu's Paste and Match Style command (Cmd + Option + Shift + V), which forces Pages to use the plain-text layer.
- Select the pasted text and press the formatting reset shortcut, which clears inherited character and paragraph styles.
- Route the paste through an external plain-text boundary first, so the only thing Pages ever sees is raw text.
The third option is the most reliable when the source mix is unpredictable, because it removes the rich layer before Pages can decide to use it.
How to Remove Text Formatting in Apple Pages
Use this sequence when you have styled text already sitting in a Pages document and you want the same words back without any of the styling:
- Select the text in Pages whose formatting you want to strip. A click and drag through the document works for a passage; Cmd + A selects the whole document.
- Cut or copy the selection with Cmd + X or Cmd + C. The styled content is now on the clipboard.
- Open the Remove Text Formatting tool in your browser. The page is a single textarea on a plain background with no rich content area, no contenteditable region, and no markup interpreter.
- Click into the textarea and paste with Cmd + V. The browser hands the textarea the clipboard's plain-text representation directly, which means the rich HTML and RTF layers are dropped at this boundary.
- Click the Create plain text action. The page validates the input, normalizes any CRLF or standalone CR line endings to LF, and renders the result in the preview panel.
- Inspect the preview. List markers, table separators, and line breaks come from the source application's plain-text representation, so what you see in the preview is exactly what Pages will receive when you paste it back.
- Click Copy plain text. The browser's Clipboard API writes the exact preview string to the clipboard after a successful clipboard write request, with no extra newline or invisible prefix.
- Return to Pages and place the cursor where you want the clean text. Use Cmd + Option + Shift + V (Paste and Match Style) so Pages consumes the clipboard as plain text.
- Confirm the result. The pasted characters should now sit in Pages' default body style with no inherited color, weight, or links.
If you would rather hand the cleaned text to Pages as a file, click Download TXT instead of Copy plain text. The browser creates a short-lived object URL for a Blob whose media type is text/plain;charset=utf-8 and whose filename is plain-text.txt, then revokes the URL after the download begins. The downloaded bytes match the preview exactly, so you can drag the file into Pages as well.
What the Plain Text Converter Changes and What It Leaves Alone
The tool is deliberately small. There is exactly one transformation applied to the input string, and every other character is preserved as it was received. The table below summarizes the contract.
| Behavior | Detail |
|---|---|
| Line-ending normalization | CRLF and standalone CR become LF. This is the only character change applied to the accepted input. |
| Tabs | Preserved exactly, including runs of multiple tabs. |
| Ordinary and repeated spaces | Preserved exactly; the tool does not collapse horizontal spacing. |
| Blank lines | Preserved exactly; empty lines are not removed. |
| Leading and trailing whitespace | Not trimmed. |
| Punctuation, emoji, accented letters, and other scripts | Preserved exactly. No Unicode normalization, smart-quote rewriting, or language-specific cleanup. |
| Literal HTML source | Stays literal. The characters <b>literal</b> appear in the output as the same tag characters, not as bold text and not stripped as markup. |
| Markdown conversion | Not performed. The tool is not a Markdown-to-text converter. |
| Smart-punctuation replacement | Not performed. Curly quotes stay curly; straight quotes stay straight. |
| Output encoding | UTF-8 in both the clipboard payload and the downloaded TXT file. |
| Input ceiling | One million Unicode code points. Longer input is rejected without truncation. |
That contract exists for two reasons. First, the tool is not an HTML sanitizer, parser, DOM text extractor, or security filter; making it look like one would invite misuse. Second, the source application and the browser jointly decide what the plain-text clipboard representation looks like, so a deterministic preview is the most honest answer you can give the user.
When a Plain-Text Round Trip Is the Wrong Choice
Stripping styling is not always what you want. Hold off on the workflow above if any of the following apply.
- The selection contains a structured table you want to keep. Word processors, spreadsheets, and web pages each represent tables differently in their text/plain representation, so a tab-separated grid from one app can become a comma-separated or fixed-column grid in another. Pages in particular may not rebuild the table layout from the converted text.
- You are moving the text into a Markdown, HTML, or rich-text environment where the styling is the point. The plain-text converter preserves literal HTML source as literal characters, which means a snippet like <strong>key</strong> arrives in Pages as the tag characters and the word "key", with no bold.
- The selection is close to one million Unicode code points. The tool rejects input that exceeds that ceiling rather than truncating it, so a long document needs to be split before it can be processed. The MDN Blob documentation describes how browsers cap Blob construction in similar ways.
- You actually want to scrub zero-width characters, tracking tokens, or stray AI punctuation. For that, use a dedicated cleaner rather than a plain-text boundary.
Quick Checks Before Pasting Back Into Pages
The preview is the truth, so spend a few seconds reading it before you click Copy plain text. Three checks catch almost every surprise.
- List markers. Pages often renders text that begins with a hyphen, an asterisk, or a digit followed by a period as a list item. If the source application emitted literal asterisks for emphasis, the converter preserves them, and Pages will happily turn them into a bulleted list.
- Line breaks. A paragraph split in the source app should still be a paragraph split in the preview. If the preview has merged lines, the source's plain-text representation used a soft break or a non-breaking space where you expected a hard break.
- Tabs and table separators. Pages imports tab-separated columns as tab characters, so a pasted table becomes a single paragraph with embedded tabs. Restructure the columns in Pages itself if you want a real table.
When the preview matches what you expected, click Copy plain text. The Clipboard API only runs after a direct click on the action, so you will not see a hidden write, and a permission failure produces an honest manual-copy instruction instead of a false success message (the underlying Clipboard.writeText contract is a Promise that resolves on success and rejects on denial). The exact preview string is what lands on the clipboard, so the next Cmd + Option + Shift + V in Pages drops the cleaned text into the document with no inherited styling.
For long runs of cleaned text that you would rather not keep on the clipboard, use Download TXT instead. The downloaded file is plain-text.txt, encoded as UTF-8, and it contains the same characters as the preview. You can drag that file onto Pages, open it directly, or hand it to another tool that expects a plain UTF-8 text file.
For a deeper look, see How to Remove Duplicate Lines in Notepad++.
For a deeper look, see How to Remove Whitespace in Google Sheets With Three Modes.