SumatraPDF XPS or OXPS Not Opening: How to Fix It

When an XPS or OXPS document does not open in SumatraPDF, opens in another Windows app, displays a blank page, or renders incorrectly, the cause usually falls into one of four categories: Windows is sending the file to the wrong application, the document is damaged or mislabeled, the page is unusually complex, or a persistent SumatraPDF setting is interfering. The quickest solution is to isolate those possibilities in order. This guide focuses specifically on XPS-family documents, including files with .xps and .oxps extensions, rather than unrelated PDF or eBook problems.

1. Confirm the Symptom With One Simple Test

Before changing settings or reinstalling anything, determine whether the problem follows one document or affects every XPS-family file. This distinction prevents unnecessary changes to an installation that may already be working correctly.

1.1 Test a second known-good XPS document

Open SumatraPDF first, and then use its file-opening command to select a different .xps or .oxps document. Choose a small file from a trusted source, ideally one you created locally. If necessary, print a short text document to an available XPS printer, and then try opening the resulting file.

Interpret the result as follows:

• If the second document opens normally, SumatraPDF's XPS reader is functioning. The original file is probably damaged, incomplete, unusually complex, or not actually an XPS-family document.
• If no XPS or OXPS document opens, investigate the application, Windows association, and saved settings.
• If documents open from inside SumatraPDF but not when double-clicked, the problem is probably the Windows file association rather than document rendering.
• If a document opens but pages are blank, incomplete, or distorted, focus on file integrity and rendering complexity.

Success at this stage means at least one known-good XPS or OXPS file displays readable pages. Once that happens, stop making global application changes and troubleshoot the failing document itself.

1.2 Identify the exact failure behavior

Write down what actually happens. Useful distinctions include whether SumatraPDF shows an error, opens an empty window, becomes slow, displays only some pages, or never starts because Windows launches another program. These symptoms point to different fixes.

A slow response is not always a failed open. XPS documents can contain many fixed-position elements, embedded fonts, high-resolution images, transparency, and complex print output. A large or intricate document may require more time and memory than a simple text file. Allow a reasonable amount of time once, while watching whether SumatraPDF remains responsive, before concluding that loading has failed.

2. Check the File Format and Windows Association

The standard filename extensions to test directly are .xps for XML Paper Specification documents and .oxps for OpenXPS documents. A filename alone does not prove that its contents use the expected format. Files can be renamed incorrectly, downloaded as error pages, or saved incompletely.

2.1 Verify the complete filename extension

In Windows File Explorer, enable the display of filename extensions. On current Windows versions, this option is available from the View menu under Show. Confirm that the file ends in .xps or .oxps, not something such as .xps.pdf, .oxps.zip, or .xps.html.

A file with an .xod extension should not automatically be treated as a standard XPS or OXPS document. That extension can be used by other products or workflows. Ask the sender which application created it, or inspect it with the originating software. Do not simply rename an unknown file to .xps. Renaming changes only the label, not the underlying format.

Success means the extension and the source application's stated export format agree. If they do not, obtain a new export in XPS, OXPS, or PDF format rather than repeatedly changing the filename.

2.2 Open the document from inside SumatraPDF

Start SumatraPDF directly, choose the command to open a file, and browse to the document. This bypasses the Windows double-click association and tests whether SumatraPDF itself can read the file.

If the file opens this way, the reader is working. Stop changing SumatraPDF settings and repair the Windows association instead. Reinstalling the reader or modifying rendering options will not fix an association problem.

2.3 Set the correct Windows file association

Right-click the XPS or OXPS file, select Open with, and choose SumatraPDF. If Windows presents an option to always use that application for the file type, select it. You can also open Windows Settings, go to the default-app controls, and assign an application by the .xps or .oxps extension.

Windows manages associations separately for different extensions. Associating .xps with SumatraPDF does not necessarily associate .oxps with it. Check both if you use both formats.

Success means double-clicking the document launches SumatraPDF and displays the same content that appears when the file is opened from inside the program. Once both opening methods work, no further association changes are required.

3. Check the Source Document and Rendering Load

If one file fails while another XPS-family file works, the source document deserves attention. XPS is a fixed-layout print format, so problems introduced during printing or export can be preserved inside the output file.

3.1 Replace incomplete or corrupt files

Check whether the file has a plausible size. A zero-byte file, an unusually tiny attachment, or a download that ended early cannot be repaired through a SumatraPDF preference. Download the document again, copy it again from the original drive, or ask the sender to resend it.

