Changelog

October 6, 2026

The licence key gets its own menu entry, instead of being the fourth section of a ten-section Settings page.

• Licence is its own entry in the DocxToWP menu. It used to sit below Smart Image Optimization on the Settings screen, which is a reasonable place for a setting and a poor place for the one control a new customer needs in their first five minutes. People wrote in unable to find it.
• The Licence screen answers the three activation failures itself while the licence is inactive: being in the free plugin rather than this one, pasting the order number instead of the key, and a licence already in use on another site. Previously you had to leave the page to find any of that out.
• Licence, Settings and Help links on the plugin row on the Plugins screen, which is where you land the moment after uploading the .zip. Help & Support also links to the new activation guide.
• Settings → Licence is now a pointer to the new screen rather than a second copy of the form. Two licence boxes on one site is its own support thread.
• The plugin now calls itself DocxToWP Pro everywhere it appears: the sidebar entry, every screen heading and the Plugins row. It used to say DocxToWP, which is also the name of this site and one word off the free plugin, so the one place a confused buyer could check which plugin they were in did not actually tell them.
• Nothing about licensing itself changed. Keys, activation, deactivation, site limits, renewal reminders and the daily background re-check all behave exactly as they did in 1.3.5. This release moves one screen and signposts it.

October 2, 2026

A YouTube or Vimeo link on a line of its own imports as a playable video rather than a link.

• Paste a YouTube or Vimeo link into a document and the imported post has the video in it, not a link to it. Covers youtube.com/watch, youtu.be, Shorts, the mobile address and vimeo.com, including links Word has already turned into hyperlinks.
• Video frames copied out of YouTube or Vimeo are converted the same way, so a document built from an embed code gets the same result as one built from a link.
• A link inside a sentence stays a link. Only a paragraph containing nothing but the URL becomes a video, because replacing three words mid-sentence with a full-width player would wreck the paragraph around it. Settings → Video Embeds turns the whole thing off.

October 1, 2026

Licence handling moves to the background, and the settings screen tells you what your licence actually covers.

• A Help & Support screen in the plugin menu: documentation, changelog and download links, a support address, and a system report you can copy straight into an email. Your licence key is shortened in that report on purpose. It is written to be pasted, and a full key in pasted text is an activation a stranger could burn.
• Licence checks run on a daily background schedule instead of during a page load. Admin screens no longer wait on a network request, which was noticeable on hosts that block outbound connections.
• The licence screen shows your plan, how many sites it covers and when it renews.
• Renewal reminders before a licence lapses, dismissible, and never shown to anyone holding a lifetime licence.
• Lifetime licences are recognised explicitly and can never be expired by a licence check. Everyone who bought before 1 October 2026 keeps lifetime access with unlimited sites, permanently.

September 30, 2026

Coloured text arrives in the colour it was written in, instead of as plain body text.

• A word set in red, or a link-blue heading, keeps its colour through the import rather than arriving as ordinary body text.
• Black and near-black are left alone deliberately. They are body text saying so, and importing them would pin your text to black for anyone reading your site on a dark theme. A colour with real hue in it is kept however dark it is, so Word’s Dark Red survives.
• White text is kept only where it sits on a highlight. White on nothing is an invisible paragraph, which is a worse outcome than a missing colour.

September 29, 2026

The same picture used across many documents is stored once instead of once per document.

• A letterhead, logo or diagram shared by a batch of documents used to be added to the Media Library once per document. Fifty reports sharing one logo meant fifty copies of that logo. Re-importing a document duplicated its pictures again. Pictures already in the Media Library are now reused.
• Pictures are matched on their contents rather than their filename, so the same image is recognised however each document happened to name it, and two genuinely different images that share a name are still kept apart.
• Settings → Repeated Images turns the reuse off, for anyone who would rather each post owned its own copy. On by default.

September 29, 2026

Highlighted text keeps its colour, and strikethrough, superscript and subscript survive the import.

• Highlighted text is preserved, in the colour it was highlighted. Word and Google Docs write highlighting in two completely different ways and neither was being read; both are now, so a document highlighted in either program arrives highlighted.
• Strikethrough, including Word’s double strikethrough, and superscript and subscript, which footnote markers, trademark symbols and chemical or mathematical notation all depend on.
• Tables arrived with no borders and wide images overflowed their column. The cleanup that strips Word’s own inline styling, which genuinely does need removing because it fights your theme, was also deleting the styling the importer adds itself.

September 25, 2026

Pictures inside your documents are converted to WebP as they are imported, but only when that actually makes them smaller.

