When you submit a query to Perplexity, the search process sometimes stops at the “Reading Sources” stage and never completes. This leaves you staring at a frozen progress indicator with no answer. The problem usually stems from a stalled connection to Perplexity’s source servers, a corrupted browser cache, or an extension interfering with the page’s scripts. This article explains the root causes and provides step-by-step fixes you can apply right now.
Key Takeaways: Fixing Perplexity Hanging on “Reading Sources”
- Ctrl + Shift + R (hard refresh): Forces the browser to reload the page from the server instead of using cached files.
- Browser Settings > Privacy and Security > Clear Browsing Data: Removes corrupted cache and cookies that block source loading.
- Disable browser extensions one by one: Ad blockers and script blockers often prevent Perplexity from fetching source content.
Why Perplexity Stops at “Reading Sources”
When you type a question, Perplexity sends it to its AI model and then fetches supporting web pages to verify the answer. The “Reading Sources” stage is the moment when the browser downloads those external pages. If a source server is slow, the connection times out, or your browser blocks the request, the process appears to hang indefinitely.
Common technical causes include:
- Stale or corrupted browser cache. Old files conflict with the latest Perplexity scripts.
- Browser extensions that block scripts or ads. uBlock Origin, Ghostery, or similar tools can stop source loading.
- Slow or unstable internet connection. The source fetch times out before completing.
- Perplexity server-side issues. Rare, but the service may be temporarily overloaded.
Steps to Unstick Perplexity From “Reading Sources”
Method 1: Hard Refresh the Page
A hard refresh bypasses the browser cache and reloads the page directly from Perplexity’s servers. This fixes most temporary hang-ups.
- Press Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac)
This shortcut forces the browser to ignore cached files and fetch the entire page anew. - Wait for the page to reload completely
Type your query again if the input field is empty. The search should now progress past “Reading Sources.”
Method 2: Clear Browser Cache and Cookies
If a hard refresh does not help, corrupted cache or cookies are the likely culprit. Clearing them removes any broken data that interferes with source loading.
- Open your browser’s settings menu
In Chrome, click the three-dot menu at the top right and select Settings. In Edge, use the three-dot menu and choose Settings. In Firefox, open the menu and select Options. - Navigate to Privacy and Security
In Chrome, go to Privacy and Security > Clear Browsing Data. In Edge, go to Privacy, Search, and Services > Choose what to clear. In Firefox, go to Privacy and Security > Cookies and Site Data > Clear Data. - Select a time range of “All time”
Check the boxes for “Cookies and other site data” and “Cached images and files.” Uncheck other items unless you want to clear passwords or history. - Click Clear Data or Clear Now
Wait for the process to finish. Reload Perplexity and try your search again.
Method 3: Disable Browser Extensions Temporarily
Extensions that block ads, scripts, or trackers often prevent Perplexity from loading external sources. Test by disabling all extensions and then re-enabling them one by one.
- Open your browser’s extension manager
In Chrome, typechrome://extensionsin the address bar. In Edge, typeedge://extensions. In Firefox, typeabout:addons. - Toggle off all extensions
Use the switch or disable button next to each extension to turn them off. - Reload Perplexity and run a test search
If the search completes, one of the extensions was causing the problem. Re-enable extensions one at a time, testing after each, until you find the culprit. - Keep the problematic extension disabled or whitelist Perplexity
For ad blockers, addperplexity.aiand all subdomains to the allowlist or whitelist.
Method 4: Switch to a Different Browser or Device
If the issue persists, test Perplexity in another browser or on another device. This helps determine if the problem is browser-specific or device-specific.
- Open Perplexity in a browser you rarely use
For example, if you normally use Chrome, try Edge, Firefox, or Brave. - Log in to your Perplexity account if needed
Run the same query that caused the hang. If it works, the original browser has a deeper configuration issue. - Reset the original browser’s settings
In Chrome, go to Settings > Reset and clean up > Restore settings to their original defaults. In Edge, go to Settings > Reset settings > Restore settings to their default values.
If Perplexity Still Hangs After the Main Fix
“Reading Sources” Stuck on Mobile
On the Perplexity mobile app, the same hang can occur. Force-close the app from your device’s app switcher. Then clear the app cache in your phone’s settings (Android: Settings > Apps > Perplexity > Storage > Clear Cache; iOS: Offload the app via Settings > General > iPhone Storage > Perplexity > Offload App, then reinstall).
Search Works in Incognito Mode but Not Normal Mode
This indicates a browser extension or cached data is causing the problem. Open an incognito or private window and test Perplexity. If it works, follow Method 3 to disable extensions, and clear your cache using Method 2.
Perplexity Server Outage
Sometimes the hang is not on your end. Check Perplexity’s status page at status.perplexity.ai or visit a third-party site like Downdetector. If an outage is confirmed, wait for Perplexity to resolve it. No local fix will work during a server outage.
Perplexity Free vs Pro: Source Fetching Differences
| Item | Perplexity Free | Perplexity Pro |
|---|---|---|
| Number of sources fetched per query | Up to 5 | Up to 10 |
| Source types | Web pages and news articles | Web pages, news, academic papers, and social media |
| Source loading timeout | 30 seconds | 60 seconds |
| Priority support for loading issues | Standard support | Priority support via email |
The “Reading Sources” hang can affect both Free and Pro users equally. Pro users get a longer timeout, which reduces the chance of a timeout-related hang but does not eliminate it entirely. If you are a Pro user and the hang persists, contact Perplexity support directly through the Pro support channel.
You can now troubleshoot and fix the “Reading Sources” hang using hard refresh, cache clearing, or extension management. If the problem returns, check for browser updates or try a different browser entirely. For persistent issues, consider switching to the Perplexity desktop app or using the mobile app as a fallback. Remember to whitelist Perplexity in your ad blocker to prevent future source-loading failures.