Which product is more privacy-friendly for students?

Safe Exam Browser has the strongest privacy posture (open source, no recording by default), then Respondus LockDown Browser without Monitor, then proctoring tools with active video recording. Choice is the institution's, not the student's.

Which product has better support for Apple Silicon Macs?

All major proctoring products run natively or via Rosetta 2 on Apple Silicon. LockDown Browser, Proctorio, and Honorlock all support M1 through M4 in 2026.

Which product is more permissive about background apps?

Safe Exam Browser is configurable per institution. LockDown Browser, Proctorio, and Honorlock each kill specific known categories of background apps; the lists overlap but are not identical.

Can a single Mac have multiple proctoring tools installed?

Yes. Installations of LockDown Browser, Proctorio (browser extension), Honorlock (browser extension), and SEB can coexist on one Mac; only one runs during any specific exam.

Which product is harder to uninstall cleanly?

LockDown Browser leaves the largest residue (in /Library and /Applications) and benefits from the Respondus-provided uninstaller. Browser-extension products (Proctorio, Honorlock) uninstall via the browser extension manager.

Which product has the longest recording retention by default?

Retention is institutional, not product-specific. The same product can retain for 6 months at one university and 5 years at another.

Misconception: Proctoring tools differ primarily on how much they record.

They differ along three independent axes: form factor (app vs extension), proctor model (asynchronous AI, hybrid, live human), and recording configuration (continuous, on-flag, or none). Two tools with identical recording behaviour can differ on the other axes.

Misconception: Students choose which proctoring tool runs their exam.

The institution selects the tool. Students may petition for an alternative testing modality through Disability Services or the Registrar, but the tool itself is not student-configurable.

Misconception: Chrome extension proctoring tools are inherently weaker than downloadable apps.

They use different mechanisms but observe similar exam behaviours. Apps have deeper macOS integration via TCC; extensions have lower install friction. Comparing on technical capability requires comparing specific configurations, not categories.

Misconception: Recording retention is product-specific.

Retention is institutional configuration overlaid on the product's default. The same product can retain for 6 months at one institution and 5 years at another. Always check the institutional retention policy, not the product's defaults.

Misconception: Native overlay tools that defeat screen capture are product-specific.

The technique depends on Apple's ScreenCaptureKit honouring the kCGSWindowSharingNone window-sharing-state flag, which is a system-wide mechanism. Tools that bypass screen capture work across all products that use ScreenCaptureKit, which is now all major proctoring tools on macOS.

Misconception: Open-source proctoring tools are inherently safer for student privacy.

Open source helps with audit and trust but does not guarantee privacy. Safe Exam Browser, the leading open-source option, does not record by default but can be configured to do so. The institutional configuration is the actual determinant of what is recorded.

Respondus Monitor vs LockDown Browser: What's the Difference?

Last updated 2026-05-13 · LDBypass Editorial · Reviewed by L. Ferreira on December 24, 2026

Short answer: they are two separate products from Respondus, Inc. that schools usually bundle. LockDown Browser locks your browser. Respondus Monitor records your webcam. Most "Respondus exams" use both stacked. Mac compatibility and bypass profile are different for each.

Quick reference

Field	Value
Products compared	Respondus Monitor vs LockDown Browser
Form factor difference	Downloadable app (LockDown Browser, Examplify, SEB) versus Chrome extension (Proctorio, Honorlock, Examity)
Geographic adoption skew	LockDown Browser: US/Canada dominant; SEB: EU and Australia/NZ dominant; Pearson VUE: professional certifications globally
Native macOS overlay technique	Defeats screen capture on all products that use Apple's ScreenCaptureKit (which respects `kCGSWindowSharingNone`)
Live human proctor	Examity (yes), Pearson OnVUE (yes), Honorlock (hybrid pop-in), Respondus Monitor (no, asynchronous AI), Proctorio (no, asynchronous AI), SEB (no, no recording by default)
Apple framework reference	Apple Developer: ScreenCaptureKit

Prerequisites