• JPEG and PNG images from your .docx are converted to WebP during import, so your pages load faster without a separate optimisation plugin.
• WebP is used only when it is genuinely smaller. Photographs usually shrink a lot; flat logos, icons and simple diagrams are often smaller as PNG, and those keep their original format.
• Transparency in PNG images is preserved, including partial transparency. Transparent logos do not come out with a box behind them.
• A summary after publishing: how many images were processed, how many were converted, and how much smaller the result is.
• Totals for a whole bulk run, so a hundred-document import reports what it saved across every image.
• Settings for quality and which formats to convert, with everything off-limits left alone: nothing outside DocxToWP’s own imports is touched.
• Your original images are never deleted or overwritten. A conversion cannot lose the only copy of a picture.
• On a server without WebP support, images import exactly as they do today. Optimisation is never allowed to stop a document publishing.

September 23, 2026

The document’s heading is no longer repeated in the body, and how a filename becomes a title is now a setting.

• A document whose top heading was Heading 2 had that heading repeated as the first line of the post, directly under the identical post title. The title is taken from the first Heading 1 or Heading 2, but only a Heading 1 was ever removed. Whichever heading supplies the title is now the one removed; later headings of the same level are untouched.
• Settings → Content → Title From Filename: sentence case (the new default), Title Case, or leave as written. It used to capitalise every word (“Annual Report For The Board”), which matches no house style. Only used when a document has no heading to take a title from; a document with a heading keeps that heading exactly as written.
• Sentence case never lowercases anything: it capitalises the first word and leaves the rest as typed, so meeting-with-John-Smith.docx stays “Meeting with John Smith” and report-NHS.docx keeps NHS.

September 19, 2026

Tested up to WordPress 7.1.1.

• Declared tested up to WordPress 7.1.1, the current release, as the exact version.

September 19, 2026

Tested up to WordPress 7.1, and the update details screen now shows the full release history.

• The plugin is now declared tested up to WordPress 7.1. It said 7.0.4, so sites on 7.1 saw a "has not been tested with your current version" warning in the update details for a plugin that was built on 7.1.
• The changelog in the "View version details" screen shows every release, not only the newest one.

September 19, 2026

In bulk import, the images a Markdown file refers to by relative path are matched to the files you drop in alongside it.

• Drop the images folder in with your .md files (Joplin’s _resources, Obsidian’s attachments, the folder a Notion export puts beside each page) and every image a document refers to by a relative path is matched by its filename and placed in the post. Until now those images were left out with a notice; now only the ones that were not uploaded are.
• The first image resolved this way becomes the post’s featured image when nothing else claims the slot, the same step of the cascade a Word document’s first picture takes. A companion image named after the document, a manual pick or an explicit “none” still win.
• The notice for an image that could not be resolved now says what to do: drop the file in with the document in Bulk Import, or add it in the editor. The single-file screen is unchanged.

September 19, 2026

Headings in Word documents from non-English Word, or using custom heading styles, now import as headings.

• Some Word documents with genuine Heading styles imported every heading as an ordinary paragraph. The importer only recognised a heading when the style’s internal ID was literally "Heading1", and that ID is not stable: German Word writes "berschrift1", French "Titre1", Word mints "Heading11" when a style is pasted between documents, and a custom style based on a heading has any ID at all. The importer now reads the document’s style definitions and resolves headings the way Word’s own navigation pane does: by the style’s canonical name, its outline level, or the heading it is based on.
• The bulk review table’s title detection uses the same resolution, so a localised or custom Heading 1 becomes the row’s title instead of the filename.
• Twelve generated Word fixtures (English, German and French Word, copied styles, custom styles, outline-level-only styles, the TOC Heading opt-out, a document with no style definitions, and a corrupt one) are checked on every build. The same fix ships in the free plugin as DocxToPost 1.2.1.

September 19, 2026

Markdown files go through bulk import too: drop .md files in with your .docx, up to 100 per run.

• The Bulk Import screen accepts .md and .markdown files alongside .docx, mixed however you like, up to the same per-job limit. Every job setting applies to them: post type, status, author, categories, tags, drip schedule, duplicate policy and SEO templates.
• Each Markdown file gets a row in the review table with its title detected the same way as on the single-file screen: front matter title, else the first heading, else the filename.
• Companion images match Markdown files by name, exactly as they match Word documents: chapter-01.jpg beside chapter-01.md becomes that post’s featured image. Drop the images folder in with the documents and the relative-path problem largely takes care of itself.
• A finished row now carries a note when the parser had to leave something out, such as a Markdown image with a relative path, so it shows on the run screen and in Import History rather than only in the moment.
• The {filename} SEO template token strips .md and .markdown as it strips .docx.

September 19, 2026

Upload a Markdown (.md) file and it goes through the same preview-and-publish flow as a Word document.

