XPS File Won't Convert? How to Diagnose and Fix It

There is an important difference between an XPS file that won't open and one that opens but won't convert. If the XPS Viewer shows the document correctly, the file itself is probably intact — but something about its content or protection is blocking the conversion step. This page covers the specific causes of conversion failure and what can be done about each.

Password protection and Microsoft IRM

XPS files can carry Microsoft Information Rights Management (IRM) restrictions that prevent printing or copying. They can also be protected by a document password, depending on how they were created.

This converter cannot bypass password protection or IRM. The XPS container is encrypted, and the converter has no way to access the content without the correct credentials. If the file is IRM-protected, it was issued by an organisation's rights-management server, and only an authorised account on that network can open or print it. Conversion will fail — this is not a bug in the tool.

If you own the document and know the password, remove the protection in the source application before re-exporting to XPS. If the file is under corporate IRM, contact the person who sent it to request an unprotected version or a PDF export from their end.

Corrupted or incomplete ZIP container

An XPS that opens in the XPS Viewer is not always fully intact. The Viewer can sometimes render an incomplete file by ignoring missing resources, but a converter that must reconstruct every page will fail when it hits a missing or malformed entry in the ZIP.

Signs that the container is the problem:

• Conversion starts but stops partway through — particularly on a specific page.
• The output PDF is shorter than expected (e.g. a 20-page XPS produces a 12-page PDF).
• The error message mentions a parsing failure or unexpected end of file.

The fix is to obtain a clean copy of the file. Re-download it if it came via the internet, or ask the sender to resend. If you created it, re-export from the source document.

Wrong or misleading file extension

A file named .xps is not necessarily a valid XPS document. Some workflows accidentally produce files with the wrong extension — for example, a PDF renamed to .xps or an incomplete export where the tool wrote a partial file and named it incorrectly.

You can confirm what the file actually is by renaming it to .zip and trying to open it in Windows Explorer. A valid XPS or OXPS file will open as a folder containing a _rels folder, a Documents folder, and a [Content_Types].xml file. If the rename produces an invalid archive or something unexpected, the file is not a proper XPS regardless of its extension.

Similarly, an .oxps file uploaded as .xps will usually convert correctly since both use the same OPC container — but if you renamed a genuine OXPS to avoid an extension problem elsewhere, the original extension is worth restoring.

Unsupported or unusual content

Most XPS files are produced by the Microsoft XPS Document Writer virtual printer, which creates straightforward documents. Occasionally, specialist publishing tools produce XPS with non-standard XAML constructs or unusual colour profiles that a converter cannot handle.

If the document displays perfectly in the XPS Viewer but conversion consistently fails with no obvious cause, the content may contain something outside the converter's supported subset. In that case, the best alternative route is to open the file in the XPS Viewer on Windows and use File → Print → Microsoft Print to PDF to create a PDF offline. This uses Windows' own rendering engine and will handle whatever the Viewer can handle.

Transient error or timeout — try again

Conversion involves uploading the file, unpacking the XPS container, rendering each page, and assembling the output. On a slow connection or if the server is under momentary load, this pipeline can time out for large files. The error in this case is not permanent.

Wait a minute and try again. If the file is large (approaching 25 MB), check that the upload completed fully before conversion started — a partial upload will always fail. A stable broadband or wired connection is more reliable than a weak mobile signal for large uploads.

Frequently asked questions

Can XPS2PDF.co.uk remove IRM or password protection to convert the file?

No. The converter cannot bypass Microsoft IRM or document password protection. The encryption prevents any tool from accessing the content without valid credentials. You will need an unprotected copy of the file.

My XPS opens in the XPS Viewer but won't convert — is the file damaged?

Possibly. The XPS Viewer tolerates minor damage and can display incomplete files by skipping missing resources. A converter is stricter. Try re-downloading or re-exporting the file from its source application and converting again.

How do I check whether my XPS is actually a valid XPS file?

Rename it to .zip and open it in Windows Explorer. A valid XPS is a ZIP archive containing a _rels folder, a Documents folder, and [Content_Types].xml at the root. If the archive is invalid or the structure is wrong, the file is not a proper XPS.

The conversion fails on page 15 of 30 — what does that mean?

This usually indicates a corrupted or missing resource partway through the file — an image, font, or page entry that is truncated in the ZIP. Re-exporting from the source application is the cleanest fix. If that is not possible, printing pages 1–14 and 15–30 as separate XPS files and converting each may work around the damaged section.

Could the file format be OXPS rather than XPS — does that matter for conversion?

This converter accepts both .xps and .oxps. The two formats use the same OPC container structure, so the extension itself is not the problem. If an OXPS consistently fails to convert, the cause lies elsewhere — check for corruption or protection.

Is there an offline way to convert an XPS that won't go through an online converter?

Yes. On Windows, open the file in the XPS Viewer, then File → Print → Microsoft Print to PDF. This is a built-in virtual printer on Windows 10 and 11 that produces a PDF without any third-party software.

Last updated: June 2026