How to Paste With Formatting on Mac

Published on
Written by
Pastea Team
Reading time
5 min read

To paste with formatting on a Mac, start with ⌘V, or choose Edit → Paste. Copy from a source that provides rich content and paste into an editor that supports it.

If the result arrives as plain text, the shortcut may be fine. The source, a clipboard utility, or the destination may have stripped the formatting. Work through those three places before changing system settings.

This guide is for keeping the source's style. If you want the opposite, use our paste without formatting guide.

These commands can all insert the same words while producing different results.

OperationWhat you are asking the app to do
PasteInsert supported content from the clipboard, potentially including source styling
Paste and Match StyleAdapt the insertion to the surrounding destination style
Paste without formatting or Paste text onlyInsert text without the original rich styling
Paste as an image, where availablePreserve a visual appearance as a picture rather than editable text

Apple documents ⌘V for normal Paste and ⌥⇧⌘V for Paste and Match Style in its Mac copy-and-paste instructions. The names and extra commands still depend on the destination app.

There is no universal shortcut that forces every Mac app to preserve every detail of a copied document. The destination needs to understand the representation the source supplied.

In Pages:

Apple's Pages guide explicitly distinguishes pasting text with its current formatting from Paste and Match Style.

If you want the style from a nearby paragraph instead, matching style is useful. It is just a different goal from retaining the original source.

A practical test: create a short line with one bold word and one link in a rich document. Copy it directly into a new Pages document. If that works, repeat with the source that caused the problem. The difference tells you whether the source is supplying something Pages can use.

Google lists ⌘V for Paste and ⇧⌘V for Paste without formatting on Mac in its Docs keyboard shortcuts.

Click inside the editable document body and use normal Paste. Make sure you are editing the document rather than typing into a comment, search field, or another browser control.

If a global clipboard shortcut intercepts your key combination, compare the menu command with the keyboard action. A shortcut conflict can change what happens without changing the clipboard itself.

Docs may still interpret the incoming content differently from the original app. Inspect tables, nested lists, and links after transfer. For a problem specifically involving stripped formatting, our Google Docs plain-text paste guide explains the neighboring commands and shortcut conflicts.

In Outlook for Mac, the paste control beside newly pasted content can offer Keep Source Formatting, Match Destination Formatting, or Keep Text Only. Microsoft describes these choices in its Outlook for Mac formatting guide.

Choose Keep Source Formatting when the source styling is the goal. Check that the message supports rich formatting before expecting fonts or images to survive.

This is particularly useful for a signature: the visible words can look correct while the link target, line spacing, or logo has changed. Send yourself a draft test if appearance in email matters. The editor preview alone does not tell you how every recipient's mail client will render it.

A plain-text field accepts characters, not a source font or paragraph style. Terminal, a plain-text editor, and many form fields are therefore useful places to paste text but poor tests of whether a rich copy survived.

TextEdit can work with both rich text and plain text. For a rich-text test, create a new document and inspect the Format menu. If it offers Make Rich Text, the document is currently plain text; switching it gives you a rich-text destination for a fresh copy. Apple's TextEdit guide covers these document formats.

Switching an already-pasted plain-text paragraph to rich text does not recreate its original font or link metadata. Copy again from the rich source after preparing the destination.

Think of the transfer as three boundaries:

Source selection → clipboard representation → destination interpretation.

Apple's NSPasteboard documentation explains that applications exchange typed data through the pasteboard. Your visible selection and the data offered for paste are related, but they are not the same thing.

Use this diagnostic order:

Common examples are easy to miss. Copying a URL from the address bar is different from copying linked text in a document. Copying Markdown characters does not require a destination to render them as rich text. Moving content through a plain-text note can remove metadata before the final paste ever happens.

If you maintain a Raycast extension that transforms copied content, see our guide to preserving HTML with the Clipboard API. Reading text and writing a string back is a deliberate text conversion, even if the source started rich.

History tools can offer both normal and plain-text paste. Check which action you selected and whether the app has a preference that prioritizes plain text.

Pastea's changelog documents normal paste with Return and plain-text paste with ⌘Return. For styling, choose normal paste and test the receiving app. A normal action cannot restore source formats that were absent from the captured copy.

If the same historical item repeatedly pastes correctly into Pages but loses styling in another destination, that comparison is useful evidence about the destination. If both fail while a fresh direct copy works, inspect the saved item and your history tool's paste action.

Before sending an important result, check the specific details that matter:

For a quote, the words and attribution may matter more than the original font. For a signature, links and layout may matter more. Choosing the requirement makes troubleshooting much faster.

If you also need to retrieve the styled material after copying other things, Pastea keeps a searchable history on your Mac. Keep the rich source available until you have checked the destination; history is useful recovery, not a guarantee that every app will interpret a paste identically.