TL;DR

Perplexity's built-in Export → PDF is the fastest route and it keeps the numbered citation markers, but it renders the sources as plain text — the links stop being clickable, and the source cards at the top of the answer are dropped. If the citations are the reason you're saving the answer, use Chrome's print dialog or Convert: Web to PDF, both of which produce a real PDF with live, clickable source URLs. The extension additionally captures the full scroll — every follow-up turn in the thread, plus the "Sources" panel — in one file, which is where Ctrl+P tends to clip.

One thing worth being clear about up front: a PDF of a Perplexity answer is a dated snapshot for your own records, not a citable primary source. Cite the underlying sources, not the answer. More on that below.

Why citations are the whole problem

Saving a ChatGPT or Gemini conversation is mostly a layout problem — you want the text and the code blocks to come out intact. Perplexity is different. The answer body is the least valuable part of the page. What you actually need six months later is:

  1. Which sources it drew from — the numbered list, in order.
  2. The URLs behind those numbers — resolvable, not truncated to "reuters.com…".
  3. Which claim mapped to which source — the inline [1] [3] markers sitting next to the sentence they support.
  4. When you ran it — because Perplexity re-runs the search each time and the answer changes.

Lose any one of those and the archive is close to worthless. A screenshot loses 2 and 4. A copy-paste into a doc usually loses 2 and 3. This is why "just take a screenshot" is bad advice for Perplexity specifically, even though it's tolerable for a plain chatbot transcript.

Method 1: Perplexity's built-in export

Perplexity ships an export, and for a lot of people it's enough.

  1. Open the thread on perplexity.ai
  2. Click the share / export control at the top-right of the answer block
  3. Choose Export → PDF

What you get is a clean, readable document with the answer text and the numbered markers preserved inline. What you don't get:

  • Clickable links. The source list is rendered as text. You can read the domain; you can't click through, and long URLs are frequently truncated with an ellipsis, which makes them unrecoverable.
  • The source cards. The row of preview cards Perplexity shows above the answer doesn't make it into the export.
  • Follow-up turns, reliably. Long threads with several follow-up questions sometimes export only the current answer rather than the whole thread. Check the page count before you close the tab.
  • Images and generated charts are inconsistent.

It's the right tool when you want the prose and you're going to re-find the sources yourself anyway.

Method 2: Ctrl+P → Save as PDF

Chrome's own print pipeline gives you something the built-in export doesn't: real hyperlinks. Chrome's print-to-PDF preserves <a href> as a PDF link annotation, so the numbered citations remain clickable in the output.

  1. Open the thread
  2. Expand the Sources panel so it's rendered in the DOM
  3. Scroll the full thread to the bottom first — this matters, see below
  4. Ctrl+P (Windows/Linux) or Cmd+P (Mac)
  5. Destination → Save as PDF
  6. Under More settings, enable Background graphics if you want the source cards to keep their borders

Where it breaks down:

  • Sticky headers. Perplexity's top bar is fixed-position, and Chrome sometimes stamps it onto every page of the PDF.
  • Clipping. Very long threads with many follow-ups can truncate, because the print engine snapshots what the page reports as its height, and lazily-mounted turns further up may not be measured correctly.
  • Collapsed sources. Anything behind a "show more" control is not in the DOM and therefore not in the PDF. Expand everything first.

For a single-answer thread, Ctrl+P is genuinely fine and costs nothing.

Method 3: Convert: Web to PDF

This is the method to reach for when the thread is long, or when the citation panel is the point.

  1. Install Convert: Web to PDF
  2. Open the Perplexity thread and scroll to the bottom once, so every follow-up turn has mounted
  3. Expand the Sources panel and any "show more" toggles
  4. Click the extension icon
  5. Optionally click Remove elements to delete the sticky header, the input box, and the sidebar — each click removes one, and there's an undo
  6. Pick your paper size (A4 or Letter; A3 is there if you want fewer page breaks in a long thread)
  7. Download

You get a true PDF: selectable text, embedded fonts, and working hyperlinks on every citation, because it uses Chrome's own print engine rather than rasterising the page. Everything runs locally in your browser — the page is never uploaded to a server, which also means it works on a thread in a logged-in Perplexity Pro account, where a server-side "paste a URL" converter would just get a login wall.

Two honest caveats:

  • Article Mode is the wrong choice here. It runs a Readability-style extraction to strip everything but the main content — which on Perplexity tends to take the sources panel with it. Use the default mode.
  • It captures what's loaded. If you didn't scroll and expand, it can't invent the content. Scroll first.

Method 4: Copy the markdown

Underrated for anyone keeping a research log. Perplexity's copy control puts the answer on the clipboard as markdown with the citation links inline as real markdown links. Paste that into Obsidian, a .md file, or a notes app, and you have a plain-text record with resolvable URLs and no PDF at all.

If you later want it as a PDF, Convert: Anything to PDF converts a .md file to PDF locally, with the links preserved. That two-step route — markdown now, PDF when needed — is the most durable of the four, because the markdown stays greppable and diffable in a way a PDF never is.

