Drop a .md file and read it as a page. Nothing is uploaded.
Drop a .md file here
Drop a markdown file or paste some text — it renders here.
Drop a .md file here
Drop a markdown file onto the panel, or paste the text. It renders immediately as a page — headings, paragraphs, lists, tables, block quotes, links, images, inline code and fenced code blocks.
Everything happens in your browser. The file is read locally and drawn into a sandboxed frame; nothing is sent anywhere, which matters when the markdown is a draft, a client report, or notes you would not paste into a random web form.
Raw HTML inside the markdown is shown as text rather than executed. That is deliberate: AI-written markdown is full of bare angle brackets in placeholders like <your-api-key>, and rendering those as tags eats the text more often than an author actually meant HTML.
Drop the file onto the panel above. Your browser reads it locally and draws it as a page, so there is nothing to install and nothing to sign into. This is the common case when the file came from someone else — or from an assistant — and you only need to read it once rather than set up a markdown editor for a single document.
No. The file is read in your browser and rendered in a sandboxed frame on the same page. Nothing is sent to a server, which is the point when the document is an unpublished draft or a client report.
Yes — GitHub-style pipe tables, including column alignment. Tables are the construct that degrades worst when markdown is read raw, and they are extremely common in anything an AI assistant generates, so they render properly here.
That is deliberate. Angle brackets appear constantly in placeholders — <your-key>, <slug>, <name> — and treating them as tags silently deletes the text between them. Showing them as written is the safer of the two failures. If you want the HTML to actually render, the file is really an HTML document, and the HTML viewer is the right tool for it.
Viewing it here solves the problem for you, not for them — the rendering lives in your browser and cannot be sent. To hand the readable version to someone else, the document needs to be a page at an address they can open. That means converting it to a self-contained HTML file and hosting it at a link, rather than sending the .md and hoping their machine knows what to do with it.
A viewer answers what does this say. An editor answers what should this say. If you are writing over days, want live preview while typing, and need your files synced, an editor is the right tool. If a file arrived and you need to read it now, a viewer is less machinery for the same answer.