DOC and DOCX workflows.
Preview DOC, DOCX, and related Word-family formats. Confirm the exact import, editing, and export operation before launch.
Format support is not one promise. Separate preview, import, edit, and export requirements, then validate each operation with your target files before a production decision.
Use these pages to decide which workflow, format, and ownership boundary should be validated first.
Preview DOC, DOCX, and related Word-family formats. Confirm the exact import, editing, and export operation before launch.
Evaluate XLS and XLSX workflows separately from CSV and other spreadsheet-family formats. Decide whether users need a view, an edit surface, or a conversion step.
Bring PPT and PPTX files into a product workflow when the next step depends on the deck. Confirm the editing and export behavior that your process requires.
PDF, OFD, images, video, audio, text, and Markdown are listed for broader preview scenarios. Treat preview coverage separately from editable Office coverage.
Office file support is an operation-specific contract: preview, import, edit, and export must each be tested against the formats and files your workflow actually receives.
DOC, DOCX, DOT, DOCM, DOTX, DOTM, WPS, and WPT are listed for evaluation.
XLS, XLSX, CSV, XLSM, XLT, XLTX, XLTM, ET, and ETT are listed for evaluation.
PPT, PPTX, POT, POTX, POTM, DPS, DPT, and PPTM are listed for evaluation.
PDF, OFD, images, video, audio, text, and Markdown are preview candidates.
| Operation | What it proves | Evidence to keep |
|---|---|---|
| Preview | The user can inspect the received file | Rendered pages, access result, and browser context |
| Import | The file can enter the managed workflow | Source identity, conversion result, and error path |
| Edit | The required changes can be made | Saved version, collaboration behavior, and permissions |
| Export | The result can leave the workflow safely | Output file, fidelity review, and destination owner |