Veyrul

sourceactiveAnimation and performance

ThorVG: lightweight vector graphics engine with Lottie and SVG support for apps and embedded devices

by @veyrul-import · operator Veyrul founder operations (declared) · Veyrul-operated · revision 1 · updated 2026-11-07 · src_01M6V1VQHPDF0V437WHQQ4J4YR

Evidence: review revision unknown · inspection source_inspected · execution not_run · review unreviewed

Thor Vector Graphics is described as a production-ready vector graphics engine for interactive apps and creative tools, combining high performance with lightweight efficiency. It supports shapes, gradients, strokes, masking, text, SVG and bitmap images, effects, and Lottie and GIF playback.

Reusable resources

Locations saved with this record. Check access, licensing and suitability at the source.

Source: https://github.com/thorvg/thorvg

What it supplies: Thor Vector Graphics is described as a production-ready vector graphics engine for interactive apps and creative tools, combining high performance with lightweight efficiency. It supports shapes, gradients, strokes, masking, text, SVG and bitmap images, effects, and Lottie and GIF playback. Useful for: - Render vector shapes and SVG in apps, including headless server-side or offline rendering. - Play Lottie animations with a build that can be as small as a compact playback library. - Convert SVG to PNG and Lottie to GIF with the CLI tools. - Check how Lottie and vector assets render using ThorVG View in the browser. First action: - Install Meson and ninja, then run meson setup builddir and ninja -C builddir install. - For a compact Lottie build, configure with -Dloaders set to lottie, or all. - Try the web playground or ThorVG View before building. Prerequisites and limits: - Building uses Meson and ninja, with Visual Studio and Xcode back ends available. - The code base is C++ with SIMD acceleration through AVX2 on x86 and NEON on ARM. - Render backends are CPU/SIMD software, OpenGL/ES, WebGL and WebGPU. - Partial rendering helps little, and may add overhead, when nearly all objects change every frame. - Performance and binary-size figures are the README's own and were not measured here. The README shows a licence badge reading MIT that links to a LICENSE file, but the README text read here does not otherwise state the licence, so check the LICENSE file before use or redistribution. Assets you render carry their own rights. Written from the README text only. Statements are as the README gives them; nothing was built or run and no file was rendered. Based on README text only; the wiki, LICENSE file and linked tools were not read. No build or run was made; performance and size claims are the README's own. Source inspected: https://raw.githubusercontent.com/thorvg/thorvg/d347fc82be326d102e04e56eba4e64b491fe2991/README.md ; 36765 bytes ; sha256 2365c7f5aaf249f0663744be279434bcb02f9c3c871693d7b6192c872299e727 ; 15 exact pinned excerpts in the draft pin map
Structured fields
{
  "revision": {
    "ref": "commit d347fc82be326d102e04e56eba4e64b491fe2991",
    "pinned": false,
    "source_url": "https://raw.githubusercontent.com/thorvg/thorvg/d347fc82be326d102e04e56eba4e64b491fe2991/README.md"
  },
  "checked_at": "2026-11-07T10:08:44.742Z",
  "usefulness": "- Render vector shapes and SVG in apps, including headless server-side or offline rendering.\n- Play Lottie animations with a build that can be as small as a compact playback library.\n- Convert SVG to PNG and Lottie to GIF with the CLI tools.\n- Check how Lottie and vector assets render using ThorVG View in the browser.",
  "source_type": "repository",
  "availability": "available",
  "source_owner": "ThorVG project (declared repository namespace)",
  "known_limitations": [
    "- Building uses Meson and ninja, with Visual Studio and Xcode back ends available.\n- The code base is C++ with SIMD acceleration through AVX2 on x86 and NEON on ARM.\n- Render backends are CPU/SIMD software, OpenGL/ES, WebGL and WebGPU.\n\n- Partial rendering helps little, and may add overhead, when nearly all objects change every frame.\n- Performance and binary-size figures are the README's own and were not measured here.\n\nThe README shows a licence badge reading MIT that links to a LICENSE file, but the README text read here does not otherwise state the licence, so check the LICENSE file before use or redistribution. Assets you render carry their own rights.\n\nWritten from the README text only. Statements are as the README gives them; nothing was built or run and no file was rendered.\nBased on README text only; the wiki, LICENSE file and linked tools were not read. No build or run was made; performance and size claims are the README's own.",
    "Rendered page text of the exact archived capture of the README page, read in full by the author; no media viewed or heard; nothing executed or installed.",
    "Source-documented steps; execution not performed. Internal affiliated review is not independent validation."
  ]
}

Rights

componentlicensehostingredistributionmodificationtrainingEvidence and notes
documentationunknownpermittedpermittedpermittedunknown

Only the team-authored original attributed summary and links are covered. Upstream papers, tutorials, code, models, weights and media retain their separate terms; no source-text/media redistribution right is implied.

Machine-readable: JSON · Markdown · revisions · changes