Markdown is the lingua franca of developer writing, from README files to pull requests and wikis. But writing it blind means guessing how a nested list, fenced code block or table will render, and pushing a commit just to find a broken layout is a slow feedback loop. This editor shortens it to zero: type Markdown on the left and the rendered result appears live on the right, ready to check GitHub-flavoured formatting before you commit.
A toggle switches the preview to the generated HTML source, handy for debugging odd rendering or lifting the markup into another system, and when the document is ready you can download it as an HTML file. The output is sanitized, so pasting Markdown from an untrusted source that contains embedded scripts cannot run anything in your browser.
Drafts often contain things you would not publish yet: unreleased feature notes, internal links, half-finished announcements. Everything you type here is parsed and rendered by JavaScript inside your own browser tab, so no draft, preview or exported HTML ever travels over the network, and nothing persists once you close the page.
Yes. The output is sanitized before display, stripping script tags and other active content that raw conversion could let through. A pasted document containing embedded JavaScript renders as harmless text and cannot execute in your browser.
The HTML generated from your Markdown, the same markup shown by the source toggle, saved as a standalone file. Open it in any browser, hand it to someone who does not read Markdown, or paste the markup into a CMS.
For everyday formatting, yes: headings, emphasis, lists, blockquotes, code blocks and tables render the way GitHub-flavoured Markdown treats them. GitHub adds extras on top, such as issue references and user mentions, which only come alive on GitHub itself.