Can You Tell If Someone Screenshotted a PDF?

If a sensitive document is about to go out, you can create a free tracked link with downloading switched off in a couple of minutes — or open the live demo first to see what a reading record contains.

Why a browser page is not told about a screenshot

Because the capture is not something the page does. On a phone it is a button combination; on a Mac a keyboard shortcut handled by macOS; on Windows a key, a shortcut or a separate capture app. In every case the operating system copies what is on the display, and the browser tab showing your document is one rectangle in that picture. A page can see keys pressed while it has focus, but a capture started from a shortcut the system intercepts, from a taskbar tool or from a second device produces nothing the page receives.

Native apps are different, and that difference is where the idea that a screenshot can be detected comes from. Apple documents a notification, posted when a person takes a screenshot, that an iPhone app can listen for. Android 14 added a screenshot-detection callback an app can register, and Android's own documentation is candid about its limits: it detects a capture made with the hardware button combination, it does not hand the app the image, and a capture made through test commands is not reported. Both belong to software installed on the reader's device. A PDF you attached, or a document the reader opens from a link in a browser, is running inside neither.

The same boundary explains printing, which is covered in detail at whether you can tell if someone printed a PDF, and it is the reason an ordinary PDF reports nothing about opening either — the mechanism behind that is set out at what PDF tracking is.

What our viewer blocks, and what it does not

Be precise here. PDFTrackr's viewer suppresses the right-click menu, swallows the save and print keyboard shortcuts, and ships a print stylesheet that blanks the page on every share link. Those are deterrents against the casual routes to a copy. None of them touches a screenshot, and none of them is recorded: nothing appears in your analytics when a reader presses a blocked shortcut.

It also does not listen for a Print Screen key, and it would be the wrong thing to build. A keypress is not a capture — plenty of people remap the key, and plenty of captures never use it — so a record built on it would report screenshots that did not happen and miss the ones that did. The text on the page stays selectable, too, because the viewer keeps a text layer. A reader who wants the words has them; the controls here are about the file and the casual copy, not about what a person can see.

Switching downloading off is the setting worth pairing with any of this. It removes the download button, not the bytes the browser was sent to draw the page, and it stops no screenshot. What it does is keep the document inside the viewer for the whole reading, which is exactly where the watermark in the next section applies.

Attribution instead of detection: what a watermark does

If you cannot know that a capture happened, the useful question becomes whether a capture that surfaces later can be traced. That is what a visible watermark is for. On PDFTrackr the owner writes the text and the viewer tiles it across every page. The template can carry the address the reader typed at the email gate, the date and time of the view, and the link's title; the default reads CONFIDENTIAL · Provided to [email] · [date] [time], with the bracketed parts filled in at the moment of the view. A screenshot of that page carries the mark, so a copy that turns up in the wrong inbox carries whatever the mark identified.

Three limits, stated plainly. It is an overlay drawn in the viewer, never a stamp written into the file, so a downloaded copy does not carry it. A determined reader can hide markup on their own screen with browser developer tools. And the address in it is what the reader typed unless the link verifies the address with a one-time code, which is a Pro setting. Where the gate is off, the email segment is simply dropped and the mark carries the date, time and whatever text you wrote.

DRM goes further, and the honest comparison says so. Locklizard markets Print Screen and screen-capture blocking for its Safeguard viewer on Windows, Mac and Android, and a VeryPDF knowledge-base article says its DRM Protector blocks screen-capture tools and logs attempts. Both depend on a viewer the reader installs first, and neither reaches a phone camera pointed at the screen. Microsoft makes the same point about its own capture-exclusion setting for Windows apps: unlike a security feature or DRM, it carries no guarantee of protecting what is on screen, and a photograph of the screen is its example. The watermark, compared side by side with DRM, is set out at watermark vs DRM vs tracking.

Five ways to send it, compared on screenshots

The verdict is ours and it is narrow. For a document going to people outside your organisation who will not install anything, the tracked link with a watermark is the pick: it is the row that makes a capture traceable without asking the reader to install anything and still tells you whether the pages you worry about were read at all. Where DRM and native apps genuinely win is detection itself — the bottom two rows are in a position to see a capture attempt because they run on the reader's device. If knowing about the attempt is the actual requirement, buy one of those and accept the install.

When Pro becomes the right choice

Most of this is on the plan that costs nothing — downloading switched off, the email gate, a password, link expiry, per-page reading, the exclusion of automated opens, 500MB, 50 files, 50 active share links, twelve months of history, no card. If your worry is the file leaving through the download button, free covers it.

Pro becomes the right choice when the worry is the screen rather than the file — when a capture of a pricing sheet or a draft term sheet would do the damage, and you want that capture to carry a mark saying which link, and which reader, it came from. That is the watermark, and it is worth pairing with verified viewer emails, so the address printed across the page is one the reader proved with a code rather than one they typed. It is $9 a month; see what a reading record looks like in the demo dashboard before deciding.

Keep reading: whether you can tell if someone printed a PDF, watermark vs DRM vs tracking, and what PDF tracking is. Or start with how free PDF tracking works.