mirror of
https://github.com/open-webui/open-webui.git
synced 2026-07-17 08:21:12 -05:00
[GH-ISSUE #16086] issue: PDF OCR fails to extract text from images when Content Extraction Engine set to Default (regression since v0.6.16) #17779
Reference in New Issue
Block a user
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?
Originally created by @hifun0916 on GitHub (Jul 28, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/16086
Check Existing Issues
Installation Method
Docker
Open WebUI Version
v0.6.18
Ollama Version (if applicable)
No response
Operating System
Ubuntu 22.04
Browser (if applicable)
Chrome 138.0.7204.159
Confirmation
README.md.Expected Behavior
When I navigate to Workspace -> Knowledge -> Add Content and upload a PDF file that contains only one image with text, I expect the system to successfully perform PDF OCR functionality and extract the text from the image.
Actual Behavior
Failed to add file.
400: The content provided is empty. Please ensure that there is text or data present before proceeding.
Request URL
http://192.168.120.176:8003/api/v1/files/
Response:
Request URL
http://192.168.120.176:8003/api/v1/knowledge/6b675494-97e0-4f42-b28b-88e8a059a4c2/file/add
{file_id:2dbf904e-f205-4259-83f4-7217d25263c5}
Response:
400: The content provided is empty. Please ensure that there is text or data present before proceeding.Steps to Reproduce
Connected to the OpenWebUI
Admin Panel -> Settings -> Documents:
Logs & Screenshots
Browser console logs.
Docker container logs.
Additional Information
I have confirmed that the last version that worked correctly was v0.6.15.
All versions >= 0.6.16 exhibit this error.
Additionally, can someone tell me what OpenWebUI uses to perform PDF OCR when the Content Extraction Engine is set to Default?
@rgaricano commented on GitHub (Jul 28, 2025):
It's not a regression, it's a well know issue of the pypdf lib, that fault when ocr some pdfs within certain images types inside. It had same faults in all versions.
@hifun0916 commented on GitHub (Jul 28, 2025):
But I can confirm that the exact same PDF file worked correctly in v0.6.15.
Could you help explain why it worked in v0.6.15 if this is a consistent pypdf library issue across all versions?
@SlavikCA commented on GitHub (Aug 13, 2025):
I have same (or similar?) issue.
I was using Med Gemma 3 to look at the images (JPG, not PDF).
Now that doesn't work. Error:
I apologize, if that's different issue. Let me know and I'll create separate ticket.
@hifun0916 commented on GitHub (Aug 15, 2025):
Your issue looks quite similar to mine, but I’m not entirely sure if it’s the same root cause. Have you tried running it on v0.6.15? I only started seeing this error after upgrading to v0.6.16.
@tjbck commented on GitHub (Aug 21, 2025):
Upstream issue: https://github.com/langchain-ai/langchain/issues/26225