PRNX File Documentation

Summary

A PRNX (DevExpress XtraReports Document) file is a saved, already-rendered report produced by DevExpress XtraReports, a .NET reporting toolkit built into business applications. It is a ZIP archive of XML plus embedded images, not a normal document, and its MIME type is application/octet-stream. No consumer app opens it: a PRNX is meant to be reloaded by the same DevExpress-based program that created it. If you were sent a .prnx, ask the sender to re-export it as PDF, Excel or RTF.

Technical details

FeatureValue
Full nameDevExpress XtraReports Document
File extension.prnx
MIME typeapplication/octet-stream
Format typeRendered report document (ZIP-based XML)
Container formatZIP archive
DeveloperDeveloper Express Inc. (DevExpress)
Part ofDevExpress .NET Reporting (XtraReports) suite
Introduced2000s (XtraReports for WinForms/WPF/ASP.NET)
Magic number (hex)50 4B 03 04 (ZIP local file header, “PK”)
ContainsRendered pages as XML + embedded images
Layout template.repx (the report design, a separate file)
Opened byDevExpress Document Viewer (WinForms/WPF)
Consumer viewer?No standalone viewer exists
Export targetsPDF, XLSX, RTF, DOCX, CSV, HTML, image, XPS, TXT
Open standardNo — proprietary application format
Related extensions.repx, .pdf, .rtf
Specificationdocs.devexpress.com/XtraReports
File signature (magic bytes)
50 4B 03 04

Offset 0, 4 bytes, ASCII PK followed by 03 04: the standard ZIP local file header. A PRNX is a ZIP archive, so it begins the same way as any .zip. Inside are the XML parts that describe the rendered pages and the images embedded in the report. You can open it with 7-Zip to inspect those parts, but that only exposes the raw XML — it does not render the report, which still needs the DevExpress Document Viewer.

What is a PRNX file?

A PRNX file is a saved report document from DevExpress XtraReports, the .NET reporting engine that software developers embed in WinForms, WPF and ASP.NET business applications. Developer Express Inc. (DevExpress) introduced XtraReports in the 2000s as part of its .NET component suite. A .prnx is not a design or a template; it is a rendered document, a specific report that has already been generated with real data, paginated, and saved to disk so it can be reopened or reprinted later exactly as it was produced.

The practical fact that brings most people to this page is that a .prnx has no consumer viewer. It is an application-internal format meant to be reloaded by the same DevExpress-based program that wrote it. If a business, ERP or accounting application saved a report as .prnx and you do not have that application, the supported route is to have the sender re-export the report to a portable format such as PDF, Excel or RTF.

PRNX versus REPX: rendered document versus layout template

DevExpress reporting uses two related file types, and confusing them is common. A .repx is the report layout: the design created in the End-User or Visual Studio Report Designer, describing bands, controls, data bindings and formatting but containing no data. A .prnx is the rendered output: the layout already filled with data, laid out into concrete pages, and frozen for later viewing or printing. In XtraReports terms, a report’s SaveLayout produces the .repx design, while saving the generated document (the PrintingSystem) produces the .prnx. A .repx can be re-run against fresh data; a .prnx is a snapshot of one particular run.

The ZIP container and what is inside

Technically a PRNX is a ZIP archive: it begins with the PK local file header (50 4B 03 04), the same signature as any .zip, DOCX or XLSX. Inside, DevExpress stores the serialised rendered document as XML together with the images, charts and barcodes that appear in the report. The XML records the document’s pages, the position and content of every text and graphic element (the “bricks” that XtraReports lays down during rendering), and the print and page metadata such as page size and pagination.

Because it is a ZIP, you can open a .prnx with 7-Zip or any archive tool to inspect the inner XML and extract embedded pictures. That is useful for investigation, but it does not reconstruct the report: the XML is a DevExpress-internal serialisation with no public schema, and only the DevExpress Document Viewer knows how to turn those bricks back into a laid-out, printable document. There is no third-party renderer.

How a PRNX is actually opened

The only native opener is the DevExpress Document Viewer, a WinForms or WPF control that is part of an application built on the DevExpress Reporting suite. Typically that is the program that created the file, or a small custom viewer a developer compiled against the DevExpress runtime. In code, an application loads a .prnx by reading it into the report’s PrintingSystem.LoadDocument, after which the viewer displays the stored pages. There is no general-purpose “PRNX viewer” you can install, and Windows has no default association for the extension, which is why double-clicking one does nothing.

Getting the content out: export from the viewer

Since the format is proprietary and tied to the DevExpress runtime, the realistic way to read a .prnx you received is to have it re-exported. The DevExpress Document Viewer’s Export As menu writes the same document to PDF, XLSX or XLS, RTF or DOCX, CSV, HTML, plain text, page images (PNG/JPEG) or XPS. These exports happen inside the DevExpress runtime, not through any standalone converter, so there is no legitimate third-party tool that turns a .prnx directly into a PDF. If you are the recipient, the fastest path is to ask whoever generated the report to choose Export As > PDF (for faithful print layout) or Export As > XLSX (for the underlying tabular data).

References