How to convert a blog post to Markdown for Notion or GitHub

When you copy a blog post or a document and paste it somewhere else, the layout often breaks. Font sizes and line spacing come out uneven, or the formatting disappears and only the plain text is left. Notion, GitHub and many blog editors accept text written in a simple notation called Markdown, but a web page or a Word document is not in that format.

Moving it takes three steps. Select the part you want in the post and copy it, paste it into Convert to Markdown, then press [Copy] on the result and paste it where it is going. Copying puts formatting information on the clipboard along with the text, and the tool reads that information to convert it. If you paste into a plain-text editor such as Notepad and copy again, the formatting information is lost, so copy straight from the source.

Headings become #, ## and so on, and bold, italics, links, lists, tables and divider lines become their Markdown notation. Font size, color, underline and centering have no Markdown equivalent, so they are not carried over. A heading that was made only by enlarging the text comes out as a plain paragraph, so add ## and a space at the start of that line yourself.

Images that have a web address are kept as that address only, in the form ![description](address), not as files. Pictures embedded in a document, such as a Word file, are left out. An image hosted on one site may not display on another, so it is safer to save the pictures separately and upload them again where the post is going.

If a post is too long to convert at once, split it into parts and convert and copy each part in turn. What you paste is not sent to a server or stored.

Move a post with Convert to Markdown