To move a Word document to WordPress with Tenwrite, save it as DOCX, open WordPress → New Export, select your site and use Upload a file. Enter the post details, keep the status as Draft, review the image and formatting settings, then confirm the export. Open the saved WordPress draft to check the result.
You can upload directly from your computer. You do not need to put the DOCX in Google Drive or convert it into a Google Doc first. When you revise the Word file, open the existing post in Tenwrite and upload the revised DOCX there to update the same destination.
This walkthrough follows a real demonstration document through upload, settings, draft review and a subsequent update. It contains headings, a table, a list, a hyperlink, a featured cover and an inline image. The example stays a draft; the steps apply when you are preparing an article for your own site.
What you need before uploading
Have a connected WordPress site in Tenwrite and permission to create or update its posts. If your site is not connected yet, follow the WordPress connection guide. Check the site’s name and hostname before exporting, particularly when your account contains production and demonstration sites.
Use a .docx file, up to 25 MiB. An older .doc file needs to be saved as DOCX in Word or another compatible editor. Renaming the filename extension does not convert the document. A PDF is also a different format and is not supported by this upload route.
WordPress local-file publishing does not require a Google Drive connection. Your Tenwrite account, WordPress connection and normal publishing limits still apply. The upload is a snapshot of the selected file: Tenwrite does not continuously watch the file on your computer.
Uploading an article and offering a Word download are different tasks. This workflow turns the document’s content into a WordPress post. If visitors need the original document as a downloadable resource, arrange that file separately and check its download link.
Prepare the Word document for a website article
Use real paragraph styles for section headings. A large, bold line can look like a heading while still being ordinary text. For an article whose title will be entered in Tenwrite, use Heading 2 for major body sections and Heading 3 for subsections. Check whether the body already contains a duplicate article title.
Keep a clear reading order. Ordinary paragraphs, lists, links, inline images and simple data tables give you a useful starting point. A brochure with floating text boxes, overlapping shapes or several newspaper-style columns needs more care. A web article should remain readable as the screen narrows; matching every printed page break is rarely the right goal.
Insert the actual images into the Word file. A sentence such as “[add screenshot here]” is a placement note, not an embedded image. Use images you have permission to publish, add useful alt text, and put each image near the relevant explanation. If the first image will become the featured cover, place that dedicated cover before the article body.
Resolve tracked changes and remove editorial notes that do not belong in the published article. Save the final file under a recognizable name. Keep the original DOCX so you can compare the conversion and make later revisions without reconstructing the source from WordPress.
The representative DOCX used in this walkthrough
Our example is A Publishing Checklist for a Small Website, a short demonstration article created for this test. It is not a customer result. Its body has two H2 sections, one H3 subsection, three bullet points, one documentation link and this three-column table:
| Element | What to inspect | Expected result |
|---|---|---|
| Heading | Section hierarchy | Real H2 and H3 headings |
| Table | Header and body rows | Labels above readable values |
| Images | Cover and inline screenshot | Saved media in the right places |
The file also contains two images: a dedicated cover first and a Tenwrite settings screenshot inside the article. This combination lets us check whether the first image becomes featured, whether the second stays in the body, and whether the table and heading hierarchy remain intact.
Use an equally representative document for your first transfer. A one-paragraph test cannot tell you much about a long tutorial with tables and screenshots. You do not need a complicated test suite; you need a source containing the elements you actually publish and a clear expectation for each one.
1. Upload the DOCX directly in Tenwrite
In the web app, open WordPress → New Export. Select the correct destination site and choose whether the result should be a Post or Page. This example uses a post on our connected Tenwrite Blog site.
Under Google Docs or local files, choose Upload a file and select the saved DOCX from your computer. Wait for the document to appear in the selected-content list. The prepared filename in that list is the useful confirmation that Tenwrite has accepted the source; choosing a file is not the same as creating a WordPress post.

