Convert XSN to PDF — the way that actually works
The obvious route — open the form in InfoPath, print to PDF — dies with InfoPath itself, and generic converter sites choke on .xsn files because a .xsn isn’t a document at all. Yet auditors and records requests still expect to see each form the way it looked when it was signed off.
To convert XSN to PDF, render each submitted .xml record through the .xsn template’s own view stylesheets, then print the rendered output. The openxsn tool does this for an entire form library at once, in your browser, producing one searchable PDF with one record per page — nothing uploads.
Below: the three-step batch process, what lands in the PDF, and why it stays searchable.
How to convert InfoPath forms to PDF
- Open the tool and drop in your .xsn template. (Don’t have it? Here’s where the .xsn lives and how to open it.)
- Add the submitted .xml records — one or one thousand. The first three render free so you can check fidelity against what InfoPath used to show.
- Click Print all to PDF. Every record renders through the form’s own stylesheets into one searchable PDF, one record per page. The ZIP export adds a self-contained HTML file per record and an Excel extract of every field.
What the searchable PDF contains
One record per page, laid out by the form’s original view — the tables, section headings, and labels its designer built, so a 2014 inspection report still reads like a 2014 inspection report. Because the rendered form is real HTML text, the browser’s print engine writes genuine selectable text into the PDF: every field can be found with Ctrl-F, copied out, or indexed by a document-management system. No OCR, no screenshots, no image-only pages.
That searchability is the point of the exercise. Retention rules, eDiscovery requests, and public-records obligations don’t just require you to have the record — someone has to be able to find it by its contents years from now, without knowing which file it’s in. Need individual files rather than one big PDF? The same unlock’s ZIP export covers that: each record as a standalone HTML document, plus the full data tables.
Why this beats re-typing or screenshots
Microsoft’s retirement guidance covers migrating live forms to Power Apps — it ships nothing for the archive of already-submitted records. Making those readable is left to you, and the practical answer is exactly this: render each record and convert it to searchable PDF. Screenshotting forms loses searchability; re-typing loses your weekend. Rendering through the original view stylesheets keeps the layout auditors recognize and the text searchable, and the one-time $39 unlock covers as many libraries as you have. Deadline context, if you need to make the case internally: what stops working on July 14, 2026.
Batch-convert your forms now. Free previews first — pay only when you’ve seen your own forms render.
Convert XSN to PDFQuestions
Why do generic PDF converter sites fail on .xsn files?
Because a .xsn isn’t a document — it’s a template archive. There is nothing in it to “convert” until a submitted .xml record is rendered through its view stylesheets. Generic converters don’t know the InfoPath format, so they error out or produce an empty page. This tool renders the record through the form’s own views first, then makes the PDF.
Are the PDFs searchable, or just images?
Searchable. The rendered form is real HTML text, and your browser’s print engine writes it into the PDF as text. You can select, copy, and index every field — no OCR, no screenshots.
Can I convert hundreds of InfoPath forms to PDF at once?
Yes — batch is the default. Drop the whole set of .xml records; the combined export renders every one through the template and produces a single searchable PDF, one record per page, plus per-record HTML files in the ZIP if you need them individually.
Do I need SharePoint access to convert the forms?
No — only the files. If the .xsn template and .xml records are already downloaded (or on a network share), the conversion runs entirely from those, which also means it keeps working after your SharePoint access or the site itself is gone.