[PR #18604] [CLOSED] Add DeepSeek OCR integration for document processing #40481

New Issue

GiteaMirror · 2026-04-25T12:58:09-05:00

GiteaMirror commented

2026-04-25 12:58:09 -05:00

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/18604
Author: @devrandom
Created: 10/24/2025
Status: ❌ Closed

Base: main ← Head: claude/integrate-deepseek-ocr-011CURd6ZNYLEHnxfT6CB6Hf

📝 Commits (1)

281b2dd Add DeepSeek OCR integration for document processing

📊 Changes

5 files changed (+478 additions, -0 deletions)

View changed files

📝 backend/open_webui/config.py (+37 -0)
➕ backend/open_webui/retrieval/loaders/deepseek_ocr.py (+372 -0)
📝 backend/open_webui/retrieval/loaders/main.py (+17 -0)
📝 backend/open_webui/routers/retrieval.py (+51 -0)
📝 pyproject.toml (+1 -0)

📄 Description

This commit integrates DeepSeek OCR as a new content extraction engine using vLLM server with OpenAI-compatible API.

Changes:

Added DeepSeekOCRLoader class for API-based OCR processing
- Supports PDF to image conversion with pdf2image
- Returns LangChain Document objects with rich metadata
- Supports various image formats
Added relevant configuration variables in config.py.
Integrated into loader factory (main.py):
- Added to engine selection logic
- Supports when CONTENT_EXTRACTION_ENGINE=deepseek_ocr
Updated retrieval router API:
- Exposed DeepSeek OCR settings in GET /api/config/retrieval
- Added form fields in POST /api/config/retrieval/update
- Pass config to Loader in process_file()
Added pdf2image dependency for PDF processing

Usage:
Set environment variables:
CONTENT_EXTRACTION_ENGINE=deepseek_ocr DEEPSEEK_OCR_API_BASE_URL=http://your-gpu-server:8000/v1 DEEPSEEK_OCR_API_KEY=your-secret-key

🤖 Generated with Claude Code

Pull Request Checklist

Note to first-time contributors: Please open a discussion post in Discussions and describe your changes before submitting a pull request.

Before submitting, make sure you've checked the following:

Target branch: Verify that the pull request targets the dev branch. Not targeting the dev branch may lead to immediate closure of the PR.
Description: Provide a concise description of the changes made in this pull request.
Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
Documentation: If necessary, update relevant documentation Open WebUI Docs like environment variables, the tutorials, or other documentation sources.
Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?
Testing: Perform manual tests to verify the implemented fix/feature works as intended AND does not break any other functionality. Take this as an opportunity to make screenshots of the feature/fix and include it in the PR description.
Agentic AI Code:: Confirm this Pull Request is not written by any AI Agent or has at least gone through additional human review and manual testing. If any AI Agent is the co-author of this PR, it may lead to immediate closure of the PR.
Code review: Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards?
Title Prefix: To clearly categorize this pull request, prefix the pull request title using one of the following:
- BREAKING CHANGE: Significant changes that may affect compatibility
- build: Changes that affect the build system or external dependencies
- ci: Changes to our continuous integration processes or workflows
- chore: Refactor, cleanup, or other non-functional code changes
- docs: Documentation update or addition
- feat: Introduces a new feature or enhancement to the codebase
- fix: Bug fix or error correction
- i18n: Internationalization or localization changes
- perf: Performance improvement
- refactor: Code restructuring for better maintainability, readability, or scalability
- style: Changes that do not affect the meaning of the code (white space, formatting, missing semi-colons, etc.)
- test: Adding missing tests or correcting existing tests
- WIP: Work in progress, a temporary label for incomplete or ongoing work

Changelog Entry

Description

[Concisely describe the changes made in this pull request, including any relevant motivation and impact (e.g., fixing a bug, adding a feature, or improving performance)]

Added

[List any new features, functionalities, or additions]

Changed

[List any changes, updates, refactorings, or optimizations]

Deprecated

[List any deprecated functionality or features that have been removed]

Removed

[List any removed features, files, or functionalities]

Fixed

[List any fixes, corrections, or bug fixes]

Security

[List any new or updated security-related changes, including vulnerability fixes]

Breaking Changes

BREAKING CHANGE: [List any breaking changes affecting compatibility or functionality]

Additional Information

[Insert any additional context, notes, or explanations for the changes]
- [Reference any related issues, commits, or other relevant information]

Screenshots or Videos

[Attach any relevant screenshots or videos demonstrating the changes]

Contributor License Agreement

By submitting this pull request, I confirm that I have read and fully agree to the Contributor License Agreement (CLA), and I am providing my contributions under its terms.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/open-webui/open-webui/pull/18604 **Author:** [@devrandom](https://github.com/devrandom) **Created:** 10/24/2025 **Status:** ❌ Closed **Base:** `main` ← **Head:** `claude/integrate-deepseek-ocr-011CURd6ZNYLEHnxfT6CB6Hf` --- ### 📝 Commits (1) - [`281b2dd`](https://github.com/open-webui/open-webui/commit/281b2ddd4fd29113bc7c73f6aba8650cb39465ae) Add DeepSeek OCR integration for document processing ### 📊 Changes **5 files changed** (+478 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `backend/open_webui/config.py` (+37 -0) ➕ `backend/open_webui/retrieval/loaders/deepseek_ocr.py` (+372 -0) 📝 `backend/open_webui/retrieval/loaders/main.py` (+17 -0) 📝 `backend/open_webui/routers/retrieval.py` (+51 -0) 📝 `pyproject.toml` (+1 -0) </details> ### 📄 Description This commit integrates DeepSeek OCR as a new content extraction engine using vLLM server with OpenAI-compatible API. Changes: - Added DeepSeekOCRLoader class for API-based OCR processing - Supports PDF to image conversion with pdf2image - Returns LangChain Document objects with rich metadata - Supports various image formats - Added relevant configuration variables in config.py. - Integrated into loader factory (main.py): - Added to engine selection logic - Supports when CONTENT_EXTRACTION_ENGINE=deepseek_ocr - Updated retrieval router API: - Exposed DeepSeek OCR settings in GET /api/config/retrieval - Added form fields in POST /api/config/retrieval/update - Pass config to Loader in process_file() - Added pdf2image dependency for PDF processing Usage: Set environment variables: CONTENT_EXTRACTION_ENGINE=deepseek_ocr DEEPSEEK_OCR_API_BASE_URL=http://your-gpu-server:8000/v1 DEEPSEEK_OCR_API_KEY=your-secret-key 🤖 Generated with [Claude Code](https://claude.com/claude-code) # Pull Request Checklist ### Note to first-time contributors: Please open a discussion post in [Discussions](https://github.com/open-webui/open-webui/discussions) and describe your changes before submitting a pull request. **Before submitting, make sure you've checked the following:** - [ ] **Target branch:** Verify that the pull request targets the `dev` branch. Not targeting the `dev` branch may lead to immediate closure of the PR. - [ ] **Description:** Provide a concise description of the changes made in this pull request. - [ ] **Changelog:** Ensure a changelog entry following the format of [Keep a Changelog](https://keepachangelog.com/) is added at the bottom of the PR description. - [ ] **Documentation:** If necessary, update relevant documentation [Open WebUI Docs](https://github.com/open-webui/docs) like environment variables, the tutorials, or other documentation sources. - [ ] **Dependencies:** Are there any new dependencies? Have you updated the dependency versions in the documentation? - [ ] **Testing:** Perform manual tests to verify the implemented fix/feature works as intended AND does not break any other functionality. Take this as an opportunity to make screenshots of the feature/fix and include it in the PR description. - [ ] **Agentic AI Code:**: Confirm this Pull Request is **not written by any AI Agent** or has at least gone through additional human review **and** manual testing. If any AI Agent is the co-author of this PR, it may lead to immediate closure of the PR. - [ ] **Code review:** Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards? - [ ] **Title Prefix:** To clearly categorize this pull request, prefix the pull request title using one of the following: - **BREAKING CHANGE**: Significant changes that may affect compatibility - **build**: Changes that affect the build system or external dependencies - **ci**: Changes to our continuous integration processes or workflows - **chore**: Refactor, cleanup, or other non-functional code changes - **docs**: Documentation update or addition - **feat**: Introduces a new feature or enhancement to the codebase - **fix**: Bug fix or error correction - **i18n**: Internationalization or localization changes - **perf**: Performance improvement - **refactor**: Code restructuring for better maintainability, readability, or scalability - **style**: Changes that do not affect the meaning of the code (white space, formatting, missing semi-colons, etc.) - **test**: Adding missing tests or correcting existing tests - **WIP**: Work in progress, a temporary label for incomplete or ongoing work # Changelog Entry ### Description - [Concisely describe the changes made in this pull request, including any relevant motivation and impact (e.g., fixing a bug, adding a feature, or improving performance)] ### Added - [List any new features, functionalities, or additions] ### Changed - [List any changes, updates, refactorings, or optimizations] ### Deprecated - [List any deprecated functionality or features that have been removed] ### Removed - [List any removed features, files, or functionalities] ### Fixed - [List any fixes, corrections, or bug fixes] ### Security - [List any new or updated security-related changes, including vulnerability fixes] ### Breaking Changes - **BREAKING CHANGE**: [List any breaking changes affecting compatibility or functionality] --- ### Additional Information - [Insert any additional context, notes, or explanations for the changes] - [Reference any related issues, commits, or other relevant information] ### Screenshots or Videos - [Attach any relevant screenshots or videos demonstrating the changes] ### Contributor License Agreement By submitting this pull request, I confirm that I have read and fully agree to the [Contributor License Agreement (CLA)](https://github.com/open-webui/open-webui/blob/main/CONTRIBUTOR_LICENSE_AGREEMENT), and I am providing my contributions under its terms. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-04-25 12:58:09 -05:00

GiteaMirror closed this issue

2026-04-25 12:58:10 -05:00

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/open-webui#40481