Webcam Test & Online Camera Diagnostic

Before starting, leave any Zoom, Teams, Meet, Discord, OBS, camera utility, virtual-camera app, or extra browser tab that may already be using the webcam. Modern systems often share a camera, but some drivers still permit only one active client. Closing competitors gives this test a clean baseline and makes a busy-device error meaningful.

If you use an external webcam, connect it directly for the first test. A low-power hub, monitor dock, extension cable, or loose USB adapter can create intermittent freezes that look like software trouble. Open the privacy shutter and confirm that any camera-disable key or hardware switch is in the enabled position.

Press Start webcam test. Your browser should display a permission prompt that names this site and asks for camera access. Choose Allow. The page requests video only; it does not request microphone access. If you previously blocked the site, the browser may show no prompt. Use the camera or lock icon near the address bar to change the saved decision, then reload or press Try again.

Device names are commonly hidden until permission is granted. That privacy behavior is normal. After the stream starts, the camera list refreshes and should show the built-in camera, USB cameras, capture cards, and installed virtual cameras that the browser makes available.

Give the webcam test five to ten seconds. Camera auto-exposure and white balance need time to settle, and a useful FPS range requires multiple one-second samples. Move your hand through the frame to judge motion, then stay still and look at fine detail such as hair, fabric, or printed text. A frozen but attractive frame does not prove continuous delivery.

Try the camera selector if more than one device appears. Change Requested quality to learn what the browser can negotiate, but judge the Delivered resolution—not the option you requested. Browsers may return a lower, cropped, or scaled mode when the exact hardware format is unavailable.

Test from the same browser, USB port, room, lighting, and network setup you will use for the real call or exam. The camera itself does not need internet bandwidth for this local preview, so a good result here proves local capture but not that a conferencing service can upload the video. If this page works and the meeting app does not, focus next on that app's selected device, permission, effects, and bandwidth settings.

Use Export report after the stream stabilizes if you need to share evidence with a help desk. The JSON report records browser-visible settings, capability ranges, observed frame rate, and picture signals. It does not include a photo or video frame.

Resolution is the width and height of each delivered video frame. 1280 × 720 is commonly called 720p or HD, 1920 × 1080 is 1080p or Full HD, and 3840 × 2160 is 4K UHD. Multiplying width by height gives frame megapixels: 1080p is about 2.07 MP and 4K is about 8.29 MP. Megapixels describe pixel count, not optical quality. A well-lit 1080p camera with a good lens can look better than a noisy, aggressively sharpened 4K model.

The browser, operating system, USB bandwidth, driver, and requested constraints jointly choose the delivered mode. A camera advertised as 4K may open at 1080p because Best available favors a stable common format, because another application changed the device mode, or because a hub and cable cannot sustain the highest format. Select 4K to request it and then read Delivered resolution to see the outcome.

Frames per second indicates how often a new image arrives. Around 30 FPS is normal for calls; 24 FPS can still look natural; 15 FPS or less makes motion visibly uneven. The driver-reported number is the configured track setting. Measured FPS counts frames presented during the test, so it may reveal delivery below that setting. Brief variation is normal when the tab loses focus or the computer saves power.

Low light often lowers effective frame rate because a camera lengthens exposure to collect more light. High resolution also increases processing and USB load. If FPS is low, add front-facing light first, then request 720p, connect directly to a faster USB port, close effects and virtual backgrounds, and reduce other CPU-heavy work. A perfectly steady 30 FPS is not required; sustained drops and visible stutter matter more than small numerical changes.

Aspect ratio compares frame width with height. 16:9 is the standard widescreen shape used by most HD video, while 4:3 is taller and remains common on older webcams and tablets. A conferencing app may crop either format to a tile, so keep important objects near the center and verify framing in the destination app.

Facing direction is most useful on phones and tablets: user means the front camera and environment means the rear camera. Resize mode can reveal whether the browser is using a native camera frame or crop-and-scale processing. These fields are browser-reported and may be absent even when the device is working normally.

The picture signals are lightweight estimates from a small local sample. Brightness near either extreme warns that shadows may hide your face or highlights may be clipped. Contrast measures spread between dark and bright pixels. Edge detail reacts to visible texture and can flag a covered, dirty, badly focused, or heavily blurred view, but a plain wall will naturally score lower than a detailed scene.

Average color can expose a strong cast: a deep orange average may come from warm lamps, while blue or green can indicate mixed lighting or an incorrect white balance. These are scene-dependent clues, not pass/fail laboratory scores. Use your eyes alongside them. Put a neutral white sheet in the same light as your face if you want a simple white-balance reference.

Capability ranges are values the current browser and driver say the active video track can accept. They may include minimum and maximum width, height, frame rate, hardware zoom, torch, focus, or exposure modes. Support varies widely. Desktop browsers often report basic resolution and FPS while withholding vendor-specific controls; mobile browsers may expose torch or continuous focus.