If the document came from email, save it to a normal local folder before opening it. Do not rely on a temporary attachment preview. For files from cloud storage, confirm that the complete file is available locally rather than represented by an online-only placeholder.

Success means a fresh copy opens while the old copy does not. In that case, delete or clearly label the damaged copy and stop changing the reader.

3.2 Recreate corrupt print-to-XPS output

A document produced through a print-to-XPS workflow can be defective even when the source document appears normal. Reopen the source in the application that created it, simplify the print job if necessary, and produce a new XPS file with a different filename.

For a useful diagnostic test, print only one or two simple pages first. If the short output opens, create the full document. If the full document fails, try dividing it into smaller page ranges or removing a page containing an unusually large image, custom font, transparency effect, or complex drawing.

Success means the newly generated XPS file opens and renders all expected pages. Keep the regenerated file and avoid spending time trying to repair the malformed output through SumatraPDF.

3.3 Allow for large or complex XPS pages

Very large engineering drawings, image-heavy scans, detailed charts, and print jobs containing thousands of positioned elements can render slowly. Copy the file to a fast local drive, close memory-intensive applications, and test it again. Avoid repeatedly double-clicking the file because that can start multiple loading attempts.

If only a specific page causes trouble, recreate that page from the source application or split the document around it. If the file eventually displays correctly after a longer load, the issue is performance rather than an unsupported extension or broken association.

3.4 Know when PDF conversion is practical

Converting the document to PDF can be a sensible workaround when you control the source, need broad compatibility, or cannot obtain reliable XPS output. The safest method is to export or print to PDF from the original application. This avoids depending on a damaged XPS file as the conversion source.

If only the XPS file remains, use a trusted application that can open it correctly and save or print a PDF copy. Check the PDF visually before relying on it, especially for forms, precise page dimensions, searchable text, fonts, or technical drawings. Do not use conversion to bypass permissions, DRM, or document restrictions.

Success means the PDF preserves the pages and information you need. Conversion is a workaround, not proof that the original XPS file was valid.

4. Check Windows and Installation-Specific Factors

XPS opening normally does not require Ghostscript, a printer driver, or a media codec merely to display an existing XPS file in SumatraPDF. Those components matter only when a separate creation, printing, or conversion workflow depends on them. Installing unrelated codecs or Ghostscript is therefore not a sensible first response to a failed XPS open.

4.1 Test from a local folder with normal permissions

Copy the document to a folder you can write to, such as a temporary folder inside your user profile. Use a short, ordinary filename for the test. This helps distinguish document-reading problems from unavailable network locations, cloud placeholders, removable-drive errors, or restrictive folder permissions.

If Windows displays an Unblock option in the file's Properties dialog for a trusted downloaded file, review the file's origin before using it. Only unblock a document when you trust its source. SumatraPDF is a reader, not a guarantee that every downloaded document is safe.

Success means the local copy opens correctly. If so, keep SumatraPDF unchanged and address access, synchronization, or connectivity on the original storage location.

4.2 Compare installed and portable operation

SumatraPDF is available in installed and portable forms. A portable copy can provide a clean comparison without immediately altering the installed setup. Download it only from the official SumatraPDF site, extract it to a new folder, start it directly, and open the same known-good test document.

If the portable copy opens the file but the installed copy does not, the document and general format support are probably fine. The likely difference is saved configuration, an older or damaged program copy, or the way Windows launches the installed application.

If neither copy opens the known-good file, return to the file-format and source-document checks. Do not assume that reinstalling repeatedly will repair a malformed document.

4.3 Separate viewing from printing problems

If the XPS document displays correctly but fails when printed, opening has already succeeded. Troubleshoot the selected printer, its driver, print queue, paper settings, and spooler separately. Update or reinstall a printer driver only when the symptom occurs during printing, not merely because an XPS file will not open.

Likewise, Ghostscript can be relevant to certain PostScript workflows, but it is not a general repair tool for an existing XPS or OXPS document. Media codecs are also unrelated to fixed-layout XPS page rendering in this scenario.

5. Inspect or Reset SumatraPDF-settings.txt Safely

SumatraPDF stores persistent preferences in a text settings file named SumatraPDF-settings.txt. Its location can differ between installed and portable use. Before editing or resetting it, close every SumatraPDF window so the application does not overwrite your changes when it exits.

5.1 Back up the settings file first

