mirror of
https://github.com/langgenius/dify-official-plugins.git
synced 2026-07-21 17:45:23 -04:00
OpenRouter's Claude does not support PDF parsing. #920
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 @dimsky on GitHub (Jan 6, 2026).
Self Checks
Dify version
1.11.1
Plugin version
latest
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
Current models such as Claude, GPT, and Gemini natively support the parsing of PDF and other files, so I don't need to go through any other steps for parsing.
✔️ Error log
No response
@dosubot[bot] commented on GitHub (Jan 6, 2026):
OpenRouter's Claude integration does not actually parse or extract content from PDF files. Instead, when you upload a PDF, the plugin just inserts a placeholder like
[Document file uploaded]: <url>into the prompt, not the PDF's text or images. There is no code in the OpenRouter plugin that performs PDF content extraction for Claude models — this is a design limitation, not a bug or configuration issue (source).However, Dify itself extracts text and images from PDFs before sending content to any model, using its core extraction pipeline. The
PdfExtractorclass parses PDF pages and images, saving them and embedding image links as Markdown in the extracted text (source). This means that, in most Dify workflows, the model (including Claude via OpenRouter) receives the extracted text and image links, not the raw PDF file.If you need Claude to process PDF content, make sure your workflow uses Dify's document/RAG pipeline to extract the text and images first, then passes that extracted content to the model. If you need direct PDF parsing by the model itself, consider using a model or plugin that advertises native document or vision support (like Gemini 3 via OpenRouter), but for Claude via OpenRouter, direct PDF parsing is not supported (source).
If you have a specific workflow where the extracted content is not reaching Claude, it may be a configuration or pipeline issue in how files are routed, not a limitation of Claude's PDF support in Dify.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other