FORMAT COVERAGE

Office file preview, import, editing, and export.

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.

OFFICE SDK / FORMAT COVERAGE
Sample workbook.xlsxXLSX · preview surface
Preview
12345
Illustrative workbook
RegionPipelineRenewalForecastNorth AmericaIn review-ConfirmEMEADraft-ConfirmAPACReady-ShareExpansionPending-Review
Product context → Office surface → business result
A CLEAR BOUNDARY

Useful detail for the next technical question.

Use these pages to decide which workflow, format, and ownership boundary should be validated first.

Your system keeps file storage and permissions.
Preview, edit, review, import, and export are separate decisions.
Callbacks and SDK surfaces connect the document to your product.
01
WORD

DOC and DOCX workflows.

Preview DOC, DOCX, and related Word-family formats. Confirm the exact import, editing, and export operation before launch.

02
EXCEL

Workbooks, tables, and operational data.

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.

03
POWERPOINT

Slides and presentation handoffs.

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.

04
BROADER PREVIEW

Inspect more than Office files.

PDF, OFD, images, video, audio, text, and Markdown are listed for broader preview scenarios. Treat preview coverage separately from editable Office coverage.

IN ONE SENTENCE

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.

8 formats:

Word-family entries

DOC, DOCX, DOT, DOCM, DOTX, DOTM, WPS, and WPT are listed for evaluation.

9 formats:

Excel-family entries

XLS, XLSX, CSV, XLSM, XLT, XLTX, XLTM, ET, and ETT are listed for evaluation.

8 formats:

PowerPoint-family entries

PPT, PPTX, POT, POTX, POTM, DPS, DPT, and PPTM are listed for evaluation.

7 types:

broader preview types

PDF, OFD, images, video, audio, text, and Markdown are preview candidates.

COMPARE THE BOUNDARY

Separate format questions by operation

OperationWhat it provesEvidence to keep
PreviewThe user can inspect the received fileRendered pages, access result, and browser context
ImportThe file can enter the managed workflowSource identity, conversion result, and error path
EditThe required changes can be madeSaved version, collaboration behavior, and permissions
ExportThe result can leave the workflow safelyOutput file, fidelity review, and destination owner
APPLY THE GUIDANCE

Four checks before the next decision.

  1. Collect representative files, including the largest and most structurally complex examples.
  2. Test preview, import, edit, and export separately instead of treating format support as one claim.
  3. Inspect layout, formulas, comments, media, and accessibility in the application that receives the result.
  4. Publish an operation-by-format matrix with a named owner for every unresolved case.
KEEP EXPLORING

Choose the next proof point.