Convert the First XPS Page to JPG

How it works

XPS describes a page as positioned drawing operations stored in an XML package. Instead of asking an office application to reconstruct that layout, the server uses xpstojpeg from libgxps. The renderer opens the package, follows each page's font, path, brush, image, and coordinate references, and paints the pages at the default 150 PPI onto white image surfaces. The worker keeps page one and encodes that surface as JPEG.

The command-line utility's normal multi-page behavior is worth making explicit. It writes numbered outputs such as xps-page.jpeg-1.jpeg and xps-page.jpeg-2.jpeg, rather than a single multi-page JPG, because JPG has no page container. The worker looks for the first numbered output, moves it to the requested result path, and checks the JPEG signature before making the download available. This is a deliberate first-page contract, not an accidental omission of the rest of the document.

What changes in the handoff

The original XPS can preserve exact coordinates and keep text as text. The JPG cannot. Every visible ingredient is composited into a rectangular pixel grid: letters become colored samples, vector rules become sampled edges, and embedded photographs become part of the same picture. A recipient can open the result in a browser or attach it to a form, but cannot select a sentence or inspect a vector path from the image itself.

JPEG also trades some information for a smaller file. Its compression is usually a good decision for a page with photographs or a simple preview, but high-contrast small type and thin lines are the places where artifacts show first. The output uses the renderer's ordinary white background and keeps the page geometry; it does not crop margins, OCR the text, sharpen a scan, or repair a source with missing fonts. What is visible in the first rendered page is what the JPG carries.

Why the first page is the safe server choice

Rendering a whole XPS manual at 150 PPI could produce dozens of separate images and a much larger download than the input. It would also make the output contract awkward: a browser would need a ZIP, while a single download link could hide the fact that pages were omitted or renamed. Returning only page one is predictable and useful for cover cards, receipts, title pages, and image-only upload fields.

The limitation affects selection as well as count. Uploading a 12-page document with the relevant content on page 7 still returns page 1. Prepare a one-page source first if the later page is required. If the recipient needs the entire document, use XPS to PDF instead; PDF is designed to retain multiple pages in one portable file, while JPG is best understood as a single-page visual derivative.

JPG or PNG for the same page

Choose JPG when compatibility and modest download size are the priority, especially for photographic pages or an upload field with a strict size limit. Choose PNG when the page is mostly line art, diagrams, or small text and lossless edges matter more than the file size. Both routes here render only page one at 150 PPI on the server. Neither replaces the XPS for searchable text, signatures, or future edits, so keep the source alongside whichever image you send.

If you wanted the whole document

This gives you the first page as an image, because one image file holds one picture. That is the right answer for a thumbnail, a slide or a bug report, and the wrong one for almost everything else.

To read the document — every page, with the text still searchable — use the XPS viewer; nothing is installed and it works on a Mac or a phone. To keep or send it, convert it to PDF: every page comes across, the layout is identical, and PDF opens everywhere without a viewer. XPS to PNG is the same first-page image in the other format.