How to see who read your PDF

You sent a PDF and heard nothing back. Did they open it? Read it? Stop on page two? Here's why a normal PDF can't tell you - and the ways to actually find out.

Why you can't track a PDF you emailed

A PDF file is just a document. Once you email it or hand over a file, it opens in whatever app the reader uses, on their device, with no connection back to you. There's nothing to report an "open," let alone how far someone read. Read receipts in email only confirm the message was opened - not the attachment, and not which pages got attention.

This isn't a setting you can flip. Adobe Acrobat, Apple Preview, and every browser's built-in PDF viewer are deliberately designed not to phone home when a document opens. The PDF format technically allows embedded JavaScript, but mainstream readers disable or sandbox it precisely because a script that calls out to a remote server is indistinguishable from malware - and security software flags documents that try. There is no reliable way to make the file itself report back, and any product claiming otherwise is depending on the one reader configuration where the trick still works.

To know what happens inside the document, the PDF has to be opened through something that can measure the reading. That means sharing a link to a hosted viewer rather than sending the raw file.

The methods, ranked by what they tell you

1. Email read receipts - weakest

A read receipt confirms your email was opened. That is all. It says nothing about whether the attachment was opened, which pages were read, or how long anyone spent. Most mail clients now block tracking pixels or ask the recipient before loading them, so even the "opened" signal is unreliable. Use it when you only need to know a message landed. It fails when the real question is "did they read the document?"

It also fails in the other direction: Apple Mail Privacy Protection and Gmail's image proxy pre-fetch tracking pixels on the recipient's behalf, so a pixel can fire when no human ever opened the email. An email tracker can therefore report both false negatives and false positives - and even a true "opened" only ever proves the email was opened, never that the PDF inside it was read. If your workflow lives in email, the fix is to keep the email and swap the attachment for a measured link - here's how to track a PDF you'd normally send as an email attachment.

2. A tracking pixel or a "link to a file"

Hosting the PDF somewhere (Drive, Dropbox, your own server) and sharing a link can register that the link was clicked or the file was fetched. That is a real step up: you at least learn the document was opened, and roughly when. But you usually get a single "viewed" event with no depth - not how far they read, not how long they stayed, not whether they came back. Use it when a binary opened/not-opened is enough. It fails when you need to know which pages actually got read.

The gap matters more than it looks. A fetched file tells you the bytes were downloaded, not that anyone read past the cover. Someone who opened your proposal, glanced at page one, and closed the tab produces exactly the same signal as someone who read all thirty pages twice. If you're deciding whether to follow up, those two readers deserve completely different calls.

3. A document viewer with page-level analytics - strongest

Sharing through a viewer that measures reading gives you the full picture: which pages were seen, how long each one held attention, where people dropped off, and whether the same reader came back. Because the document opens inside an instrumented viewer, every page turn is a data point. This is the only method that answers "did they actually read it, and how far did they get?" - and the rest of this guide assumes it.

It's also the only method that is structurally reliable, and the reason is where the measurement happens. The viewer serves each page as the reader reaches it, so every page turn is an event the server observes directly - nothing has to execute on the reader's machine, no pixel has to load, no mail client has to cooperate. The first two methods ask the reader's software for a favour; this one simply watches its own viewer do its job. That's why link-based measurement keeps working where receipts and pixels silently fail. See how PDF tracking works in practice for the mechanics end to end.

How EveryPage does it

EveryPage is built for the third method. Upload a PDF, share the link, and you get a page-by-page readership report: a read-through funnel showing the percentage of readers who reached each page, time spent per page, returning-reader detection, and where each read came from (link, QR, email, or embed).

And it does this without storing a single visitor IP address - readers become stable, pseudonymous identities via a one-way hash, so you get the insight without tracking people. There's a free plan to try it on your own document.

Who is "who"? Pseudonymous readers, not surveillance

