Conversion guide

Check a Word or Google Docs draft before WordPress.

Choose a small example first, inspect what changes, then save and reopen an unpublished post in your own editor.

Draft to Page prepares editable article structure. Your source document, browser clipboard, WordPress version, plugins and theme can change the result. Keep the original document and a private workspace backup.

Word: try a complete, fictional file

Download the fictional Word sample. It is generated by this project's exporter, not a customer's document or evidence from a current Microsoft Word session. It contains a title, a heading, bold text, a link, a numbered list and a two-column table.

Open Word to WordPress and select the downloaded .docx. File selection only prepares a preview; existing article writing stays in place.
Compare the preview with the file. Expect the separate title “A small publishing plan”, the heading “Before publishing”, the two numbered steps, and a table ending with “Publish” and “Planned”. Inspect every conversion notice.
Acknowledge the conversion, then import. Read the article, review the WordPress findings and approve the export. Copy or download WordPress blocks. The post title is separate.
Follow the save-and-reopen check below. Once the small sample works, try your own article and compare its ending, lists, notes, links and images with the original.

The file is rejected, or part of it is missing

Keep the original and read the stated reason. The importer accepts plain .docx files up to 8 MiB and articles up to 60,000 characters. Old .doc, encrypted files, complex fields, equations, merged tables and unsupported document structures need review in the source editor. A rejection does not mean the missing structure was converted. Try a smaller formatted selection rather than repeatedly importing the same rejected file. Word conversion limits.

Pictures became numbered text

Before applying the import, optionally prepare and download the supported embedded PNG/JPEG package. Inspect original files for metadata and uncropped areas. Upload pictures yourself in WordPress and match the numbered placements. Linked images are not fetched, and a workspace backup does not contain the original image files. Image recovery steps.

The title or review comments are not in the post body

A recognized opening title moves to the separate title field. Enter it in WordPress's title field. Word editorial comments are excluded from the article; recover eligible comment text separately before applying if you need it. Referenced supported footnotes and endnotes become ordinary article sections, so check those separately from comments.

Google Docs: check what your clipboard supplies

In your document, select a short passage with one heading, a bold phrase, a link and two list items. Copy it normally and paste into Google Docs to WordPress. This site reads the selection you paste; it does not open your Google account or fetch a document URL.

The preview says plain text, or bold and headings disappeared

The clipboard did not supply supported formatted HTML. Missing formatting cannot be reconstructed. Keep the article unchanged, copy the selection again with normal Copy and Paste, and inspect the new preview. If your browser still supplies only text, use a .docx downloaded from your document editor and the Word file alternative. Plain-text import deliberately keeps Markdown-looking punctuation literal. Choose the explicit Markdown import format for authored Markdown.

A table needs a header decision

Check whether the first row contains column names. Only then select the first-row header option and preview again. It is an explicit meaning decision, not a repair for merged or irregular tables. Do not label a data row as a header just to make the import pass.

Checklists have labels, or a selection is rejected

Supported checklists keep explicit checked and unchecked states as [Checked] and [Unchecked] text labels, including the retained Google Docs checklist sample. These labels are editable ordinary list text, not clickable checkboxes. Compare the states, nesting and strikethrough with your original before applying. Conflicting or missing states, partly checked items and ambiguous nesting are rejected. Include the parent item when copying a nested selection, or simplify the source and copy it again. Suggestions, comments and document history still require review in the source editor. Checklist conversion details.

WordPress: verify the actual saved draft

Create a new, empty unpublished post and enter its title separately.
Use the full post Code editor for block source. A Code block or Custom HTML block serves a different purpose. Return to Visual editor and inspect the editable blocks.
Check the first and last paragraph, list numbering, table headings and cells, note markers, links and image placements against your source. Add destination settings yourself.
Save as a draft, close the editor and reopen the saved post. Check for unexpected-content warnings and try editing one paragraph. Save and reopen again if you change it.
Preview the actual post on desktop and mobile before you publish. A successful clipboard message or download request does not establish that WordPress received or saved it.

I see source code, or an unexpected-content warning

Keep your original and downloaded block source. Confirm that block comments were pasted into the full post Code editor rather than a Code or Custom HTML block. Recheck in a new empty draft. If a warning persists, leave that draft unpublished and inspect the affected block in your actual installation. Do not assume an editor recovery action preserved all text or settings. Detailed handoff steps.

Copy was blocked or the result belongs to an earlier version

Leave the working tab open. Use the current approved block download or the visible source fallback, then inspect the saved file. When writing or export options change during a copy, review and copy the current version again. Clipboard permission and file handling vary by device. Keep unfinished work safely.

What the current evidence establishes

Evidence checkpoint: October 16, 2026, application PR #93. These are reproducible developer checks, not customer outcomes, time-saving measurements or universal compatibility claims.

Application-origin corpus: 13 retained licensed inputs and 15 explicit preservation, disclosure, rejection or sampled contracts. Word packages carry application metadata; Google Docs HTML comes from upstream paste tests with unspecified capture versions. These are not fresh sessions in the original applications. Corpus provenance and limits.
Actual local WordPress save/reopen: Eleven unpublished cases passed on WordPress 7.1.3, PHP 8.3.33 and SQLite, using an Author account without unfiltered HTML. Checks include native blocks, stored and rendered content, reopen and an intentionally invalid block control. This is one local configuration, not every host, plugin, theme or device. Dated application release evidence.
Still needs independent acceptance: Current Word and Google Docs application sessions, physical-device clipboard behavior, real assistive technology, your hosted WordPress setup and real-writer completion or repeat use. No production-rendering or customer-success result is implied by a local build.

Found a reproducible problem? Report the action and visible error using fictional text. Keep private writing, document metadata, credentials and workspace backups out of public issues.