Markdown Snippet Runner
Executes JavaScript / TypeScript code blocks from a Markdown doc inside a sandboxed iframe — perfect for live tutorials and runnable READMEs.
How to run Markdown snippets
Wrap JavaScript in fenced code blocks tagged js or ts — click Run to execute inside a sandboxed iframe.
- 01
Fence with `js`
Only fences tagged js / javascript / ts / typescript are runnable.
Parsing runs through marked with GFM extensions enabled — tables, task lists, strikethrough, and fenced code blocks all match GitHub’s rendering.
fenceGFMmarkedCommonMarklivelang · markdownjs · GFM```js console.log(1); ```
loaded · GFMGFM · ready - 02
Pick + run
The Pick dropdown lists each runnable snippet — choose one and click Run.
Soft-break behaviour is configurable: by default a single newline becomes a space (CommonMark), toggle on for chat-style
<br>insertion.runsoft-breaksoptionsconfiglivesnippet · options1 · live▶ run
options applied · livelive - 03
See output
console.log and console.error appear in the iframe panel.
The preview is scoped under a
.mdeclass so its CSS doesn’t bleed into the rest of the page. Output HTML is whitespace-controlled for clean diffs.consolepreviewscoped CSSrenderstablestdout · renderedcaptured · ready1 + 2 = 3
rendered · liverendered - 04
Run all
Combine every snippet into one run — separator lines between each.
Export covers both raw Markdown and rendered HTML; downloads stream as
text/markdownortext/htmlviaBlob+ object URL.batchclipboard.md.htmlblob✓ · exportedall · done✓ Running all
shipped · ready to shipsuccess
Author Markdown that renders everywhere
GFM is the safe default
GitHub-Flavored Markdown is the de-facto baseline (tables, task lists, strikethrough). CommonMark is stricter but ubiquitous as a fallback.
Soft-break behaviour varies
A single newline is a space in CommonMark, a <br> in GFM. Toggle soft breaks when source matters.
Escape inside code fences
Backticks inside fenced blocks need a longer fence — three becomes four. Use ~~~ if your content has many backticks.
Anchors are slugified
GitHub lowercases, strips punctuation, and joins with hyphens. Duplicate headings get -1, -2 suffixes.
Tables need a header row
The dash row sets alignment (:---, :-:, ---:). Use Table Aligner for diff-friendly columns.
Front matter is YAML
Triple-dash blocks at the top of files are parsed by static-site generators. Use the Front-Matter Validator to catch syntax errors.
When to run snippets
Tutorials, demos, education.
Live tutorials
Verify every snippet in a docs page actually runs. Render path uses marked with GFM extensions enabled (tables, task lists, strikethrough, autolinks), so what you preview matches what GitHub publishes bit-for-bit. Soft-break behaviour is configurable for chat-style vs prose Markdown.
GFM-compliantRunnable READMEs
Embed quick-start code that readers can try inline. Pairs cleanly with the Markdown Cheatsheet for syntax you can't quite remember — callout blocks, footnotes, definition lists. Output stays diff-friendly so style-only changes don't drown out real edits in PRs.
GitHub-perfectCode samples
Test the demo before publishing a blog post. Cross-platform safe: anchors, code fences, and tables behave identically on GitHub, GitLab, Bitbucket, and Gitea. Heading-anchor slugs follow GitHub's lowercase-and-hyphenate rules so deep links survive a docs migration.
diff-friendlyWorkshops
Run every step's code without leaving the slide deck. No server roundtrip — perfect for proprietary content you can't paste into a public tool. The full marked + GFM bundle ships with the page, so it works offline once loaded.
render-stableSpec exploration
Quickly try out a JavaScript API while reading the spec. Front matter (YAML / TOML / JSON) passes through unchanged so static-site pipelines (Jekyll, Hugo, Astro, Eleventy) read it correctly. Pair with the Front-Matter Validator to catch syntax errors before deploy.
cross-platformBug repros
Drop a snippet into the runner to share a minimal repro. Output is reproducible: identical input always produces identical Markdown, so doc-generation scripts can rely on it for snapshot tests and embedded into release workflows.
SEO-friendlyFrequently asked questions
Something missing?
Tell us what you need. We ship the top requests every two weeks.