The short answer: on a school-managed Chromebook, the camera is usually controlled by the school's Google Admin console, not by the teacher or the student. A web game can't use the camera if the admin has turned camera input off for websites that aren't on an allow list, if the site is blocked by the URL filter, or if someone clicked "Block" when the site first asked. A teacher can check the last one in a minute; the first two need whoever runs the school's Admin console. Below is what to check, in order, and the exact settings to send to IT.
This page uses Hoppo as the example: free webcam movement games for kids 5-8 that run in the browser, with no student accounts. The same checks apply to any web page that uses the camera.
For teachers: three checks before you email IT
- Is the camera switched on at all? Some Chromebooks have a physical camera switch or slider; it has to be on. Then open Settings, choose Privacy and security, then Privacy controls, and make sure Camera access is on. Google notes that turning it off there blocks the camera everywhere. (Google: camera settings on a Chromebook)
- Was the site blocked by mistake? In Chrome, open the menu, then Settings, Privacy and security, Site settings, Camera. If playhoppo.com is in the "not allowed" list, select it and change Camera to Allow, or delete the entry so the site can ask again. Typing
chrome://settings/contentin the address bar gets to the same place. Reload the game page afterwards. (Google: use your camera in Chrome) - Is the setting greyed out? Then it's managed. Google's help says that at work or school, the network administrator can set camera settings and you may not be able to change them. That's the point to send the next section to IT.
For school IT: the Admin console settings
These are in the Google Admin console under Devices, then Chrome, then Settings (User & browser settings), for the organizational unit the student or teacher accounts are in. All of the wording below is from Google's own help pages, linked at the end of each item.
- Video input (Hardware section). The default lets websites ask for the camera. If it's set to disable camera input for websites and apps, only the URLs in the next setting can use the camera. (Google: Chrome policies for users or browsers)
- Video input allowed URLs. URLs listed here get the camera without a prompt. Patterns are matched against the site's origin, so add
https://playhoppo.com. Students then won't be asked at all, so only add sites your school is happy to allow. (Hoppo doesn't use the microphone, so audio input doesn't need to change.) - URL Blocking (Content section). If the school blocks most sites, add these to Blocked URL exceptions:
playhoppo.com, pluscdn.jsdelivr.netandstorage.googleapis.com, which are the backup source for the tracking files when the main copy can't load. (Google: allow or block access to websites) - Disabled system features. Google recommends this, rather than URL blocking, for turning off features like the camera. If the camera is disabled there, no site can use it, and an allow list won't help.
If the district also uses a separate web filter, the same three domains go on its allow list. What the camera data does and doesn't do is written up for administrators on how Hoppo keeps webcam video private: tracking runs in the browser, no video, pictures or body points are sent, and there are no student accounts.
Test it before the lesson
- Use the same kind of account the class will use (a test student account in the same organizational unit), on the same kind of Chromebook. A teacher account often has different settings.
- Open Bubble Pop. It's a hand game, so sitting one big step back from the screen is enough.
- Allow the camera if Chrome asks. (If the site is on the allowed URLs list, Chrome won't ask.)
- Wave. If the bubbles pop, the camera and tracking work. If nothing responds in good light, one of the settings above is still blocking the camera. The first load downloads the tracking files once, so give it a moment on a slow network.
- For whole-class use on a smartboard, run the same test on the computer driving the board. See smartboard games for camera placement.
When the camera works but the game can't see the kids
- Light in front, not behind. A bright window behind the player turns them into a silhouette. Face the camera away from the window, or close the blind.
- Step back. About one big step back for hand games; two or three for whole-body games like Hoppo Says.
- Keep it plugged in. The camera and tracking use a lot of battery.
- Give it the whole machine. Close other tabs and video calls; a busy or older machine tracks less smoothly.
- Use touch. Many games also play by tapping, and if the camera can't see well in one of them, the game offers to switch to touch. That helps on touchscreen Chromebooks.
More in setup tips.
If the camera has to stay off
Some districts don't allow webcams on student devices at all. The free Brain Break doesn't use the camera, so it works on school computers where the camera is blocked: Hoppo calls each move on the screen and the whole class copies, for 2, 3 or 5 minutes.
When Hoppo fits, and when it doesn't
It fits when IT can allow one site for the camera on a classroom computer or Chromebook: no installs, no extensions, no student accounts and no student data.
It doesn't fit where policy keeps the camera off for every website. Then the camera games won't run, and the Brain Break or the touch games are the options. We can't change a school's settings from our side, and we wouldn't want to.