MD -> READABLE · Local tool
Markdown Viewer
Open a markdown file and read it rendered, with a contents list.
Last updated
How do I open a .md file and read it properly?
Drop it into filetity's markdown viewer and it renders in the browser tab, with a contents list built from the headings and an estimated reading time. Nothing is uploaded. The rendered document is drawn inside a sandboxed frame with scripts switched off, which matters because markdown is allowed to contain raw HTML and raw HTML can contain a script. Images hosted on other servers are blocked until you ask for them, so opening a README does not tell a badge service that you did. There is a source view for reading the markdown itself, and the file on disk is never changed.
01 / Your device
the file stays here
02 / Browser memory
the work runs locally
03 / Back to you
saved on this device
When you would use this
Situations, not settings.
- A README from a repository you are deciding whether to trust
- It renders in a sandbox with scripts off and badge images blocked, so reading it tells nobody that you did.
- Notes exported from Obsidian, Bear or Notion
- A .md file on a machine with no markdown editor is a wall of hashes and asterisks. This reads it the way it was written.
- A long document you need to navigate
- The contents list is built from the headings, and skips the ones inside code blocks that other tools mistake for headings.
How it works / no cloud
A conversion engine, not an upload form.
Markdown is rendered in the page and then drawn inside a frame with an empty sandbox attribute and a content policy of its own. That is not decoration. Markdown is allowed to contain raw HTML, raw HTML can contain a script, and a viewer is opened precisely when a file is not yet trusted. The same policy blocks images hosted elsewhere unless you switch them on, because an image tag in a document tells whoever hosts it that you opened the file and when. The contents list is read from the markdown source rather than the rendered output, so a # inside a fenced code block stays a shell comment instead of becoming a heading.
- Offline ready
- Installable app
- No file limit queue
Straight answers
No accordion. Nothing hidden.
- Is it free?
- Yes, with no watermark and no page limit.
- Does it need an account?
- No. There is no account system.
- Is my file processed on my device?
- Yes. The file is read by your browser and never uploaded. There is no server to send it to.
- What formats are supported?
- MD, MARKDOWN, MDX and TXT in, or pasted text. Nothing comes out: this one reads.
- What are the limits?
- Whatever your browser will hold. Very long documents render fine; the contents list is what makes them navigable.
- Does it work on mobile?
- Yes, on any modern mobile browser. Large files are limited by the memory the phone gives the browser.
- Does it work offline?
- Yes, once the page has loaded. The tool keeps working with no network connection.
- Why are the images in my README not showing?
- Remote images are blocked until you ask for them. Badges and screenshots in a README are usually hosted on someone else's server, and loading them tells that server your address and the moment you opened the file. There is a checkbox under the document to turn them on when you want to see them.
- Does it render GitHub flavoured markdown?
- Tables, fenced code blocks, task lists and strikethrough, yes. What it does not do is GitHub's own extensions to its own site: issue references, @mentions and the coloured note and warning blocks are GitHub features rather than markdown, and they render as the plain text they are.
- Can markdown be dangerous to open?
- The markdown itself, no. What it can carry is raw HTML, which is part of the format, and a script tag inside that HTML runs when a viewer inlines the result into its own page. Here the document is drawn inside a sandboxed frame with scripts, forms and navigation all switched off, so it renders exactly as it should and can do nothing else.
- Where does the reading time come from?
- The word count divided by 200 words a minute, rounded up to at least one. Two hundred is the low end of the range adult reading studies report and what most publishing tools use. Code blocks are counted, because they are on the page and reading them takes time too.
Keep working locally
3 available · more coming