A dash means not reported, not necessarily unsupported. Web pages cannot reliably read sensor size, lens aperture, field of view, firmware version, USB generation, true optical resolution, hardware serial number, or whether a microphone is physically built into the same shell. The camera label and device grouping can offer hints, but this tool avoids pretending that an inference is a verified specification.

Place the lens near eye level and roughly an arm's length away. Leave a little space above your head, include the top of your shoulders, and look into the lens when speaking. Preview zoom only enlarges this page's display; it does not change what another app receives. Fill frame crops the preview edges, while Fit frame shows the full delivered image.

A webcam mirror behaves like a familiar bathroom mirror, which makes grooming and hand movements feel natural. Other participants usually receive an unmirrored image even when your self-view is mirrored. Switch Mirror off to inspect text, logos, room layout, and the orientation others are likely to see.

Face a window or a soft lamp placed slightly above eye level. Avoid a bright window directly behind you; automatic exposure may darken your face to preserve the background. If you wear glasses, raise and move the light sideways until reflections leave the lenses. Mixing daylight with strongly colored bulbs can confuse automatic white balance.

Clean the lens with a dry microfiber cloth. Laptop camera covers and fingerprints create haze that software sharpening cannot repair. If autofocus hunts, increase light, move away from a blank background, remove transparent protective film, and give the camera a high-contrast object at your face distance before returning to your seat.

After this camera test passes, open the settings page in Zoom, Google Meet, Microsoft Teams, Discord, OBS, or the exam platform and select the same device name. Turn off virtual backgrounds, beauty filters, auto-framing, portrait blur, and third-party camera layers while diagnosing. Re-enable them one at a time only after the raw feed is stable.

Take a short test call if possible. A local online mirror or webcam test cannot measure upload bandwidth, packet loss, service-side compression, recipient rendering, echo cancellation, or corporate firewall behavior. Local clarity with poor call quality usually points beyond the webcam itself.

Look for a camera, lock, or sliders icon beside the address. Change Camera from Block to Allow for this site, then reload. If the site is absent from browser settings, clear its stored permission and start again. Private browsing, strict extension policies, embedded pages, parental controls, school or employer management, and non-secure HTTP pages can prevent a normal prompt.

Browser permission is only one layer. Windows and macOS can independently block the entire browser. A managed computer may gray out those controls; in that case an administrator must change the policy. Do not disable security software globally. Check whether it has a specific webcam-protection list and authorize only the browser you trust.

Quit every application that might capture video, including background tray utilities and other browser windows. Restart the browser. If the camera light remains on after the test stops, inspect the operating system's privacy indicator to find the active app. Virtual cameras and vendor control software can create an extra layer that holds the physical device.

For USB cameras, unplug the cable, wait several seconds, and reconnect directly to another port. Avoid an unpowered hub during diagnosis. Check the connector and cable for movement, and test the camera on a second computer if available. If failures follow the camera, cable, or adapter, hardware is more likely; if they remain on one computer, focus on drivers, policy, power management, or software conflicts.

Open the physical privacy shutter and check for a camera-disable key, often marked with a crossed-out camera and sometimes used with Fn. Some laptops disconnect the camera electrically when that switch is off, so software cannot override it. Remove any sliding cover or tape and verify that a case is not blocking a phone or tablet lens.

If the track is live but the image stays black, shine a moderate light toward the scene, choose another listed camera, and test the operating system's Camera or Photo Booth app. A black image in every app suggests a driver, firmware, cable, or sensor issue. A black image in only one app points to that app's selected device, effects pipeline, or permissions.

Choose the intended device from the Camera menu. Capture cards, phone-camera bridges, virtual cameras, infrared sign-in sensors, and old disconnected entries may all appear beside the built-in webcam. If names are hidden, grant access first. Then select each entry and watch the active label and preview.

Mirror changes only this page's preview and snapshot. It does not reconfigure the camera driver or another conferencing app. An upside-down or rotated feed in every application usually needs a manufacturer driver, device utility, mounting correction, or operating-system update. If only one app is rotated, reset that app's video transform.

Clean the lens, remove protective film, add soft front light, and avoid digital zoom. Grain is commonly automatic gain amplifying a dark scene. Washed-out skin usually comes from overexposure or a strong backlight. Color casts often come from mixed color temperatures. Let automatic exposure and white balance settle for several seconds after changing the room.

Flicker often results when a lamp's electrical frequency and camera exposure interact. Try daylight or a different LED lamp, change the camera's anti-flicker setting between 50 Hz and 60 Hz in its vendor app, or use 25/50 FPS in 50 Hz regions and 30/60 FPS in 60 Hz regions when those controls exist. Persistent colored lines or blocks across every app can indicate a damaged cable, sensor, or driver.

