How to open InfoPath forms without InfoPath

Updated 11 October 2026

Microsoft removed InfoPath Forms Services from SharePoint Online after 14 July 2026, and support for InfoPath 2013, the last desktop version, ended the same day. Without InfoPath, an old form in a library is a file nothing opens the way it used to. The good news: the data is still there. A filled-in InfoPath form is an ordinary XML file, and its template is an ordinary cabinet archive. This guide shows the free ways to read them, from the quickest to the most complete, and what each one leaves out.

What you actually have

  • Filled-in forms: .xml files. Each one holds the values someone typed, plus attachments and pictures encoded as text. The first lines contain a <?mso-infoPathSolution … href="…/template.xsn"?> instruction that points to the template.
  • The template: one .xsn file. It holds the layout (views), the field definitions and the print settings. In a SharePoint form library it is normally Forms/template.xsn; a form that was emailed or saved locally usually points to its template in that href.

To see a form the way people filled it in, you need both: the data from the .xml and the layout from the .xsn. Keep the template together with the forms when you copy an archive.

Method 1: read the raw XML (one minute, no layout)

Open the .xml file in Notepad, VS Code or any web browser. You will see every field as an XML element, for example <my:requestDate>2026-03-02</my:requestDate>. This is enough to look up one value in one form.

What you don't get: the form layout, the labels people saw (fields are named by the form designer, such as my:field14), readable attachments (they appear as long blocks of base64 text) and anything you could print or hand to an auditor.

Method 2: unpack the template and apply its view (free, works for many simple forms)

An .xsn file is a Microsoft cabinet (CAB) archive. Windows can unpack it with the built-in expand command, with nothing to install. In Command Prompt:

mkdir C:\Archive\template
expand C:\Archive\template.xsn -F:* C:\Archive\template

Inside you will usually find manifest.xsf (the template definition), myschema.xsd (the fields), template.xml (an empty form) and one view1.xsl, view2.xsl… for each view. A view is an XSLT stylesheet, so you can apply it to a filled-in form with PowerShell, which also comes with Windows:

$xslt = New-Object System.Xml.Xsl.XslCompiledTransform
$settings = New-Object System.Xml.Xsl.XsltSettings($true, $false)
$xslt.Load("C:\Archive\template\view1.xsl", $settings, (New-Object System.Xml.XmlUrlResolver))
$xslt.Transform("C:\Archive\Forms\form1.xml", "C:\Archive\form1.html")

Open form1.html in a browser. In our test with 30 publicly available InfoPath templates and sample data, this produced an HTML page for 27 of them. For the other 3, PowerShell stopped with an error saying it cannot find a script or an extension object for an InfoPath namespace: their views call InfoPath's own XSLT functions (formatting, secondary data), which exist only inside InfoPath.

Know the limits before you rely on it. The result is the on-screen view with input boxes, the form's buttons and broken calendar icons, not the print layout. Drop-down fields can appear empty even when the form has a value, and pictures stored in the template or number and date formatting may be missing. Attachments are not extracted. Only apply views from templates you trust: with these settings a view can read other files the stylesheet points to. It is one form at a time unless you script a loop.

Method 3: an old InfoPath installation

If a PC in your organisation still has InfoPath Filler or Designer 2013 installed, it should still be able to open a local .xml form when the template is reachable, and print it. This is the most faithful option for a handful of forms. It is also unsupported software, and opening and printing forms one by one is slow work once there are more than a few dozen. If you don't have it, see whether InfoPath 2013 can still be downloaded.

When you have hundreds or thousands of forms

Records you have to keep usually need three things the free methods don't give you in one go: a PDF that looks like the original form, the data in a spreadsheet, and the attachments as real files. That is the job XSN Archive Viewer was built for. Point it at a folder of forms and their template, and it writes a PDF per form using the form's own print view, CSV files with the data and repeating tables, and every attachment with its original file name, plus a report of anything it could not convert. It runs on Windows. Conversion runs on your PC; your forms are never uploaded.

Related: convert InfoPath XML forms to PDF · extract attachments from InfoPath forms.

Quick answers

Can I open an .xsn file without InfoPath?

Yes, as an archive: expand template.xsn -F:* folder unpacks it. You can read the views and the schema, but an .xsn on its own is an empty form. The records are in the .xml files.

Is there a free InfoPath viewer from Microsoft?

No. Microsoft never shipped a free stand-alone InfoPath viewer. Outside SharePoint's browser forms, filling in or opening a form needed InfoPath installed. The free options today are the methods above.

Can I open InfoPath forms in Word or Excel?

Not in the original layout. Excel can import the XML data of a form as a table, without the layout or the attachments: see how to export InfoPath form data to Excel.

Is the data lost if I delete the form library?

It can be. Once the library is deleted and the recycle bins are emptied, the .xml files, which are the records, are gone unless a backup or retention policy kept them. Download them, together with Forms/template.xsn, before a library is cleaned up.