open-webui · pratikgx · Sep 28, 2026
diff --git a/docs/alternatives/onyx.mdx b/docs/alternatives/onyx.mdx
@@ -33,7 +33,7 @@ If something here is wrong or has aged badly, including in Onyx's favour, [tell
 
 ## What Onyx Does Well
 
-- **Enterprise connectors**, [40+ by Onyx's count](https://docs.onyx.app/connectors/overview), with native integrations for Slack, Google Drive, Confluence, Jira, GitHub, Notion, and more
+- **Enterprise connectors**, [40+ by Onyx's count](https://docs.onyx.app/admins/connectors/overview), with native integrations for Slack, Google Drive, Confluence, Jira, GitHub, Notion, and more
 - **Automatic syncing** that keeps connected sources up to date without manual re-ingestion
 - **Permission-aware retrieval** that respects source system access controls when returning search results
 - **Enterprise search** purpose-built for searching across your organization's internal knowledge

diff --git a/...tures/chat-conversations/audio/text-to-speech/chatterbox-tts-api-integration.md b/...tures/chat-conversations/audio/text-to-speech/chatterbox-tts-api-integration.md
@@ -36,7 +36,7 @@ This tutorial is a community contribution and is not supported by the Open WebUI
 
 :::info
 
-Chatterbox can use a good deal of memory and has hardware requirements that might be higher than you're used to with other local TTS solutions. If you have trouble meeting the requirements, you might find [OpenAI Edge TTS](https://docs.openwebui.com/tutorials/text-to-speech/openai-edge-tts-integration) or [Kokoro-FastAPI](https://docs.openwebui.com/tutorials/text-to-speech/Kokoro-FastAPI-integration) to be suitable replacements.
+Chatterbox can use a good deal of memory and has hardware requirements that might be higher than you're used to with other local TTS solutions. If you have trouble meeting the requirements, you might find [OpenAI Edge TTS](https://docs.openwebui.com/features/chat-conversations/audio/text-to-speech/openai-edge-tts-integration) or [Kokoro-FastAPI](https://docs.openwebui.com/features/chat-conversations/audio/text-to-speech/Kokoro-FastAPI-integration) to be suitable replacements.
 
 :::
 

diff --git a/docs/features/chat-conversations/rag/document-extraction/mistral-ocr.md b/docs/features/chat-conversations/rag/document-extraction/mistral-ocr.md
@@ -52,7 +52,7 @@ Open WebUI sends only `.pdf` uploads to Mistral OCR. Every other file type, imag
 
 ## Verifying Mistral OCR
 
-To verify that Mistral OCR is working correctly in script, please refer to `https://docs.mistral.ai/capabilities/document/`
+To verify that Mistral OCR is working correctly in script, please refer to `https://docs.mistral.ai/capabilities/document_ai/basic_ocr/`
 
 ### Conclusion
 

diff --git a/docs/features/chat-conversations/web-search/providers/linkup.md b/docs/features/chat-conversations/web-search/providers/linkup.md
@@ -77,7 +77,7 @@ These map to the [`LINKUP_SEARCH_PARAMS`](/reference/env-configuration#linkup_se
 -e LINKUP_SEARCH_PARAMS='{"depth": "deep", "outputType": "searchResults"}'
 ```
 
-The same JSON object is exposed as the single **Parameters** field in the Admin UI when the `linkup` engine is selected, so you do not need environment variables unless you prefer to manage configuration that way. See [Environment Variable Configuration](https://docs.openwebui.com/environment) for details and the [`ENABLE_PERSISTENT_CONFIG`](/reference/env-configuration#enable_persistent_config) behavior.
+The same JSON object is exposed as the single **Parameters** field in the Admin UI when the `linkup` engine is selected, so you do not need environment variables unless you prefer to manage configuration that way. See [Environment Variable Configuration](https://docs.openwebui.com/reference/env-configuration) for details and the [`ENABLE_PERSISTENT_CONFIG`](/reference/env-configuration#enable_persistent_config) behavior.
 
 ## Troubleshooting
 

diff --git a/docs/features/chat-conversations/web-search/providers/tavily.md b/docs/features/chat-conversations/web-search/providers/tavily.md
@@ -77,7 +77,7 @@ Ensure you have:
   -e TAVILY_API_KEY="your_tavily_api_key"
   ```
 
-  See [Environment Variable Configuration](https://docs.openwebui.com/environment).
+  See [Environment Variable Configuration](https://docs.openwebui.com/reference/env-configuration).
 - **RAG Integration**: Combine Tavily results with local data using Retrieval Augmented Generation. Refer to [RAG Documentation](https://docs.openwebui.com/features/chat-conversations/rag).
 
 ## Troubleshooting
@@ -91,7 +91,7 @@ For further help, visit the [Open WebUI Community](https://openwebui.com/search)
 
 ## Additional Resources
 
-- [Tavily API Documentation](https://docs.tavily.com/docs/introduction): API reference and advanced options.
+- [Tavily API Documentation](https://docs.tavily.com/welcome): API reference and advanced options.
 - [Open WebUI Features](https://docs.openwebui.com/features): Details on RAG and web search.
 - [Contributing to Open WebUI](https://docs.openwebui.com/contributing): Share improvements or report issues.
 

diff --git a/docs/features/extensibility/plugin/functions/action.mdx b/docs/features/extensibility/plugin/functions/action.mdx
@@ -75,7 +75,7 @@ Actions can utilize Open WebUI's real-time event system for interactive experien
 
 ### Event Emitter (`__event_emitter__`)
 
-**For more information about Events and Event emitters, see [Events and Event Emitters](https://docs.openwebui.com/features/extensibility/plugin/events/).**
+**For more information about Events and Event emitters, see [Events and Event Emitters](https://docs.openwebui.com/features/extensibility/plugin/development/events).**
 
 Send real-time updates to the frontend during action execution:
 

diff --git a/docs/features/extensibility/plugin/tools/development.mdx b/docs/features/extensibility/plugin/tools/development.mdx
@@ -111,7 +111,7 @@ Below is a list of optional arguments your tools can depend on:
 - `__request__`: The FastAPI request
 - `__oauth_token__`: A dictionary containing the user's valid, automatically refreshed OAuth token payload. This is the **new, recommended, and secure** way to access user tokens for making authenticated API calls. The dictionary typically contains `access_token`, `id_token`, and other provider-specific data.
 
-For more information about `__oauth_token__` and how to configure this token to be sent to tools, check out the OAuth section in the [environment variable docs page](https://docs.openwebui.com/reference/env-configuration/) and the [SSO documentation](https://docs.openwebui.com/features/auth/).
+For more information about `__oauth_token__` and how to configure this token to be sent to tools, check out the OAuth section in the [environment variable docs page](https://docs.openwebui.com/reference/env-configuration/) and the [SSO documentation](https://docs.openwebui.com/features/authentication-access/).
 
 Just add them as argument to any method of your Tool class just like `__user__` in the example above. `__messages__` and `__files__` are refreshed before every native tool call. The others are fixed when the request starts.
 

diff --git a/...ting-started/quick-start/connect-a-provider/starting-with-openai-compatible.mdx b/...ting-started/quick-start/connect-a-provider/starting-with-openai-compatible.mdx
@@ -244,7 +244,7 @@ Each connection has a **toggle switch** that lets you enable or disable it witho
   | Setting | Value |
   |---|---|
   | **URL** | `https://ai-gateway.vercel.sh/v1` |
-  | **API Key** | Your AI Gateway API key from the [Vercel dashboard](https://vercel.com/docs/ai-gateway/authentication/api-keys) |
+  | **API Key** | Your AI Gateway API key from the [Vercel dashboard](https://vercel.com/docs/ai-gateway/authentication) |
   | **Model IDs** | Auto-detected; optionally filter to specific gateway model IDs such as `anthropic/claude-opus-5` |
 
   :::tip

diff --git a/docs/troubleshooting/connection-error.mdx b/docs/troubleshooting/connection-error.mdx
@@ -258,7 +258,7 @@ If Open WebUI cannot reach Ollama, it's likely because Ollama is only listening
 2. **Ensure the variable is set** in your deployment environment (systemd service, Docker, shell profile).
 3. **Restart Ollama** for the change to take effect.
 
-Verify connectivity by accessing the WebUI interface after restarting. For detailed instructions, see the [Ollama documentation](https://github.com/ollama/ollama/blob/main/docs/faq.md#setting-environment-variables-on-linux).
+Verify connectivity by accessing the WebUI interface after restarting. For detailed instructions, see the [Ollama documentation](https://github.com/ollama/ollama/blob/main/docs/faq.mdx#setting-environment-variables-on-linux).
 
 ### Docker Connection Error
 

diff --git a/docs/tutorials/integrations/dev-tools/continue-dev.md b/docs/tutorials/integrations/dev-tools/continue-dev.md
@@ -79,7 +79,7 @@ version: 1.0.0
 schema: v1
 ```
 
-The context section provides additional information to the models. Find more information in the [official config guide](https://docs.continue.dev/reference#context) and in the [context provider guide](https://docs.continue.dev/customize/custom-providers).
+The context section provides additional information to the models. Find more information in the [official config guide](https://docs.continue.dev/reference#context) and in the [context provider guide](https://docs.continue.dev/customize/model-providers/overview).
 
 ```yaml
 context:
@@ -140,7 +140,7 @@ model: qwen3.6:27b
 
 ### Legacy completions endpoint
 
-This setting is not needed for Open WebUI, though more information is available in the [original guide](https://platform.openai.com/docs/guides/completions/completions-api-legacy).
+This setting is not needed for Open WebUI, though more information is available in the [original guide](https://platform.openai.com/docs/guides/completions).
 
 ```yaml
 env:

diff --git a/docs/tutorials/integrations/dev-tools/iterm2.md b/docs/tutorials/integrations/dev-tools/iterm2.md
@@ -98,7 +98,7 @@ You can find more information about the URLs in the [API Endpoints guide](/refer
 
 ### Legacy Completions API
 
-This setting is not needed for Open WebUI, though more information is available in the [original guide](https://platform.openai.com/docs/guides/completions/completions-api-legacy).
+This setting is not needed for Open WebUI, though more information is available in the [original guide](https://platform.openai.com/docs/guides/completions).
 
 ---
-Original file line number
+Diff line change
@@ Expand Up @@
     :::info
-    Chatterbox can use a good deal of memory and has hardware requirements that might be higher than you're used to with other local TTS solutions. If you have trouble meeting the requirements, you might find [OpenAI Edge TTS](https://docs.openwebui.com/tutorials/text-to-speech/openai-edge-tts-integration) or [Kokoro-FastAPI](https://docs.openwebui.com/tutorials/text-to-speech/Kokoro-FastAPI-integration) to be suitable replacements.
+    Chatterbox can use a good deal of memory and has hardware requirements that might be higher than you're used to with other local TTS solutions. If you have trouble meeting the requirements, you might find [OpenAI Edge TTS](https://docs.openwebui.com/features/chat-conversations/audio/text-to-speech/openai-edge-tts-integration) or [Kokoro-FastAPI](https://docs.openwebui.com/features/chat-conversations/audio/text-to-speech/Kokoro-FastAPI-integration) to be suitable replacements.
     :::
@@ Expand Down @@