Convert SVG icons to Android Vector Drawable XML in your browser, with paste, batch, folder and ZIP import. A single Vector Drawable scales crisply across every screen density, so you ship one file instead of five PNG buckets — smaller APK, sharper icons. PNG and JPEG can be traced to vectors too.
A Vector Drawable is Android's native XML format for scalable vector graphics. It defines paths, fills, strokes, and gradients in a single <vector> element that renders crisply at any density without shipping multiple PNGs.
No. The entire conversion runs in your browser using JavaScript — your files never leave your device, which makes it safe for proprietary icons and assets.
Yes. Raster images (PNG, JPEG, GIF, BMP, WebP) are traced to vectors first using a selectable tracer preset, then converted to a Vector Drawable. Tracing works best on flat, logo-style images.
Yes. Drop multiple files, a whole folder, or a ZIP archive in the Batch tab. Conversion runs in the background via the Processing manager and the original folder structure is preserved in the downloaded ZIP.
Vector Drawable supports linear and radial gradients but not every SVG feature. Filters, masks, patterns, text, and embedded images can't be represented, so the converter flags them instead of failing silently.
It forces an explicit android:fillType on every filled path. This keeps fills rendering consistently across Android API levels, especially for compound paths with holes.
This tool converts SVG markup into Android VectorDrawable XML entirely in the browser. Each SVG is first optimized with SVGO, then its elements are mapped to the VectorDrawable schema: <path> elements become <path android:pathData>, fill-rule maps to android:fillType (nonZero/evenOdd), linear and radial gradients are emitted as aapt:attr gradient blocks, groups and transforms collapse into <group> nodes or are baked into path data, and clip paths become <clip-path>. Raster inputs (PNG, JPEG, GIF) are vectorized first using an image tracer with selectable presets, then converted through the same pipeline. Batch jobs run through a background processing queue and are packaged as a structure-preserving ZIP. All processing happens locally — no file is ever uploaded.