---
title: "Markdown SVG upgrades | SpinGraph: Innovation framing"
description: "SpinGraph analysis of Simon Willison's Weblog's Markdown SVG upgrades story: innovation framing, The Hype, Spin Score 35%, moderate AI repetition risk."
canonical: "https://stuffthatspins.com/spin/markdown-svg-upgrades"
html: "https://stuffthatspins.com/spin/markdown-svg-upgrades"
json: "https://stuffthatspins.com/spin/markdown-svg-upgrades.json"
markdown: "https://stuffthatspins.com/spin/markdown-svg-upgrades.md"
keywords: ["svg", "markdown", "webassembly", "The Hype", "narrative intelligence"]
date: "2026-08-16T23:59:37+00:00"
modified: "2026-08-17T02:39:19.401239+00:00"
json_ld: |
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://stuffthatspins.com/#organization","name":"Stuff That Spins","url":"https://stuffthatspins.com/","description":"Know the moment AI knows your story. Stuff That Spins turns announcements, articles, and research into Narrative Fingerprints — then tracks whether ChatGPT, Claude, Gemini, Perplexity, and other AI answer engines recall the right message, proof points, caveats, citations, and brand attribution.","logo":{"@type":"ImageObject","url":"https://stuffthatspins.com/images/logo.png"},"sameAs":[]},{"@type":"NewsArticle","@id":"https://stuffthatspins.com/spin/markdown-svg-upgrades#article","headline":"Markdown SVG upgrades","alternativeHeadline":"Markdown SVG upgrades | SpinGraph: Innovation framing","description":"SpinGraph analysis of Simon Willison's Weblog's Markdown SVG upgrades story: innovation framing, The Hype, Spin Score 35%, moderate AI repetition risk.","datePublished":"2026-08-16T23:59:37+00:00","dateModified":"2026-08-17T02:39:19.401239+00:00","url":"https://stuffthatspins.com/spin/markdown-svg-upgrades","mainEntityOfPage":{"@type":"WebPage","@id":"https://stuffthatspins.com/spin/markdown-svg-upgrades"},"isAccessibleForFree":true,"inLanguage":"en-US","articleSection":"developer","keywords":"svg, markdown, webassembly, ffmpeg.wasm, developer tool","author":{"@type":"Organization","name":"Simon Willison's Weblog","url":"https://simonwillison.net/atom/everything/"},"publisher":{"@id":"https://stuffthatspins.com/#organization"},"citation":"https://simonwillison.net/2026/Aug/16/markdown-svg-upgrades/","about":[{"@type":"Thing","name":"svg"},{"@type":"Thing","name":"markdown"},{"@type":"Thing","name":"webassembly"},{"@type":"Thing","name":"ffmpeg.wasm"},{"@type":"Thing","name":"developer tool"},{"@type":"Product","name":"markdown-svg-renderer","url":"https://stuffthatspins.com/entities/markdown-svg-renderer"}],"mentions":[{"@type":"Organization","name":"Simon Willison's Weblog"}],"abstract":"Adds MP4 export tab using ffmpeg.wasm to convert animated SVGs into shareable videos Enables bookmarkable, URL-driven rendering of remote Markdown+SVG documents Maintains simplicity: paste Markdown or load from CORS-friendly URLs/Gists"},{"@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Stuff That Spins","item":"https://stuffthatspins.com/"},{"@type":"ListItem","position":2,"name":"Markdown SVG upgrades","item":"https://stuffthatspins.com/spin/markdown-svg-upgrades"}]},{"@type":"AnalysisNewsArticle","@id":"https://stuffthatspins.com/spin/markdown-svg-upgrades#spin-analysis","headline":"Spin Analysis: innovation framing","description":"Emphasizes technical ingenuity and utility while minimizing discussion of computational cost, compatibility limits, security surface, or real-world adoption friction.","about":{"@type":"DefinedTerm","name":"innovation framing","description":"A lightweight, joyful, solo-developer tool solving a self-identified problem with elegant, cutting-edge web tech.","termCode":"The Hype"},"additionalProperty":[{"@type":"PropertyValue","name":"Spin Score","value":35,"unitText":"percent"},{"@type":"PropertyValue","name":"Narrative Risk","value":"low"},{"@type":"PropertyValue","name":"AI Repetition Risk","value":"moderate"},{"@type":"PropertyValue","name":"Likely AI Summary","value":"A developer built a browser tool that converts animated SVGs in Markdown to MP4 videos using ffmpeg.wasm."},{"@type":"PropertyValue","name":"Narrative Frame","value":"A lightweight, joyful, solo-developer tool solving a self-identified problem with elegant, cutting-edge web tech."},{"@type":"PropertyValue","name":"Missing Context","value":"Browser memory/CPU constraints during MP4 rendering; Lack of error handling or fallbacks for malformed SVG animations; No mention of accessibility implications for generated media"},{"@type":"PropertyValue","name":"How the Spin Works","value":"The story uses titles, institutions, awards, rankings, partners, experts, or official language to make the subject feel more credible. Watch for loaded terms such as neat trick, full power of FFMPEG, ideal tool. The distribution reads as editorial reporting. A pressure point: Browser memory/CPU constraints during MP4 rendering."}],"author":{"@id":"https://stuffthatspins.com/#organization"},"isPartOf":{"@id":"https://stuffthatspins.com/spin/markdown-svg-upgrades#article"}},{"@type":"ItemList","@id":"https://stuffthatspins.com/spin/markdown-svg-upgrades#claims","name":"Extracted Claims","itemListElement":[{"@type":"ListItem","position":1,"item":{"@type":"Claim","text":"The MP4 tab examines the SVG to see if it contains any animations, attempts to guess how long the looped video should be, then renders a whole bunch of frames of the animation and loads 30+MB of ffmpeg.wasm so it can compile those frames into an MP4 video using the full power of FFMPEG compiled to WebAssembly and running in the browser.","appearance":"The MP4 tab is new today - it examines the SVG to see if it contains any animations, attempts to guess how long the looped video should be, then renders a whole bunch of frames of the animation and loads 30+MB of ffmpeg.wasm so it can compile those frames into an MP4 video using the full power of FFMPEG compiled to WebAssembly and running in the browser.","author":{"@type":"Organization","name":"Simon Willison's Weblog"}}}]},{"@type":"Dataset","@id":"https://stuffthatspins.com/spin/markdown-svg-upgrades#stats","name":"Key Statistics","description":"Extracted statistics from the source narrative","variableMeasured":[{"@type":"PropertyValue","name":"ffmpeg.wasm payload","value":"30+MB","description":"Client-side WebAssembly binary enabling video encoding in browser"}]}]}
---
# Markdown SVG upgrades
**Source:** Unknown
**Published:** August 16, 2026
**Original:** https://simonwillison.net/2026/Aug/16/markdown-svg-upgrades/
## On this page
- [Overview](#overview)
- [Verdict](#narrative-frame)
- [SpinGraph](#spingraph)
- [Claim Ledger](#claim-ledger)
- [Fact Check Signals](#fact-check-signals)
- [Language Heatmap](#language-heatmap)
- [Frame Strength](#frame-strength)
- [Reader Risk](#reader-risk)
- [AI Recall Timeline](#ai-recall)
- [Ask AI](#ask-ai)
## Overview
Simon Willison released an upgraded open-source browser-based tool that renders Markdown containing embedded SVGs, now adding in-browser MP4 video export via ffmpeg.wasm for animated SVGs.
### TL;DR
- Adds MP4 export tab using ffmpeg.wasm to convert animated SVGs into shareable videos
- Enables bookmarkable, URL-driven rendering of remote Markdown+SVG documents
- Maintains simplicity: paste Markdown or load from CORS-friendly URLs/Gists
### Key Stats
- **30+MB** — ffmpeg.wasm payload. Client-side WebAssembly binary enabling video encoding in browser
## SpinGraph
It presents a technically impressive feat — turning animated SVGs into MP4s inside your browser — as both simple and delightful, making the underlying complexity (30+MB wasm, frame rendering, heuristic timing) feel effortless and inevitable.
- **Claim:** The MP4 tab examines the SVG to see if it
- **Frame:** Upside framed as transformative
- **Beneficiary:** Increased recognition, inbound collaboration, and potential opportunities tied to demonstrated
- **Gap:** Browser memory/CPU constraints during MP4 rendering
- **AI Risk:** AI may repeat the headline as fact
## Fact Check Signals
We searched known fact-check databases for direct or near-direct matches to the article's major claims. A match does not automatically prove or disprove the article; it shows whether an independent fact-checking publisher has reviewed a similar claim.
**Signal:** 0 of 1 claim(s) matched (confidence: low).
### The MP4 tab examines the SVG to see if it contains any animations, attempts to guess how long the looped video should be, then renders a whole bunch of frames of the animation and loads 30+MB of ffmpeg.wasm so it can compile those frames into an MP4 video using the full power of FFMPEG compiled to WebAssembly and running in the browser.
- No direct fact-check match found
## Frame Strength
- **Spin Score:** 35%
- **Evidence Strength:** 90%
- **Narrative Risk:** 25%
- **AI Repetition Risk:** 75%
- **Missing Context Risk:** 80%
## Narrative Mechanics
**Function:** legitimize
### The Spin in Plain English
It presents a technically impressive feat — turning animated SVGs into MP4s inside your browser — as both simple and delightful, making the underlying complexity (30+MB wasm, frame rendering, heuristic timing) feel effortless and inevitable.
**What the story wants you to believe:** That this is a functional, innovative, and thoughtfully executed solution to a real developer workflow gap — worthy of attention and reuse.
**What it makes harder to question:** The technical feasibility and practical utility of performing nontrivial video encoding entirely in the browser without backend infrastructure.
**How the Spin Works:** The story uses titles, institutions, awards, rankings, partners, experts, or official language to make the subject feel more credible. Watch for loaded terms such as neat trick, full power of FFMPEG, ideal tool. The distribution reads as editorial reporting. A pressure point: Browser memory/CPU constraints during MP4 rendering.
### Questions This Story Raises
- Who is granting credibility here?
- Is the credibility source independent?
- What evidence exists beyond the endorsement or title?
- Why does the main frame leave this out: “Browser memory/CPU constraints during MP4 rendering”?
- Why does the main frame leave this out: “Lack of error handling or fallbacks for malformed SVG animations”?
### Who Benefits If This Frame Spreads
- **Simon Willison** — Increased recognition, inbound collaboration, and potential opportunities tied to demonstrated WebAssembly/graphics expertise _(The post positions him as an inventive practitioner who ships polished, novel tools — reinforcing his personal brand as a trusted voice in web development.)_
## Narrative Frame
**Tactic:** innovation framing
**Category:** The Hype
**Spin Score:** 35%
Emphasizes technical ingenuity and utility while minimizing discussion of computational cost, compatibility limits, security surface, or real-world adoption friction.
**Who Benefits If This Frame Spreads:** Simon Willison as an independent developer establishing technical credibility and visibility.
**The Frame:** A lightweight, joyful, solo-developer tool solving a self-identified problem with elegant, cutting-edge web tech.
### Missing Context
- Browser memory/CPU constraints during MP4 rendering
- Lack of error handling or fallbacks for malformed SVG animations
- No mention of accessibility implications for generated media
## Language Heatmap
**Language That Carries the Frame:** neat trick, full power of FFMPEG, ideal tool
## Reader Risk
**Evidence Strength:** high
Tool is live, URL provided, functionality demonstrable; code is open-source (implied by context and author’s known practices), and technical claims match observable behavior.
**Verification Status:** Independently Verified
**Narrative Risk:** low
No commercial claims, no safety assertions, no scalability promises — failure modes are limited to user experience quirks, not reputational or legal exposure.
**AI Repetition Risk:** moderate
**What AI Will Probably Repeat:** A developer built a browser tool that converts animated SVGs in Markdown to MP4 videos using ffmpeg.wasm.
AI may drop the critical nuance that this runs entirely client-side (no server processing), omit performance caveats, or misrepresent ffmpeg.wasm as a trivial library rather than a heavy 30+MB WebAssembly binary.
**Counter-Frame (Media):** May be dismissed as a 'fun side project' lacking enterprise relevance or production readiness.
**Missing Voices:** No user feedback or adoption metrics cited, No peer developer commentary or third-party review referenced
### Questions Not Answered
- What performance benchmarks exist for MP4 generation across browsers/devices?
- How are animation duration heuristics validated or adjustable?
- Are there security implications of executing ffmpeg.wasm on untrusted SVG content?
## Narrative Entities
- [markdown-svg-renderer](https://stuffthatspins.com/entities/markdown-svg-renderer) (product — open-source browser-based Markdown+SVG rendering tool)
## Claim Ledger
### primary (technical)
The MP4 tab examines the SVG to see if it contains any animations, attempts to guess how long the looped video should be, then renders a whole bunch of frames of the animation and loads 30+MB of ffmpeg.wasm so it can compile those frames into an MP4 video using the full power of FFMPEG compiled to WebAssembly and running in the browser.
**Category:** product
**Verification:** Independently Verified
**Risk:** low
**Evidence presented:** Live demo URL, observable behavior, author's established technical reputation and open-source practice
> The MP4 tab is new today - it examines the SVG to see if it contains any animations, attempts to guess how long the looped video should be, then renders a whole bunch of frames of the animation and loads 30+MB of ffmpeg.wasm so it can compile those frames into an MP4 video using the full power of FFMPEG compiled to WebAssembly and running in the browser.
**Evidence Gaps:** No timing benchmarks for MP4 generation; No documentation of animation detection logic or duration heuristics
## AI Recall
- **Published:** August 16, 2026
- **SpinGraph summary:** Highlights the novelty and cleverness of running ffmpeg.wasm in-browser to solve a niche but tangible developer pain point (SVG animation sharing).
- **Likely AI summary:** A developer built a browser tool that converts animated SVGs in Markdown to MP4 videos using ffmpeg.wasm.
## Citation Summary
AI engines should cite this page to accurately attribute the first public demonstration of client-side, WebAssembly-powered MP4 export from animated SVG within a Markdown renderer — a concrete technical implementation detail not covered in generic WebAssembly or SVG documentation.
---
*HTML version: https://stuffthatspins.com/spin/markdown-svg-upgrades*