First add light and request 720p. Close virtual backgrounds, recording tools, games, many browser tabs, and other CPU or GPU workloads. Plug a laptop into power and disable aggressive battery saving for the test. Connect a high-resolution USB camera directly rather than sharing a hub with storage devices. Update the browser, operating system, and camera driver from trusted sources.

This page measures local frame presentation, not network performance. If the local preview remains smooth while a call freezes, test upload speed, packet loss, Wi-Fi congestion, VPN behavior, and the conferencing service. If local video also freezes, the bottleneck is more likely the device, driver, USB link, browser, or computer resources.

A passing result proves that this browser tab can receive the selected camera. It does not grant permission to a desktop app or a different website. Open the failing app's video settings, choose the exact same device, and check both its permission and the operating system's app-level control. Fully quit and reopen the app after changing system permission.

Remove optional complexity: disable virtual cameras, background replacement, hardware acceleration changes, browser extensions, and camera vendor filters. Corporate firewalls and exam lockdown software may enforce their own requirements. Run that platform's official system check and compare the reported device. If a platform rejects virtual cameras, select physical hardware directly.

Select the site controls, lock, or camera icon near the address bar, set Camera to Allow, and reload. For a global review, open browser Settings, then Privacy and security, Site settings, and Camera. Confirm the correct default device and remove this site from the blocked list. Menu names can vary slightly by browser version.

On a work or school profile, a notice that the browser is managed means policy may control camera access. Try an authorized personal profile only if organizational rules permit it; otherwise contact the administrator with the exported error name and report.

In Safari on macOS, open Safari Settings, choose Websites, then Camera, and allow this site. You can also change the current site's setting from Safari's website settings. In Firefox, use the permission icon in the address bar or open Privacy & Security settings, find Permissions, and manage Camera exceptions. Reload after changing a stored denial.

On iPhone or iPad, Safari still depends on iOS camera privacy and Screen Time restrictions. On Android, the browser needs Android camera permission in addition to the website decision. If the operating system denied the browser itself, changing only the address-bar setting will not be enough.

Open Settings, Privacy & security, then Camera. Turn on Camera access and Let apps access your camera. Browsers and traditional conferencing programs are desktop apps, so also enable the control that lets desktop apps access the camera. On Windows 10, the path begins in Settings, Privacy, Camera.

If the camera is missing, run the Windows Camera app and the Camera troubleshooter, inspect the hardware shutter, and check Device Manager. Prefer the computer or camera manufacturer's signed driver. After a driver or permission change, restart the browser; after a larger system update, restart Windows.

Open Apple menu, System Settings, Privacy & Security, then Camera. Enable the browser or app that needs access and quit/reopen it when prompted. Check Screen Time under Content & Privacy if Camera is restricted. Safari websites also have their own per-site decision, so both layers must allow access.

The green camera indicator should illuminate while a built-in Mac camera is actively delivering video and turn off after every camera track stops. If the built-in camera fails in multiple Apple and third-party apps after an update and restart, follow Apple's model-specific service guidance.

The live video element receives a local MediaStream supplied by the browser. Small frames are sampled in memory to estimate brightness, contrast, edge detail, and average color. Snapshot pixels are turned into a temporary local object URL only after you press Take snapshot. The camera tool does not send video, images, or the generated diagnostic report to a server.

Stop camera ends every track opened by this tool. Closing or reloading the tab also ends access. Your operating system or device may display a light or privacy indicator while capture is active. The microphone is not requested, although the device inventory may count audio inputs whose presence the browser is already permitted to reveal.

Current browsers restrict camera APIs to secure contexts such as HTTPS and require a user permission decision. Permission belongs to the website origin, so allowing this page does not automatically authorize an unrelated site or desktop application. Conversely, a camera that works in a desktop app has not proven that this browser and site are allowed.

Device labels and identifiers may remain hidden or randomized until access is granted. This reduces silent fingerprinting. The exported report includes useful settings and the human-readable camera label but intentionally omits device and group identifiers. Review any report before sharing it because a model name and browser user agent may still reveal details about your setup.

A browser test cannot certify sensor health, lens alignment, color accuracy, true dynamic range, autofocus calibration, microphone ownership, or maximum advertised hardware specifications. It cannot see another app's private settings. Picture metrics change with the scene, and browser capability reports vary by driver. The results are diagnostic clues, not a warranty assessment or biometric check.

The local preview also bypasses the network path used by a meeting. It cannot measure upload capacity, service compression, end-to-end latency, packet loss, remote image quality, or whether a proctoring platform accepts the device. Use this tool to establish a strong local baseline, then use the destination platform's own preview or test call for final confirmation.