Comparison table

Built-in exportCtrl+PConvert: Web to PDFCopy markdown
Clickable source URLsNoYesYesYes
Full URL (not truncated)Often noYesYesYes
Inline [n] markersYesYesYesYes
Source preview cardsNoYesYesNo
Whole multi-turn threadUnreliableSometimes clipsYesOne answer at a time
Remove sticky header/sidebarn/aNoYesn/a
Works on a Pro-account threadYesYesYesYes
Runs locallyYesYesYesYes
Output is a real PDFYesYesYesNo (markdown)

The bit nobody mentions: the answer is not stable

Run the same Perplexity query twice a week apart and you will often get a different answer with a different source list. The model changes, the index changes, and pages get rewritten under their own URLs.

That has two consequences for how you archive:

Date the file. Put the run date in the filename — perplexity-2026-09-07-eu-ai-act-timeline.pdf. Convert: Web to PDF lets you set the filename before download, so you don't end up with forty files called perplexity.pdf.

Archive the sources, not just the answer. If a specific source page is load-bearing for your work, open it and save that as PDF too. The Perplexity answer tells you what it said; only the source PDF proves what the source said. This is the same discipline behind archiving a page before it changes — the citation is only as durable as the page underneath it.

Can you cite a Perplexity answer in academic work?

Generally, no — and not because of any tool limitation.

Style guides now broadly treat AI-generated output as a personal communication or a non-recoverable source: something you can acknowledge but that a reader cannot independently retrieve, because re-running the prompt does not reproduce the output. APA's guidance on generative AI, for instance, has you cite the model itself rather than the answer, and disclose the prompt.

The practical rule that keeps you out of trouble: use Perplexity to find sources, then read and cite the sources. Your PDF of the answer is a record of your research process — useful in a methods appendix, useful for your own audit trail, not a substitute for the primary material. If your institution or publisher has an AI-disclosure policy, that policy governs, not this blog post.

Comparison with saving other AI chats

If you're building a general habit of archiving AI output, the mechanics differ a little per platform. We've covered saving a ChatGPT conversation as PDF, saving a Gemini chat as PDF, and saving a Claude conversation as PDF separately, because each has a different built-in export with different gaps. Perplexity is the one where citation fidelity dominates every other consideration.

For a research workflow that spans many tabs at once — twelve source pages open after a Perplexity session — ScrapeMaster can pull the structured bits (titles, URLs, dates) from a listing page into CSV, which is a faster way to build a source table than saving twelve PDFs you'll never reopen.

Frequently asked questions

Does Perplexity have a built-in PDF export?

Yes. Open a thread, click the share/export control at the top of the answer, and choose Export → PDF. It preserves the answer text and the inline numbered citation markers, but renders the source list as plain text — the URLs are not clickable and long ones may be truncated.

How do I keep Perplexity citations clickable in a PDF?

Use Chrome's Ctrl+P → Save as PDF, or a browser extension like Convert: Web to PDF. Both go through Chrome's print engine, which converts <a href> elements into real PDF link annotations, so the numbered citations remain clickable. The built-in Perplexity export does not do this.

Why is my Perplexity PDF missing the sources panel?

Two common causes. Either the panel was collapsed when you exported — anything behind a "show more" control isn't in the page and can't be captured — or you used Article Mode, which strips everything outside the main article body and usually removes the sources with it. Expand the panel and use the default (non-Article) mode.

How do I save a long Perplexity thread with follow-up questions?

Scroll the whole thread to the bottom first so every turn is loaded, then use Convert: Web to PDF, which captures the full scrollable page as one continuous document. Chrome's print dialog and Perplexity's own export both truncate long multi-turn threads fairly often.

Can I cite a Perplexity answer in a paper?

Usually not as a source. Major style guides treat generative-AI output as non-recoverable, since re-running the prompt does not reproduce the answer. Cite the underlying sources Perplexity surfaced, and disclose your use of the tool according to your institution's or publisher's AI policy. Keep the PDF as part of your own research record.

Does saving a Perplexity page upload it anywhere?

Not with the methods above. Chrome's print-to-PDF and Convert: Web to PDF both run entirely on your machine — the page is rendered locally and the PDF is written to your downloads folder. Nothing is sent to a server, which is also why they work on threads inside a logged-in Pro account.

Bottom line

Pick by what you need to survive. If you want the prose, Perplexity's own export is one click and it's fine. If you need the citations to still work — clickable, untruncated, mapped to the claims they support — go through Chrome's print engine, either with Ctrl+P for a short answer or with Convert: Web to PDF for a long thread where you also want to strip the sticky header and keep the sources panel.

And whatever you use: date the file, and save the sources that actually matter separately. The answer is a pointer. The sources are the thing.

Free, no account, no watermark, and nothing leaves your machine — Convert: Web to PDF on the Chrome Web Store.