Markdown Here VS Markdown Reader

• Cross-Platform Compatibility
  Markdown Here is available as a browser extension for multiple platforms, including Chrome, Firefox, Safari, and Opera. This ensures that users can use it across different browsers without compatibility issues.
• Ease of Use
  The extension simplifies the process of writing in Markdown for emails and provides a quick conversion to formatted HTML, making it user-friendly even for those new to Markdown.
• Consistent Email Formatting
  With Markdown Here, users can write emails in Markdown, which allows for a neat and consistent look. The tool converts the Markdown into HTML, ensuring that the formatting is preserved across different email clients.
• Open Source
  Being open-source, Markdown Here encourages community contributions, allowing users to suggest improvements and customize the tool based on their needs.

Possible disadvantages

• Browser Dependence
  As a browser extension, its functionality is limited to supported browsers. Users relying on unsupported browsers will not be able to utilize the tool.
• Limited to Email Clients
  The primary focus of Markdown Here is on rendering Markdown text in emails. Users seeking Markdown support in other applications beyond email will find this tool limited.
• Rendering Limitations
  Some complex Markdown features or custom styling may not render correctly when converted to HTML, depending on the email client's capabilities and restrictions.
• Potential Security Concerns
  As with any browser extension, there are inherent security risks, such as potential vulnerabilities that could be exploited. Users need to regularly update the extension to mitigate these risks.

• Lightweight, distraction-free reading
  Markdown readers generally render plain-text files as clean, formatted content (headings, lists, code blocks, links) with little clutter. This makes technical guides and playbooks easy to scan. I can't browse the URL, so this is a general trait of Markdown readers rather than a verified feature of the Twistag page.
• Portable, future-proof content format
  Markdown is plain text, so guides can be version-controlled in Git, edited in any editor and reused across platforms without vendor lock-in. This suits engineering playbooks that change often.
• Good fit for developer documentation
  Markdown supports code fences, tables, and simple structure, which suits technical guides and playbooks like those a software agency such as Twistag would publish.
• Fast loading and accessible
  Content rendered from Markdown is mostly simple semantic HTML, so pages tend to load quickly, work on mobile and work well with screen readers and search engines.
• Easy to maintain and contribute to
  Because writing Markdown has a low learning curve, non-developers and developers alike can update guides quickly, which helps keep playbooks current.

• Cheat-sheet maker; a react app for creating and sharing cheat sheets (with markdown)

  If I got your point correctly, I think markdown is a great solution for this. For this particular app, I used react-markdown as parser but there are other libraries of course. Source: over 5 years ago

Tracking Markdown Reader since Aug 2026.