When you ask Perplexity a question, the response may stop at a red banner that says “Sources failed to load.” This means the search engine could not retrieve the web pages or documents it needs to cite. The error can happen due to network interruptions, browser cache conflicts, or server-side restrictions. This article explains the root causes and provides a clear set of diagnostic steps to resolve the problem.
Key Takeaways: Fixing the “Sources Failed to Load” Error in Perplexity
- Clear browser cache and cookies: Stale or corrupted site data often blocks source loading for Perplexity.
- Disable VPN or proxy extensions: Some VPNs or ad blockers prevent Perplexity from reaching its source URLs.
- Switch to a different browser or incognito mode: Isolating the issue from extensions or cached data helps pinpoint the cause.
Why Perplexity Cannot Load Sources
Perplexity relies on live web crawling to fetch the content behind each source link it displays. When you submit a query, the service sends multiple HTTP requests to the URLs it plans to cite. If any of those requests fail, the system shows the “Sources failed to load” message instead of the source previews.
The failure can originate from three layers:
Network-Level Blocking
Corporate networks, school Wi-Fi, or home routers sometimes block outbound connections to unknown domains. VPNs and proxy services can also interfere by routing traffic through servers that the target websites reject. If the source website uses a strict Content Delivery Network (CDN), it may block the VPN exit node.
Browser-Side Conflicts
Browser extensions such as ad blockers, script blockers, or privacy tools can prevent JavaScript or image requests from loading. A corrupted cache or outdated cookies for the Perplexity domain can also cause the source retrieval script to fail.
Server-Side Restrictions
The target websites themselves may block Perplexity’s crawler via robots.txt rules or IP bans. This is rare but happens with paywalled or heavily protected sites. When the crawler receives a 403 or 404 status, Perplexity shows the error.
Diagnostic Steps to Resolve the Error
Follow these steps in order. Test after each step by asking a simple question like “What is the weather in London?” to see if the error persists.
- Refresh the page
Press F5 or click the refresh icon in your browser. A temporary network glitch may have interrupted the source request. If the error disappears, no further action is needed. - Clear browser cache and cookies for Perplexity
Open your browser settings. Find the privacy or history section. Clear cached images and files along with cookies for the site perplexity.ai. After clearing, reload Perplexity and sign in again. - Disable browser extensions
Temporarily turn off ad blockers (uBlock Origin, AdBlock Plus), privacy extensions (Privacy Badger, Ghostery), and script blockers (NoScript). Reload the page and test. If the error goes away, re-enable extensions one by one to identify the culprit. - Turn off VPN or proxy
Disconnect from your VPN service or disable any system-wide proxy. Try the query again. If the error resolves, your VPN exit node may be blocked by source websites. Switch to a different VPN server or use a split-tunneling feature that excludes Perplexity. - Use incognito or private mode
Open a new incognito window (Ctrl+Shift+N in Chrome, Ctrl+Shift+P in Firefox). Navigate to Perplexity and ask your question. If the error does not appear, the problem is caused by cached data or an extension active in your regular browser session. - Try a different browser
Switch to a browser you rarely use, such as Edge, Brave, or Firefox. Test the query. If the error is gone, the original browser may have a corrupted profile or a persistent extension conflict. - Check your network connection
Open a command prompt (Windows) or terminal (Mac). Run ping 8.8.8.8 to test basic internet connectivity. Then run nslookup perplexity.ai to confirm DNS resolution works. If either command fails, restart your router or contact your ISP. - Disable firewall or security software temporarily
Some antivirus suites include web shields that block certain HTTP requests. Pause the security software for 60 seconds and test Perplexity. If the error disappears, add perplexity.ai and its subdomains to the software’s allowed list. - Switch from Wi-Fi to wired or mobile hotspot
Connect your computer to a different network. If the error resolves, your original network has restrictions. Contact your network administrator or change Wi-Fi channels to avoid interference. - Update your browser to the latest version
Outdated browsers may lack support for modern TLS certificates or HTTP protocols that Perplexity’s source crawler uses. Check your browser’s About page and install any pending updates.
If Perplexity Still Cannot Load Sources After All Steps
The Error Appears Only for Certain Queries
Some queries trigger sources behind paywalls or login gates. For example, asking about a news article behind a subscription wall may fail. Try rephrasing the question to avoid specific paywalled URLs.
The Error Appears on Mobile But Not Desktop
Mobile browsers often have aggressive data-saving features that block background requests. On Android, go to Settings > Connections > Data usage > Data saver and turn it off. On iOS, go to Settings > Cellular > Cellular Data Options and disable Low Data Mode.
The Error Appears Only in the Perplexity Desktop App
The desktop app uses an embedded WebView that may have its own cache. Clear the app’s cache from the application settings (Windows: Settings > Apps > Perplexity > Advanced options > Reset).
Perplexity Server Outage
Rarely, the error is caused by a server-side failure at Perplexity. Check the Perplexity status page or community forums. If others report the same issue, wait for the engineering team to deploy a fix.
Perplexity Source Loading: Desktop App vs Browser
| Item | Desktop App (Windows/Mac) | Browser (Chrome, Edge, Firefox) |
|---|---|---|
| Cache location | App data folder (e.g., %AppData%\Perplexity) | Browser profile cache |
| Extension interference | None by default | Possible from ad blockers and privacy tools |
| VPN/proxy effect | Uses system proxy settings | Uses system proxy or browser proxy settings |
| Incognito mode | Not available | Available as a separate session |
| Update method | Auto-update from Microsoft Store or direct download | Browser auto-updates |
You can now diagnose and fix the “Sources failed to load” error on Perplexity using the ten-step sequence above. Start with the simplest fix — a page refresh — and escalate only if needed. If the error persists across all networks and devices, report the issue to Perplexity support with the exact query text and a screenshot of the error banner. As an advanced tip, you can open the browser developer console (F12) and look for red HTTP 403 or 404 errors in the Network tab to identify exactly which source URL failed.