"See who read it" usually doesn't require a name - it requires telling readers apart. EveryPage does that without keeping anything that identifies a person. When a read happens, the visitor's IP address is run through a salted one-way hash - a cryptographic function that always maps the same address to the same output but can't be reversed - and the result becomes a stable pseudonymous identity like Reader #214. The salt is a server-side secret, so the stored value is useless to anyone who obtains it; the raw address is used only to resolve a country in-flight, then discarded.

The practical payoff: your report can say "Reader #214 opened the deck on Tuesday, got to page 9, and came back Thursday to finish it" - a genuinely useful pattern - while the database contains no IP to leak, subpoena, or mishandle. That distinction is what separates readership measurement from reader surveillance, and it's why this approach holds up under the GDPR where IP-logging trackers create liability.

What the readership data tells you

A view count is a vanity metric; a read-through funnel is a story. Imagine you share a 20-page deck and the funnel comes back: 100% reached page 1, 78% reached page 6, 52% reached page 12, and 24% reached page 20. In one glance you know most people got past the introduction, half made it through the middle, and a quarter finished. The sharp drop between page 6 and page 12 is where you are losing your audience, so that is the section to tighten.

Funnels also surface thresholds you can act on. If readers who pass page 3 finish 80% of the time while half of everyone else bails on the cover, your document doesn't have a length problem - it has a first-three-pages problem, and that's where the rewrite effort should go. Run the same funnel after the edit and you have a before/after measurement instead of a hunch. What a read-through funnel is walks through reading one in detail.

Per-page reading time adds the second dimension. A page with high time-on-page was read; a page everyone flipped past in two seconds was skimmed. Returning-reader signals tell you when someone came back for a second look - often the strongest interest signal you will get. And source attribution shows whether a read came from your direct link, a QR scan, an email, or an embed.

Combine the dimensions and the interpretations get specific. If your pricing page averages 45 seconds while every other page averages 12, price is the sticking point - lead your follow-up call with it. If a proposal's funnel collapses exactly at the terms section, that's the clause to renegotiate, not the design to polish. And a reader who returns three times but never passes the same page is telling you precisely where the internal objection lives.

Step by step: track a PDF with EveryPage

1. Upload your PDF at everypage.co - no account needed to try it.
2. Copy the share link (or grab the QR code or embed code) and send it the way you normally would.
3. Open your readership report and watch the read-through funnel, per-page time, and returning readers update as people read.
4. Optionally require an email before the document opens, set a password, or schedule the link to expire - each is a control you choose per link, not a default.

The honest limits

Link-based tracking is the strongest method, not a magic one. Knowing the edges keeps you from over-reading the data.

Can I see the reader's actual name or email?

Not by default - readers appear as pseudonymous identities like Reader #214. If you need names, turn on the email gate: the reader enters an email before the document opens, knowingly identifying themselves. That's the only way any honest tool gets a name; products that claim to name anonymous visitors are guessing from data you shouldn't want stored anyway.

What if someone downloads or prints it?

A downloaded or printed copy is a plain PDF again - it stops reporting the moment it leaves the viewer, for the same reason your emailed attachment never reported in the first place. If page-level data matters for a given document, disable downloads on that link so every read goes through the measured viewer.

What if the link gets forwarded?

Forwarding works in your favour: each new person shows up as a distinct reader with their own funnel, so you can see your deck travelled - five readers when you sent it to one person is a signal in itself. What you can't see is who forwarded it or the chain it travelled through.

Can two readers ever blur together?

Occasionally. Because identity comes from a one-way hash of the network address, two colleagues reading from the same office network can register as one returning reader, and one person hopping VPN exits can register as several. That's the deliberate cost of never storing IPs - the aggregate funnel and per-page numbers stay accurate either way.

Related reading

See the full readership feature set, how PDF tracking works in practice, or how EveryPage compares as a DocSend alternative.

Going deeper: what a read-through funnel is, how to send a pitch deck and know if investors read it, and how to track whether a sales proposal was read.