Markdown to HTML for Email Newsletters
Convert Markdown into HTML for email newsletters, then inline the styles so it renders in Gmail, Outlook, and Apple Mail.
Direct answer
Write the newsletter in Markdown, convert it to HTML, then inline the CSS because many email clients strip <style> and <head>. Keep the layout simple — headings, paragraphs, links, and single-column content — so it renders reliably across Gmail, Outlook, and Apple Mail.
Open Markdown to HTML converterWhen to use this
- You draft newsletters in Markdown and need email-ready HTML.
- You want a simple, single-column email body without a heavy email builder.
- You are pasting HTML into an ESP that accepts raw HTML.
Steps
- Write the newsletter in Markdown: a heading, short paragraphs, a link or two, and a list.
- Convert it to HTML.
- Inline the CSS (move any styles into style attributes) because email clients often drop <style> blocks.
- Keep it single-column and avoid modern CSS like flexbox or grid that email clients ignore.
- Send yourself a test and check it in Gmail, Outlook, and Apple Mail before the real send.
Example conversion
# This week at CloudYeti Two quick updates for you. - New live Markdown editor - Faster HTML export Read the full post on the [blog](https://example.com/blog). Thanks for reading!
<h1>This week at CloudYeti</h1> <p>Two quick updates for you.</p> <ul> <li>New live Markdown editor</li> <li>Faster HTML export</li> </ul> <p>Read the full post on the <a href="https://example.com/blog">blog</a>.</p> <p>Thanks for reading!</p> <!-- Then inline styles, e.g. <p style="margin:0 0 16px;font-family:Arial,sans-serif"> -->
Common mistakes
- Do not rely on a <style> block or external stylesheet; Gmail and Outlook strip them, so inline the CSS.
- Avoid flexbox and grid; older email clients (especially Outlook) ignore them — use simple stacked blocks or tables.
- Always send a test to yourself and check multiple clients; email rendering varies more than browser rendering.
FAQ
- Why does my HTML email look broken in Outlook?
- Outlook uses a limited rendering engine and strips <style> blocks and modern CSS. Inline your styles and keep the layout to simple stacked blocks or tables.
- Do I need to inline CSS for email?
- Yes. Most email clients ignore <head> and <style>, so styles must live in style attributes on each element. Convert to HTML first, then inline.
- Can I paste this HTML into Mailchimp or another ESP?
- Yes, if the ESP has a raw-HTML or code block. Paste the converted HTML there and send a test before your campaign.
Related Markdown to HTML guides
How to Convert Markdown to HTML
Convert Markdown into clean, semantic HTML — headings, paragraphs, lists, links, and emphasis — ready to paste into a page or CMS.
Convert a README to an HTML Page
Turn a README.md into a standalone HTML page you can host, preview, or embed — headings, code blocks, and tables intact.
Markdown to HTML With Inline CSS and Styling
Convert Markdown to HTML and wrap it in styles — inline CSS or a stylesheet — so the exported page looks designed, not raw.
Convert a Markdown Table to an HTML Table
Turn a Markdown pipe table into a full HTML <table> with thead, tbody, and alignment preserved.
Embed HTML in Markdown (and When to Mix Them)
Use raw HTML inside Markdown for things Markdown can't express — collapsible sections, keyboard keys, subscript — and know when not to.
Markdown to HTML: CLI vs Online Converter
When to use a command-line tool like pandoc or markdown-it versus a fast, no-login online Markdown to HTML converter.