langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 20:15:31 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Multimodal knowledges don’t support locally uploaded images #21151

New Issue
Closed
opened 2026-02-21 20:11:10 -05:00 by yindo · 3 comments
yindo commented 2026-02-21 20:11:10 -05:00
Owner
Copy Link
Copy Source

Originally created by @zufall1985 on GitHub (Dec 18, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • 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.

Dify version

1.11.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Multimodal knowledges don’t support locally uploaded images. When I use an image as input, the retrieval test returns empty results.

✔️ Expected Behavior

How can I make a knowledge that includes locally uploaded images work?

❌ Actual Behavior

No response

Originally created by @zufall1985 on GitHub (Dec 18, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [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. ### Dify version 1.11.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Multimodal knowledges don’t support locally uploaded images. When I use an image as input, the retrieval test returns empty results. ### ✔️ Expected Behavior How can I make a knowledge that includes locally uploaded images work? ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 20:11:10 -05:00
yindo closed this issue 2026-02-21 20:11:10 -05:00
yindo commented 2026-02-21 20:11:10 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Dec 18, 2025):

Dify's codebase is designed to support locally uploaded images in multimodal knowledge bases, but successful retrieval depends on several key conditions: the dataset must be explicitly marked as multimodal, images must be properly indexed as attachments (with SegmentAttachmentBinding entries), and retrieval queries must reference the correct attachment IDs—not raw image files. If any of these steps are missing, retrieval will return empty results even if the images are uploaded and stored locally.

There is no hardcoded restriction against local images, but the system requires that images are registered and indexed correctly. The retrieval logic expects image queries to use attachment IDs, and the dataset must have the multimodal flag enabled for image search to work. If you are seeing empty results, it's likely due to missing one of these prerequisites in your setup. The recently updated documentation on multimodal embedding and retrieval may provide more detailed, step-by-step guidance for ensuring images are indexed and retrievable in knowledge bases, so it's worth reviewing the new docs for specifics on configuration and workflow requirements (see docs PR #600).

If you need to troubleshoot, check that:

  • Your dataset is set as multimodal.
  • Uploaded images are indexed and have corresponding SegmentAttachmentBinding records.
  • Retrieval queries use the correct attachment IDs.

There is ongoing interest in improving multimodal image support, but no immediate workaround or fix is documented for v1.11.1. If all prerequisites are met, locally uploaded images should be retrievable as intended.

To reply, just mention @dosu.

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

Chat with Dosu Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Dec 18, 2025): <!-- Answer --> Dify's codebase is designed to support locally uploaded images in multimodal knowledge bases, but successful retrieval depends on several key conditions: the dataset must be explicitly marked as multimodal, images must be properly indexed as attachments (with SegmentAttachmentBinding entries), and retrieval queries must reference the correct attachment IDs—not raw image files. If any of these steps are missing, retrieval will return empty results even if the images are uploaded and stored locally. There is no hardcoded restriction against local images, but the system requires that images are registered and indexed correctly. The retrieval logic expects image queries to use attachment IDs, and the dataset must have the multimodal flag enabled for image search to work. If you are seeing empty results, it's likely due to missing one of these prerequisites in your setup. The recently updated documentation on multimodal embedding and retrieval may provide more detailed, step-by-step guidance for ensuring images are indexed and retrievable in knowledge bases, so it's worth reviewing the new docs for specifics on configuration and workflow requirements [(see docs PR #600)](https://github.com/langgenius/dify-docs/pull/600). If you need to troubleshoot, check that: - Your dataset is set as multimodal. - Uploaded images are indexed and have corresponding SegmentAttachmentBinding records. - Retrieval queries use the correct attachment IDs. There is ongoing interest in improving multimodal image support, but no immediate workaround or fix is documented for v1.11.1. If all prerequisites are met, locally uploaded images should be retrievable as intended. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/03ae733a-ed12-4bbf-9f8a-b3229a6ab9ab?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/03ae733a-ed12-4bbf-9f8a-b3229a6ab9ab?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/03ae733a-ed12-4bbf-9f8a-b3229a6ab9ab?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/03ae733a-ed12-4bbf-9f8a-b3229a6ab9ab?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/03ae733a-ed12-4bbf-9f8a-b3229a6ab9ab?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/03ae733a-ed12-4bbf-9f8a-b3229a6ab9ab?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/03ae733a-ed12-4bbf-9f8a-b3229a6ab9ab?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=Dify%27s%20codebase%20is%20designed%20to%20support%20locally%20uploaded%20images%20in%20multimodal%20knowledge%20bases%2C%20but%20successful%20retrieval%20depends%20on%20several%20key%20conditions%3A%20the%20dataset%20must%20be%20explicitly%20marked%20as%20multimodal%2C%20images%20must%20be%20properly%20indexed%20as%20attachments%20%28with%20SegmentAttachmentBinding%20entries%29%2C%20and%20retrieval%20queries%20must%20reference%20the%20correct%20attachment%20IDs%E2%80%94not%20raw%20image%20files.%20If%20any%20of%20these%20steps%20are%20missing%2C%20retrieval%20will%20return%20empty%20results%20even%20if%20the%20images%20are%20uploaded%20and%20stored%20locally.%0A%0AThere%20is%20no%20hardcoded%20restriction%20against%20local%20images%2C%20but%20the%20system%20requires%20that%20images%20are%20registered%20and%20indexed%20correctly.%20The%20retrieval%20logic%20expects%20image%20queries%20to%20use%20attachment%20IDs%2C%20and%20the%20dataset%20must%20have%20the%20multimodal%20flag%20enabled%20for%20image%20search%20to%20work.%20If%20you%20are%20seeing%20empty%20results%2C%20it%27s%20likely%20due%20to%20missing%20one%20of%20these%20prerequisites%20in%20your%20setup.%20The%20recently%20updated%20documentation%20on%20multimodal%20embedding%20and%20retrieval%20may%20provide%20more%20detailed%2C%20step-by-step%20guidance%20for%20ensuring%20images%20are%20indexed%20and%20retrievable%20in%20knowledge%20bases%2C%20so%20it%27s%20worth%20reviewing%20the%20new%20docs%20for%20specifics%20on%20configuration%20and%20workflow%20requirements%20%5B%28see%20docs%20PR%20%23600%29%5D%28https%3A//github.com/langgenius/dify-docs/pull/600%29.%0A%0AIf%20you%20need%20to%20troubleshoot%2C%20check%20that%3A%0A-%20Your%20dataset%20is%20set%20as%20multimodal.%0A-%20Uploaded%20images%20are%20indexed%20and%20have%20corresponding%20SegmentAttachmentBinding%20records.%0A-%20Retrieval%20queries%20use%20the%20correct%20attachment%20IDs.%0A%0AThere%20is%20ongoing%20interest%20in%20improving%20multimodal%20image%20support%2C%20but%20no%20immediate%20workaround%20or%20fix%20is%20documented%20for%20v1.11.1.%20If%20all%20prerequisites%20are%20met%2C%20locally%20uploaded%20images%20should%20be%20retrievable%20as%20intended.)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![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/issues/29900)
yindo commented 2026-02-21 20:11:10 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Dec 18, 2025):

This is only for bug report, if you would like to ask a question, please head to Discussions.

Please provide more details.

@crazywoola commented on GitHub (Dec 18, 2025): This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). Please provide more details.
yindo commented 2026-02-21 20:11:10 -05:00
Author
Owner
Copy Link
Copy Source

@Light-Towers commented on GitHub (Dec 26, 2025):

@zufall1985 请问后来多模态知识库问题解决了吗？我也遇到这个问题

@Light-Towers commented on GitHub (Dec 26, 2025): @zufall1985 请问后来多模态知识库问题解决了吗？我也遇到这个问题
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 🐞 bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#21151
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?