XPS → PNG draws each page as a picture, so a receipt or report printed to XPS can be pasted somewhere that would never preview the original file.
From real runs
| Element | Result | What happens |
|---|---|---|
| One image per page | Kept | The three-page Go record came back as three PNGs in one ZIP; the single-page Word sample came back as one PNG with no archive around it. |
| Pixel size | Changed | At the default 144 DPI an XPS A4 page is 1190 × 1683 pixels and a PowerPoint slide 1440 × 1080. With dpi 300 the A4 page was 2479 × 3507. |
| Typefaces | Kept | Pages are drawn with the fonts stored inside the XPS, so the Japanese player names and Consolas listings look as they did in Windows. |
| Text | Changed | The words become pixels: nothing on a PNG page can be selected, searched or read aloud, so paste the important numbers as text next to the image. |
| Fine table lines | Kept | One-pixel borders between the 60 table rows stay crisp because PNG compresses without loss. |
| Web links | Lost | An image has no place for a link; the underlined link in the Tika test page is just blue text in the PNG. |
| File size | Changed | A 76,412-byte XPS became 838,390 bytes of PNGs, because the XPS stores text as font references and the PNG stores every pixel. |
The three-page Go record came back as three PNGs in one ZIP; the single-page Word sample came back as one PNG with no archive around it.
At the default 144 DPI an XPS A4 page is 1190 × 1683 pixels and a PowerPoint slide 1440 × 1080. With dpi 300 the A4 page was 2479 × 3507.
Pages are drawn with the fonts stored inside the XPS, so the Japanese player names and Consolas listings look as they did in Windows.
The words become pixels: nothing on a PNG page can be selected, searched or read aloud, so paste the important numbers as text next to the image.
One-pixel borders between the 60 table rows stay crisp because PNG compresses without loss.
An image has no place for a link; the underlined link in the Tika test page is just blue text in the PNG.
A 76,412-byte XPS became 838,390 bytes of PNGs, because the XPS stores text as font references and the PNG stores every pixel.
We converted our XPS / OpenXPS sample (74 KB) with Image engine on 2026-10-20. It took 521 ms and produced a 85 KB PNG file, 1.2× larger than the input. The engine raised 2 warnings, listed below.
Input · sample.xps · 74 KB
ZIP with 18 parts
Output · sample.zip · 85 KB
ZIP with 3 page images (sample-page-1.png … sample-page-3.png)
MuPDF (mutool)
mutool draw -r 144 -o page-%d.png document.xpsWrites one numbered PNG per page; -r sets the resolution in DPI and there is no ZIP step.
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=xps&to=png.
curl -X POST https://filetypeconverters.com/api/v1/convert \
-H "Authorization: Bearer $FTC_API_KEY" \
-F "file=@input.xps" -F "from=xps" -F "to=png" \
-F 'options={"width":0}' \
--output output.png| Key | Applies to | Type | Default |
|---|---|---|---|
| width | Writing PNG | number | 0 |
| height | Writing PNG | number | 0 |
| fit | Writing PNG | contain · cover · fill | contain |
| quality | Writing PNG | number | 90 |
| background | Writing PNG | string | #ffffff |
| stripMetadata | Writing PNG | boolean | true |
An XPS page stores each letter as a reference to an embedded font, which is tiny. A PNG stores the colour of every pixel. Dense tables at 144 DPI came to roughly 400 KB a page in our tests.
Set max_pages to 1. You get a single PNG instead of a ZIP, which is handy for attaching a receipt or a cover sheet.
Yes. Both are read by the same page renderer; our OpenXPS sample produced a 1190 × 1683 PNG of 41,922 bytes in 0.19 s, just like an .xps page of the same size.