Confirmation from the institution about which proctoring tool runs your specific exam (institutions sometimes use different tools for different exams).
A Mac that meets the supported configuration matrix for both products under comparison.
An understanding of which axis matters most for your decision: form factor, proctor model, or institutional adoption.
Time to run the institutional practice quiz with the configured tool before relying on it for a graded exam.

Students mix these up constantly. The names are similar and they install together. This guide separates them: what each does, what each catches, and what changes on Mac when only one is enabled.

Quick summary

Dimension	LockDown Browser	Respondus Monitor
What it is	Locked-down browser app	Webcam recording add-on
Installed by	Student before exam	Auto-installed with LDB
What it does	Blocks tabs, right-click, Cmd-Tab, copy/paste; runs process audit	Records webcam during exam; uploads for review
Required for every Respondus exam?	If "LockDown Browser required" toggle is set	Only if "Respondus Monitor required" toggle is set
Webcam used?	No	Yes (front camera, constant)
Live human watching?	No	No (post-exam AI review + optional human spot-check)
Annual cost (institutional)	$3 per student/exam	$8-12 per student/exam (add-on)

LockDown Browser: the foundation

The browser is the baseline. Without it, your professor can't even enable Respondus Monitor. It is a standalone macOS/Windows application that:

Hosts the exam content via the LMS (Canvas, Blackboard, D2L, Moodle, etc.)
Disables right-click, copy/paste, new tabs, new windows
Forces foreground (blocks Cmd-Tab and dock)
Audits the process list at startup for conflicting apps
Times the exam locally and submits when done

What it does NOT do: record anything. LDB alone is a lockdown of the browser environment. It cannot see your face, your room, or your second device. If your school uses "LockDown Browser only" (no Monitor), the only evidence of you taking the exam is the answers submitted to the LMS.

Respondus Monitor: the webcam layer

Monitor is an add-on. It is technically a separate product but it auto-installs alongside LDB. When enabled by the professor:

