Six minute read

Can Canvas Detect Cheating on Your Phone?

Canvas cannot see a phone sitting next to your laptop. It can see plenty about the device actually taking the quiz. Here is the exact line between the two, what changes the moment proctoring is switched on, and why a phone is the worst tool in a monitored exam.

Short answer. Canvas can only see the browser session taking the quiz. A phone sitting beside your laptop is not part of that session, so Canvas records nothing about it. That answer changes completely if the phone is the device taking the quiz, or if a proctoring service is watching the room. Those are three different situations and they get confused constantly.

Situation 1: phone beside you, quiz on your laptop

This is what most people mean by the question, and the answer is no. Canvas has no mechanism to detect a second device in the room. It is a web application. It receives requests from the browser that is logged in and taking the quiz, and it knows nothing else exists.

Specifically, Canvas cannot see:

  • That a phone is nearby, powered on, or in use.
  • What you look up on it.
  • That it is on the same Wi-Fi as your laptop. Canvas records the IP address of the request, and does not scan the network for other devices. We took apart that particular myth in Canvas Privacy Myths.
  • Anything at all through your laptop camera. Canvas has no camera access without a proctoring tool bolted on.

The reason students use a phone in the first place is precisely this: it produces no events in the quiz log, because your browser never leaves the quiz page. Compare that with a second tab, which does produce events, as covered in Canvas Stopped Viewing Flag Explained.

What it costs you is time. Typing a question into a phone, reading a result on a small screen, and translating it back to the laptop is the slowest workflow available, and on a timed quiz that is a real risk of its own. An unfinished quiz is a worse outcome than a slightly odd log.

Situation 2: the phone is taking the quiz

Now Canvas sees the device, because the device is the client. From the request itself, it records:

  • The user agent, which identifies mobile Safari or Chrome on Android, and often the OS version.
  • The IP address, which shows a cellular network if you are on data rather than Wi-Fi.
  • Whether the request came through the Canvas Student app rather than a mobile browser.

None of that is cheating detection. It is ordinary web server logging, and taking a quiz on your phone is completely legitimate at most institutions. It matters only in one scenario: if the log shows the quiz was taken on a phone while you told your professor you were at your desk on a laptop, the inconsistency is what causes the problem, not the phone.

One practical warning that has nothing to do with integrity. Mobile browsers aggressively suspend background tabs, and switching apps on a phone can register the same "stopped viewing" event as a tab switch on a desktop. A phone call arriving mid-quiz can do it. If you take quizzes on a phone, the log is noisier through no fault of your own, which is a good reason to use a laptop for anything graded.

Situation 3: proctoring is switched on

Everything above inverts. Proctoring software is not Canvas, it is a separate layer that runs alongside it, and detecting phones is one of the things it is explicitly built to do.

Signal Canvas alone With proctoring
Phone visible in the room No Yes, webcam and room scan
Eyes repeatedly looking off-screen No Yes, gaze heuristics
Second device on the same network No Sometimes, depending on the service
Audio in the room No Yes, if microphone monitoring is on
Browser events in the quiz Yes Yes, plus screen recording

Under Honorlock, ProctorU, Respondus Monitor or similar, a phone is the most detectable thing you can reach for. It requires a distinctive physical movement, repeated, on camera, and the recording is reviewable long after the exam ends. Some services also run a pre-exam room scan specifically to establish that no second device is present, which turns a phone from an ambiguous signal into a documented contradiction.

We broke down what each service actually monitors in ProctorU, Respondus and Honorlock and what runs at the browser level in Browser Lockdown and Exam Security.

So how does Canvas detect cheating on quizzes at all?

It does not, in the sense people mean. Canvas is a logger, not a detector. There is no flag that says a student cheated. What exists is a timeline of events that a human reads and interprets: when you viewed each question, when you answered, when you changed an answer, and when your browser left the page.

Cases are built on patterns, not on single events, and usually on more than the log alone: a score that does not match previous work, an answer a student cannot explain when asked, or several students in the same section producing identical unusual answers. The full picture is in Does Canvas Detect Cheating? and the process that follows is in What Happens If You Get Caught Cheating on Canvas?.

The honest summary

  • Phone next to you, unproctored quiz on a laptop: invisible to Canvas, slow to use.
  • Phone taking the quiz: logged as a device, which is normal, but the log is noisier.
  • Anything proctored: the phone is the easiest thing in the room to catch, and reaching for it is a worse decision than any browser behaviour.

The phone is popular because it avoids the quiz log, not because it is fast. If avoiding the log is the actual goal, there is a better way to get it.

Keep the log clean without the phone

ExamClutch does the thing the phone workaround is trying to do, without the phone. It reads the question from the Canvas page you are already on, gets the answer, and applies it on a double-click. Your browser never leaves the quiz, so there is no "stopped viewing" event, and you are not typing questions with your thumbs while a timer runs.

It covers Canvas, Blackboard, Brightspace, Moodle, Schoology, McGraw Hill and Google Forms, across multiple choice, multi-select, dropdown and fill-in-the-blank. It fills the answer in and leaves submitting to you. It also does not pretend to work under lockdown browsers, because no extension does.

Ready to stop fighting your LMS?