Free XPS to PDF Converter Online – No Registration, No Watermark

What Is an XPS File? A Brief Format History

XPS stands for XML Paper Specification — a fixed-layout document format Microsoft introduced alongside Windows Vista in November 2006. The format was Microsoft's answer to Adobe's PDF: a way to share documents that look identical on any compliant viewer, regardless of the printer, screen, or operating system rendering them.

Under the hood, an .xps file is a ZIP archive containing XAML (eXtensible Application Markup Language) for the document content, an Open Packaging Conventions (OPC) manifest, and embedded resources — fonts, images, and any other assets the document needs to render. The OPC container is the same packaging scheme Microsoft uses for Office Open XML formats like .docx and .xlsx.

Microsoft shipped XPS with three things in Windows Vista:

• XPS Document Writer — a virtual printer driver that produced an .xps file from any Print dialog
• XPS Viewer — a bundled application for reading .xps documents
• Save as XPS — built into Office 2007 onwards as an export option alongside Save as PDF

In 2009, ECMA International ratified OpenXPS (ECMA-388) as an open standard variant of XPS. Files following this newer specification use the .oxps extension. Windows 8 and later create .oxps files by default when you print to XPS Document Writer, although Windows still reads both formats. See our OXPS vs XPS comparison for the full breakdown.

Despite shipping in every version of Windows since Vista, XPS never gained meaningful traction outside the Windows print pipeline. By 2017 Microsoft started removing it from default installations: the XPS Viewer became an Optional Feature in Windows 10 version 1709 (the Fall Creators Update, October 2017), and Windows 11 ships without any XPS viewer at all. You can still install it under Settings → Apps → Optional Features → "XPS Viewer", but it's no longer a default capability of the operating system.

Today XPS files turn up in three common situations: documents printed to XPS from older Windows machines, scanner software that defaults to XPS output, and enterprise document-management systems that adopted the format internally. Outside those contexts the format is essentially defunct — which is why most people who receive an XPS file want to convert it to PDF.

XPS vs PDF: Practical Differences You'll Hit

Both XPS and PDF are fixed-layout document formats, meaning a page in either format looks identical on any viewer, on any device, regardless of the printer or screen rendering it. From a user perspective the formats are interchangeable; from a practical perspective PDF wins on almost every axis except first-party Windows integration.

The differences that matter day to day:

• Native support. PDF opens natively on Mac (Preview), iOS, Android, Chrome OS, Linux (Evince, Okular), and every modern browser. XPS opens natively on no operating system that isn't Windows — and on Windows 10/11 you have to install the viewer manually.
• File size. PDFs are typically 20–50% smaller than the equivalent XPS, because PDF's compression is more efficient than XPS's ZIP packaging. A 12 MB XPS scan often produces a 6–8 MB PDF after conversion.
• Software ecosystem. Adobe Acrobat, Foxit, Preview, Nitro, Smallpdf, ILovePDF — the PDF tooling ecosystem dwarfs XPS by orders of magnitude. If you want to redact, merge, split, sign, or compress a document, every tool you can name supports PDF; almost none of them open XPS.
• Web friendliness. Almost every web form, content management system, e-commerce platform, and HR portal that accepts document uploads supports PDF. XPS uploads are widely rejected — by Workday, Greenhouse, most LMS platforms, most government e-services, and most CRM document-attachment fields.
• Long-term readability. PDF is an ISO standard (ISO 32000) maintained by an active committee. XPS is technically still an ECMA standard (388) but Microsoft has stopped investing in viewers — relying on a defunct format is a long-term readability risk.

For a deeper side-by-side comparison including technical compression, font handling, and DRM differences, see our dedicated XPS vs PDF page.

XPS Compatibility by Platform

Different platforms handle XPS differently, and the gap is wider than most people expect:

Windows 10 and 11. XPS Viewer was a default install through Windows 10 v1703 (Creators Update). From v1709 onwards it's an Optional Feature you have to enable: Settings → Apps → Optional Features → Add a feature → search "XPS Viewer". Windows 11 keeps the same opt-in approach. Once installed you can double-click an .xps or .oxps file and read it natively. Note that the XPS Viewer hasn't received feature updates in years — it lacks modern accessibility features, annotation tools, and updated print previewing.

macOS. No native XPS support on any version of macOS. Apple's Preview application doesn't read XPS. The Quick Look extension architecture has no XPS plugin shipping by default. You have three options: (1) convert the file to PDF first using a service like this one, (2) install a third-party reader from the Mac App Store, or (3) use LibreOffice, which can open XPS read-only since version 4.4 (2015). See our open XPS on Mac guide for the practical steps.

iOS and iPadOS. No native XPS support. The Files app doesn't recognise the format, and no Apple application can render it. The Mail app shows .xps attachments as generic file icons with no preview. Conversion is the only practical option for reading XPS content on an iPhone or iPad.

Android. Same picture as iOS. No system-level XPS reader; Google's Files app and the default Gmail viewer both show .xps as generic attachments. Some third-party viewers exist on the Play Store, but most are wrappers around an upload-and-convert service rather than native renderers. Converting to PDF first is faster and more reliable.

Linux. No first-party support, but the open-source libgxps library powers XPS rendering in Evince (GNOME Document Viewer) and Okular (KDE). On Debian/Ubuntu, sudo apt install libgxps2 adds XPS support to Evince. The gxps-tools package includes xpstopdf which converts at the command line. Chromebooks running Crostini can install the same packages.

Chrome OS (non-Crostini). The Files app doesn't read XPS, and Chrome's built-in document viewer doesn't either. Converting to PDF before opening is the standard workflow.

