Formatted copy can contain HTML without showing HTML code
When you copy formatted content from a browser, document editor or notes app, the clipboard can carry more than one representation of the same selection. One is plain text. Another can be text/html: a small, hidden description of headings, links, emphasis, lists and tables. You do not see tags, and you do not need to write HTML. It is simply how many apps move rich document structure through the clipboard.
That hidden representation is different from copying visible HTML code. If the source shows a heading and a table, choose Rich text. If the source literally shows tags such as <h2>, <table> and <a>, choose HTML code or file. Pasteful keeps those inputs separate so a normal formatted copy is not mistaken for code, and code is not pasted as ordinary prose.
Pasteful reads the plain and rich representations locally. It keeps useful document meaning, removes source fonts, colours, classes, tracking attributes and page layout, then shows the recovered result before you copy. If the rich representation disagrees with the text you selected, the safer visible text wins and the preview explains the fallback.
Open the rich text to Notion formatter · MDN guide to reading clipboard representations
Why formatting disappears between apps
Copy and paste is a negotiation between the source app, the browser, the operating system and the destination. The source decides which clipboard representations to provide. The destination decides which one to accept and how to map it into its own blocks. A heading in one editor might arrive as a real heading, a bold paragraph or plain text depending on those choices. A table might arrive as cells, tab-separated lines or one collapsed paragraph.
The visible design is not the portable part. Notion does not need the source page's font family, exact margin or coloured container. It needs to know that a line is a heading, these items form a list, this phrase is a link and these values occupy table cells. Pasteful strips visual decoration and rebuilds that smaller semantic layer. The Notion page can then apply its own typography and spacing without losing the structure that makes the content editable.
No formatter can force a receiving app to accept every clipboard type. Browser permissions, app versions and editor behaviour can change. That is why Pasteful gives you a rich preview, a readable plain-text fallback and a loss report. The final check still happens in the actual Notion page, where you can confirm that blocks behave correctly when edited.
See destination formatting and limitations · Read how Pasteful tests copy and paste
A simple copied table can stay a table
A source table has the best chance of surviving when the clipboard contains an actual HTML table with clear rows and cells. Pasteful reads header cells and data cells, converts them to a rectangular document table, and produces clean semantic HTML for the destination. The plain-text fallback remains available if the browser cannot write rich clipboard data. In the preview, rows and columns should line up before anything reaches Notion.
This works for ordinary comparison tables, project summaries, short status grids, meeting decisions and other document tables. It does not turn a screenshot into editable cells, infer columns from arbitrary spaces or rebuild a visual dashboard. If the source app copied only a picture or plain text, Pasteful cannot honestly claim that a table structure exists. It preserves what is available and tells you what is missing.
Keep the test small when the source is unfamiliar. Copy a header row and two data rows first. Confirm that the correct values remain under each heading, then move the rest. This catches source apps that expose a visual table but place only flattened text on the clipboard. It also makes it easier to spot a row that contains nested lists, images or other content Notion may handle differently.
- Column headings remain distinguishable from data cells
- Links and basic emphasis inside cells remain meaningful
- Rows are rebuilt as a rectangular grid
- Source CSS, widths, colours and page layout are removed
- Remote images are not fetched during clipboard conversion
Merged cells need a visible fallback
Merged cells are not portable in the same way as ordinary rows and columns. A cell can span several columns in HTML, while a Markdown table has no shared merged-cell syntax and a receiving editor may apply its own rules. Pasteful flattens row spans and column spans into a bounded rectangular table and records that change in the loss report. The content stays visible, but the original visual grouping may need to be rebuilt in Notion.
Treat layout tables with extra caution. Some websites use table markup to position unrelated panels, navigation or labels. Turning that layout into a document table can preserve the words while producing a poor reading order. The preview is the decision point: if the recovered rows do not make sense when read left to right and top to bottom, use the plain-text result or rewrite the section before copying.
Complex cells also deserve inspection. Nested tables, controls, embedded content and scripts do not belong in a portable note. Pasteful removes active content and does not fetch external resources. A clean document table should contain text, safe links and modest inline emphasis. Anything beyond that is reported or reduced to a readable alternative rather than silently presented as a perfect conversion.
A Notion table is not a Notion database
Notion has simple tables and database table views, but they solve different jobs. A simple table is part of a document: rows, columns, headers and text arranged for reading. A database contains pages and typed properties, and can add filters, sorts, relations, formulas and multiple views. Clipboard formatting can preserve a document table. It cannot invent the database schema your workspace needs.
If the copied material is a short matrix inside meeting notes, a brief or a handoff, rich text is the direct route. If every row should become a task, contact or project with owners, dates and statuses, use structured data such as CSV and map those columns in Notion. Notion's own import guidance describes CSV rows as database items and columns as properties, while HTML, Markdown and Word imports become page content.
The distinction matters because promising a database from an ordinary paste would hide important choices. A column called Owner might need to be a person property, plain text or a relation. A date might need a timezone. A status might need a controlled set of options. Pasteful keeps the table you copied; Notion remains the place where you decide whether that information should become a database.
| If you need to | Use this route |
|---|---|
| A comparison or status table inside a page | Use Rich text to Notion and paste the result as document content. |
| Rows with owners, dates, relations or formulas | Prepare a structured CSV and use Notion's database import. |
| Visible HTML tags or a local .html file | Use HTML code or file, then convert to Word or Markdown. |
| A portable local document | Convert the recovered structure to Markdown and save the .md file. |
Notion's official import guide · Notion's guide to simple tables and databases
What else rich text can preserve
The same rich clipboard path covers more than tables. Headings can stay headings rather than oversized bold lines. Ordered and unordered lists can keep their item boundaries and nesting. Labelled links can keep both the readable label and safe destination. Bold, italic and strikethrough text can remain inline emphasis. Quotes and code blocks can stay separate from surrounding prose when the source exposes them semantically.
What does not travel cleanly is just as important. Comments, edit history, page permissions, database properties, people mentions, live embeds, app-specific callouts and automation rules are not generic clipboard formatting. Images may be omitted when they are remote or when the browser does not expose safe local bytes. Equations, footnotes and deeply nested structures require a destination check. Pasteful reports known reductions instead of folding them into a vague promise to keep everything.
This narrower contract produces a more useful result. The content remains editable and adopts the receiving page's visual system. You can change a heading level, continue a list or edit a table cell in Notion without fighting the source app's CSS. The goal is not a screenshot-like clone; it is a clean working document that still knows what each part is.
Convert rich text to Markdown · Compare Notion and Word workflows
What happens when rich formatting is missing
Some source apps place only plain text on the clipboard. Others provide rich content only after a normal copy command, not when text is dragged or copied through a secondary menu. Private browser modes and clipboard permissions can also limit what a web tool can read or write. When Pasteful receives no useful rich representation, it keeps the visible plain text and shows a fallback warning. It does not fabricate headings or tables from appearance alone.
Try the source app's standard copy command first. Select the actual text or table cells, copy, then use Paste in Pasteful. If the preview remains plain, compare it with a direct paste into a blank Notion page. A direct paste that is also plain means the source probably did not supply portable structure. A direct paste that is rich while Pasteful is plain may indicate a browser permission or representation issue worth reporting.
You can still use the editor to restore obvious structure before copying. Turn labels into headings, rebuild short lists and verify link addresses. For a large or recurring workflow, do not rely on manual repair without a fixture. Save a small representative sample, repeat it after browser or destination updates, and stop if the preview or final paste changes unexpectedly.
How to paste formatted text into Notion
First, copy the content normally from the source app. Open Rich text to Notion and press Paste. The browser may ask for clipboard permission. Check the source indicator: it should say that a rich representation was read when formatting is available. Then compare the recovered headings, lists, links and table cells with the source. Read the loss report before copying.
Second, edit the recovered content if necessary. Remove navigation copied from a webpage, shorten a heading, fix a flattened merged cell or separate a code block from surrounding prose. The preview is deliberately editable because the correct destination document may not be identical to the source selection. This is also where you can remove visual debris without sending the draft to another service.
Finally, press Copy and paste into an empty place in the target Notion page. Check structure, not only appearance. Click a heading and confirm it behaves as a heading block. Add an item to a list and confirm numbering or bullets continue. Open the first and last link. Click through table cells and make sure the values remain under the correct headings. Keep the source until those checks pass.
- Copy with the source app's normal copy command
- Choose Rich text, not HTML code or file
- Confirm the preview contains the expected structure
- Read every warning before copying
- Test the result inside the real Notion page
When an HTML file import is the better route
Clipboard paste is best for moving a selected passage into a page that already exists. A file import is better when the HTML itself is the source document, when several pages need to move together or when local assets belong beside the text. Notion officially supports HTML imports and maps headings, paragraphs, lists, links, code blocks and simple tables into page content, with limitations for complex layouts, scripts, embeds and complex tables.
Pasteful's HTML route is deliberately narrower. It opens one local .html or .htm file, removes active and decorative content, shows the semantic document, and can produce Word-ready rich text, DOCX or Markdown. It does not upload related assets or recreate a website. If you need Notion to ingest an entire export folder with images, use Notion's documented HTML or ZIP importer and inspect the imported pages afterward.
Do not paste visible HTML tags into the Rich text route and expect them to execute. Rich text is for a formatted clipboard selection. HTML code or file is for source you can see. Keeping that language precise makes the tool easier to choose and prevents the site from presenting the same intent under several slightly different pages.
Convert an HTML file to Word · Convert an HTML file to Markdown
Use a repeatable destination check
A useful fixture contains one real heading, a bold and italic phrase, a labelled link, a two-level list, a quote, a short code block and a two-column table. Copy that fixture from the source app, inspect it in Pasteful, then paste into Notion. Record which structures survive and which fall back. This is more reliable than judging one polished screenshot because it exercises the actual clipboard representations and editor blocks.
Repeat the check after a meaningful browser, operating-system or Notion editor update. Receiving applications can change their paste rules without changing the text you copied. Pasteful's automated corpus verifies its own parser and destination output, but it cannot control Notion's release cycle. A current manual paste remains the final evidence for a destination-specific claim.
If something breaks, keep the smallest failing example and include the source app, browser, operating system, destination and the exact structure that changed. Do not include private document content. A two-row table or three-item list is usually enough to reproduce a formatting bug and improve the converter without exposing the work that revealed it.
Read the reproducible formatting corpus · Review Pasteful's privacy boundaries