Find the settings file associated with the exact SumatraPDF executable you are testing. Portable operation may keep configuration near the executable, while an installed copy commonly uses the user's application-data area. If you are uncertain, use Windows search and compare modification times after changing a harmless preference.

Copy the file to a backup name such as SumatraPDF-settings-backup.txt. Do not delete it immediately. The backup preserves preferences such as view behavior, history, and other customized options.

5.2 Reset by renaming rather than editing random entries

With SumatraPDF closed, rename SumatraPDF-settings.txt to a temporary name. Start SumatraPDF again so it can create or use clean defaults, and then open a known-good XPS file.

• If the file now opens, a persistent setting or damaged settings file was involved.
• If the file still fails, restore the backup if you want your previous preferences back.
• If only the original document fails, the settings file was probably not the cause.

Avoid copying the entire old settings file over the clean one immediately. Reapply only the preferences you need, testing the XPS document after meaningful changes. This makes it easier to identify whether a specific preference triggers the symptom.

Success means XPS and OXPS files open consistently with clean settings. At that point, stop resetting files and rebuild only necessary preferences.

6. Run a Clean Temporary Test Before Reinstalling

A clean test is more informative than an immediate reinstall because uninstallers may leave user settings in place. It also separates the application executable from Windows associations and saved preferences.

1. Close all SumatraPDF windows.
2. Download a current official portable build from the SumatraPDF website.
3. Extract it into a new empty folder.
4. Use a small, known-good .xps or .oxps file stored locally.
5. Launch the portable executable first, and then open the test file from inside it.
6. Compare the result with the installed copy and the original problem document.

If the clean portable build works, repair or update the installed copy, reset its settings carefully, or continue using the portable copy if that suits your workflow. If the portable build fails only with one document, replace or recreate that document. If it fails with multiple verified files, record the exact error and report the issue through the official SumatraPDF support channels with non-confidential sample details.

Reinstall only after this comparison indicates that the installed program files are the likely cause. A reinstall is successful when the same known-good XPS file opens from inside the program and by double-clicking it in Explorer.

7. Quick Fix Checklist

• Confirm the file uses the .xps or .oxps extension.
• Make sure the extension matches the format created by the source application.
• Open the file from inside SumatraPDF to bypass Windows associations.
• Test a second, small, known-good XPS document.
• Set separate Windows associations for XPS and OXPS if needed.
• Save email or cloud files completely to a local folder.
• Recreate suspicious print-to-XPS output from the original source.
• Allow extra loading time for image-heavy or highly complex pages.
• Test an official portable SumatraPDF copy in a clean folder.
• Back up and temporarily rename SumatraPDF-settings.txt.
• Convert from the original source to PDF when compatibility matters more than XPS.
• Stop changing settings as soon as a known-good document opens consistently.

8. Frequently Asked Questions

8.1 Does SumatraPDF support XPS and OXPS files?

SumatraPDF lists XPS among its supported document formats, and its XPS-family handling is intended for files such as .xps and .oxps. Support for an extension does not guarantee that every generated document will render correctly. Individual files can still be malformed, incomplete, mislabeled, or too complex for trouble-free processing.

8.2 Why does an XPS file open in another app instead?

Windows controls which application handles a file when you double-click it. If SumatraPDF can open the file through its own open command, change the default app for the relevant extension. Remember that XPS and OXPS associations may need to be configured separately.

8.3 Why does one XPS file fail while others work?

That usually points to the document rather than SumatraPDF. Download or copy it again, verify its size and extension, and recreate it from the source application if possible. Print-generated XPS files can contain malformed or unusually complex page content even when other documents from the same computer work.

8.4 Will installing Ghostscript or a codec fix XPS opening?

Usually not. Ghostscript is associated with PostScript-related workflows, while media codecs handle audio or video formats. Neither is a general requirement for opening an existing XPS or OXPS document in SumatraPDF. Investigate those tools only when a separate conversion or creation process explicitly requires them.

8.5 Should I rename an XOD file to XPS?

Not unless you have verified that the file is truly an XPS document with the wrong extension. An XOD file may belong to another product or document workflow. Ask the sender for a standard XPS, OXPS, or PDF export. Blindly renaming it does not convert its contents.

8.6 When should I convert the document to PDF?

Use PDF as a practical workaround when you can export from the original application, need easier sharing, or have a valid XPS file that another trusted viewer can render correctly. Verify the converted pages, fonts, dimensions, and searchable text. If the XPS is corrupt, obtain a fresh source or regenerate it rather than expecting conversion to repair missing information.