A .docx file can usually be opened in Microsoft Word, a compatible Mac document app such as Pages, or a browser-based editor such as Google Docs. Choose based on what you already have and whether you need to edit. If the document is for publishing, treat opening it as an access check—not proof that it is the approved source. Before using it for a CMS draft, confirm its owner and version, then inspect the content that matters to the handoff.
Choose a route to open the DOCX file
Start with the application available to you and the task you need to do. If you only need to read the file, a viewing route may be enough. If you need to revise it, confirm that the application gives you editing access and that the owner expects you to make changes.
| Route | Use it when | Editing need | Check after opening |
|---|---|---|---|
| Microsoft Word | Word is already available on your computer | Read or edit, depending on your access and the document’s settings | Confirm the filename, then check that the text and visible elements you need are present. |
| A Mac document app, such as Pages | You are on a Mac and have a compatible app available | Read or edit if the app and file allow it | Check the document’s headings, links, images, and any layout details relevant to your task. |
| A browser-based editor, such as Google Docs | You want to work in a browser and can use an online editor | Read or edit, depending on the editor, account, and file access | Confirm the right file opened and check key content before relying on it. |
If you are opening a document for a content team, ask the sender which file is the approved source before choosing a working copy. The route that makes a file accessible is not necessarily the route that establishes approval.
Open the file in Word or an available alternative
First locate the received file. Check its name and make sure it has a .docx extension. If it arrived as an email attachment, save or download it to a location you can find again.
On Windows: Find the file in File Explorer and open it. If it opens in an unexpected app, use the available Open with option to select Word or another compatible application. The exact choices can vary by computer. Once it opens, check the filename and read a few lines to confirm you have the intended document.
On a Mac: Find the file in Finder and open it. If needed, use the available app-selection option to choose Word or a compatible document app such as Pages. Confirm that the expected text and visible elements loaded; do not assume that a successful opening means every detail appears as intended.
In a browser-based editor: Open the editor you plan to use and follow its available option to upload or open a file from your computer. Select the DOCX, wait for it to load, and check the filename and content. If you plan to edit, verify that editing is available before making changes. Keep track of whether you are working in the received DOCX or a separate copy created by the editor.
For a quick read, a compatible application you already have is often the simplest route. For collaboration, a browser-based editor may fit better. In either case, keep the original file identifiable and ask the sender before creating or treating another version as the working source.
Resolve a file that will not open or cannot be edited
Work out whether the problem is with loading the file or with permission to change it. Repeatedly trying unrelated apps will not resolve a view-only restriction, and view-only access does not necessarily mean the file failed to load.
- If the file does not open: Check that you have the complete file and that its name ends in
.docx. A renamed file is not necessarily a DOCX. Try opening it with another compatible route, such as Word or a Mac document app. If it still fails, ask the sender for a fresh or usable copy and mention what happens when you try to open it. - If the document opens but you cannot edit: Confirm whether the app is showing a read-only or view-only document, or whether your access is limited. Ask the document owner to confirm whether you should edit it and, if so, to provide the appropriate access or a copy intended for editing.
- If the text appears but an element is missing or changed: Note what you see and where it occurs. Compare with the source if you have it. If the difference could affect meaning or approval, pause and ask the document owner rather than silently repairing or converting the file.
When asking for help, include the filename, the application you tried, and whether the issue is opening, editing, or a specific content difference. That gives the sender a concrete problem to resolve.
Confirm the source and inspect the opened document before CMS handoff
An opened document is accessible; an approved document is the version the responsible owner has confirmed for use. A CMS draft is a later work state, not another name for the source. Before anyone creates or updates a draft, identify the source owner and confirm which version is approved.
Use the decision table to determine the next step. If the source or approval status is unclear, keep the file out of the CMS handoff until the named owner resolves it.
| Application and need | Source approval status | Next action | Owner for an exception |
|---|---|---|---|
| Any compatible app; read only | Owner and approved version are confirmed | Inspect the opened file against that version, then pass the identified source to the CMS draft owner | Source owner decides questions about approval or content changes |
| Any compatible app; editing needed | Owner and approved version are confirmed | Confirm that editing is authorized; identify the working file separately from the approved source | Source owner confirms permission and which version remains authoritative |
| Any app; a mismatch or uncertain version appears | Approval is unknown, or the opened file differs from the expected source | Record the difference and pause before creating or updating a CMS draft | Document owner resolves source, version, or content questions |
| Browser editor; separate copy is being used | Approval is confirmed for a specific version | Record which file is the approved source and which is the working copy; inspect the working copy against the approved version | Source owner decides whether a changed copy is acceptable |
For a practical comparison, check the same elements in the approved source and the opened file:
- Headings: Compare the wording, order, and level where structure matters.
- Links: Check that the linked text and destination match the approved source.
- Images: Confirm that expected images are present and appear with the relevant content.
- Comments and requested changes: Check whether required review notes or changes are visible and accounted for. If their status is unclear, ask the owner whether they have been resolved.
Record each discrepancy with its location, what appears in the source and opened file, and who will decide or correct it. For example: “Section ‘Next steps’: the source has a linked phrase; the opened copy does not. Source owner to confirm the intended link before CMS drafting.” A clear match—or a recorded, owner-resolved exception—is the pass condition for this source check. It does not complete destination-field QA or published-page verification.
If the source owner confirms the DOCX is approved, continue to the relevant document-to-CMS handoff guidance for preparing and checking content at the next stage. If you find a discrepancy or cannot identify the approved version, contact the source owner first.