Screenshots and screen recordings are among the most common methods students use to leak exam questions. Learn how ProctrMe's multi-layered DRM system makes capturing exam content extremely difficult.
The Screenshot Problem
When exam questions are leaked via screenshots, the damage extends far beyond a single exam session. Leaked question banks can circulate on social media, cheating forums, and messaging groups for years, compromising the integrity of future assessments that draw from the same question pool. For institutions that invest significant resources in developing high-quality assessment items, this represents both an academic and financial threat.
Thinking Like an Attacker
Effective anti-capture design starts by enumerating how content actually gets extracted in practice. The common paths are: OS-level screenshot shortcuts (Print Screen, Cmd+Shift+4, Win+Shift+S), browser or OS screen-recording APIs, printing to PDF, programmatic extraction via automation tools and canvas APIs, clipboard copy-paste, and — the hardest case — simply photographing the screen with a second device. Each path requires its own countermeasure, which is why single-technique "screenshot blockers" fail: they close one door and leave five open. The layered approach below closes each path in turn.
Layer 1: Preemptive Modifier Key Detection
The first line of defence monitors for keyboard modifier keys (Ctrl, Meta/Windows, Alt) being pressed. Since all screenshot shortcuts require at least one modifier key, ProctrMe instantly applies a heavy blur filter to the page content the moment any modifier key is detected — before the screenshot shortcut can be completed. The content becomes an unreadable blur in any captured frame.
Layer 2: Clipboard Neutralisation
Even if a screenshot somehow captures readable content, ProctrMe intercepts clipboard operations. Copy, cut, and paste events are blocked during the exam. The clipboard is cleared when modifier keys are released, neutralising any screenshot that may have been written to it.
Layer 3: Screen Capture API Interception
Modern browsers provide the getDisplayMedia API for screen sharing and recording. ProctrMe intercepts this API during active exam sessions, preventing browser-based screen recording tools, OBS Browser Source captures, and screen-sharing via video conferencing platforms from accessing exam content.
Layer 4: Canvas Export Poisoning
Automation tools like Puppeteer and browser extensions can attempt to extract page content via the Canvas API (toDataURL, toBlob). ProctrMe overrides these methods during exam sessions, returning a single black pixel instead of actual content when extraction is attempted from any canvas element other than the proctoring webcam overlay.
Layer 5: Print Media Blocking
CSS @media print rules hide all page content when printing is attempted, replacing it with a warning message. Combined with Ctrl+P keyboard interception, this prevents print-to-PDF content extraction.
Layer 6: Dynamic Watermarking
Watermarks are the deterrent of last resort: if content is captured despite every technical barrier, the capture itself should incriminate the person who made it. During an exam, a repeating diagonal watermark containing the student's ID and session identifier is rendered across the content at low opacity — light enough not to impede reading, dense enough that it cannot be cropped out of any usable capture. A leaked question photographed from the screen carries the leaker's identity in every corner of the image, which converts leaking from a low-risk act into a traceable one.
Mobile-Specific Protections
Mobile devices present unique challenges since hardware button combinations (Power + Volume Down on Android) trigger screenshots at the OS level before any web application code can respond. ProctrMe addresses this with: (1) Anti-screenshot watermarks displaying the student's ID across the page, (2) AI-poison text embedded in watermarks that instructs LLMs to refuse answering if they detect exam content, (3) Split-screen and floating window detection to prevent secondary app usage, and (4) Three-finger gesture monitoring to detect alternative screenshot methods.
Why No System Is 100% Capture-Proof — and Why That's Acceptable
It is important to be honest about the ceiling: a determined person with a second camera pointed at the screen will always be able to photograph content, because that act happens entirely outside the computer. The goal of anti-capture technology is not perfection but economics. Each layer raises the effort, skill, and risk required to extract content, while watermarking ensures that whatever does leak is attributable. When capturing one question requires defeating six independent mechanisms and still stamps your student ID on the result, casual leaking — which accounts for the overwhelming majority of question-bank compromise — effectively stops.
What Institutions Should Do Beyond Technology
Technical controls work best alongside assessment design and policy. Institutions can rotate and retire question banks on a schedule so that any leak has a limited lifespan, draw exam papers from large randomised pools so no two students see identical sets, and state clearly in academic-integrity policies that capturing or distributing exam content is a severe violation with defined consequences. Combined with the technical layers above, this turns question-bank security from a single point of failure into a managed, renewable asset.