DWFX File Documentation

---

Technical details

Feature	Value
Full name	Design Web Format XPS (DWFx)
File extension	.dwfx
MIME type	model/vnd.dwfx+xps
Format type	Published read-only design package (binary container)
Developer	Autodesk (DWF), on Microsoft XPS / Open Packaging Conventions
Introduced	2007 (the XPS-based successor to binary DWF)
Container / base format	XPS package = Open Packaging Conventions (OPC) ZIP
Magic number	50 4B 03 04 (“PK” ZIP local file header)
Byte order	Little-endian (ZIP structures)
Page markup	XPS FixedDocumentSequence / FixedDocument / FixedPage
Payload	DWF design data (2D geometry, 3D model) + object properties
Standard / Spec	OPC (ISO/IEC 29500-2); XPS (built on OOXML packaging)
Open standard	Partial — XPS/OPC is open; DWF payload is Autodesk’s
Editable source	No — a flattened snapshot, not the DWG
Markup / redline	Yes — round-trips back to the author in Design Review
Free viewer (Windows)	Autodesk Design Review; XPS Viewer for 2D only
Cross-platform viewer	Autodesk Viewer (web)
Related extensions	.dwf, .dwg, .dxf, .xps, .pdf
Specification	docs.fileformat.com/cad/dwfx/

What is a DWFx file?

DWFx is the XPS-based member of Autodesk’s Design Web Format family. DWF was created by Autodesk to publish design data, 2D drawings and 3D models, in a compact package meant for sharing and review rather than editing. DWFx, introduced in 2007, keeps the same DWF design payload but wraps it in Microsoft’s XML Paper Specification (XPS). That single change is what defines the format in practice: because an XPS document is an Open Packaging Conventions package, a DWFx opens in any XPS-capable reader, including the XPS Viewer that shipped with Windows, so a recipient who owns neither AutoCAD nor Autodesk Design Review can still view basic sheets.

The purpose is collaboration without handing over the editable source. A designer publishes a drawing from AutoCAD, Inventor or Revit to DWFx; the file carries the visible geometry, the sheet layout, object properties and metadata, and is heavily compressed, far smaller than the DWG and safe to send because it does not expose the full editable model. Reviewers open it, pan and zoom, measure, print, and add markups that round-trip back to the author. Its closest competitor for design review is PDF: PDF is more universal, while DWFx retains CAD-specific intelligence such as layers, object data and 3D navigation.

The OPC package: it is a ZIP, part by part

A DWFx file is physically a ZIP archive that follows the Open Packaging Conventions (OPC), the same packaging profile standardised as ISO/IEC 29500-2 and used by XPS and by Office’s DOCX/XLSX. OPC borrows two terms: a package is the ZIP archive as a whole, and a part is an individual file stored inside it. Rename a .dwfx to .zip and a normal archiver lists the parts. Two housekeeping parts are always present and define how the rest is interpreted:

[Content_Types].xml     maps file extensions / part names to MIME content types
_rels/.rels             package-level relationships: the entry points
/FixedDocSeq.fdseq      the XPS FixedDocumentSequence (the document root)
/Documents/1/...        FixedDocument + FixedPage parts (the paginated sheets)
/Metadata/...           DWF section and object properties
...                     DWF design payload, fonts, images, resources

[Content_Types].xml is mandatory in every OPC package: XPS/OPC does not trust file extensions inside the ZIP, so this part declares the media type of each part by extension or by explicit override. _rels/.rels holds the package’s starting relationships, pointing a reader at the root of the fixed-document structure. Every part that references others has its own _rels companion, so the whole package is a graph of typed relationships rather than a flat file list. This is why a plain unzip works but tells you little on its own: the meaning lives in the content-types and relationship parts.

FixedDocumentSequence, FixedDocument and FixedPage

The XPS layer gives DWFx its paginated, viewer-independent 2D representation. XPS describes fixed-layout pages, so a page renders identically everywhere, and it uses a three-level hierarchy:

FixedDocumentSequence   (.fdseq)  ordered list of documents in the package
 └─ FixedDocument       (.fdoc)   one document: an ordered list of pages
     └─ PageContent               reference to a single page, in display order
         └─ FixedPage   (.fpage)  the actual page: paths, glyphs, images

A FixedDocumentSequence lists the documents; each FixedDocument lists its pages as PageContent elements in exact display order; and each FixedPage holds the drawn content as XPS markup, vector Path elements, Glyphs for text, and raster images. An XPS reader that knows nothing about CAD can walk this tree and paint the 2D sheets, which is precisely how the Windows XPS Viewer manages to display a DWFx it was never designed for.

The DWF design payload alongside the XPS pages

The XPS FixedPage tree is only the flat, printable face of the file. Beside it, the package carries the real DWF design payload: the CAD-aware content that Design Review and Autodesk tools understand. This includes the 2D section geometry, and for a 3D DWFx a tessellated model, together with object properties (layer names, block and object data, sheet information) and, once a reviewer has worked on the file, markup and redline parts that can travel back to the author. The two representations coexist deliberately: the XPS pages guarantee that something displays in any XPS reader, while the DWF payload preserves the structured design data for tools that can use it.

That split is exactly why the built-in Windows XPS Viewer is only a partial reader. It renders the FixedPage sheets, so 2D drawings appear, but it cannot show 3D content, object properties, password-protected or otherwise restricted content, or georeferenced map coordinates, because none of that lives in the XPS pages; it lives in the DWF payload the viewer ignores. For anything past a flat 2D sheet you need Autodesk Design Review, the web-based Autodesk Viewer, or the original CAD application.

DWFx versus DWF, and why you cannot get a DWG back

DWF and DWFx are two wrappers around the same Autodesk design data. Classic DWF is an older binary container and is not a ZIP, so it lacks the 50 4B 03 04 header; .dwfx is the XPS/OPC re-wrap, which is what buys it universal XPS-viewer support. The design content is essentially equivalent, and Autodesk’s publish tools can output either from the same drawing.

What neither can do is turn back into an editable DWG or DXF. A DWFx is a published snapshot that intentionally drops the full editable model so it is safe to share, so there is no faithful DWFx-to-DWG converter. The most you can do is attach the DWFx as an underlay in AutoCAD and re-trace geometry over it, which recreates lines, not the original parametric model. If you need to edit, ask the author for the source DWG. The realistic and useful conversion is DWFx to PDF for universal sharing or printing, produced by printing from Design Review or publishing from AutoCAD, though that flattens the sheet and loses the CAD layers and object data.

A confidentiality note on embedded metadata

A DWFx is view-only and runs no macros or scripts, so opening one to review is low risk from a malware standpoint; the usual ZIP-archive caution about untrusted downloads still applies since it is an OPC/ZIP package. The subtler issue is data leakage. Because the published file can embed object properties and metadata carried over from the source model, layer names, block attributes, sheet notes, a DWFx may reveal more design detail than the author intended. That is a confidentiality consideration rather than a security one: before sending a published file outside a team, it is worth reviewing what object data the publish step included.

References

• Autodesk — About DWF and DWFx Files (AutoCAD help)
• Autodesk Design Review — overview and download
• FileFormat.com — DWFx file format reference

Feedback

Was this page helpful?

Yes No

Glad to hear it! Please tell us how we can improve.

Sorry to hear that. Please tell us how we can improve.