Remove Markdown Formatting from Pasted Text

What this removes

Each rule below has its own checkbox above, so you can turn off anything you'd rather keep.

• Bold and italic markers — **text**, __text__, *text*, and _text_ are removed, leaving the plain word.
• Inline code backticks — `code` becomes code.
• Heading markers — a leading # through ###### is removed from the start of a line.
• Blockquote markers — a leading > is removed from quoted lines.
• Markdown links — [text](url) becomes just "text"; the URL is dropped.
• Fenced code blocks — the ``` marker lines (including any language tag) are removed; the code between them is kept exactly as written, with no other cleanup applied to it.
• Horizontal rules — standalone ***, ---, and ___ separator lines are removed entirely.
• Table separator rows — rows like | --- | --- | and | :--- | ---: | are removed; table content rows are kept.
• List markers — lines starting with -, *, or + are normalized to "- " by default, or stripped entirely if you untick "Preserve bullet lists".

Before and after

# Project notes from a README

Here is a quick summary with a [reference link](https://example.com/).

> This paragraph was copied with Markdown quote formatting.

- First action item
- **Second action item** with `inline code`

Project notes from a README

Here is a quick summary with a reference link.

This paragraph was copied with Markdown quote formatting.

- First action item
- Second action item with inline code

Common Markdown paste problems

Markdown is meant to be rendered, but when you copy text out of a tool that displays it, you often get the raw source instead of the formatted result:

• AI chat answers are written in Markdown, so a copied response can arrive full of **bold**, # headings, and [link](url) syntax instead of formatted text.
• GitHub READMEs, issues, and pull requests render Markdown on the page, but copying from them — or from the raw file — brings the source marks along.
• Notion, Obsidian, and other Markdown-based notes apps store content as Markdown under the hood, which can leak through when you copy and paste elsewhere.
• Documentation sites and wikis are often generated from Markdown source, so copied snippets can carry headings, links, and emphasis marks.
• Code answers with fenced blocks wrap example code in ``` markers, which paste as literal triple backticks around the code.

In each case the words themselves are fine — it's the leftover formatting marks that make the text look broken when pasted somewhere that doesn't render Markdown.

How it works

Text copied from GitHub, Notion, README files, and documentation sites often brings its Markdown source along with it — asterisks around bold and italic words, backticks around inline code, # marks in front of headings, > in front of quoted paragraphs, and full [text](url) link syntax. This tool strips those marks with a fixed set of rules, each one its own checkbox above, so the words underneath read cleanly when pasted into an email, document, or plain-text note.

Bold and italic markers (**text**, __text__, *text*, _text_) and inline code backticks are removed, leaving the plain word. Markdown links become just their link text. Heading markers (# through ######) and blockquote markers (>) are removed from the start of a line. Bullet lines starting with -, *, or + stay as bullet lines by default — untick "Preserve bullet lists" to remove the bullet marker too.

Fenced code blocks (text wrapped in triple backticks) are handled separately: the marker lines — including any language tag, like ```js — are removed, but everything between them is left exactly as written. No formatting rules run inside a fenced block, so code samples keep their original spacing and punctuation.