How to Test Webcams in Ubuntu Without Installing Cheese

Firefox and Chrome on Ubuntu support the exact same browser-based camera testing technology as any other operating system — no Cheese or other dedicated app required. For a lower-level check of what Linux itself sees at the driver level, two quick terminal commands, ls /dev/video* and v4l2-ctl --list-devices, tell you plainly what hardware is actually detected.

Browser-Based Webcam Diagnostics on Linux

Open Firefox or Chrome on your Ubuntu machine and visit a browser-based camera test, such as the widget above. Click to allow access when prompted through your desktop's standard permission dialog, and your live feed appears directly in the page — this uses the same getUserMedia web standard that works identically across Windows, macOS, and Linux, so there's nothing Linux-specific required on the browser side at all.

This is genuinely often faster and more informative than installing Cheese specifically for a quick check, since a browser test also reports the actual negotiated resolution and frame rate your camera is delivering, which Cheese's simple preview window typically doesn't surface anywhere in its interface.

One Linux-specific detail worth knowing: the first time any browser requests camera access on a fresh Ubuntu install, your desktop environment (GNOME, KDE, or whichever you use) may show its own separate system-level permission prompt in addition to the browser's own permission request — both need to be approved for the camera to actually work.

Terminal Commands to Verify Linux Video Devices

Step 1: Open a terminal.

Step 2: Run

ls /dev/video* to list detected video device nodes. A working, recognized camera typically appears as /dev/video0 (and sometimes additional nodes like /dev/video1 for the same physical camera).

Step 3: Install v4l-utils if needed

With sudo apt install v4l-utils — many Ubuntu installs already include it, but a fresh system may not.

Step 4: Run

v4l2-ctl --list-devices for a friendlier, named list showing your camera's actual product name alongside which device node(s) it created.

If no device nodes appear at all, that points to a driver or hardware-detection issue rather than a browser or permission problem — check dmesg | grep -i usb right after plugging the camera in for any relevant kernel error messages.

Ubuntu's Own Camera Indicator

Ubuntu's own desktop camera indicator is worth knowing about too: on modern GNOME-based Ubuntu, a small camera icon can appear in the top status bar while any app actively holds the camera, giving you a quick visual confirmation of whether something else already has it open before you go looking for a deeper cause — genuinely similar in spirit to the indicator light built into the camera hardware itself.

If you regularly switch between a browser-based test and terminal commands while troubleshooting, it's worth keeping both approaches in mind as complementary rather than competing: the browser confirms whether the camera works for real-world use exactly the way a video call would use it, while the terminal commands confirm what the underlying driver layer itself detects, which is the more useful starting point specifically when the browser test itself fails to find any camera at all.

A Few More Things to Check on Linux

Am I actually in the video group, and does that matter?

Linux gates /dev/video0 access through the video group at the OS permission level, independent of any app or browser setting. Check membership with groups $USER in a terminal — if video isn’t listed, add yourself with sudo usermod -aG video $USER, then fully log out and back in for the change to take effect. Without this, every application will fail to open the camera regardless of any other setting.

How do I confirm the camera is even detected before troubleshooting software?

Run v4l2-ctl --list-devices (or the simpler ls /dev/video*) in a terminal before changing any application setting. This confirms whether the kernel sees the hardware at all — if no device node appears, the problem is detection or a driver, and no amount of app-level configuration will fix it. If a device does appear, you’ve confirmed the hardware layer is fine and the problem sits higher up, in permissions or a specific application.

Does my laptop or external webcam have a physical privacy switch?

Some laptops and most dedicated external webcams include a physical shutter or hardware switch that mechanically blocks the lens or cuts power, entirely separate from any Linux permission or driver setting. Check the camera housing itself, and the laptop’s screen bezel near the lens, before assuming a software fix is needed — a closed physical shutter produces exactly the same black frame as a permissions problem.

For a full check of resolution, frame rate, and audio together, not just this one issue, the free webcam test covers all of it in one place.