Supported formats
Accepted document families, content-based detection, optional format packs, and explicit support boundaries.
Accepted inputs
| Family | Accepted file extensions | Runtime path |
|---|---|---|
| OOXML presentations | .pptx, .pptm, .ppsx, .ppsm, .potx, .potm | Core |
| OOXML spreadsheets | .xlsx, .xlsm, .xltx, .xltm | Core |
| OOXML text documents | .docx, .docm, .dotx, .dotm | Core |
| Flat documents | .csv, .rtf | Core |
| OpenDocument | .odp, .otp, .fodp, .odg, .otg, .fodg, .ods, .ots, .fods, .odt, .ott, .fodt | ODF pack |
| iWork single-file packages | .pages, .numbers, .key | iWork pack |
| Legacy Office | .doc, .xls, .ppt | Legacy Office pack |
| WPS Office | .wps, .et, .dps | WPS pack |
| Fixed layout | .pdf, .xps, .oxps | PDF or XPS pack |
| OFD fixed layout | .ofd | OFD pack |
TXT, standalone HTML or HTM, XLSB, and unsupported top-level formats return an explicit unsupported-format result rather than being guessed from their file extension.
Content-based detection
DocViewKit identifies packages from bounded content probes such as OPC content types, ODF mimetype and manifest data, CFB records, PDF headers, XPS relationships, OFD.xml package structure, and iWork IWA identity. A filename hint is used only to isolate a structurally recognized WPS-family input.
Opening a family does not imply that every authored feature is exact. Applications must read DocumentInfo capabilities and structured diagnostics.
OFD support boundary
OFD 1.0 and 1.1 fixed-layout documents use a dedicated on-demand pack. The implemented subset includes positioned searchable text, browser-supported embedded fonts and raster images, vector paths and composite graphics, common solid and gradient paints, drawing parameters, transforms, opacity, geometry clips, templates, static annotations, vector OFD seals, outlines, and local SM3/SM2 signature-integrity checks.
Other patterns, complex or post-1.1 clip transforms, non-OFD seal appearances, attachments, and interactive actions are incomplete or inactive. A valid signature check does not establish certificate trust, revocation, timestamp status, signer identity, or regulatory compliance; unavailable checks are reported through diagnostics.
Read-only and inactive by design
Macro-enabled packages are parsed as their document family, but VBA, scripts, ActiveX, PDF actions, launch targets, and other active content never execute. External resources are blocked unless the host explicitly provides a safe local resource path.