SVG to JPG fixes scalable artwork to opaque JPEG pixels, so transparent icons and editable vector text become a flat image.
From real runs
| Element | Result | What happens |
|---|---|---|
| Output raster | Changed | The 640 byte SVG rendered to a 7,413 byte JPEG at 320×180 pixels using the default size. |
| Transparency | Lost | Transparent SVG areas were filled before JPEG writing, because the JPEG file has no alpha channel. |
| Inline styles | Kept | Class rules inside the SVG were applied before rasterization, so the test logo colors rendered as expected. |
| External CSS | Lost | The external stylesheet control rendered default black text, proving linked CSS was unavailable to the conversion. |
| Text rendering | Changed | Text with an unavailable font rendered through fallback metrics and then became JPEG pixels. |
| JPEG artifacts | Changed | Flat fills and text edges can pick up JPEG ringing because quality 90 is still a lossy encode. |
The 640 byte SVG rendered to a 7,413 byte JPEG at 320×180 pixels using the default size.
Transparent SVG areas were filled before JPEG writing, because the JPEG file has no alpha channel.
Class rules inside the SVG were applied before rasterization, so the test logo colors rendered as expected.
The external stylesheet control rendered default black text, proving linked CSS was unavailable to the conversion.
Text with an unavailable font rendered through fallback metrics and then became JPEG pixels.
Flat fills and text edges can pick up JPEG ringing because quality 90 is still a lossy encode.
We converted our SVG sample (389 B) with Image engine on 2026-10-20. It took 15 ms and produced a 5 KB JPEG file, 14× larger than the input. The engine raised 2 warnings, listed below.
Input · sample.svg · 389 B
SVG viewBox 0 0 320 200, 0 paths
Output · sample.jpg · 5 KB
320 × 200 px, baseline
CairoSVG plus Pillow
import cairosvg
from PIL import Image
from io import BytesIO
png = cairosvg.svg2png(url="in.svg", dpi=96)
Image.open(BytesIO(png)).convert("RGBA").convert("RGB").save("out.jpg", quality=90)Flatten intentionally and inline critical styles before conversion, otherwise browser and server renders can disagree.
The HTTP API and the MCP server run the exact engine this page uses (Image engine); the response carries the same warnings the web converter shows. Check support first with GET /api/v1/pairs?from=svg&to=jpg.
curl -X POST https://filetypeconverters.com/api/v1/convert \
-H "Authorization: Bearer $FTC_API_KEY" \
-F "file=@input.svg" -F "from=svg" -F "to=jpg" \
-F 'options={"dpi":96}' \
--output output.jpg| Key | Applies to | Type | Default |
|---|---|---|---|
| dpi | Reading SVG | number | 96 |
| width | Writing JPEG | number | 0 |
| height | Writing JPEG | number | 0 |
| fit | Writing JPEG | contain · cover · fill | contain |
| quality | Writing JPEG | number | 90 |
| background | Writing JPEG | string | #ffffff |
| stripMetadata | Writing JPEG | boolean | true |
No. JPEG is opaque, so transparent SVG regions are flattened to the chosen background color before save.
The API upload contains the SVG file, not its neighboring CSS files. Inline the rules that control fills, strokes, and fonts.
Do that when exact typography matters. Otherwise the server fallback font can change line length before the text becomes pixels.