• Markdown import on the Upload Document screen. Headings, paragraphs, bold, italic, strikethrough, links, nested lists, blockquotes, tables with column alignment, horizontal rules and fenced code blocks are all preserved, and post type, status, author, categories, tags, featured image and the SEO fields apply exactly as they do for .docx.
• The first # heading becomes the post title, or the filename if there is none. A title: in front matter takes precedence, and the front matter block is removed from the post rather than shown.
• The preview screen lists anything the parser had to leave out. For Markdown that is images with a relative path, which cannot be resolved from a single uploaded file; images with a full https:// URL are kept.
• Every converted Markdown document goes through WordPress’s post-content sanitiser before it reaches the preview screen, because Markdown permits raw HTML.
• Undo and Delete record on the Import History tab did nothing. Their handlers were bound before the page’s config object existed; they now read it when clicked.
• Bulk import is unchanged and still .docx only. Word import itself is untouched.

August 13, 2026

A manual "Check for updates" link, so you never have to wait on WordPress to notice a new release.

• A "Check for updates" link on the Plugins screen. WordPress only checks twice a day. This asks immediately and tells you the answer either way.

August 12, 2026

Licence keys, so updates arrive automatically and your purchase is tied to your site.

• Licence activation. Enter the key from your purchase email under Settings → Licence to unlock the plugin on this site.
• A Deactivate button, so you can move your licence to another site yourself when changing domain or setting up staging.
• A licence is now required to import. Posts you have already created are never affected. They are ordinary WordPress posts and stay exactly as they are.
• The changelog shown inside WordPress displayed mangled dashes and broken list items.

August 12, 2026

The last release you have to install by hand, from here on, updates appear on your Plugins screen like any other plugin.

• Automatic updates. DocxToWP Pro now checks for new versions itself, so updates install in one click from your WordPress dashboard.
• Data Retention setting. Decide whether deleting the plugin should also delete your data. Off by default.
• Deleting the plugin wiped the activity log, bulk import history and every setting, with no warning and no way to opt out. Uninstalling now leaves your data alone unless you explicitly ask for it to go.
• Each release used to install into its own folder, which is why updates could not be automatic. Releases now always unpack to the same place.

August 8, 2026

Import a whole content library today and publish it gradually, every document gets its own scheduled date.

• Drip publishing. Schedule imported documents automatically instead of publishing them all at once.
• Pick the first publish date and time with a date picker.
• Publish every X hours, days, weeks or months.
• Restrict publishing to selected weekdays. Weekends are excluded by default.
• Override the date on any individual document. A date you set by hand is never overwritten when the schedule regenerates, and it does not consume a slot. The rest of the sequence closes up behind it.
• All dates use your WordPress site timezone.
• Scheduled posts published at the wrong time, off by the site’s UTC offset. A post set for 2:30 PM on an IST site went live at 8:00 PM. This affected the single-file Schedule option in 1.0 and 1.1, not just bulk imports.
• Monthly schedules starting on the 31st no longer skip a month. 31 January now steps to 28 February and recovers to 31 March, rather than overflowing to 3 March.

August 7, 2026

Import up to 100 Word documents in one go, with shared settings, live progress, and a one-click undo.

• Bulk import. Drag in up to 100 .docx files and import them in a single run.
• Review screen. Edit every title, set featured images, and exclude documents before anything is created.
• Shared settings applied across the batch: post type, status, author, categories and tags.
• Featured image matching. Drop chapter-01.jpg beside chapter-01.docx and it becomes that post’s featured image. Falls back to the first image inside the document, then to a default you pick.
• SEO templates with {title}, {sitename}, {excerpt}, {filename}, {category} and {date} placeholders, plus per-document overrides.
• Yoast and Rank Math focus keyphrase support, on both single and bulk imports.
• Live progress with pause, resume and cancel. Close the tab mid-import and it picks up where it left off.
• Per-file error isolation, one bad document fails its own row instead of stopping the run. Retry just the failures.
• One-click undo moves every post an import created to the Trash.
• Import history, with rollback available on past runs.
• Duplicate handling: import anyway, skip, or update the existing post.
• SEO title and meta description no longer cap what you can type. The counters stay as guidance, but nothing is truncated.
• A malformed .docx could crash the import instead of falling back to recovery parsing.
• Files renamed to .docx from another format are now rejected on upload rather than failing later.

April 17, 2026

Major release of DocxToWP with dedicated Free and Pro versions.

• Official Pro version with priority email support.
• Automatic image extraction. Embedded images go straight to the Media Library.
• SEO automation for Yoast and RankMath (Pro).
• Support for Pages and custom post types.
• Re-import functionality from Activity Log (Pro).
• Improved table formatting and semantic header detection.
• Resolved conflict issues when both Free and Pro versions were present.

April 15, 2026

Beta refinement and UI/UX modernization.

• New Gutenberg-style live preview editor.
• Enhanced drag-and-drop upload interface.
• Fixed character encoding issues in specific Word versions.