
AsciiDoc Files
Edit AsciiDoc source and see its preview side by side.
Export a DOCX with comments attached to the preceding word.
MIT · no telemetry · core features free

The directory takes these platforms from the plugin manifest. The automated tests run in the desktop app only.
Directory facts fetched from community.obsidian.md/users/theluckystrike.
You review a prose draft in Obsidian and need to share its inline comments through a DOCX file.
Write a review comment immediately after the word it concerns. Word Comment Export turns supported %% comments into native comments in a new DOCX file.
Play demoPlace an inline comment after its anchor word. Preview its text, author and output path before export.
Export creates a DOCX beside the note. If the name exists, a numbered name preserves the earlier file.

The preview reports unsupported Markdown and invalid comments by line. Export stays off while problems remain.

The free version exports one note with plain paragraphs, headings and supported inline comments.
Pro costs $5 a month or $15 one time through GitHub Sponsors. One sponsorship turns on Pro in every plugin that has it.
A name at the start of a comment can set its author. Unlabelled comments use the configured author.

Convert supported Markdown tables and local images with Pro. Comments in table cells become document comments too.

Choose notes from the active note’s folder in name order. Joined output starts each later note on a new page.

needs
steps
Open a note in the editor with an inline comment after its anchor word.
Run Export the active note to a docx file.
Read the preview and correct any unsupported text it lists.
Check the author, select Export, and find the new DOCX beside your note.
If the app can't find a new plugin yet, try again later. Obsidian says a plugin that passes the review shows in the app within 24 hours.
How to export your inline comments as Word comments in Obsidian
%% comments convert; HTML comments and externally stored SideNote comments do not.Need a change for your team? I build custom Obsidian plugins and features.
The active note export reads the editor text. Unsaved changes are included.
Each comment anchors to the word immediately before it. End punctuation stays outside the comment anchor.
The export chooses a new numbered name when the original name exists. Your source note also keeps its text.
The tests inspect DOCX XML for comment structure. Opening the generated files in Word was not tested for this release.
Before sign-in, requests stay off; sign-in sends the client ID and read:user scope to github.com and polls for a token. After sign-in, api.github.com receives authenticated sponsorship queries for tier and total payments; no note content, file names or vault data leaves. Successful checks last seven days, failures retry after six hours, and Refresh requests an earlier check.
Tell me what is broken in Word Comment Export, or what it should do next.
Word Comment Export 1.1.0, MIT license
MIT · no telemetry · core features free