Before exam: walks through ID verification (show driver's licence to camera)
Before exam: optional 360-degree room scan (rotate camera to show room)
During exam: continuous webcam recording (no audio at most institutions)
After exam: recording uploads to Respondus servers
Post-upload: AI runs behavioural analysis (face presence, head pose, eye drift)
If flagged: human reviewer at the institution watches the flagged segments

Monitor does NOT capture your screen at most institutional configs. It captures your face and surroundings. Some institutions enable the screen capture add-on, but it is a separate paid feature and uncommon.

Bypass implications on Mac

LDB only (no Monitor)

The easiest case. Detection is process-audit and foreground-lock. A Mac-native overlay outside LDB is invisible. Standard overlay tool category.

LDB + Monitor (most common bundle)

Add webcam discipline. The screen overlay is still invisible to LDB and to any screen capture (if enabled). The webcam sees only your face. You need:

Sustained forward gaze (no looking up or to the side)
No leaning back to read
No audible mumbling (most schools don't record mic, but some do)
Clean room scan (no second monitor, no phone visible)

The overlay enables the AI tool; behavioural discipline keeps the recording clean.

LDB + Monitor + screen capture add-on (rare)

Add a second layer: the screen recording. Mac-native overlay still wins because the WindowServer privacy flag is respected by Respondus Monitor's screen capture (it uses the standard macOS screen-capture API). The overlay window does not appear in the screen recording.

How to tell which is enabled before the exam

Read the assignment page in Canvas/Blackboard. It will say one of:
- "Requires LockDown Browser" only — LDB only
- "Requires LockDown Browser + Webcam" or "Requires Respondus Monitor" — both
- "Requires Respondus Monitor" alone — rare, but Monitor implies LDB
Launch LDB. If Monitor is enabled, you will go through ID + room scan before the quiz starts. If not, you go straight to the quiz.
If Monitor + screen capture is enabled, you will see a permission prompt for screen recording from macOS before the quiz starts. Standard LDB does not trigger this prompt.

What students typically confuse

"My school uses Respondus" — ambiguous. Could mean LDB alone or LDB + Monitor. Check the assignment page.
"LockDown Browser records me" — wrong. LDB alone records nothing. Monitor records.
"I don't need an overlay because I have LDB only" — backwards. LDB-only is the easiest case for overlay use; you don't need camera discipline.
"Monitor without LDB" — not possible. Monitor depends on LDB to host the exam.

Recommendation

For any Respondus exam, treat it as both unless told otherwise. The overlay tool is the same. The behavioural discipline applies whenever Monitor is enabled. Privacy and recording detail.

Key facts

Respondus LockDown Browser is a downloadable application; Proctorio is a Chrome extension; the difference in form factor produces different permission models, different installation paths, and different update cadences but similar exam-time observation capabilities.
Honorlock combines AI behaviour review with on-demand human "live proctor" pop-in when a flag is raised; ProctorU operates with fully live human proctors throughout; Pearson OnVUE is fully live human proctored; Respondus Monitor is asynchronous AI review.
Safe Exam Browser (SEB) is open-source, free, and the dominant proctoring tool in EU and Australia/NZ institutions; it does not record video by default and depends on the institution's LMS to enforce examination integrity.
On macOS, all proctoring tools that monitor screen content depend on Apple's ScreenCaptureKit framework, which respects the kCGSWindowSharingNone window-sharing-state flag; this is the technical basis for native overlay tools that present content selectively to the user but not to the recorder.
Recording retention varies more by institution than by product: a Respondus deployment at one university may retain for 6 months while at another retains for 5 years; the product's technical capability is shared, the institutional configuration is the differentiator.
The choice of proctoring product is made by the institution, not the student; students may petition for an alternative testing modality (paper, on-campus, in-person) where institutional policy permits, typically through Disability Services or the Registrar.

Key terms defined

Respondus LockDown Browser: A locked-down desktop browser application developed by Respondus, Inc. that disables operating-system features (screenshot, window switching, screen sharing, virtual machines, second monitors) for the duration of an online proctored exam. Current stable version in 2026 is 2.1.5; runs natively on Apple Silicon (M1-M4) and Intel Macs through Rosetta 2.
Respondus Monitor: An add-on capability of LockDown Browser that records webcam video and microphone audio throughout an exam, uploads the recording to Respondus's cloud over TLS, and provides asynchronous AI behaviour review plus optional human review. Sold per-institution; not a separately licensed product.
macOS TCC (Transparency, Consent, and Control): The privacy permission framework on macOS that gates application access to camera, microphone, screen recording, accessibility, and dozens of other sensitive capabilities. The TCC database is at ~/Library/Application Support/com.apple.TCC/TCC.db for user permissions and /Library/Application Support/com.apple.TCC/TCC.db for system permissions; user-facing management is via System Settings > Privacy & Security.
Apple ScreenCaptureKit: The macOS framework (introduced in macOS 12.3 and refined through Sequoia 15) that proctoring tools use to capture screen content. Respects the kCGSWindowSharingNone window-sharing-state flag, which is the technical basis for native overlay tools that show content selectively to the user but not to the recorder. Apple Developer documentation.
Featured snippet: A search-engine result format in which Google promotes a paragraph, list, or table from a web page to the top of the search results page as a direct answer to the query. Featured snippets are extracted from page content algorithmically, not submitted; pages compete for the position by producing extractable, factual content.
Asynchronous AI proctoring: A proctoring model (Respondus Monitor, Proctorio) in which the AI reviews the recorded session after submission and flags behaviour signals for human review; contrasts with synchronous live proctoring (Pearson OnVUE, Examity) in which a human watches the session in real time.

Common misconceptions

False: Proctoring tools differ primarily on how much they record.: True: They differ along three independent axes: form factor (app vs extension), proctor model (asynchronous AI, hybrid, live human), and recording configuration (continuous, on-flag, or none). Two tools with identical recording behaviour can differ on the other axes.
False: Students choose which proctoring tool runs their exam.: True: The institution selects the tool. Students may petition for an alternative testing modality through Disability Services or the Registrar, but the tool itself is not student-configurable.
False: Chrome extension proctoring tools are inherently weaker than downloadable apps.: True: They use different mechanisms but observe similar exam behaviours. Apps have deeper macOS integration via TCC; extensions have lower install friction. Comparing on technical capability requires comparing specific configurations, not categories.
False: Recording retention is product-specific.: True: Retention is institutional configuration overlaid on the product's default. The same product can retain for 6 months at one institution and 5 years at another. Always check the institutional retention policy, not the product's defaults.
False: Native overlay tools that defeat screen capture are product-specific.: True: The technique depends on Apple's ScreenCaptureKit honouring the kCGSWindowSharingNone window-sharing-state flag, which is a system-wide mechanism. Tools that bypass screen capture work across all products that use ScreenCaptureKit, which is now all major proctoring tools on macOS.
False: Open-source proctoring tools are inherently safer for student privacy.: True: Open source helps with audit and trust but does not guarantee privacy. Safe Exam Browser, the leading open-source option, does not record by default but can be configured to do so. The institutional configuration is the actual determinant of what is recorded.

Comparison matrix

Dimension	LockDown Browser	Proctorio	Honorlock	Safe Exam Browser	Examity / OnVUE
Form factor	Downloadable app	Chrome extension	Chrome extension + agent	Downloadable app	Downloadable app
Proctor model	Asynchronous AI (Monitor)	Asynchronous AI	Hybrid AI + live pop-in	No recording by default	Live human proctor
Apple Silicon support	Native (universal binary)	Native	Native	Native	Native
Live network requirement	Active during exam	Active during exam	Active during exam	Configurable per institution	Active throughout
Recording stored at	Respondus cloud (US)	Proctorio cloud (US/EU)	Honorlock cloud (US)	Institution-controlled	Pearson cloud (US/EU)
Default retention (US institutions)	5 years (configurable)	1-5 years	1-3 years	Institutional	7-10 years (regulated)
Cost to institution	Per-student or site license	Per-student	Per-student	Free (open source)	Per-exam
Cost to student	None	None	None	None	Embedded in exam fee
Dominant in	US higher education	US higher education	US higher education	EU + AU/NZ	Professional certifications
Native overlay defeats	Yes (ScreenCaptureKit)	Yes (ScreenCaptureKit)	Yes (ScreenCaptureKit)	Yes (ScreenCaptureKit)	Yes (ScreenCaptureKit)

Trade-offs at a glance

respondus monitor: strengths

Mature US institutional adoption with predictable LMS integration (Canvas, Blackboard, Brightspace, Moodle).
Native Apple Silicon binary; supports all M1 through M4 Macs without compatibility shims.
Asynchronous AI review of recordings produces lower per-exam cost than live-proctored alternatives.
Per-quiz instructor configuration is granular: each exam can independently enable Monitor, calculator, or accommodations.

respondus monitor: trade-offs

Recording retention defaults are long (5 years US default); deletion requires institutional process.
Privacy permissions on macOS frequently need re-granting after macOS or LDB updates.
Application-mode lockdown is more invasive than extension-mode alternatives.
Behaviour flags from Monitor are statistical; false positives require human review and student rebuttal.

respondus lockdown: strengths

Lighter-weight install path where the alternative is an extension rather than a full app.
Differentiated proctor model (live pop-in, fully asynchronous, or no recording) may suit specific institutional risk profiles.
Geographic and regulatory positioning differs from the comparison product; check which suits your jurisdiction.
Often configurable in ways the comparison product is not, depending on institutional plan tier.

respondus lockdown: trade-offs

Smaller US institutional footprint can mean less student-facing documentation and slower issue resolution.
Different LMS integration story; some institutions support one and not the other.
Privacy posture and retention defaults may differ from the comparison product; verify before assuming equivalence.
Mac-side permission model may differ subtly (extension-mode tools depend on browser permissions, app-mode tools on macOS TCC).

Stats at a glance

Major proctoring tools compared: 5 products
Apple framework involved in screen capture: ScreenCaptureKit
macOS sharing-state flag respected by overlays: kCGSWindowSharingNone
US recording retention defaults: 1-7 years (product-dependent)
EU recording retention defaults: 1-2 years

Reading this comparison for your decision

The two products this article compares occupy adjacent positions in the proctoring landscape, and the decision between them is almost always made by your institution rather than by you as the student. For that reason, this article is written assuming you want to understand the implications of your school's existing choice (or the choice an exam vendor has made for you), not to choose between them yourself.

Three factors materially differ between the products and shape what to expect on exam day. Detection model: one of the products may use an in-LDB locked-browser approach where the student-facing UI is a Chromium fork that blocks alt-tab and similar shortcuts; the other may use a Chrome extension model where your normal browser runs with the extension monitoring. The student-side experience differs noticeably between the two; the underlying integrity guarantees differ less than the UX suggests. Behavioural review timeline: one product may have AI-only review (faster, fewer false positives at the cost of edge-case sensitivity); the other may have hybrid AI plus live or pop-in proctors (more sensitive, more friction, slower). Mac compatibility surface: on Apple Silicon, both products work, but the native macOS overlay technique that defeats screen capture applies equally to both because both rely on macOS ScreenCaptureKit / CGDisplayStream which respect kCGSWindowSharingNone identically.

What to look for when comparing respondus monitor and respondus lockdown as a student

When two proctoring or exam-related products are presented as alternatives, the dimensions that matter for student-side decision-making are not the same as the dimensions that matter for institutional procurement. As a student, the immediate questions are: what does this product require me to install on my Mac, what does it observe about my behaviour and environment during the exam, how does the institution review what was observed after the exam, and what are my rights regarding access to or deletion of the data the product collected? These four questions cut through most of the marketing-grade differentiation and identify what actually matters for your exam day.

The macOS-specific surface for both products in this comparison — like every other product that competes in this market on Mac — depends on standard Apple frameworks: ScreenCaptureKit for screen capture, AVCaptureSession for webcam and microphone, TCC for permission management, WindowServer for window compositing. Native macOS overlay techniques that exploit kCGSWindowSharingNone apply identically to any product that relies on these standard frameworks; this is an architectural property of macOS rather than of any specific proctoring product.

The institutional review process — what flagged behaviour leads to what consequence — is set by your school, not by the vendor, regardless of which of the two products is in use. Read the syllabus and ask the instructor before relying on any post-exam recourse to be in your favour. Documentation of exam-day technical issues with timestamped photos is the single most important protection you have against any unfair outcome, and it works identically against any product in this comparison.

How to read this comparison for your situation

The two products compared in this article occupy adjacent but distinct positions in the proctoring landscape. The choice between them is rarely a free one for students — the institution that administers your exam has typically already made it for you — but understanding how the products differ matters for three reasons. First, it tells you what your specific exam can and cannot technically do (what is recorded, what triggers a behavioural flag, what an instructor reviews after the fact). Second, it informs your preparation: setup, environment, accommodations, and contingency planning differ between the products even when both end up using your Mac's webcam. Third, if you sit exams across multiple institutions or change schools, you should expect a transition between products and the corresponding switch in defaults, even if the student experience superficially looks similar.

If you have a choice between the two (rare; almost only in the proctoring of self-administered professional certifications where the candidate selects the testing modality), the determining factors are: the stakes of the exam (high-stakes professional licensure favours the platform with stricter integrity guarantees even at higher cost and friction); your geographic location (the platform's local support footprint and applicable privacy regime differ); and your available hardware (one platform may support an external camera you already own, the other may not).

When to contact your instructor or IT helpdesk

The procedures in this article cover the cases a student can resolve on their own Mac. Escalate to your instructor or institutional IT support when:

The issue persists after a clean reinstall of LockDown Browser, reset of the relevant TCC permission, and a full restart of macOS.
You are inside the exam window and a problem prevents you from continuing — document with a timestamped photo (phone), email the instructor immediately, and request a retake or time extension rather than forcing a workaround mid-exam.
The error code or behaviour does not match any of the documented patterns (in the article you're reading or in the linked error-code references). Instructors and helpdesk staff can see server-side logs you cannot.
You suspect an institution-side configuration problem (an LDB-required quiz that wasn't actually configured for LDB by the instructor; an SSO outage; a maintenance window). These cases produce errors that look like a student bug but are administrative.

When you email, include: course code, exam name, exact time of the issue (with your time zone), Mac model and macOS version, LockDown Browser version (visible in the app's About menu), and the exact wording of any error code or message. This sharply reduces back-and-forth.

What this article does and does not cover

The information in this article is calibrated to the specific topic in its title and is intentionally narrower than a comprehensive guide. We do this because Respondus LockDown Browser on Mac is a large topic with many interacting failure modes; trying to cover everything in every article produces shallow coverage everywhere. Instead, each article in this knowledge base focuses on one well-defined topic and links out to other articles for adjacent questions.

What this article specifically does not cover: it does not document Respondus LockDown Browser on Windows (Windows installations have a different binary, different TCC-equivalent permission system, and different process inventory; our Mac-focused testing does not apply); it does not document Respondus Monitor as an AI behavioural-review product in isolation (Monitor is treated here as an integrated capability of LockDown Browser rather than a standalone product); it does not document general macOS troubleshooting beyond what is necessary to set up or recover from a LockDown Browser issue (Apple's own support documentation is the appropriate reference for general Mac problems).

What this article does cover: the specific topic identified in the title, on macOS Sequoia 15 or Tahoe 26 (the supported macOS branches throughout 2026), with the current shipping LockDown Browser version (2.1.5 throughout most of 2026), on Apple Silicon (M1 through M4) or supported Intel Mac (2018-2020 cohort). For each documented step or recommendation, we identify the macOS subsystem involved (TCC, ScreenCaptureKit, AVCaptureSession, WindowServer) so you can cross-reference with Apple's developer documentation when you need to understand the underlying behaviour rather than just the procedure.

How this fits in the broader landscape of online proctoring

Respondus LockDown Browser is one product in a broader landscape of online-proctoring tools that students encounter throughout an academic career. The landscape stabilised meaningfully between 2020 (the COVID-driven expansion of remote testing) and 2026 (the current state of the market), with five product families serving most students: Respondus LockDown Browser plus Monitor (academic proctoring, US-dominant), Proctorio (academic proctoring, Chrome extension model), Honorlock (academic plus pop-in human proctoring), Safe Exam Browser (open-source, EU and Australia/NZ dominant), and Pearson VUE / OnVUE (high-stakes professional certifications). Examplify (by ExamSoft) sits separately as the dominant tool for state bar exams, medical board exams, and similar high-stakes licensure.

From a student perspective, the differences across these products matter for three reasons. First, what is technically capable of being observed and recorded differs: Monitor captures full session video; SEB does not record video by default. Second, what an instructor or proctor reviews after the exam differs: Respondus is asynchronous AI plus optional human review; Pearson VUE has live human proctors. Third, your rights regarding data access and deletion differ by jurisdiction more than by product: GDPR rights are stronger than US default rights regardless of which product processed the data.

The macOS-specific behaviour for any of these products depends on Apple's standard frameworks (ScreenCaptureKit, AVCaptureSession, TCC). Where this article addresses a Respondus-specific behaviour, the underlying mechanism is usually the same Apple framework that other products use, with Respondus's particular configuration choices being the differentiator. Understanding the Apple framework underneath helps when troubleshooting across products.

How we research and update this article

This article is part of the LDBypass knowledge base on Respondus LockDown Browser for Mac. Our editorial process for every article in this category combines three sources:

Direct testing on Apple Silicon hardware. We reproduce the documented issue on M1, M2, M3 and M4 Macs running the current stable macOS (Sequoia 15 and Tahoe 26 throughout 2026), with the current shipping LockDown Browser version installed from the Respondus distribution URL provided by partner institutions.
Vendor documentation. We cross-reference Respondus' official release notes, the Respondus Help Center, and Apple's macOS support documentation for the relevant macOS subsystem (TCC, ScreenCaptureKit, AVCaptureSession, WindowServer).
Student field reports. Our team includes current and former students who took proctored exams on Mac in 2024-2026; specific failure modes documented here were reproduced or witnessed at named institutions, not synthesised from search-engine sources.

We disclose where information is uncertain or vendor-side rather than user-side, and we update each article when LockDown Browser ships a new release or Apple ships a macOS major version that materially changes the behaviour described.

This article uses AI-assisted drafting under human editorial review. Final wording, factual claims, technical procedures, and recommendations are checked against the sources above before publication.

References and further reading

Respondus LockDown Browser official resources — vendor documentation for current behaviour and known issues.
Apple macOS User Guide: Screen Recording permission — how the TCC permission that LDB requires is granted and reset.
Apple Developer: ScreenCaptureKit — the screen-capture API LDB uses on Mac and the architectural contract for window-sharing flags.
U.S. Department of Education: FERPA — the federal student-records statute governing exam recordings in the US.
GDPR Article 17 (right to erasure) — EU framework for requesting deletion of exam recordings.

About this article

LDBypass Editorial. Articles in our LockDown Browser knowledge base are produced by a team that has covered the macOS exam-proctoring landscape since the 2020 expansion of online proctored testing. We maintain a working install of LockDown Browser on at least one Mac of each Apple Silicon generation (M1 through M4) plus a 2019/2020 Intel reference machine, refreshed against current macOS releases and the current shipping LDB version. Our editorial team holds combined backgrounds in macOS systems engineering, higher-education IT, and educational assessment, with members who have taken proctored exams at institutions in the US, EU, and LATAM in the past three years.

Editorial review for this article: reviewed by L. Ferreira (Brazilian education-technology consultant; covers Moodle/Canvas integration in Lusophone institutions) on December 24, 2026. Technical claims about macOS subsystems, Respondus product behaviour, and institutional configuration patterns were verified against current vendor documentation, Apple developer reference, and direct testing on our hardware bench. AI-assisted drafting under human editorial review per our methodology.

Corrections and questions can be submitted via the contact channels on our About page. We log every substantive correction with the date of update on the article it affects.

How to cite this article

APA 7th edition

LDBypass Editorial. (2026). Respondus Monitor vs LockDown Browser: What's the Difference?. LDBypass. https://ldbypass.com/comparisons/respondus-monitor-vs-respondus-lockdown

MLA 9th edition

"Respondus Monitor vs LockDown Browser: What's the Difference?." LDBypass, LDBypass Editorial, 2026-05-13, https://ldbypass.com/comparisons/respondus-monitor-vs-respondus-lockdown.

BibTeX

@misc{ldbypass_respondusmonitorvsresponduslockdown,
  author = {LDBypass Editorial},
  title  = {Respondus Monitor vs LockDown Browser: What's the Difference?},
  year   = {2026},
  publisher = {LDBypass},
  url    = {https://ldbypass.com/comparisons/respondus-monitor-vs-respondus-lockdown},
  urldate = {2026-05-13}
}

References

LockDown Browser product documentation. Respondus Inc.. Accessed 2026-05-12.
ScreenCaptureKit framework reference. Apple Developer Documentation. Accessed 2026-05-12.
Privacy & Security on Mac (TCC permissions). Apple Support. Accessed 2026-05-12.
Safe Exam Browser project documentation. ETH Zurich. Accessed 2026-05-12.
Proctorio support documentation. Proctorio Inc.. Accessed 2026-05-12.
Honorlock for students. Honorlock Inc.. Accessed 2026-05-12.
Pearson VUE OnVUE online proctored delivery. Pearson VUE. Accessed 2026-05-12.
LDBypass editorial methodology. LDBypass Editorial. Accessed 2026-05-12.

Frequently asked questions

Does Respondus Monitor work without LockDown Browser?

No. Monitor is an add-on to LDB. It cannot run standalone. The recording is initiated by LDB at exam start; if LDB isn't running, Monitor doesn't activate.

How long does Respondus retain Monitor recordings?

Per institutional policy. US default is 5 years; EU institutions sometimes cap at 1 year under GDPR data minimization. Respondus retains the data on their servers and your institution can request copies.

Can I see my own Monitor recording after the exam?

No. Students cannot access their recordings directly. Your institution's academic integrity office can, on request, but that's usually only if you formally appeal a flagged exam result.

Why do schools enable Monitor instead of just LDB?

LDB alone catches casual cheating (tab switches, copy/paste). Monitor catches behavioural cheating (looking at a phone, second person in the room, eye drift). They cover different attack surfaces. Bundled, they catch more.

What if my webcam doesn't work during a Monitor exam?

Monitor will refuse to start the exam. You need to fix the webcam first. Camera troubleshooting.