Tiny Online Tools logoTiny Online ToolssearchSearch tools…grid_viewAll Tools
Homechevron_rightDocument Toolschevron_rightXPS / OXPS ViewerXPS / OXPS Viewer

XPS / OXPS Viewer

Open Microsoft's XPS and OXPS fixed-layout documents and read them page by page, with no Windows components needed.

upload_file

Click to browse or drag & drop files here

XPS or OXPS

Accepted: .xps,.oxps

Similar Tools

XPS Converter

XPS Converter

Convert XPS and OXPS documents to PDF, SVG, PNG or JPEG, with page ranges, resolution and background control.

CHM Viewer

CHM Viewer

Open a legacy Microsoft Compiled HTML Help file, browse its contents tree and read its pages in your browser.

Email File Viewer

Email File Viewer

Open EML and Outlook MSG files in your browser — headers, rendered body, MIME structure and attachments, with no mail client installed.

MHTML / MHT Viewer

MHTML / MHT Viewer

Open a web page archived as a single MHT or MHTML file and see it rendered with its own images and stylesheets.

3D Texture Optimizer

3D Texture Optimizer

Resize, convert and compress the textures embedded in GLB, GLTF, FBX and USDZ models, free and entirely in your browser.

PDF Metadata Editor

PDF Metadata Editor

View and edit PDF metadata including title, author, subject, keywords, and creator.

Convert AVIF to PNG

Convert AVIF to PNG

Convert modern AVIF images to lossless PNG format directly in your browser.

apps

More Tools

Browse our full collection of free online tools.

Why XPS files are hard to open

XPS was Microsoft's answer to PDF. The XPS Viewer shipped with Windows for years and was then removed; on macOS and Linux it never existed at all. So a perfectly ordinary document ends up unopenable on the machine in front of you.

An XPS file is not a mystery, though. It is an Open Packaging Convention ZIP — the same container as a .docx — whose pages are FixedPage XML, a small subset of XAML. That subset maps onto SVG almost one element at a time, which is why a browser can draw it:

  • FixedPage becomes an <svg> with a viewBox in units of 1/96 inch
  • Canvas becomes a <g>, carrying its transform and opacity
  • Path.Data becomes <path d="…"> after translating XAML's geometry syntax and its F0/F1 fill rules
  • Glyphs becomes <text> positioned at its baseline origin
  • an ImageBrush becomes <image> with the picture inlined from the package

OXPS is the ISO-standardised version of the same thing. Both open here.

Page order comes from the package, not the filenames

Pages are found by following the FixedDocumentSequence to its FixedDocuments and then to each PageContent, exactly as a real reader does. Sorting .fpage files by name gives the wrong order the moment a document has ten pages or has ever been rearranged.

What it will and will not draw

Every page reports what the renderer produced: how many paths, glyph runs, images and canvases it emitted, and how many elements it had no mapping for. If that last number is not zero, the page is not complete, and it says so on the page rather than in a footnote. Renderer warnings — a missing image part, a font part that is not in the package — are listed too.

One limitation is worth stating plainly. XPS supplies per-glyph advances in each text run's Indices attribute; honouring them exactly needs the font's own metrics. Instead each run is placed at its baseline origin and the browser lays the string out. Ordinary text is right; heavily kerned or justified runs can drift by a fraction of a character.

Also here

The document's title, author and dates from its core properties, its package structure, the list of embedded images and fonts, page navigation with thumbnails, zoom, and a per-page SVG download. To get PDFs or PNGs, use the XPS Converter.

Privacy

The document is opened in your browser. Nothing is uploaded.