SVG to Video

What SVG to Video does

SVG to Video MCP server turns CSS-animated SVG files into video or animated-image files. Supported video formats are MP4, WebM, MKV, and MOV. It also produces animated PNG and GIF files, including transparent output where the selected format supports it.

The project is intended for AI-assisted conversion as well as command-line automation. An assistant can receive a request such as converting an SVG to a 60 fps transparent WebM, while batch jobs can invoke the same rendering system through the CLI or Docker image. The browser-based Web Studio is a separate client-side entry point for manual conversion.

How it works

The renderer isolates the SVG, advances its Web Animations API state frame by frame, and captures the rendered frames. WebCodecs or FFmpeg then encode those frames into the requested output format. This approach is designed to preserve the animation as rendered rather than treating the SVG as a static image.

The MCP server communicates over the standard input/output process started by the configured command. A typical MCP configuration runs npx with the @gehdoc/svg-to-video package and its svg-to-video-mcp entry point. The README identifies Claude Desktop and Cursor as clients that can connect this way; it also references Antigravity and AutoGPT as AI-agent integrations.

SVG to Video MCP server is a suitable choice when the input is an animated SVG and the output must be generated as part of an agent workflow. Reach for the CLI or Docker mode instead when processing many files, running on a server, or integrating conversion into CI/CD.

Setup and configuration

The documented setup uses an MCP client configuration similar to:

{
  "mcpServers": {
    "svg-to-video": {
      "command": "npx",
      "args": ["-y", "-p", "@gehdoc/svg-to-video", "svg-to-video-mcp"]
    }
  }
}

This runs the package on demand, so a separate global installation is not required. The package is also distributed through npm, and an official Docker image is available. Docker execution is intended for headless use and requires additional shared memory for Chromium rendering; the documented example uses --shm-size=2gb.

For non-MCP automation, the CLI requires Node.js and FFmpeg. It accepts an SVG input, a frame-rate or timing value, an output directory, and options such as duration, format, and transparency. The Web Studio requires no local installation because rendering occurs in the browser.

Tools and capabilities

• Convert animated SVG input to MP4, WebM, MKV, or MOV.
• Generate APNG and GIF animations.
• Request transparent backgrounds for supported output formats.
• Control rendering settings such as duration, resolution, and frame rate through the available interfaces.
• Run conversion from an MCP client, npm-based CLI, Docker, or the browser studio.
• Add custom titles and comments to supported video and animated-image formats.

That browser interface keeps SVG files on the local device during rendering. The project’s analytics can be disabled with DO_NOT_TRACK=1.