The DOCX appears as a prepared upload below the file control. No Google Docs selection or Drive conversion was used.
Prepared uploads expire after 24 hours. This is the lifetime of the temporary publishing source, not a deadline for an already-created WordPress article. If the prepared source expires before you use it, upload the file again. Your saved destination content does not disappear when that preparation window ends.
Read any upload warnings before continuing. Fix a file-format or image problem at this stage rather than assuming the export will repair it. Once the file is ready, the content-details section lets you set how the article should appear on the destination.
2. Set the title, status, formatting and images
Enter the post details explicitly
Replace the filename-based default title with the actual article title. In our example, we entered A Publishing Checklist for a Small Website — DOCX walkthrough example so the test draft was easy to identify. The filename and public-facing post title serve different purposes.
Add an accurate excerpt, choose relevant categories and tags, and review the slug. Keep Draft selected for the first export. If you are updating an existing article later, preserving its established slug avoids changing the address people already use.
For local uploads, enter publication settings in the form. Do not rely on a metadata table inside the DOCX to choose the status or destination: Tenwrite ignores recognized DOCX frontmatter metadata and uses the export settings. Google Docs frontmatter follows a different workflow.
Choose web formatting deliberately
Select WordPress Blocks when you want the block-editor output, then review the cleanup controls. Balanced is a useful starting point. For this example, we also removed font size, text colors and background colors so the destination theme could control the article’s typography and colors.
The Word conversion is shared by the cleanup modes; choosing Original is not a promise to reproduce every Word page exactly. Inspect the result instead of assuming a preset can preserve every layout feature. Leave heading demotion off when the source already starts its body sections at the levels you want.
Review link controls too. Opening external links in a new tab is a separate choice from marking them nofollow. We did not blanket-mark the ordinary editorial documentation link as nofollow. Choose link treatment according to the relationship and your site’s policy.
Save the images and choose the cover
Check Upload Images to Media Library. To use a dedicated cover placed first in the DOCX, also check Set First Image as Featured Image. In our test, Tenwrite used the first image as the featured cover and kept the later screenshot inside the body.

Use the first-image option when the first source image is actually the intended cover. Otherwise a useful explanatory screenshot could become the featured image.
Do not leave a cover-only caption at the start of the article if the cover will be removed from body content. Keep inline captions with their corresponding images, and verify both the featured image and the body images after export. A featured cover is a separate part of a WordPress post, even when it came from the same DOCX.
Review supported SEO fields
For supported self-hosted WordPress sites, Tenwrite exposes SEO title, description, focus keyword, canonical and robots fields through its WordPress plugin integration. The Tenwrite plugin must be installed and active; having Yoast SEO or Rank Math alone is insufficient. See the SEO fields and plugin guide for the integration requirements.
Write a description that matches the article and check the rendered page after release. Saving a field does not prove every SEO plugin or theme will display it. An excerpt, featured image and custom SEO title are useful inputs, but the destination determines the actual page metadata.
3. Confirm that the first export will remain a draft
Click Start Export. Tenwrite checks the effective publication outcome and displays a confirmation. Read that result rather than relying only on the status you remember selecting earlier.
For our example, the confirmation said Will remain a draft. We then chose Confirm Export and waited for Success — Export completed successfully. The result supplied Edit and Preview links for the created WordPress post.

Confirm the destination outcome before sending the file. This test created a draft, not a public example article.
If the outcome says it will publish now when you wanted a draft, return to settings and correct it before confirming. If the outcome check fails before export begins, resolve that check rather than repeatedly pressing export. After a successful result, open the saved post; the next step is verifying the content at its destination.
4. Review the saved WordPress draft
Use Edit to inspect the post in WordPress and Preview to inspect the theme’s presentation. You may need to sign in to WordPress separately. In our test, the draft preview initially returned a not-found page while signed out; after signing in with access to the draft, the same preview opened correctly.
Check headings and the table
Compare the saved article with the source, starting with the structure. Our two major sections remained H2 headings, and Keep the same post remained an H3 subsection. The bullet list also remained a list. This is more useful evidence than judging whether the font happens to resemble Word.
The table arrived with three header cells and three body rows. We checked the cell text and that the first row used header cells while the data rows used ordinary cells. In the editor, inspect the table’s rows and columns; in preview, check wrapping and readability. WordPress’s Table block documentation explains its table controls and supported settings.

