LockDown Browser does two jobs, and only one of them involves seeing anything. The first is locking the machine: full screen with no address bar, copy and paste cut off, printing and screen capture disabled, other applications unreachable, and a flat refusal to run inside a virtual machine or a remote desktop session. The second is recording you, and that half exists only when the instructor has switched on Respondus Monitor, the webcam add-on. A plain locked exam has no camera and no microphone attached to it, so there is nothing to record and nobody watching.
Almost every confused answer about this tool comes from collapsing those two halves into one. People describe a browser that watches everything they do, when what they sat was a locked exam with no camera anywhere in it. Other people assume there is no camera because nobody mentioned one, then meet a room scan on exam day. Same download, two very different sessions.
The lock: what it stops, and what stopping it reveals
Read this column by column as restrictions rather than surveillance. Every row is the browser preventing something on the machine it is running on, not a feed going anywhere.
| What is locked | How it behaves in the session | What that means for "can it see" |
|---|---|---|
| Copy and paste | Copying out of the exam and pasting in from another application are blocked, and the right click menu is stripped back to almost nothing. | Nothing to see. The transfer never happens, so there is no paste event to log the way an ordinary web assessment would. |
| Printing and screen capture | Print is off unless the instructor enabled it, and the operating system screenshot path is disabled while the exam is open. | The exam pages are meant to leave no artefact. This is about stopping the question bank from walking out, not about watching you. |
| Other applications | Tools it classes as screen capture, screen sharing, streaming or remote control must be closed before the exam will start, and launching one part way through can halt the attempt. | This is the one place it genuinely reads your machine. It looks at what is running by name, matches against a blocklist, and tells you what to close. |
| Task switching and navigation | The exam is full screen and cannot be minimised, task switching is blocked, and you cannot type a different address because there is no address bar. | It has no need for tab switching detection, because there are no tabs to switch to. Contrast an ordinary browser based test, which logs that focus left and nothing more. |
| Virtual machines | Running inside VMware, VirtualBox, Parallels or Hyper-V is refused unless the instructor has explicitly allowed virtual machines for that exam. | It sees the markers of a guest operating system, not what is on the host. The usual outcome is a blunt error message before the exam ever opens. |
| Remote desktop sessions | Connecting in over RDP, VNC or a remote support tool is detected and refused on the same principle. | The check is whether the session is local. It cannot tell who is at the other end, only that somebody could be. |
| Extra displays | Where more than one display is attached, the standard behaviour is to stop and ask you to disconnect the extra screen before continuing. | It knows how many displays exist and how they are arranged. It does not receive an image of what a second monitor was showing. |
| Leaving early | The exam cannot be exited until it is submitted, unless the instructor supplies a password that breaks out of it. | An abandoned attempt shows up to the instructor as an attempt. That is a record of behaviour rather than a picture of anything. |
Notice what the whole right hand column has in common. The lock knows the shape of your machine, running process names, display count, whether the session is virtual or remote, and it knows when the exam window lost its grip. None of that is content. It is not indexing your files, reading saved passwords, or pulling another browser's history, and it stops when the exam closes.
The recording half, in the order you meet it
Respondus Monitor is enabled per exam by the instructor, and it announces itself loudly before the timer starts. If you never saw this sequence, you were not recorded.
Webcam check
A short clip records and plays back so you can confirm the camera and microphone work. Audio is part of that check, which is the first clear signal that the room, and not only the screen, is in scope.
Student photo
A still of your face is captured and stored against the attempt, so the video can be tied to a person rather than to a login.
Photo ID
Where the instructor requires it, you hold a student card or government ID up to the camera and it is captured as a second image.
Environment check
You pan the webcam around the room and across the desk. This is the step people describe afterwards as invasive, and it is the one that captures the space rather than the machine.
Instructor steps and guidelines
Custom instructions, a rules page to accept, sometimes an extra prompt written by the department. These vary course to course, so two exams at one university can differ here.
Continuous recording until submit
Video and audio run for the length of the attempt and upload when you finish. The lock is still doing every single thing in the table above at the same time.
What the instructor receives is not raw footage they have to watch end to end. It is a timeline with marks on it. Events such as the face leaving the frame, a second face appearing, light dropping too low to make anything out, or an interruption in the connection get flagged, and those marks roll up into a review priority that sorts the class list. Treat that priority as triage. It decides which videos a human opens first, and a human opening yours can look at a flagged minute and see somebody who stretched, rubbed their eyes, or had a housemate walk behind them. Whether the exam screen itself is captured alongside the webcam varies by version and by how your institution has it configured, so read your course's own instructions rather than assuming either way.
The blind spots that follow from the design
Stating these plainly is not advice, it is the reason the tool is shaped the way it is. LockDown Browser controls exactly one machine, the one it is installed on. It has no view of a phone on your lap, a tablet on the next chair, a second computer, or a person standing behind the camera. Monitor closes part of that gap by pointing a lens at the room, which is precisely why the environment scan exists and why a missing face is a flag. A locked exam without Monitor is a deterrent and a controlled environment, not an observer, and institutions that need more than that still book invigilated halls.
Where OfferPilot AI is the wrong tool, and we should say so
A vendor publishes this page, so here is the honest boundary. Code Copilot is a Windows 10 and 11 desktop overlay built for job interviews and coding rounds. Its window is excluded from screen capture at the operating system level, so it is absent from Zoom, Teams, Meet, OBS and screenshots while staying visible on your own monitor. That is a screen sharing feature, and it is irrelevant to this page in three separate ways.
- A locked exam is not a screen share. Nothing is being streamed to a viewer for an overlay to be missing from. LockDown Browser blocks other applications from running at all, which lands well before any question of what a capture would have contained.
- Monitor points a camera at your face. Capture exclusion does nothing about a webcam, room audio, an ID photo, an environment scan, an invigilator in the room, eye tracking, or a phone propped up as a second camera.
- The platforms do not even match. Our software is Windows only, with no macOS, Linux, mobile or browser extension build, while LockDown Browser exams routinely run on Macs, iPads and Chromebooks.
We build for job interviews and interview preparation. A proctored academic exam under LockDown Browser is not a use we support or want, and the correct answer to one is to study for it. If an exam is what brought you to this query, the useful next click is your institution's own proctoring policy, not a product page.
Working out in sixty seconds which version you are sitting
- Did the exam ask you to close specific applications, or refuse to start until you did? That is the lock, and the lock is always on.
- Did anything request camera permission, play back a webcam test, or take your photo? No such step means no recording on that attempt.
- Were you asked to show an ID or pan the room? That is Monitor running the fuller startup flow.
- Did it halt and tell you to unplug a second screen, or refuse to run in a virtual machine? Those are environment checks, and they happen with or without a camera.
- Assume the attempt itself is logged either way. Start time, submit time and whether the session was broken out of need no permission prompt and produce no visible signal.
The short version worth carrying away: the lock is about your machine and it is thorough, the recording is about you and it is optional. Collapsing the two is what makes this tool sound either harmless or omniscient, when it is neither. The rest of the guides cover how the same split plays out on the assessment platforms used in hiring, where the line between locking and recording gets drawn very differently.
Related guides
- Does HireVue Record Your Screen or Just Your Camera and Mic?
- Can CoderPad See If You Switch Tabs? CoderPad vs HackerRank
- Can Zoom See Everything on My Computer? What It Really Holds
- Can a Zoom Host See If You Switch Tabs? The Three Signals
- Can Proctoring Software Detect a Second Monitor? How It Knows