Overview
Open WebUI’s web search integration allows AI models to access real-time information from the internet, enhancing responses with current data, facts, and sources.Supported Search Providers
Open WebUI integrates with 15+ search providers, offering flexibility for different use cases and privacy preferences.Self-Hosted Options
SearXNG
Privacy-focused metasearch engine
- Aggregates results from multiple sources
- Self-hosted, no tracking
- Highly customizable
- Free and open source
YaCy
Decentralized search
- P2P search network
- Full control over infrastructure
- No central authority
Commercial APIs
Configuration
Basic Setup
Enable and configure web search through the admin panel:Provider-Specific Configuration
- SearXNG
- Google PSE
- Brave Search
- Tavily
- Perplexity
Advanced Settings
Performance
Security
Filtering
Processing
Web Content Loading
Loading Engines
Choose how web pages are fetched and processed:- Default
- Playwright
- Firecrawl
- External
Standard HTTP requests
- Fast and lightweight
- Works for most sites
- No JavaScript execution
Using Web Search in Chat
Basic Usage
Trigger web search by mentioning URLs or topics:Search Workflow
Search Execution
Query sent to configured search provider
- Returns top N results (configurable)
- Concurrent requests for multiple queries
Content Fetching
Web loader retrieves page content
- Parallel loading of multiple URLs
- Timeout protection
- SSL verification
Processing
Content prepared for RAG:
- Text extraction
- Chunking (if enabled)
- Embedding generation (if enabled)
YouTube Integration
Extract and search YouTube video transcripts:- Automatic transcript extraction
- Multi-language support
- Translation capabilities
- Proxy support for restricted regions
Domain Filtering
Control which domains are searched:When filter list is populated, only results from these domains are returned. Leave empty to search all domains.
Performance Optimization
Concurrent Requests
Balance speed and resource usage:- Small deployments: 2-3 concurrent searches, 3-5 loaders
- Medium deployments: 3-5 concurrent searches, 5-10 loaders
- Large deployments: 5-10 concurrent searches, 10-20 loaders
Timeouts
Bypass Options
Skip Web Loader
Use search results without fetching full content:- Search summaries sufficient
- Reduce API calls/bandwidth
- Faster responses needed
Skip Embedding
Disable RAG processing for web content:- Direct content injection
- Avoid embedding costs
- Real-time freshness required
External Search Integration
Connect custom search services:API Endpoints
Configuration
Update Configuration
Best Practices
Choose Right Provider
Consider:
- Privacy requirements
- Budget constraints
- Result quality needs
- Geographic coverage
- API rate limits
Optimize Result Count
Balance:
- More results = better coverage
- Fewer results = faster responses
- Recommended: 3-7 results
- Adjust based on use case
Use Domain Filtering
Benefits:
- Improve result quality
- Reduce irrelevant content
- Focus on trusted sources
- Faster processing
Monitor Costs
Track:
- API usage per provider
- Bandwidth consumption
- Processing time
- Set up alerts for limits
Troubleshooting
No search results returned
No search results returned
Check:
- Provider API key is valid
- Search engine is properly configured
- Rate limits not exceeded
- Domain filter not too restrictive
- Network connectivity to provider
Slow web loading
Slow web loading
Solutions:
- Reduce
WEB_LOADER_TIMEOUT - Increase concurrent requests
- Use faster web loader engine
- Enable
BYPASS_WEB_SEARCH_WEB_LOADER - Check network latency
SSL certificate errors
SSL certificate errors
Options:
- Ensure
ENABLE_WEB_LOADER_SSL_VERIFICATIONis true - Update CA certificates
- Configure proxy with valid certs
- For internal sites, use custom CA
YouTube videos not working
YouTube videos not working
Verify:
- Video has captions/transcript
- Language is in
YOUTUBE_LOADER_LANGUAGE - Proxy configured if in restricted region
- Video is publicly accessible
Security Considerations
URL Validation
Open WebUI validates URLs to prevent SSRF attacks:- Blocks private IP ranges (10.0.0.0/8, 192.168.0.0/16, etc.)
- Prevents localhost access
- Validates URL format
- Enforces timeout limits