Perplexity Collection Not Saving Thread History: Fix

You create a Perplexity Collection to organize your research threads, but the threads you add disappear after you close the browser or refresh the page. This problem occurs when the browser’s local storage becomes corrupted or when the user account sync fails to write thread metadata to Perplexity’s servers. This article explains the root cause and provides four tested fixes to restore thread saving in your Collections.

Why Perplexity Collections Fail to Save Thread History

Perplexity Collections store thread metadata in two places: the browser’s local storage for quick access and Perplexity’s cloud servers for cross-device sync. When you add a thread to a Collection, the browser sends a POST request to the Perplexity API with the thread ID and Collection ID. If either the local storage write fails or the API response is blocked, the thread appears saved temporarily but disappears on reload.

The most common triggers for this failure are:

Corrupted Browser Local Storage

Perplexity uses IndexedDB and localStorage to cache Collection data. If these storage areas become corrupted due to a partial write or a browser crash, the save operation silently fails. The thread never reaches the server, so it vanishes after refresh.

Session Token Expiration or Mismatch

Your Perplexity session token authenticates every API request. If the token expires or gets out of sync with the server, the save request returns a 401 or 403 error. The browser does not display this error, but the thread does not persist.

Browser Extension Interference

Extensions that modify page content or block network requests can stop the save API call from completing. Ad blockers, script blockers, and privacy extensions are the usual culprits.

Steps to Fix Perplexity Collection Not Saving Threads

Follow these fixes in order. Test after each step by adding a thread to a Collection and refreshing the page.

1. Clear browser cache and cookies for perplexity.ai
   Open your browser settings and navigate to Privacy and Security > Clear browsing data. Select “Cookies and other site data” and “Cached images and files.” Set the time range to “All time.” Click “Clear data.” Then reload Perplexity and log in again.
2. Log out and log back into your Perplexity account
   Click your profile avatar in the bottom-left corner of the Perplexity interface. Select “Log out.” Wait 10 seconds, then log in with your email or Google account. This refreshes your session token and forces a full sync of Collection data from the server.
3. Disable browser extensions temporarily
   Open your browser’s extension manager. Disable all extensions, especially ad blockers, script blockers, and privacy tools. Restart the browser. Test the save function. If it works, re-enable extensions one by one to find the culprit.
4. Use incognito or private browsing mode
   Open a new incognito window (Ctrl+Shift+N in Chrome, Ctrl+Shift+P in Firefox). Log into Perplexity and try adding a thread to a Collection. If it saves correctly, the problem is caused by an extension or corrupted profile data. Switch to a clean browser profile for regular use.
5. Update your browser to the latest version
   An outdated browser can have bugs that break IndexedDB operations. Go to browser settings > About and check for updates. Install any pending updates and restart the browser.
6. Try a different browser
   If the issue persists across incognito mode and after clearing cache, install a second browser such as Firefox or Edge. Log into Perplexity there. If Collections save correctly, the original browser has a deeper storage issue. Consider resetting the browser or reinstalling it.

If Perplexity Still Has Issues After the Main Fix

Threads Disappear From Existing Collections

If threads that were previously saved now show as missing, the problem is likely a server sync failure. Refresh the page, then click the “Collections” tab in the left sidebar. Look for a small refresh icon next to the Collection name. Click it to force a manual sync from the server. If the threads do not reappear, contact Perplexity support and provide the Collection name and the approximate date the threads were added.

Collection Creation Works But Threads Do Not Save

This indicates that the Collection metadata writes correctly, but the thread-to-Collection mapping fails. Open the browser developer console (F12) and go to the Network tab. Add a thread to a Collection. Look for a POST request to “/api/collections/add-thread” or similar. If the response shows a 500 error, the issue is on Perplexity’s server side. Wait a few hours and try again. If the error persists, report it to Perplexity.

Only Some Threads Fail to Save

If threads with long content or many sources fail to save, the thread body may exceed Perplexity’s internal size limit for Collection entries. Shorten the thread by editing it, or split the content into multiple threads. Then try saving again.

Perplexity Free vs Pro: Collection Features and Limits

Item	Perplexity Free	Perplexity Pro
Number of Collections	Unlimited	Unlimited
Threads per Collection	Up to 50	Up to 500
Thread history retention	7 days	Unlimited
Cross-device sync	Yes	Yes
Export Collections	No	CSV export

If you are on the Free plan and exceed the 7-day retention limit, threads older than 7 days will disappear from Collections automatically. Upgrade to Pro to retain all thread history indefinitely.

Now you can fix Collection thread history loss by clearing cache, refreshing your session, and disabling conflicting extensions. If the problem persists, use the browser developer console to inspect API errors and report them to Perplexity support. For a long-term solution, switch to a browser profile with no extensions and keep your browser updated to the latest version.