This is the actual authenticated preview of the uploaded example. The table is editable post content, not a screenshot of a Word table.
Check images, links and a narrow preview
Confirm that the featured cover is set and the inline image appears in the intended section. Both example images loaded from the WordPress site’s media URLs. Inspect alt text and image details too; a picture appearing once does not establish that the right image or description was saved.
Open important links and compare their destinations with the source. For the example, the documentation link remained attached to the intended words. If an image needs repair, the WordPress Image block documentation covers Media Library saving and image details. Our missing-images troubleshooting guide provides a more detailed destination-checking process.
Preview a phone-width layout. A wide table or a small screenshot can require a simpler presentation even when the import is structurally correct. Read the surrounding instructions without enlarging the image; essential actions should also be explained in text. Keep the draft unpublished while you make these practical adjustments.
5. Upload a revision to the same post
Save changes in Word as a revised DOCX. For this test, we changed one sentence from “Review the first internal link in the preview before release.” to “Review every internal link in the preview before release.” The headings, table and two images stayed the same.
In Tenwrite, open WordPress → My Posts, locate the existing entry on the correct site, and choose Full Edit from its actions. Use Upload a file on that edit page to select the revised DOCX. Check the existing title, slug, categories and status before submitting.

The revised file belongs on the existing post’s edit page. Starting a fresh New Export would create another entry.
Click Update Post, read the publication confirmation and confirm only when it matches the intended state. Our confirmation again said the example would remain a draft. After the update, we reloaded the WordPress preview, found the revised sentence and checked that the same post still contained the expected headings, table and images.
This is an explicit replacement workflow. Saving a file on your laptop does not update WordPress automatically, and uploading a new filename does not by itself identify which existing post you mean. Choose the post first, then supply its revised source.
Coordinate any WordPress-only edits before replacing the body from Word. If someone corrected a paragraph in the destination after the previous upload, an older Word source can overwrite that correction. Bring the source up to date or deliberately keep the destination as the place you maintain the article.
Sync Post is a different action for entries linked to Google Docs. Sync Site Content refreshes Tenwrite’s index from WordPress; it does not read the revised DOCX on your device. For this local-file example, the update route is Full Edit → Upload a file → Update Post.
Troubleshoot the point where the workflow stopped
The file is rejected before preparation
Check that it is a non-empty DOCX within the 25 MiB limit. Save an old DOC file properly as DOCX instead of renaming it. If a large file contains oversized pictures, reduce their source dimensions or compression in a working copy, then save and upload again. A smaller file is easier to inspect than an unnecessarily large collection of full-resolution images.
An embedded image cannot be imported or saved
Open the source and confirm the image is embedded rather than merely linked or represented by a placement note. Insert a normal image file into Word, save the DOCX and retry the preparation. For local uploads, an image-saving failure can stop the write; do not assume a complete draft was created. Read the result and inspect any existing destination before retrying.
The title or article appears twice
Compare the Tenwrite title field with the first body paragraph. If the same title exists in both places, remove the redundant body title from the source or intentionally use a different opening heading. Also check whether the first image was consumed as featured; an isolated caption may be left behind when a cover-only caption was included in the body.
The layout differs from the printed Word file
Check semantic structure first, then presentation. Fix a wrong heading level or missing table value before adjusting spacing. Let the site’s theme control ordinary body text and rebuild a complicated print layout into a simpler reading order when needed. The desired result is a useful web article across screen sizes, with its content intact.
A later Word edit is missing from WordPress
Check which saved DOCX you selected, whether the prepared upload expired and whether the update targeted the existing post. Reload the destination after a successful result. If WordPress contains newer edits, reconcile them before another full-content update. Repeating New Export is not a repair for a missing revision on an existing entry.
When copy and paste is enough
A short, simple article can still be copied from Word into a new WordPress draft. Inspect headings, lists, links and images afterward. Current WordPress documentation says copied Word or Google Docs images may upload automatically; it is inaccurate to assume every pasted image remains externally hosted. Check the image’s actual saved state.
Direct DOCX upload is useful when you want one source file carrying the article’s structure and embedded images, with explicit destination settings and a repeatable update route. For a Google Docs source instead, use the separate Google Docs to WordPress walkthrough.
To try this workflow, open Tenwrite and upload one representative Word document as a draft. Check its headings, table, images and links, then make one small source revision and update that same post. That gives you a concrete result to evaluate before moving a larger collection of documents.
