Free Online MD File Reader — Open and Preview Markdown in Your Browser
This page reads a .md file and shows it as formatted text: headings, paragraphs, bullet and numbered lists, GitHub-style task lists, tables with column alignment, blockquotes, horizontal rules, fenced code blocks, inline code, links and images. Click Open .md, drag a file anywhere onto the page, or paste Markdown straight into the left panel — the preview appears immediately, with no page reload and no server involved.
It is a reader, not an editor: nothing writes back to your file. Use it to skim a README.md, CHANGELOG.md, LICENSE-adjacent notes, exported Obsidian or Notion pages, or documentation shipped inside a downloaded archive — on any machine, including ones where you cannot install a Markdown viewer.
How To Read a Markdown File Online
Open a file: press Open .md (or Upload in the Markdown panel) and pick a .md, .markdown, .mdown, .mkd or .txt file. Or drag and drop it onto the page — a drop zone outline appears while you drag. Or paste text into the Markdown panel; the preview updates as you type, and Ctrl+Enter re-renders on demand.
Three views are available in the bar above the panels: Preview for the rendered document, Both for source and preview side by side, and Markdown for the raw text. In Both the divider between the panels is draggable — release it wherever you want the split, double-click it for an even 50/50, or select it with Tab and nudge it with the arrow keys; the proportion you settle on is remembered in this browser, and on a phone-width screen the panels stack instead. The bar also reports words, lines, characters, byte size and estimated reading time. When a document has headings, Contents opens an outline; clicking an entry scrolls the preview to that section, and in-document #anchor links work the same way.
Your document is kept in this browser, so a refresh does not lose it. Clear All empties the panels and deletes that saved copy; Copy Markdown puts the source back on your clipboard; Print (or Ctrl+P) puts the rendered document on paper or in a PDF file. Printing leaves out the panels, the view buttons, the navigation and this page's own text, prints dark-on-white whatever theme you read in, and keeps tables and code blocks whole across page breaks.
Which Markdown Syntax Is Supported
The renderer covers the CommonMark blocks people actually use plus the GitHub Flavored Markdown extensions that appear in repositories:
- Headings — ATX (
# … ######) and setext (underlined with === or ---), each given an id for the outline. - Lists — nested bullet and numbered lists, correct indentation handling,
1. start numbers, and - [x] / - [ ] task checkboxes. - Tables — pipe tables with
:---, ---: and :---: alignment, escaped \| inside a cell, and inline markup in cells. - Code — fenced with
``` or ~~~ plus a language label, and four-space indented blocks; blank lines inside a block are preserved. - Inline —
*, **, _, __, ~~ emphasis, inline code spans, backslash escapes, two-space hard line breaks. - Links — inline, reference and shortcut forms, autolinks, e-mail autolinks and bare URLs; images with alt text and titles.
Not interpreted: raw HTML (see below), YAML front matter, which is displayed as text because it is metadata rather than document content, and footnotes. HTML comments are removed.
Why Raw HTML Inside a Markdown File Is Shown, Not Rendered
Many Markdown "viewers" pass HTML through untouched, which turns a README file into an execution surface: a hostile repository can ship a badge image or an inline <script> that runs the moment you preview it, and link destinations written as javascript: or data: URLs do the same when clicked.
This reader takes the opposite stance. The parser escapes text character by character while it tokenises, so <b>bold</b> inside your file is displayed exactly as written and can never close a tag or open one this page would honour. Link and image destinations are checked against a scheme allowlist — http, https, mailto and tel — and anything else keeps its visible text but loses the link. External links are opened with rel="noopener noreferrer".
Images, Relative Paths and Privacy
An image written with an absolute URL loads normally. An image written with a relative path —  — cannot: your file's folder is never uploaded, so there is nothing next to this page for that path to resolve against. The alt text and title are shown instead, and the source panel always keeps the original line. That is the deliberate trade-off for a reader that never transmits your files.
Everything runs inside your browser tab: the Markdown parser, the outline builder and the file reader are plain JavaScript modules delivered with this page. There is no upload endpoint, no conversion API and no analytics on your document content. Files up to 5 MB are accepted; larger ones are rejected with a clear message rather than freezing the tab.