How to Share a Perplexity Thread With a Public Link
🔍 WiseChecker

How to Share a Perplexity Thread With a Public Link

Official documentation checked October 14, 2026.

You can share a Perplexity conversation using its session-level sharing controls. “Thread” is the older term still found in many links and tutorials. Before enabling public access, review the entire conversation for private information, including follow-up questions and details quoted from files.

You do not have to delete the session to make it private again. Do not rely on an undocumented paid link-expiration button or a URL shortener as an access-control mechanism.

ADVERTISEMENT

1. Decide What the Recipient Should Be Able to See

A session can contain the initial question, follow-ups, answers and sources. Review that whole scope before sharing, not just the latest answer. Sensitive information can appear in generated prose even if the original attachment is not directly downloadable.

If the recipient needs only a short excerpt, prepare a reviewed copy in an approved document instead. A public conversation link may expose more context than you intend.

The official session guide distinguishes private access, access for anyone with the link and an organization-scoped option for Enterprise Pro. Use the narrowest option that actually fits the audience and is available to your account.

2. Share the Specific Session

  1. Open the intended session from your History and confirm that it is the correct conversation.
  2. Select Share at the top of the session. Mobile control placement may differ; inspect the current sharing panel rather than following an assumed identical menu.
  3. For intentionally public material, select Anyone with the link. Read the displayed scope before copying the link. Simply copying a private URL does not make it public.
  4. Copy the link through the available sharing control and send it only after reviewing the conversation.
  5. For a public link, test the exact URL in a signed-out or private browser context. For an organization-restricted link, have an authorized recipient test it instead of broadening the scope.

Do not paste a sensitive conversation into a public channel as a “test.” Link holders can forward the URL, so an unlisted link is not a promise that only your chosen recipient will see it.

ADVERTISEMENT

3. Stop Public Access Without Deleting the Research

Open the session’s Share panel and change it back to Private, as documented by Perplexity. Recheck the exact link outside your author session. This addresses public access while retaining the conversation in your own account.

This is different from deleting the session, which the official guide describes as unrecoverable. Do not use deletion merely because an older tutorial incorrectly says it is the only revocation method.

Changing access cannot recall screenshots, downloaded material, copied text or information another person already received. If you exposed confidential content, follow your organization’s incident process as well as restricting access.

The current source does not document the claimed Pro clock icon with one-hour, one-day and custom expiration choices. Do not buy a plan expecting those controls. Expiring a shortened URL also does not revoke the underlying Perplexity URL.

4. Distinguish a Shared Session From a Project

Projects have their own membership, role and file-sharing rules. Access to a conversation should not be interpreted as full access to the containing Project, nor should private Project membership be mistaken for public-link sharing.

In a public session, a reader can ask follow-up questions that create a separate session rather than editing your original. A separate session or exported document is not controlled by treating your original URL as an expiring token.

Do not promise that every attachment, profile field or connected-source result is always hidden. Inspect the actual shared view and assume that any visible answer text can disclose the underlying information.

ADVERTISEMENT

5. Troubleshoot the Audience, Not by Defaulting to Public

If a recipient cannot open the link, verify the complete copied URL, selected sharing scope and intended account or organization. A permission message may be the expected protection, not a fault to bypass.

If the page behaves inconsistently with its displayed setting, record the session URL and a redacted screenshot and use Help → Contact Support. Do not delete the research, publish private files elsewhere or expand organization access solely to make a link load.

ADVERTISEMENT

Did this guide solve your problem?