Do PDFs Have Read Receipts? (No — Here's What Actually Works)

You can see this for your own document before reading any further: create a free tracked link — 50 files, 12 months of history, no card. The rest of this page is the comparison.

Why can't a PDF report back? Because nothing in the file is allowed to

A PDF is a container of pages, fonts and instructions that a reader application draws on a screen. Once you attach it to an email, it is a copy on somebody else's disk, opened by software you do not control, possibly with no network connection at all. There is no step in that sequence where anything reports home, because no such step exists in the format.

The two workarounds people reach for are both blocked by design. The first is a remote image — a pixel pulled from a server when the page renders. The second is document-level JavaScript that posts a message somewhere on open. Adobe's enhanced security exists precisely to stop this class of behaviour: Acrobat warns the user when a PDF attempts to reach external resources such as images or websites, and its Trust Manager lets an administrator block PDF access to every website outright. A tracking mechanism that triggers a security warning, and that a default setting can switch off, is not a receipt. It is a request for permission that most recipients will decline without ever seeing it.

The third option, DRM, does work — and it is worth being plain about the trade. A DRM system such as Locklizard makes the reader's viewer check with the publisher's licence server before the document first opens, and that request can be logged. PDFTrackr does not do this and is not the tool for it: if your requirement is to stop a file being kept, forwarded or printed, buy DRM. What DRM buys you is control over the copy. What it does not buy you, on its own, is a picture of how much of the document anyone read.

What do people mean by “PDF read receipt”? Four different questions

The phrase collapses four questions that have four different answers, which is why the searches for it end in forum threads. Sorting them out first is how you avoid buying the wrong tool:

1. “Did my email arrive and get opened?” — a question about the message. An email read receipt answers it, conditionally.
2. “Did they open the attachment?” — unanswerable for a plain attachment. Nothing measures it, in any product, at any price.
3. “Did they open the document, and how much did they read?” — answerable, but only if you stop sending the file and send a tracked link instead.
4. “Can I stop them keeping or forwarding it?” — a DRM question, not a tracking one.

Question two is the one worth internalising, because it is the one every vendor is quiet about. A PDF sent as an email attachment cannot be tracked by anybody. That is a property of attachments, not a gap in somebody's product, and any tool claiming otherwise is describing something else — usually the email, sometimes a link they quietly substituted for your file.

Four methods that get close, ranked by what they actually confirm

Every cell below is the method's own documented behaviour, sourced at the foot of the page. Read the second column: the gap between what a method confirms and what people assume it confirms is where the disappointment lives.

Method 1 — a tracked link. You upload the PDF, share a link, and the document is served by a viewer you control. What the server records is a session rather than an event: which pages were reached, how long each one held attention, where the reader stopped, and — if you asked for an email before access — who it was. Adobe Acrobat's own share links are the low-effort version of this if you already live in Acrobat and only need the yes/no: the shared-file view reports how many people opened the file, a last-activity timestamp, and the viewer's email where they signed in. Papermark and Peony both give page-by-page data on a free plan, and both cap the history at 30 days — Papermark's also keeps only the last 20 views. DocSend has no free plan at all and starts at $10 per user per month on annual billing. All of them make you swap the attachment for a link; what differs after that swap is how much of the reading you get to see, and for how long.

PDFTrackr is the pick when the question is how much was read. Page-by-page reading time, viewer identification by email, password, expiry and download-off controls, and 12 months of history with every view retained are all on the free plan — 50 files and 50 links, no card — and automated opens are excluded from the counts before they reach your dashboard. That last part is the difference between a number you can act on and a number that includes the recipient's mail gateway, and it is why a document you send once and hear about three weeks later is still readable as data rather than an expired row.

In practice PDFTrackr changes the ask rather than answering it. Instead of requesting a receipt you will not get, you upload the file once and create a separate link for each recipient, then read the sessions against the names you sent them to. A link can carry a password, an expiry date and a download switch, and it can require an email address before the document renders — which is what turns an anonymous session into a named one. Nothing about the document itself changes: the recipient opens an ordinary PDF in a browser. What changes is that the reading leaves its record on your side of the wire instead of theirs.

Method 2 — an email read receipt. This is the feature the phrase “read receipt” was coined for, and it is the recipient's to grant. Microsoft's own Outlook documentation is unambiguous about the limit:

“In Outlook, the message recipient can decline to send read receipts. […] There is no way to force a recipient to send a read receipt.”— Microsoft Support, “Add and request read receipts and delivery notifications in Outlook”, fetched 2026-07-29

A recipient can also refuse every request permanently, and clients that do not implement receipts never answer. So a returned receipt is evidence; a missing one is nothing. And a returned one says the message was opened, not the attachment.

Method 3 — an open-tracking pixel in the email. A one-pixel image fires when the mail client loads remote content. Apple's Mail Privacy Protection broke the inference underneath that: with the setting on, Apple's documentation says the sender's view of the IP address is hidden and remote content is “privately downloaded in the background when you receive a message (instead of when you view it)”. The pixel fires on delivery, for messages nobody opened — a false positive by construction, and the same class of problem as the automated opens we exclude from our own counts; see whether PDF view counts are real for the size of it.

Method 4 — a mechanism inside the file. Covered above: blocked by default, warned about when attempted, and silently useless when it fails. The one variant that works is DRM, at DRM's price and DRM's friction. For everyone whose actual question is “did they read it”, method 1 is the answer, and the practical walk-through of who opened your PDF covers the setup end to end.

What can a tracked link measure, and what can it still not?

It can measure the session: when the link was opened, from which country, how long each page held attention, how far through the reader got, and — where you asked for an email before access — which named person it was. It can also do the thing a receipt cannot, which is tell you the reading was human rather than a security scanner opening the link before delivery.

It cannot follow the file once someone downloads it. It cannot tell you the document was understood, or read by the person it was meant for rather than the assistant who forwards their mail. And it can do nothing at all for a PDF you sent as an attachment. Those limits bind every vendor in this category; what differs is what each does with the session it can see.

Which is where the yes/no framing falls apart. Here is the share of readers reaching each page across our own tracked documents.

A receipt would have marked every one of those sessions “read”. Roughly a third of them stopped on the cover. If you are chasing a decision, the difference between a reader who stopped on page one and one who spent four minutes on your pricing page is the entire signal, and no yes/no carries it. You can see what that looks like on a live document without signing up.

PDF read receipt vs email read receipt: they answer different questions

An email read receipt is a message-level acknowledgement, granted by the recipient, that says nothing about any attachment. A tracked link is a document-level record, controlled by the sender, that says nothing about the email. They are not two grades of the same feature; they are answers to questions two people are asking at cross purposes.

The practical verdict: PDFTrackr, or any hosted-link tool, is what you want when the document is the thing that matters and you need to know whether it landed and how deep anyone got — and the counts are worth trusting because automated opens are separated out before they reach your dashboard. An Outlook read receipt is what you want when you only need to know a message was seen and you accept that the recipient may decline. If you need both, send the tracked link inside a message with a receipt request, and read the two signals as the different things they are — that is also how PDF views and downloads are tracked in practice. And whichever you choose, the underlying mechanism is the same one described in how free PDF tracking works.

Keep reading: how free PDF tracking works, how to know who opened your PDF, and whether the view counts you are shown are real. Methodology for the figures on this page: 3,017 validated sessions, extracted 10 Jul 2026.