Microsoft Office. Word, Excel, and PowerPoint don't open XPS files. They can write XPS via Save As, but they can't read one back. Don't try to open an XPS file with Word — you'll get a "file is corrupted" error.

Adobe Acrobat Reader and Pro. Neither version opens XPS. Adobe positioned PDF against XPS at launch and has never added support. The Open dialog filters .xps out of its supported file types entirely.

LibreOffice 4.4+. Read-only support since 2015. You can open the file, view it, and export it to PDF from File → Export As, but you can't edit XPS content in place. This is the closest thing to a free cross-platform XPS reader, but it's heavyweight (LibreOffice is around 300 MB installed) if XPS is the only reason you'd install it.

If your only goal is to read or share the document, converting to PDF — like this site does — is the simplest path across every platform listed above except Windows.

What Happens to Your XPS File During Conversion

When you upload a file to XPS2PDF.co.uk, the conversion pipeline runs through five steps:

1. Upload over HTTPS. Your browser sends the file to our server using TLS 1.2 or TLS 1.3 — the same encrypted transport that protects online banking. Files in transit are never readable by anyone intercepting network traffic.
2. Server-side validation. We check the file is genuinely an XPS or OXPS document by inspecting its OPC container structure, not just its file extension. Files that don't match the format are rejected immediately and never stored.
3. Rendering to PDF or JPG. A headless renderer parses the XPS document's XAML content, embedded fonts, and image resources, then emits a PDF (preserving vector content and selectable text) or JPG (one image per page). The conversion runs entirely on our infrastructure; no third party sees the document.
4. Temporary storage on the server. Converted files are written to a per-session directory so you can download them. The directory is tied to your browser session via a random session ID; no other user can see or guess your files.
5. Automatic deletion within 60 minutes. A cron job sweeps the server every few minutes and removes any converted file older than the 60-minute window. Source XPS files are deleted as soon as conversion completes — they don't survive past the request.

We don't keep logs of file contents, file names, or document text. The only data we retain is anonymous usage telemetry: which conversions succeed, which fail, average file size, and average conversion time. None of that telemetry is linkable to a specific user.

If your XPS contains sensitive content — invoices, scanned passports, medical records — the file is gone from our servers within an hour, and was only ever accessible to the automated conversion process.

Common XPS Conversion Issues and Fixes

A small percentage of XPS files won't convert cleanly. Here are the issues we see most often and how to work around them:

"File appears corrupted" error. XPS is a ZIP archive. If the archive is incomplete (truncated download, interrupted save, partial email attachment) the file will pass a basic extension check but fail the OPC validation step. Fix: re-download or re-export the source file. If you generated the XPS from Office, try Save As → PDF instead — Office's PDF export is usually more reliable than its XPS export.

Password-protected XPS. XPS files can carry Microsoft Information Rights Management (IRM) protection or password-based encryption. Our converter cannot bypass either — by design. If the file requires a password to open in XPS Viewer, you'll need to remove the protection there first, then upload the unprotected copy.

Fonts substituted in the PDF output. XPS files can embed fonts or reference system fonts by name. If the file references a font that isn't embedded and isn't a standard system font, our renderer substitutes a close visual match. Most users won't notice, but if you need pixel-perfect font reproduction, open the source file in its originating application and use "Print to PDF" instead of converting through XPS.

Page order looks wrong. Some scanner-generated XPS files write pages in scan order rather than page-numbered order. The converter preserves whatever order the file declares. If the output PDF has scrambled pages, the issue is in the source — not the conversion. Most PDF readers (Adobe Acrobat, Preview, Foxit) include a "Rearrange Pages" feature you can use post-conversion.

Conversion fails on files over 50 MB. Our service handles XPS files up to 50 MB per file. Larger files (typically scanned documents at 600+ DPI, or multi-hundred-page books) need to be split first. Use Windows Photos to extract individual pages, or use a desktop tool like NXPowerLite to compress before uploading.

Output PDF is much larger than the source XPS. Rare, but happens when the source XPS contains a lot of vector graphics (CAD drawings, complex diagrams) that don't compress as well in PDF. Our service uses Ghostscript-equivalent compression on the output; if you need further size reduction, run the PDF through a compression service like Smallpdf or Adobe's Compress PDF tool.

OXPS files showing extension error. Some older browsers report an extension mismatch when you try to upload .oxps. The fix is to either rename the file to .xps (it's the same OPC container so the rename is safe) or upgrade to a current browser. Chrome, Firefox, Safari, and Edge all accept .oxps directly.

Conversion stuck on "Processing". Usually a transient server load issue; refresh the page after 60 seconds. If the problem persists, try again with a different file to confirm the converter is responsive. The upload widget resets to ready state after a 120-second timeout.

OXPS vs XPS: When You'll See Each

If you have an .oxps file rather than .xps, you have the newer OpenXPS variant ratified by ECMA International in 2009 as ECMA-388. The differences are minor for end users:

• Container. Both are ZIP-based OPC packages. The internal layout is the same.
• Markup. Both use XAML-based content streams. OpenXPS slightly tightens the schema; older XPS viewers can read most OXPS files, but the reverse isn't guaranteed.
• Default Windows extension. Windows Vista, 7, and most Server editions write .xps when you print to XPS Document Writer. Windows 8 onwards writes .oxps by default. Windows 10 and 11 keep this behaviour.
• Microsoft's own viewer. Reads both formats interchangeably from Windows 7 onwards.

In practice, most users don't need to distinguish between the two. Our converter handles both equally — the file extension is checked at upload but the underlying renderer parses both ECMA-388 OXPS and Microsoft's original XPS specification. For the full technical comparison including which document features are exclusive to each format, see our OXPS vs XPS page.