Notion
How to copy AI text into Notion without formatting problems
Notion reads Markdown while you paste, so AI output turns into accidental headings, dividers, and broken lists. Here is the workflow that gives you the blocks you actually wanted.
To copy AI text into Notion without formatting problems, remove the Markdown before you paste. Notion interprets incoming text as Markdown: a line starting with # becomes a heading, - becomes a bullet, --- becomes a divider, and [ ] becomes a to-do. Cleaning the syntax first means Notion has nothing to interpret, so it stores your text as the block type you chose. Use rich text for prose and plain text for code blocks, properties, and callouts.
Below is what Notion does with each syntax pattern, the three paste routes and when each is right, and the fixes for the breakages people hit most often.
Notion is a Markdown editor with a block model
Notion has two ways of turning text into blocks. The first is typing: start a line with # and it becomes a heading when you press space. The second is pasting: Notion inspects the incoming text and applies the same rules.
That behaviour is genuinely useful when you paste a Markdown file or a note from Obsidian. It is unhelpful when you paste a chat answer, because the answer was written for a renderer, not for a block editor.
The failure is structural rather than visible. The text is all there, but it is in the wrong containers:
- A sentence you wanted as body copy became an H1.
- A hyphenated aside became a bulleted list item.
- A horizontal rule in the source dropped a divider through the middle of the page.
- A numbered list restarted the numbering of the list above it.
Nothing is corrupted, which is why it is annoying: you have to fix each block by hand.
What Notion converts on paste
| You paste | Notion creates |
|---|---|
# Heading |
Heading 1 block |
## Heading |
Heading 2 block |
- item |
Bulleted list item |
1. item |
Numbered list item, renumbering below it |
--- |
Divider block |
> quote |
Quote block, or a toggle in some contexts |
`code` |
Inline code with its own background |
[ ] task |
To-do block with a checkbox |
**bold** |
Bold text inside the current block |
The last row is the one people forget. Bold markers are converted rather than left literal, which is usually what you want — but only if the surrounding block type is correct.
Three paste routes, three outcomes
Route 1: paste directly. Fastest and least predictable. Whether you get formatted text or literal asterisks depends on what the clipboard carried from the chat window, and Notion will still interpret any Markdown that survives.
Route 2: paste as plain text. Ctrl+Shift+V on Windows, Cmd+Shift+V on Mac. This bypasses HTML, but it does not remove Markdown. You get the asterisks without the chat window’s font. Notion may still convert line-leading syntax into blocks.
Route 3: clean first, then paste. Remove the Markdown in the JustCleanText cleaner, then choose rich text or plain text for the destination. This is the only route where the result is predictable, because there is no syntax left to interpret.
Rich text or plain text inside Notion?
The choice depends on what the destination block should be.
| Destination | Copy mode | Why |
|---|---|---|
| Normal page body | Clean rich text | Real bold, italic, links, and lists inside a paragraph block |
| Code block | Plain text | Notion stores characters exactly; no inline formatting fights the mono style |
| Database property | Plain text | Properties are single-line fields with limited formatting |
| Callout or toggle title | Plain text | Short text where any markup is noise |
| Quote block | Clean rich text | Keeps emphasis while the block supplies the styling |
Rich text writes both text/html and text/plain to the clipboard. Notion reads the HTML and maps it onto its own inline formatting. Plain text writes only characters, which is what you want when the block type already provides the structure.
The workflow
- Copy the AI answer, raw Markdown included.
- Paste into JustCleanText and confirm the report shows a sensible Markdown count.
- Decide the destination. If it is a code block or a property, plan on plain text. Otherwise rich text.
- Copy the right flavour and paste into Notion.
- Check for stray blocks. If a divider, heading, or to-do appeared, the source had syntax the cleaner did not remove — check that Strip Markdown was on.
If you want to keep the structure but not the styling, this is also the moment to decide about bullets. Bullets from dashes turns - item into • item in plain text, which prevents Notion from re-interpreting the line as a list when you paste it into a text block.
Fixing a page that already went wrong
An accidental heading. Click the block, open the block menu, and choose Turn into → Text. Then apply the style you wanted.
A stray divider. Put the cursor at the start of the block after it and press Backspace. Dividers are their own block, so deleting text will not remove them.
Numbering that restarted. Right-click the first number in the new list and choose Restart at 1, or merge the lists by deleting the paragraph between them.
A to-do you did not want. Turn into → Text. The checkbox is a block property, not a character, so removing the brackets manually does nothing.
Search that cannot find a phrase. The phrase probably contains an invisible character. Re-paste it through the hidden character remover and try again.
Everything in one giant block. The source had no blank lines between paragraphs. Notion splits blocks on line breaks, so a paste with no empty lines becomes one block. Cleaning cannot invent paragraph breaks; add them in the source or press Enter where the structure should split.
Before and after
Pasted directly into a Notion page:
## Sprint review
- **Velocity** is up 12%
- Two bugs carried over
- See `docs/sprint.md`
---
I hope this helps!
Notion creates a Heading 2, three bullets, a divider, and a paragraph containing the closing line.
After cleaning, pasted as rich text into a single text block:
Sprint review
• Velocity is up 12%
• Two bugs carried over
• See docs/sprint.md
One heading line, one paragraph, and a list — and no divider, because the horizontal rule was removed along with the rest of the syntax.
Import versus paste
Notion can import a Markdown file, and that route deliberately interprets Markdown into blocks. If you want structure — real headings, real nested lists — importing is better than pasting, because it preserves the hierarchy that a paste flattens.
If you want text, paste. If you want a document outline, import. Choosing the wrong one is the reason people describe Notion’s Markdown handling as inconsistent: it is doing two different jobs, correctly, in two different places.
A short checklist
- Strip the Markdown before pasting, every time.
- Use plain text for code blocks and properties.
- Use rich text for prose.
- Turn on the bullet conversion if you are pasting into a text block and do not want list behaviour.
- Check the hidden-character count if a later search fails.
Open the Notion text cleaner · Read the complete Markdown to plain text guide
Put this into practice
Clean the text before you paste it
Paste the text into JustCleanText, keep the toggles that match your problem, and copy either rich text or plain text. Everything runs in this browser tab.
Open the cleaner