Note to first-time contributors: Please open a discussion post in Discussions to discuss your idea/fix with the community before creating a pull request, and describe your changes before submitting a pull request.
This is to ensure large feature PRs are discussed with the community first, before starting work on it. If the community does not want this feature or it is not relevant for Open WebUI as a project, it can be identified in the discussion before working on the feature and submitting the PR.
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 will lead to immediate closure of the PR.
Description: Provide a concise description of the changes made in this pull request down below.
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
Added a new user setting "Default Upload Mode" in Settings > Interface > File section that allows users to configure whether uploaded files default to "Using Entire Document" (full context, bypasses RAG) or "Using Focused Retrieval" (RAG processing). This addresses the issue where files were automatically processed through RAG, causing delays with local models.
Added
New user setting defaultUploadContext with values 'full' or 'focused' to store the user's preferred default upload mode
New i18n translation strings: "Default Upload Mode", "Using Entire Document by Default", "Using Focused Retrieval by Default"
UI toggle in Settings > Interface > File section following the same clickable-word pattern as "Enter Key Behavior"
Changed
Updated Settings type in src/lib/stores/index.ts to include the new defaultUploadContext property
Modified FileItemModal.svelte to initialize the context toggle based on the user's default setting when a file has no explicit context
Additional Information
The original feature request (#18431) was specifically about new uploads defaulting to the user's preference, which is exactly what this implements.
The setting is persisted per user via the existing settings API
Individual files can still be toggled in the file modal for per-file control
Follows existing design patterns in the codebase for settings UI
The added user setting only affects the initial state of the toggle in the modal for files without an explicit context value. It doesn't override anything. Users can still change each file individually, and the per-file context property is preserved.
Default to using Focused Retrieval
Default to using Entire Document
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.
Note
Deleting the CLA section will lead to immediate closure of your PR and it will not be merged in.
🔄 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/20900
**Author:** [@silentoplayz](https://github.com/silentoplayz)
**Created:** 1/23/2026
**Status:** 🔄 Open
**Base:** `dev` ← **Head:** `feat/default-upload-mode-setting`
---
### 📝 Commits (1)
- [`428a943`](https://github.com/open-webui/open-webui/commit/428a943644b7ef598f76e7478b9810562e19f3a8) feat: add default upload mode setting
### 📊 Changes
**4 files changed** (+35 additions, -0 deletions)
<details>
<summary>View changed files</summary>
📝 `src/lib/components/chat/Settings/Interface.svelte` (+29 -0)
📝 `src/lib/components/common/FileItemModal.svelte` (+3 -0)
📝 `src/lib/i18n/locales/en-US/translation.json` (+1 -0)
📝 `src/lib/stores/index.ts` (+2 -0)
</details>
### 📄 Description
# Pull Request Checklist
### Note to first-time contributors: Please open a discussion post in [Discussions](https://github.com/open-webui/open-webui/discussions) to discuss your idea/fix with the community before creating a pull request, and describe your changes before submitting a pull request.
This is to ensure large feature PRs are discussed with the community first, before starting work on it. If the community does not want this feature or it is not relevant for Open WebUI as a project, it can be identified in the discussion before working on the feature and submitting the PR.
**Before submitting, make sure you've checked the following:**
- [x] **Target branch:** Verify that the pull request targets the `dev` branch. **Not targeting the `dev` branch will lead to immediate closure of the PR.**
- [x] **Description:** Provide a concise description of the changes made in this pull request down below.
- [x] **Changelog:** Ensure a changelog entry following the format of [Keep a Changelog](https://keepachangelog.com/) is added at the bottom of the PR description.
- [x] **Documentation:** If necessary, update relevant documentation [Open WebUI Docs](https://github.com/open-webui/docs) like environment variables, the tutorials, or other documentation sources.
- [x] **Dependencies:** Are there any new dependencies? Have you updated the dependency versions in the documentation?
- [x] **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**.
- [x] **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.
- [x] **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?
- [x] **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
- Added a new user setting "Default Upload Mode" in Settings > Interface > File section that allows users to configure whether uploaded files default to "Using Entire Document" (full context, bypasses RAG) or "Using Focused Retrieval" (RAG processing). This addresses the issue where files were automatically processed through RAG, causing delays with local models.
### Added
- New user setting `defaultUploadContext` with values 'full' or 'focused' to store the user's preferred default upload mode
- New i18n translation strings: "Default Upload Mode", "Using Entire Document by Default", "Using Focused Retrieval by Default"
- UI toggle in Settings > Interface > File section following the same clickable-word pattern as "Enter Key Behavior"
### Changed
- Updated `Settings` type in `src/lib/stores/index.ts` to include the new `defaultUploadContext` property
- Modified `FileItemModal.svelte` to initialize the context toggle based on the user's default setting when a file has no explicit context
---
### Additional Information
- The original feature request (#18431) was specifically about new uploads defaulting to the user's preference, which is exactly what this implements.
- The setting is persisted per user via the existing settings API
- Individual files can still be toggled in the file modal for per-file control
- Follows existing design patterns in the codebase for settings UI
- The added user setting only affects the **initial state** of the toggle in the modal for files without an explicit `context` value. It doesn't override anything. Users can still change each file individually, and the per-file `context` property is preserved.
### Default to using `Focused Retrieval`
<img width="1369" height="792" alt="image" src="https://github.com/user-attachments/assets/17b5deac-bccb-4c6e-8ccd-ce2c8041bd11" />
<img width="930" height="546" alt="image" src="https://github.com/user-attachments/assets/8e64e0c3-4037-4650-a2f9-2abc179cf208" />
### Default to using `Entire Document`
<img width="1369" height="792" alt="image" src="https://github.com/user-attachments/assets/b2852f76-26b7-449f-8474-f7a870e7ae66" />
<img width="930" height="546" alt="image" src="https://github.com/user-attachments/assets/914a9130-997e-490f-8c51-6ed9d6d5fa5f" />
### 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.
> [!NOTE]
> Deleting the CLA section will lead to immediate closure of your PR and it will not be merged in.
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/open-webui/open-webui/pull/20900
Author: @silentoplayz
Created: 1/23/2026
Status: 🔄 Open
Base:
dev← Head:feat/default-upload-mode-setting📝 Commits (1)
428a943feat: add default upload mode setting📊 Changes
4 files changed (+35 additions, -0 deletions)
View changed files
📝
src/lib/components/chat/Settings/Interface.svelte(+29 -0)📝
src/lib/components/common/FileItemModal.svelte(+3 -0)📝
src/lib/i18n/locales/en-US/translation.json(+1 -0)📝
src/lib/stores/index.ts(+2 -0)📄 Description
Pull Request Checklist
Note to first-time contributors: Please open a discussion post in Discussions to discuss your idea/fix with the community before creating a pull request, and describe your changes before submitting a pull request.
This is to ensure large feature PRs are discussed with the community first, before starting work on it. If the community does not want this feature or it is not relevant for Open WebUI as a project, it can be identified in the discussion before working on the feature and submitting the PR.
Before submitting, make sure you've checked the following:
devbranch. Not targeting thedevbranch will lead to immediate closure of the PR.Changelog Entry
Description
Added
defaultUploadContextwith values 'full' or 'focused' to store the user's preferred default upload modeChanged
Settingstype insrc/lib/stores/index.tsto include the newdefaultUploadContextpropertyFileItemModal.svelteto initialize the context toggle based on the user's default setting when a file has no explicit contextAdditional Information
contextvalue. It doesn't override anything. Users can still change each file individually, and the per-filecontextproperty is preserved.Default to using
Focused RetrievalDefault to using
Entire DocumentContributor 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.