Can Android use an SVG directly as a drawable?
A VectorDrawable resource uses Android's XML vocabulary: a vector element with a viewport, display dimensions and drawing paths. Renaming logo.svg to logo.xml does not translate those elements. SVG uses different names for fills, strokes and transforms, and supports features that this exporter intentionally refuses.
Use the SVG to Android converter for a simple interface icon or flat illustration. It accepts your SVG upload or one of your own unlocked results. If you start with a bitmap, trace the image to vector first, inspect the outlines, and then export. Converting resources does not perform another trace or remove the unlock requirement from an existing result.
A small example you can reproduce
Save this triangle as triangle.svg and upload it. Choose the resource name ic_triangle and a longest side of 24 dp.
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24">
<path fill="#fa643c" d="M12 2L22 22H2Z"/>
</svg>
The downloaded XML contains a 24 by 24 viewport, 24 dp display dimensions and one path. Its orange fill becomes Android's alpha-first color #fffa643c. Put ic_triangle.xml in app/src/main/res/drawable/. In a layout, use android:src="@drawable/ic_triangle"; in application code, use the corresponding drawable resource identifier.
The viewport describes geometry. The dp dimensions describe the drawable's intended display size. A rectangular SVG keeps its aspect ratio: choosing a 48 dp longest side does not stretch it into a square. The resource name starts with a lowercase letter and can contain lowercase letters, digits and underscores.
What survives conversion?
Our converter supports paths and basic geometric shapes, solid colors, fill opacity, compatible stroke styles and both nonzero and even-odd fills. It flattens supported transforms into path coordinates. Even-odd filling is why this export targets API 24 and later. It does not create compatibility wrappers for older applications.
Text, gradients, masks, clipping, embedded pictures and effects need a different preparation step. Outline text in your vector editor. Convert transformed strokes to outlines if the transform scales their axes differently. Group opacity can change overlapping shapes, so the exporter refuses it instead of applying opacity separately and changing the picture. Sanitization warnings describe removed unsafe content.
For detailed artwork, a PNG export can be a more suitable resource. A very large path count can cost rendering time even when the file is technically a vector. Simplify unnecessary points and test at the actual on-screen size.
Check the result in the application
Build the resource in Android Studio and inspect it against light and dark backgrounds. Check holes inside letters, thin strokes, intended colors and transparency. Compare the original and drawable at small sizes, where minor details matter most. Successful XML compilation confirms that the resource is accepted; device rendering and your app's tint settings still determine its final appearance.
For a launcher icon, use the app icon generator. Launcher icons have density and adaptive-layer requirements that an ordinary drawable export does not package.