13 releases (breaking)
|0.11.0||Jul 4, 2020|
|0.9.0||Jan 18, 2020|
|0.8.0||Aug 17, 2019|
|0.7.0||Jun 19, 2019|
|0.1.0||Dec 18, 2017|
#10 in Images
5,286 downloads per month
Used in 17 crates (10 directly)
resvg is an SVG rendering library.
The core idea is to make a fast, small, portable SVG library designed for edge-cases.
Right now, a
resvg CLI application is less than 4MiB and doesn't require any external dependencies.
At the moment, there are no production-ready 2D rendering libraries for Rust.
Because of that,
resvg relies on Skia.
Another major difference from other SVG rendering libraries is that
resvg does a lot
of preprocessing before rendering. It converts an input SVG into a simplified one
called Micro SVG and only then it begins rendering.
So it's very easy to implement a new rendering backend.
But we officially support only the Skia one.
And you can also access Micro SVG as XML directly via the usvg tool.
resvg is aiming to support only the static
SVG subset; e.g. no
cursor elements, no events and no animations.
Results of the resvg test suite:
You can find a complete table of supported features here. It also includes alternative libraries.
Comparing performance between different SVG rendering libraries is like comparing
apples and oranges. Everyone has a very different set of supported features,
implementation languages, build flags, etc.
resvg is written in Rust and uses Skia for rendering - it's pretty fast.
cargo build --release
which will produce binaries that doesn't require any external dependencies.
And while we can leave
harfbuzz compilation to Cargo, Skia is more troublesome.
Mainly because it
clang and no other compilers.
Also, we do not support 32-bit builds and MINGW target.
resvg depends on C++ libraries, it's inherently unsafe in Rust terms.
Despite of that, most of the dependencies are actually fully safe.
The main exceptions are Skia and harfbuzz bindings, and files memory mapping.
resvg project is licensed under the MPLv2.0.