Definition. A Word document preview is a rendered view shown inside your application. OfficeAPI lists Word-family preview extensions separately from conversion inputs and outputs. Viewing a source document is therefore a different decision from producing a new PDF or DOCX file.
Which Word formats can you preview?
The preview source lists 14 documented Word-family extensions. They include documents, templates, macro-enabled formats, WPS and OpenDocument files, plus fixed-layout and text-oriented formats.
| Group | Listed extensions | Review question |
|---|---|---|
| Office Open XML | DOCX, DOTX, DOCM, DOTM | Is this a document or a template? |
| Legacy Word | DOC, DOT | Does the archive contain older files? |
| WPS and OpenDocument | WPS, WPT, ODT | Which source application produced the file? |
| Other Word-family previews | OFD, RTF, EPUB, TXT, PDF | Is preview sufficient for the user's next action? |
Use the full preview list as the supported-extension reference. For example, a format being previewable does not establish that it is a conversion input. Macro-enabled extensions also do not establish macro execution.
Where does the viewer belong in the application?
Keep document selection, access permissions and storage under your application's control. The local engine supplies document rendering; your interface decides when a document opens and what action follows review.
There are 2 product surfaces: preview and conversion. If the user needs to read a file and return to the application, preview may meet that requirement. If the user needs a new downloadable document, evaluate DOCX-to-PDF conversion separately.
How do you evaluate a Word viewer?
- Inventory the extensions your users actually open and compare them with the preview list.
- Choose one of the 2 invocation paths for your target application.
- Review representative files with tables, page breaks, images, headers and non-Latin text in the actual application layout.
- Test the surrounding experience: access denied, unsupported extension, opening another document and returning to the previous screen.
The last stage tests your UI rather than a documented OfficeAPI viewer widget. The product overview does not specify navigation controls, annotation tools or editing behavior, so implement only the surrounding features your application provides.
What should you check before shipping?
Check small and large application windows, long filenames and files stored in the locations your users use. Keep conversion and preview errors separate in your interface so a problem in one workflow does not silently block the other. For mobile applications, the mobile preview guide adds device-specific checks.
Frequently asked questions
Does preview upload the document?
OfficeAPI renders offline. Any network transfer introduced by your application is a separate design decision.
Does preview make a Word file editable?
The documented capability is preview. Do not promise an editor based on the preview-extension list.
Can I preview OFD even though it is not a conversion input?
OFD is listed for Word-family preview. Conversion support must still be checked in its own matrix.