[DOCS]: #236

New Issue

2026-02-16T05:19:31-05:00

yindo commented

2026-02-16 05:19:31 -05:00

Originally created by @y1595020-ops on GitHub (Sep 8, 2025).

Type of Documentation Change

Error/Typo fix

Documentation Page URL or Path

https://docs.dify.ai/zh-hans/guides/workflow/node/doc-extractor

Current Content

https://docs.dify.ai/zh-hans/guides/workflow/node/doc-extractor

Suggested Changes

文档提取器不能识别 docx文档输出为空

Reason for Change

想寻求帮助

Code of Conduct

I agree to follow Dify's documentation contribution guidelines
I have searched for existing issues search for existing issues, including closed ones.
I confirm that I am using English to submit this report, otherwise it will be closed.
【中文用户 & Non English User】请使用英语提交，否则会被关闭：）
Please do not modify this template :) and fill in all the required fields.

Originally created by @y1595020-ops on GitHub (Sep 8, 2025). ### Type of Documentation Change Error/Typo fix ### Documentation Page URL or Path https://docs.dify.ai/zh-hans/guides/workflow/node/doc-extractor ### Current Content https://docs.dify.ai/zh-hans/guides/workflow/node/doc-extractor ### Suggested Changes 文档提取器不能识别 docx文档输出为空 ### Reason for Change 想寻求帮助 ### Code of Conduct - [x] I agree to follow Dify's documentation [contribution guidelines](https://github.com/langgenius/dify/blob/0277a37fcad5ad86aeb239485c27fffd5cd90043/CONTRIBUTING.md) - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭：） - [x] Please do not modify this template :) and fill in all the required fields.

yindo added the documentation bug labels 2026-02-16 05:19:31 -05:00

yindo closed this issue

2026-02-16 05:19:31 -05:00

yindo commented

2026-02-16 05:19:32 -05:00

@dosubot[bot] commented on GitHub (Sep 8, 2025):

Hi @y1595020-ops! I'm Dosu and I’m helping the dify-docs team.

DOCX extraction is officially supported in the Doc Extractor node, but there are important limitations. Only paragraphs and tables are extracted; advanced DOCX features like annotations, comments, tracked changes, numbered lists, images, embedded objects, hyperlinks, and header/footer content are ignored. If your DOCX file uses these features or has a complex structure (like nested tables), extraction may return incomplete or empty results, sometimes without any error message. Some DOCX files with structural issues (e.g., invalid links) can also cause extraction to fail or output nothing, even if they open normally in Word or WPS.

To troubleshoot: try re-saving the DOCX file in Word or WPS to standardize its format, and simplify the content if possible. For complex documents, consider converting them to a simpler structure before uploading. These are known limitations of the current extraction logic, not configuration errors or bugs in your setup. For more details, see this issue and the extraction code.

It would be helpful to update the documentation to clearly state these DOCX extraction limitations and suggest these workarounds.

To reply, just mention @dosu.

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

@dosubot[bot] commented on GitHub (Sep 8, 2025):  Hi @y1595020-ops! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify-docs team.  DOCX extraction is officially supported in the Doc Extractor node, but there are important limitations. Only paragraphs and tables are extracted; advanced DOCX features like annotations, comments, tracked changes, numbered lists, images, embedded objects, hyperlinks, and header/footer content are ignored. If your DOCX file uses these features or has a complex structure (like nested tables), extraction may return incomplete or empty results, sometimes without any error message. Some DOCX files with structural issues (e.g., invalid links) can also cause extraction to fail or output nothing, even if they open normally in Word or WPS. To troubleshoot: try re-saving the DOCX file in Word or WPS to standardize its format, and simplify the content if possible. For complex documents, consider converting them to a simpler structure before uploading. These are known limitations of the current extraction logic, not configuration errors or bugs in your setup. For more details, see [this issue](https://github.com/langgenius/dify/issues/24225#issuecomment-3205109824) and [the extraction code](https://github.com/langgenius/dify/blob/d5e86d9180be736f7782bab1f04069c41eab0d6b/api/core/workflow/nodes/document_extractor/node.py). It would be helpful to update the documentation to clearly state these DOCX extraction limitations and suggest these workarounds.  *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/f7b5d3b7-6ab7-4ef2-ac84-abebad7d9c75?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/f7b5d3b7-6ab7-4ef2-ac84-abebad7d9c75?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/f7b5d3b7-6ab7-4ef2-ac84-abebad7d9c75?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/f7b5d3b7-6ab7-4ef2-ac84-abebad7d9c75?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/f7b5d3b7-6ab7-4ef2-ac84-abebad7d9c75?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/f7b5d3b7-6ab7-4ef2-ac84-abebad7d9c75?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/f7b5d3b7-6ab7-4ef2-ac84-abebad7d9c75?feedback_type=other)</sup>  [![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot) [![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify-docs/issues/457)

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: langgenius/dify-docs#236