Webcam & Mic Test Online

Yes, online exam proctoring software (such as Respondus LockDown Browser, Proctorio, Honorlock, Examity, and ProctorU) can actively detect screen sharing. These platforms employ system-level background monitoring that detects active secondary monitors, virtual display adapters (like DisplayLink or HDMI capture cards), OS screen-recording hooks, and background remote-access software such as Zoom, TeamViewer, AnyDesk, Discord, or OBS Studio.

Yes, modern online testing systems and Learning Management Systems (LMS) like Canvas, Blackboard, Moodle, and D2L Brightspace use multiple detection mechanisms to prevent cheating:

• Browser Lockdown & Focus Tracking: Flags when a student switches tabs, leaves the exam window, copies/pastes text, or opens developer tools.
• Webcam & Audio Proctoring: Monitors eye movements, head orientation, background voices, or multiple people in the room.
• Keystroke & Time Analytics: Measures time spent per question and typing rhythm patterns to detect pasted or automated responses.
• IP & Device Fingerprinting: Detects shared network access, proxy servers, or virtual machines (VMs).

Yes, AI-powered proctoring software uses computer vision and machine learning models to detect cheating in real time. AI proctoring engines analyze webcam feeds using facial recognition (ensuring the registered student is present), eye tracking (flagging prolonged glances off-screen), object detection (spotting smartphones, secondary monitors, or textbooks), voice classification (distinguishing human speech from room ambient noise), and AI text detection algorithms to scan submitted essays for ChatGPT-generated content.

Yes, online tests and web-based exam portals can detect screen sharing through browser Page Visibility APIs (detecting focus loss or window blurs), WebRTC getDisplayMedia API listeners, and proctoring lockdown clients. When an unauthorized screen share, HDMI splitter, or mirroring session is initiated, the test system can log the security event, notify the exam proctor, or automatically freeze and invalidate the assessment.

To test a gamepad on Windows 10 or 11, connect your controller via USB or Bluetooth and open our Gamepad Tester. Press any button to initialize detection. The tool automatically maps every button, analog thumbstick axis, deadzone, trigger pressure level, and vibration rumble motor in real time, helping you diagnose controller stick drift and input lag.

No. Camera, microphone, speaker, screen share, and gamepad diagnostics run 100% locally in your browser — no video streams, audio recordings, or snapshots leave your device or get uploaded to any external server.

Click the lock or tune icon on the left side of your browser's address bar (URL bar), set Camera and Microphone permissions to Allow, and refresh the page.

Testing your webcam online takes less than a minute: 1. Click 'Start Test' or 'Allow' in your browser security popup. 2. See your live camera stream on screen to check framing, room lighting, and colors. 3. If you have multiple webcams connected, use the device selector dropdown to switch between them. 4. Analyze live video stream quality including real-time FPS frame delivery and image sharpness. 5. Capture a snapshot or short test video to confirm how you look before important meetings.

If your webcam does not turn on or displays a black screen: 1. Browser permission denied: Click the lock or settings icon next to your URL bar, ensure Camera is set to 'Allow', and reload. 2. Camera in use: Zoom, Microsoft Teams, Skype, Discord, or OBS may be locking the camera feed. Close background apps. 3. System privacy: Check Windows Settings > Privacy & security > Camera, or macOS System Settings > Privacy > Camera. 4. Drivers: Update camera drivers through Device Manager. 5. Cable: Unplug and reinsert the USB cable or test on a different USB port.

To test your microphone online: 1. Click 'Test Mic' and select 'Allow' when your browser asks for microphone permissions. 2. Speak normally into your mic and observe the real-time audio waveform and decibel gauge moving. 3. Use the voice loopback playback feature to listen to your voice and confirm clear, balanced sound without static before joining calls.

If your microphone registers no sound: 1. Check browser permissions (lock icon in URL bar) and set Microphone to 'Allow'. 2. Close background apps like Zoom, Discord, or Teams that may hold an exclusive audio lock. 3. Confirm microphone access is enabled in Windows/macOS privacy settings. 4. Check for a physical mute switch or inline volume wheel on your headset. 5. In Windows Sound Settings, verify input volume is set above 80%.

To test your camera resolution and frame rate online, navigate to our Webcam Test Online tool and click Allow when your browser requests camera permissions. The tool immediately probes hardware capabilities, measuring true sensor resolution (720p HD, 1080p Full HD, or 4K Ultra HD) and calculates real-time rendering FPS by inspecting frame delivery intervals.

A black camera stream or 'device already in use' error usually means another application currently holds an exclusive lock on your camera. Check for background instances of Zoom, Microsoft Teams, Skype, Discord, OBS Studio, or Windows Camera App. Close those applications, check that your physical camera privacy shutter is slid open, and refresh the browser page.

To unblock or allow camera permissions: 1. In Google Chrome and Microsoft Edge, click the tune/padlock icon on the left side of the address bar. 2. Toggle Camera to Allow. 3. In Safari, go to Settings > Websites > Camera and set this site to Allow. 4. In Windows Settings, verify that Privacy > Camera > Let desktop apps access your camera is enabled.

Webcams have small physical optical sensors that create digital noise (grain) when lighting is dim. To instantly improve video quality: 1. Place a soft light source (lamp or ring light) directly in front of your face, avoiding harsh backlighting. 2. Keep your camera at eye level. 3. Clean the camera lens with a microfiber cloth to remove oily finger smudges.

Webcam video flickering is caused by a frequency mismatch between your room's AC electrical lighting and the camera's shutter speed. In North America and Japan (60Hz power grid), set your camera anti-flicker setting to 60 Hz. In Europe, India, and the UK (50Hz power grid), set anti-flicker to 50 Hz in your webcam utility or Windows Camera settings.

No. Modern web browsers strictly mandate explicit user consent through HTTPS before activating camera feeds. Furthermore, WebcamMicTest processes all video frames locally inside browser canvas memory using WebRTC — zero video frames, photos, or hardware IDs are ever uploaded to any cloud server.

To ensure professional video for Zoom, Teams, or streaming, measure: 1. Real-time FPS: Verify your camera maintains smooth 30 FPS or 60 FPS without frame drops in normal lighting. 2. Lighting & Exposure: Avoid underexposure (too dark) or overexposure (blown-out highlights). 3. Image Sharpness: Check facial focus clarity and sensor noise grain. 4. Rule-of-Thirds Framing: Center your eyes along the upper horizontal third of the frame. 5. Mirror vs. Natural View: Toggle views to confirm how others see you versus how you look in a mirror.

Yes. The test is 100% free and completely private. All camera feed processing, frame rate counting, and resolution detection run entirely client-side inside your local browser. No video frames, audio tracks, or captured images are ever recorded, stored on a server, or transmitted over the internet.

To test your microphone and hear your own voice, open our free Microphone Tester and click Allow for audio access. Speak into your mic and click Record & Playback. The tool captures a short 5-second audio sample and immediately replays it through your headphones so you can evaluate voice clarity, background noise, and volume levels.

In digital audio metering (dBFS), 0 dBFS is the maximum digital ceiling before distortion (clipping) occurs. For video calls, streaming, and podcasting:

• Ideal Speaking Range: Between -18 dBFS and -6 dBFS.
• Too Quiet: Below -30 dBFS (voice gets buried in noise).
• Clipping / Distorted: Above -3 dBFS (causes harsh audio crackle).

Use our real-time decibel meter to adjust your microphone gain until normal speaking peaks comfortably in the green/yellow zone.

If your microphone input volume is faint: 1. Go to Windows Settings > System > Sound > Input > Device Properties and slide Volume up to 90-100. 2. If available, increase Microphone Boost by +10 dB or +20 dB. 3. Position the mic 3 to 6 inches from your mouth and speak into the front of directional (cardioid) microphones.

Static and humming are typically caused by electrical ground loops or USB electrical interference. To fix it: 1. Plug USB microphones into a rear motherboard USB port rather than an unshielded front case jack. 2. Enable browser noise suppression. 3. Keep audio cables away from power transformers and AC cords. 4. Use a foam windscreen or pop filter to block plosive breath bursts.

In Windows 11: Navigate to Settings > Privacy & security > Microphone. Toggle Microphone access to On and confirm your browser is permitted. On macOS: Open System Settings > Privacy & Security > Microphone and ensure the checkbox next to Google Chrome, Safari, or Firefox is checked.

Our microphone tester uses the Web Audio API's AnalyserNode to run a Fast Fourier Transform (FFT) on incoming audio waveforms. It decomposes your voice into 32 discrete frequency bins spanning from 20 Hz (sub-bass) up to 20,000 Hz (treble), showing you real-time frequency resonance and vocal warmth.

Use our built-in Voice Loopback / Mic Playback module. Wear headphones to prevent acoustic feedback screeching, speak a test sentence into your microphone, and press playback. You will hear your voice exactly as others on Zoom, Google Meet, or Discord will hear you, allowing you to gauge volume, background noise level, and vocal warmth.

Yes. You can record a test audio clip with your first microphone, then switch the input device selector to your second microphone and record the same sentence under identical room conditions. Playing both back allows you to easily compare noise suppression, frequency response, and vocal presence.

To test left and right stereo channels online, open our Speaker Tester and click Test Left Channel, followed by Test Right Channel. You will hear an acoustic reference tone isolated strictly to one side at a time. This confirms whether your headphones, desktop speakers, or laptop sound drivers have correct stereo panning and channel separation.

Put on your headphones and use our dual-channel stereo sweep. The tone should sound centered directly between your ears. If the sound tilts toward one ear, check Windows Sound Settings under Device Properties > Balance to ensure Left (L) and Right (R) volume sliders are set to equal values.

Healthy human hearing spans from 20 Hz (deep sub-bass) up to 20,000 Hz (20 kHz) (ultra-high frequencies). As people age, high-frequency perception typically diminishes to around 14 kHz - 16 kHz. Our built-in sine wave frequency generator allows you to sweep frequencies from 20Hz to 20kHz to test speaker driver limits and hearing range safely.

If one side of your headphones or speakers has no sound: 1. Fully insert the 3.5mm audio jack (partial insertion shorts channels). 2. Clean lint or dust out of the headphone port using a wooden toothpick. 3. Check for cable strain or broken copper wires near the jack. 4. In Bluetooth headphones, reset the pair to re-sync true wireless stereo (TWS) channels.

White noise has equal energy per Hertz across all frequencies, sounding like harsh TV static with heavy treble. Pink noise decreases by 3 dB per octave as frequency doubles, matching the logarithmic way human hearing perceives loudness. Pink noise is the industry standard used by audio engineers to test room acoustics and calibrate studio monitor frequency balance.

Audio popping and crackling are commonly caused by: 1. Buffer Underruns (DPC Latency): Update your Realtek or sound card drivers. 2. Sample Rate Mismatch: In Windows Sound Control Panel, set both playback and recording formats to 24-bit, 48000 Hz (Studio Quality). 3. Disable audio enhancements or spatial sound effects that cause processing lag.

Testing left and right channels verifies that your headphones are worn correctly and that audio cables or Bluetooth codecs have not reversed stereo panning. In video games, directional sound cues (like footsteps) rely on accurate stereo separation. In music and video editing, inverted channels can ruin stereo imaging and phase alignment.

To evaluate newly purchased headphones or studio monitors, play acoustic sweep tones and reference recordings across the audible spectrum (20Hz to 20,000Hz). Listen for punchy sub-bass without mud, transparent mid-range for clear vocals and dialogue, and smooth treble highs without harsh sibilance or distortion.

A tone generator creates pure mathematical sine waves at specified frequencies (e.g. 50Hz, 100Hz, 1kHz, 10kHz). Playing these tones at moderate volumes reveals physical driver limitations, including driver buzzing, rattling speaker cones, loose headphone housings, or uneven acoustic volume across the frequency spectrum.

If no sound plays: 1. Confirm your physical 3.5mm audio jack is pushed completely into the port (a partial plug shorts stereo channels). 2. Verify that Windows or macOS output device is set to your headphones and not an inactive monitor speaker. 3. Check physical volume wheels or inline mute switches. 4. For Bluetooth earbuds, place both buds in the charging case to resynchronize true wireless stereo (TWS) pairing.

To test controller stick drift online, connect your controller via USB or Bluetooth and open our Gamepad Tester. Press any button to activate detection. Leave both analog thumbsticks in their resting neutral position: the live coordinate graph shows stick offsets from (0.00, 0.00). If coordinates deviate beyond 0.05 without your thumb touching the stick, your controller suffers from stick drift.

Our gamepad tester utilizes the W3C standard HTML5 Gamepad API, natively supporting:

• Xbox Series X/S & Xbox One Controllers: Native XInput plug-and-play via USB or Bluetooth.
• PlayStation 5 DualSense & PS4 DualShock 4: Supported in Chrome, Edge, and Safari.
• Nintendo Switch Pro Controller: Supported over USB and Bluetooth.
• Generic USB Arcade Sticks & DirectInput Gamepads: Full standard button and axis mapping.

Browsers do not poll connected gamepads until the user physically presses a button on the controller (a security policy preventing device fingerprinting). To detect your controller: 1. Plug in or pair the controller. 2. Press the A/X button or move an analog stick while the page is active. 3. If still undetected, close Steam or background controller emulators that may be taking exclusive control.

An analog stick deadzone is the inner area around the stick center where small movements are ignored to prevent unwanted drift in gameplay. If your controller drifts slightly, you can increase the in-game inner deadzone threshold from 5% to 10%-12%. For physical hardware fixes, clean the potentiometer sensor wipers with electronic contact cleaner or replace worn modules with Hall-effect magnetic sticks.

Analog triggers (LT/RT or L2/R2) report variable pressure values from 0.00 (unpressed) to 1.00 (fully compressed). Our live diagnostic gauge displays real-time percentage progression as you squeeze the triggers, allowing you to check for dead zones, worn trigger pads, or broken internal trigger springs.

Yes! The modern Gamepad API includes GamepadHapticActuator support. On compatible controllers and Chromium browsers, you can click our Test Vibration / Dual Rumble button to trigger the left low-frequency heavy rumble motor and right high-frequency light rumble motor independently to test motor health.

Connect your controller to your computer via USB cable or Bluetooth. Open this page and press any button on the controller. The browser will detect it automatically and show a visual layout with real-time input feedback. No download or installation is needed.

This tool works with any controller that supports the Web Gamepad API. This includes Xbox Series X/S, Xbox One, PlayStation 5 DualSense, PlayStation 4 DualShock 4, Nintendo Switch Pro Controller, 8BitDo controllers, and most generic USB and Bluetooth gamepads. Both wired and wireless connections are supported.

Switch to the Stick drift mode using the tabs at the top of the tester. Set the controller down, start the 10-second measurement, and keep your hands off the sticks. The test rates drift severity from None (under 1%) to Severe (over 15%) and shows every recorded sample in a magnified view of the stick center.

First, try connecting via USB cable instead of Bluetooth — USB is more reliable for detection. Make sure you press a button after connecting (browsers require a button press for privacy reasons). Try Chrome or Edge, which have the best gamepad support. On macOS, you may need to grant browser input permissions in System Settings. If using Bluetooth, ensure the controller is paired in your system settings first.

Vibration testing works in Chrome and Edge on Windows, with partial support on macOS and Linux. Firefox and Safari do not support the Gamepad Vibration API. If vibration is not available, the tool will show a clear message. To test rumble, connect your controller in a supported browser and use the vibration test buttons.

Yes. If your phone or tablet supports USB OTG (On-The-Go), you can connect a controller via USB adapter. Bluetooth controllers can be paired directly through your device's Bluetooth settings. The gamepad tester works in mobile browsers that support the Gamepad API, including Chrome for Android.

Yes, this gamepad tester is completely free with no limitations. There is no download, registration, or account required. The tool runs entirely in your browser and all testing happens locally on your device.

Stick drift is when an analog stick registers movement without being touched. You might notice your character walking on its own or the camera slowly rotating in games. It's caused by wear on the potentiometer sensors inside the joystick mechanism. Most controllers develop some drift over time, especially with heavy use. Controllers with Hall Effect sensors are resistant to drift.

A dead zone is a small area around the center of an analog stick where movement is ignored by the game. It exists to prevent minor stick drift from causing unwanted input. Most games use a 5-15% dead zone by default. Competitive players often reduce it for faster response, but this requires a controller with very little or no drift.

Connect your DualSense or DualShock controller to your computer via USB or Bluetooth. Press any button and the tool will auto-detect it as a PlayStation controller, showing the correct button labels (Cross, Circle, Square, Triangle). All features including stick drift detection and trigger testing work the same way.

Connect your Xbox controller via USB cable, Xbox Wireless Adapter, or Bluetooth. Press any button to start. The tool recognizes Xbox controllers and displays the correct button labels (A, B, X, Y). Works with Xbox Series X/S, Xbox One, and Xbox 360 controllers.

To test keyboard keys online, navigate to our free Keyboard Tester and begin typing on your physical keyboard. Each key you press lights up in real time on the virtual layout diagram and turns green to indicate it has successfully actuated. The tool tracks key scan codes, event history, key down/up timing, and detects whether any keys fail to register or remain stuck in an active state.

N-Key Rollover (NKRO) means a keyboard can scan and register every single key pressed simultaneously, with no limit on count. Basic office keyboards usually feature 2-Key or 6-Key Rollover (6KRO), which causes ghosting — when pressing 3 or more keys together (like W+A+Shift+Space in games) causes additional keys to fail to register or trigger unintended keypresses. High-end mechanical keyboards use diodes on each switch to deliver True Full NKRO over USB.

Keyboard chattering (key bouncing) happens when a mechanical switch's metal leaf springs degrade, become dusty, or suffer micro-corrosion, causing a single keypress to register two or three times (e.g. typing 'tthhe'). Use our keyboard test to inspect rapid double activations. You can fix chattering by: 1. Cleaning the switch with isopropyl alcohol (99%) and compressed air, 2. Swapping the hot-swappable switch if your PCB supports it, or 3. Increasing key debounce time in firmware.

Yes. Our online keyboard tester captures standard W3C KeyboardEvent.code values, allowing full testing of Mac layouts (Command ⌘, Option ⌥, Control ⌃, Caps Lock, Fn), Windows layouts (Windows Key, Alt, Menu, NumPad), and ISO/ANSI enter key variations. For F1-F12 keys on laptops, make sure Fn lock is configured according to whether you want to test hardware media keys or function keys.

Keyboard latency is the time elapsed between physical switch actuation and the OS processing the input interrupt. Debounce algorithms wait between 2ms and 15ms to ensure the mechanical contact has stabilized. Modern Hall-effect magnetic switches (Rapid Trigger) eliminate debounce delay entirely, enabling ultra-fast reset times of under 0.1mm travel distance.

If a key on your keyboard is physically sticking or not popping back up: 1. Disconnect the keyboard from your computer. 2. Remove the keycap with a wire keycap puller. 3. Clean away any debris, crumbs, or hair using compressed air. 4. If a sticky drink was spilled, use a drop of 99% isopropyl alcohol around the switch stem while pressing it repeatedly. 5. Allow it to dry completely before reconnecting.

Open this page and start pressing keys. Each key you press lights up on the on-screen keyboard and turns green once it has registered, and the counter tells you how many keys are left. Pick your layout standard and keyboard size at the top so the board on screen matches the one in front of you. There is nothing to install and no account to create.

The key is not reaching your browser. Try it in another application to confirm, then check for debris under the keycap, a loose ribbon cable on a laptop, or a remapping tool that swallows the key. If the key works elsewhere but not here, it is probably reserved by the browser or the operating system — see the note under the keyboard.

Rollover is the number of keys your keyboard can report simultaneously. Hold down several keys at once and watch the rollover figure: cheap membrane keyboards stop at three to six keys, most gaming keyboards manage six over USB, and NKRO keyboards register everything you can hold down at the same time. It matters mainly in games, where several keys are held together.

Chatter is a single press that registers twice, caused by a worn or dirty switch. It shows up as doubled letters while typing. Just type normally on this page: any key that fires twice faster than 45 milliseconds is flagged in a warning right under the keyboard, together with how often it happened and how short the gap was. A key that appears here again and again is faulty; a single entry can also be a very fast double tap.

Almost certainly not. Wrong characters mean the layout your operating system uses does not match the printed legends — a US layout on an ISO keyboard, for example. The test proves this: the key lights up in the right position while the typing check shows a different character. Change the keyboard language in your system settings to fix it.

Those states come from the keyboard event itself, so they only appear after your first key press, and some browsers and operating systems refuse to report Num Lock or Scroll Lock at all. Caps Lock is reported almost everywhere.

Yes. A laptop keyboard is treated exactly like an external one. Choose the TKL, 75% or 65% size to match a compact laptop board, and click any key your model does not have to remove it from the counter. Keys that only exist behind an Fn combination usually cannot be tested because they never send a normal key event.

Yes, and it is worth doing. Pair the keyboard as usual and run the test. Dropped or repeated keys on a wireless board often point to a weak battery, interference on the 2.4 GHz band or a receiver plugged in too far away, and the press log makes those dropouts visible.

Web pages never see certain keys and combinations. Print Screen on Windows, the Fn key on most laptops, Alt+Tab, Cmd+Tab, Ctrl+W and the media keys are handled by the operating system or the browser before the page is reached. That is a security boundary, not a fault of your keyboard.

The code is the physical position of the key and never changes, which is why this test uses it. The key is the character that position produces with your current layout and modifiers. The keyCode is a legacy number kept for older software. Together they explain why the same physical key can type different characters.

Start with the simple things: unplug the keyboard, blow compressed air under the keycap, and clean around the switch with isopropyl alcohol. Reconnect it, or try another port or cable. If a key still chatters or stays dead on a mechanical keyboard, the switch itself is worn and needs replacing; on a membrane or laptop keyboard, the whole assembly is usually the only repair.

Yes to both. The test is free, requires no download and no account, and everything runs locally in your browser. Key presses and anything you type in the typing check stay on your device — they are never sent to a server.

To test mouse polling rate online, move your mouse continuously in quick, steady circles inside the Polling Rate testing zone on our Mouse Tester. The tool captures native browser pointermove hardware interrupts and calculates frequency in Hertz (Hz) and interval timing in milliseconds (ms). Standard office mice report at 125Hz (8ms), gaming mice at 1000Hz (1ms), and esports mice up to 4000Hz-8000Hz (0.25ms-0.125ms).

A mouse double click occurs when a mechanical micro-switch (such as Omron, Kailh, or Huano) suffers from contact leaf oxidization, spring fatigue, or electrical bounce (chatter). When pressed once, the switch vibrates and sends two rapid actuation signals below the debounce threshold. To diagnose it, use our Double Click Detection module. If chatter is detected, you can: 1. Clean the switch with compressed air or electrical contact cleaner, 2. Increase the debounce delay in your mouse driver software (e.g. 8ms-12ms), or 3. Replace the switch with optical switches that are immune to double-clicking.

For everyday desktop computer tasks, a normal clicking speed is between 5 and 7 CPS. For gaming, competitive players use specialized techniques:

• Regular Clicking: 6 - 8 CPS
• Jitter Clicking: 10 - 14 CPS (rapid arm muscle tremors)
• Butterfly Clicking: 15 - 25 CPS (alternating two fingers on one mouse button)
• Drag Clicking: 20 - 30+ CPS (dragging friction across matte surface)

Our online CPS test measures clicks within 5, 10, or 30-second windows with sub-millisecond precision.

To test mouse DPI (Dots Per Inch) accuracy, measure a physical distance on your mouse pad (such as 2 inches or 5 cm) using a physical ruler. Move your mouse exactly across that physical line while tracking the pixel displacement registered on screen. Dividing the horizontal pixels traveled by the inches moved gives your effective DPI. If the calculated DPI significantly differs from your mouse setting, check that Windows 'Enhance pointer precision' (pointer acceleration) is disabled.

If scrolling down causes your page to intermittently stutter or jump upwards, the mechanical rotary encoder inside your mouse wheel is contaminated with dust, lint, or dried grease. To test it, open our Scroll Glitch Detector and spin the wheel rapidly in one direction. Any reverse directional events will be highlighted in red. You can fix this by blowing compressed air directly into the wheel axle or replacing the 9mm/11mm wheel encoder.

Angle snapping (prediction) is an algorithm in some office mouse sensors that artificially straightens diagonal movements into straight horizontal or vertical lines. Sensor smoothing averages recent positional coordinates to reduce cursor jitter at very high DPI levels, but adds 1-4ms of input latency. For competitive gaming and precise digital art, both angle snapping and smoothing should be turned off in mouse software.

Open this page and use the mouse: click each button and turn the wheel. Every part lights up in the row above as soon as its signal arrives, so anything that stays grey is not reaching the browser. For the things you cannot see by looking — double clicks, polling rate, DPI, click speed, scrolling and sensor drift — pick the matching one of the six checks above. Nothing to install, no account.

The switch under the button has worn out and bounces, sending a second click on its own. It is the most common mouse fault there is, and on most mice the switch can be replaced. The double click test measures the gap between presses and flags anything faster than a finger can move, which is the evidence a warranty claim needs.

Not every browser reports them. Chrome and Edge do, and this page stops them from navigating away while you test. Firefox and Safari handle those buttons themselves and never pass them to the page, so a button that stays grey there may still be perfectly fine. If your mouse software has remapped one to a macro, the browser sees the macro instead.

The system has them swapped — usually the left-handed setting in the mouse control panel. A browser only ever sees a primary and a secondary button, so the physical left button reports here as the right one. Change it in your system settings and the labels will match your hand again.

It is how many times a second the mouse reports its position, measured in hertz. Move the mouse in continuous circles on the polling rate page and it fills in. Chrome and Edge hand over every raw sample, so the figure there is the real one; other browsers report movement once per frame and can only show a lower bound.

Yes. Mark a distance on your desk — ten centimetres is plenty — enter it on the DPI page, then move the mouse exactly that far in a straight line with the pointer locked. Where the browser allows it, the operating system's pointer acceleration is bypassed, so the figure is the sensor's own resolution rather than your cursor speed.

Usually not. Run the drift test: put the mouse down, start it and take your hand away. Drift almost always comes from dust on the sensor lens, a glossy or patterned desk, or a mouse pad worn through. Clean the lens with a dry cotton bud and try a plain mat before replacing anything.

Yes, and it is worth doing. Pair it as usual and run the checks. Dropped samples on the polling rate page and jumps in the drift test often point to a weak battery, a receiver plugged in too far away, or interference on the 2.4 GHz band.

Yes to both. It is free, needs no download and no account, and everything runs in your browser. Your clicks and movements stay on your device — they are never sent to a server.

To test multi-touch points online, open our Touchscreen Tester on your tablet, 2-in-1 laptop, or mobile phone. Place multiple fingers simultaneously on the canvas grid: each finger registers as an independent colored touch contact with coordinate tracking and contact radius, confirming whether your digitizer supports 2-point, 5-point, or 10-point multi-touch.

The touch sampling rate (measured in Hz) is how many times per second the screen digitizer scans for finger input. While display refresh rate (e.g. 60Hz or 120Hz) controls visual smoothness, touch sampling rate (often 120Hz, 240Hz, or 360Hz) determines how instantaneously the device responds to your touches, slashing input lag in games and drawing apps.

To detect dead spots, use our Touch Grid Fill mode. Drag your finger in continuous zigzag lines across every corner, edge, and center tile of the screen. If any blocks fail to change color as your finger passes over them, that section of the capacitive digitizer grid is damaged or unresponsive.

Ghost touches occur when the screen registers input without physical contact. Common causes include: 1. Low-quality or damaged third-party USB chargers introducing electromagnetic noise. 2. Cracked or lifting screen protectors trapping moisture or air pockets. 3. Oily residue or liquid on the glass. 4. Digitizer flex cable disconnection inside the device.

Yes! Our touchscreen test is built with standard W3C TouchEvents and PointerEvents APIs. It works seamlessly across Apple iPad (iPadOS), iPhone (iOS), Android smartphones and tablets, Windows touchscreen laptops (Microsoft Surface, Lenovo Yoga), and ChromeOS Chromebooks.

Power off your screen before cleaning. Wipe gently with a dry microfiber cloth; for stubborn smudges, dampen the cloth with distilled water or a 70% isopropyl alcohol screen cleaner (never spray liquid directly onto the glass). In Windows, open Control Panel > Tablet PC Settings > Calibrate to re-align touch crosshairs.

Open this page on the device you want to check, press "Start multi-touch test" and put several fingers on the screen — each one should get its own circle that follows it smoothly. Then switch to the dead zone grid and sweep the whole surface until every tile turns green. Tiles that stay dark are the parts of the screen that never answered.

A dead zone is an area where the digitizer — the touch-sensing layer above the display — no longer registers contact. The picture underneath is usually perfect, which is what makes it confusing: the screen looks fine, but one band or corner ignores every tap. It comes from a drop, a bend, water damage or a loose ribbon connector inside.

Touches you never made. The screen reports contacts on its own, so text types itself, apps open and menus flick past while nobody is holding the device. Leave the multi-touch test open without touching anything: if the ghost counter climbs on its own, the digitizer is faulty. A charger with poor grounding is the one common cause you can fix yourself — unplug it and try again.

No, and no other web page can either. The system converts trackpad gestures into ordinary mouse movement before the browser sees them, so there is no touch data left to measure. This test only works with a real touchscreen — a phone, a tablet, or a laptop or monitor whose glass you touch directly.

Most phones and tablets made in the last decade track five fingers, and many track ten; touchscreen laptops usually track ten. The start screen shows the limit your browser reports, and the multi-touch view shows how many contacts the screen really delivers at once. If a device that should handle ten stops at two or three, the digitizer is not healthy.

It means the browser found no touch-sensing hardware — normal on a desktop computer or a laptop without a touchscreen. Both tests still run with a mouse, which is useful for checking a drawing tablet or just for a look around. If the device does have a touchscreen and still reports zero, check that the touch driver is installed and enabled in the system settings.

Sometimes. Clean the glass, remove the screen protector and the case, restart the device, and install any pending system update — a surprising number of "dead" areas come back after that. A zone that survives all of it is physical damage to the digitizer or its connector, and the fix is a repair shop replacing the panel. Back the device up before handing it over.

Yes. Everything happens in your browser: nothing is uploaded, nothing is stored, and there is no app to install. The test runs the same on Android, iPhone, iPad, Windows and any touchscreen monitor with a browser.

To test stylus pressure sensitivity online, open our Stylus Tester and draw on the canvas using your digital pen. As you vary pressure from light touches to firm strokes, the tool measures real-time pressure values from 0.00 to 1.00 via the W3C Pointer Events API, dynamically altering stroke width and displaying live pressure percentages.

Yes. The test fully supports all major active stylus protocols:

• Apple Pencil (1st, 2nd Gen & Pro): Pressure, tilt shading, and double-tap barrel switch.
• Samsung S-Pen & Wacom EMR: 4,096 levels of battery-free electromagnetic resonance pressure.
• Microsoft Surface Pen & Slim Pen: Microsoft Pen Protocol (MPP 2.0) pressure, tilt, and eraser tip.
• USI (Universal Stylus Initiative): Supported on Chromebooks and USI tablets.

Active digitizers calculate the physical inclination of the pen relative to the screen glass surface. tiltX measures left/right tilt between -90° and +90°, while tiltY measures forward/backward tilt. Digital artists use tilt to shade wide areas naturally, replicating physical graphite pencils in Photoshop and Procreate.

If your pen draws but pressure stays locked at 0.50 (mouse fallback): 1. In Windows, ensure Windows Ink is enabled in your Wacom or tablet driver control panel. 2. In Chrome, check that Touch Events API is set to Automatic. 3. On iPad, ensure you are drawing with Apple Pencil tip rather than your finger.

A passive stylus (rubber tip) simply mimics a human finger's electrical capacitance and has no pressure sensitivity or palm rejection. An active stylus (Apple Pencil, S-Pen, Surface Pen) contains internal micro-controllers, communicates wirelessly with the digitizer, and transmits thousands of pressure gradations, tilt vectors, and button clicks.

Pressure levels indicate the digitizer sensor's resolution. 2,048 levels provide smooth basic line art. 4,096 levels are the mainstream standard for pro illustration. 8,192 and 16,384 levels offer hyper-fine micro-pressure responsiveness, allowing artists to draw the faintest hairline strokes without stepping artifacts.

Open this page on the device with the stylus, then draw one slow stroke on the drawing strip: feather-light at the start, as hard as you dare in the middle, lifting off at the end. The ink should swell and thin with your hand, the meter should sweep across, and the graph under the strip should show the shape of the stroke. A flat line means the pressure never reached the browser.

0.5 is the value the pointer specification tells a browser to report while a pressureless device is touching the surface. Getting nothing but 0.5 means no force reading is arriving at all: either the stylus has no pressure sensor, or its driver is handing the browser plain mouse input. On Windows, install the manufacturer's tablet driver and make sure Windows Ink is enabled; on a passive rubber-tipped stylus, there is nothing to enable — those have no sensor.

Check that it is paired and charged: on an iPad, Bluetooth settings should list it, and the tip should be screwed on tight. A loose or worn nib is the single most common cause of a Pencil that hovers but will not draw. If the page shows "Hover: detected" but never registers contact, replace the nib before suspecting anything else.

Applications reach the pen through different interfaces — Windows Ink, the older Wintab, or plain mouse input — and browsers only speak Windows Ink. An app set to Wintab can have perfect pressure while the browser gets none, and a browser can have pressure while an app configured for the wrong interface has none. Switch your app's tablet interface setting, and only then blame the pen.

A wobble on lines that should be straight. Drawn slowly at an angle, a cheap or failing digitizer produces a regular ripple, because it is interpolating your position between the sensor wires under the surface. The jitter ruler here traces a slow diagonal on purpose: horizontals and verticals follow the sensor grid and look clean even on a bad tablet, and fast strokes get smoothed by the driver.

Yes, and no touchscreen is needed. The tablet driver presents the pen to the system and the browser receives ordinary pen events, pressure and tilt included. If the page keeps waiting for input while the cursor moves, the tablet is being delivered as a mouse: install the manufacturer's driver instead of the generic one, and on Windows enable Windows Ink for it.

Either it has no tilt sensor — most budget styluses and the first Apple Pencil-style pens for entry-level tablets do not — or you have not leaned it far enough. Browsers report a perfectly upright pen as zero rather than as missing, so a run of zeros looks the same either way. Hold the pen at roughly 45 degrees and watch the dial; if it stays dead centre, the sensor is not there.

To test screen sharing with audio, open our Screen Share Test Online and click Start Screen Share. When the browser permission dialog appears, choose either Chrome Tab or Entire Screen, and ensure the Share system audio / Share tab audio checkbox is enabled at the bottom left of the modal. The test canvas will verify whether audio tracks are actively broadcasting alongside video.

Blurry screen sharing usually stems from three causes:

1. Dynamic Bitrate Downscaling: Video conference apps downgrade resolution from 1080p to 720p or 360p when internet bandwidth or packet loss occurs.
2. Chroma Subsampling (4:2:0): Text on dark IDE backgrounds compresses poorly under aggressive video codecs.
3. Display Scaling: High-DPI screens (e.g. 4K at 150% scaling) can introduce resampling softness when shared.

Use our fine-text sharpness test grid to verify your presentation readability before meetings.

Most meeting software defaults screen sharing to 5 to 15 FPS to conserve bandwidth for static documents. To share at 60 FPS (for video playback, game demos, or smooth animations): 1. In Zoom, go to Settings > Share Screen > Advanced and check Optimize for video clip. 2. Enable browser hardware acceleration in Chrome or Edge settings so GPU video encoders (NVENC/QuickSync) can handle 60 FPS encoding smoothly.

Yes. Online exam proctoring systems (Respondus LockDown Browser, Proctorio, Honorlock, Examity) detect screen sharing via operating system process scanners, display count APIs, and WebRTC getDisplayMedia hooks. They flag active secondary monitors, virtual displays, HDMI splitters, and background streaming tools such as Discord, Zoom, or OBS Studio.

A black screen during screen sharing typically occurs due to: 1. Hardware Acceleration conflict: Try toggling Hardware Acceleration in browser settings. 2. DRM Protected Content: Streaming apps (Netflix, Disney+) intentionally black out screens to prevent recording. 3. OS Permissions: On macOS, grant permissions in System Settings > Privacy & Security > Screen Recording.

Screen sharing captures 30 to 60 full-resolution frames per second and encodes them using H.264, VP9, or AV1 codecs. If Hardware Acceleration is active, your GPU's dedicated video encoder processes this with less than 5% CPU impact. If disabled, CPU software encoding can cause fan noise and performance drops.

Because your operating system runs display scaling. At 200% scaling, Windows and macOS tell apps the screen is 1920 × 1080 so that text stays a comfortable size, while the panel still lights up its full 3840 × 2160. This page multiplies the reported size by your pixel density to recover the real number, so the headline figure should match the panel. If it does not, check for browser zoom — it changes the numbers too.

Compare the headline figure with the common standards: 1280 × 720 is HD, 1920 × 1080 Full HD, 2560 × 1440 QHD, 3840 × 2160 4K UHD and 7680 × 4320 8K. Ultrawide monitors use their own set, such as 2560 × 1080 and 3440 × 1440. The aspect ratio shown under the headline tells you whether the panel is a regular 16:9, a productivity 16:10 or an ultrawide 21:9.

Usually because something is deliberately holding it down. Phones drop to 60 Hz to save battery, laptops do the same on power-saver profiles, and on desktops the display settings may still be set to 60 Hz even though the panel can do more. The cable can also be the cap — older HDMI versions cannot carry 4K above 60 Hz. Set the rate explicitly in your display settings, then verify with the refresh rate test.

No. For privacy reasons the browser only exposes numbers — size, density, color capabilities and refresh timing. It cannot read the monitor's model name, serial number or any other identifying details, and neither can this page. Anything that claims to name your exact monitor from inside a web page is guessing from those same numbers.

Pixel density is how many real pixels the screen uses for each dot of the picture. Whole numbers like 2× come from HiDPI and Retina displays. In-between values almost always mean Windows display scaling: 125% shows up as 1.25×, 150% as 1.5×. Browser zoom changes the value too, which is why it moves when you press Ctrl and + or −.

Browser zoom makes every dot of the page bigger or smaller, and the measurements on this page scale along with it. Zooming in makes the reported resolution drop and the pixel density rise, while the physical panel obviously never changes. For accurate readings reset zoom to 100% — Ctrl+0 on Windows and Linux, Cmd+0 on a Mac.

Use the dead pixel check linked above. It fills the screen with solid red, green, blue, white and black, one after another, so a pixel that is stuck on one color or permanently dark stands out immediately. Clean the screen first — a speck of dust is the most common false alarm — and give each color a few seconds of close attention.

Yes to both. Every value on this page is read locally by your browser and never sent to a server — there is nothing to install, no account, and no way for anyone to see your results. The page simply shows you what your own browser already knows about the display it is running on.

For smooth video conferencing on Zoom, Google Meet, and Microsoft Teams:

• Excellent: Under 30 ms (instant conversation rhythm, zero voice overlap).
• Good: 30 ms - 70 ms (imperceptible delay, great for calls).
• Fair: 70 ms - 150 ms (minor pauses when two people speak simultaneously).
• Poor: Above 150 ms (noticeable conversation lag and voice collisions).

Our online internet speed tool tests real-world HTTP round-trip ping directly from your browser.

Jitter is the variance in packet arrival latency over time. For example, if one audio packet takes 20ms and the next takes 120ms, jitter is 100ms. High jitter leads to robotic voices and frozen video frames. To fix jitter: 1. Switch from Wi-Fi to a direct wired Ethernet cable. 2. Move closer to your Wi-Fi 6 router or switch from 2.4GHz to 5GHz/6GHz. 3. Pause background downloads and torrent clients.

For group video meetings: 1. 720p HD Video: 1.5 Mbps download and 1.5 Mbps upload. 2. 1080p Full HD Video: 3.8 Mbps download and 3.0 Mbps upload. 3. 4K Ultra HD Screen Share: 15+ Mbps download and 10+ Mbps upload. Symmetrical upload speed is especially vital for clear screen sharing and smooth outgoing camera feeds.

Latency is the total time it takes for data to travel from your computer to a destination server. Ping is the measurement tool and metric representing round-trip latency in milliseconds. Jitter is the statistical fluctuation or instability of that ping time over consecutive packets.

Wi-Fi signals travel through air and are prone to wall absorption, physical obstruction, and radio interference from neighboring networks, Bluetooth devices, and microwave ovens. A Cat6 Ethernet cable provides a dedicated, full-duplex shielded copper connection immune to external radio interference, delivering lower ping and zero packet loss.

Video conference platforms use UDP for real-time streaming, which drops lost packets rather than waiting for retransmission. Packet loss as low as 2% to 5% causes stuttered speech, pixelated video blocks, and desynchronized lip-sync during video meetings.

A good internet speed depends on what you do online. For general browsing and email, 5–10 Mbps is sufficient. HD video streaming needs at least 5 Mbps, while 4K streaming requires 25 Mbps or more. Households with multiple users or devices should aim for 50–100 Mbps or higher.

For most people, 25 Mbps or higher is a good download speed. This comfortably supports HD streaming, video calls, and web browsing. If you stream 4K content, download large files, or have multiple people using the connection at the same time, look for 100 Mbps or more.

An upload speed of 5 Mbps is enough for standard video calls and sending files. For HD video calls, live streaming, or uploading large files regularly, 10 Mbps or higher is recommended. Content creators and remote workers who do screen sharing or cloud backup should aim for 25 Mbps or more.

Ping (also called latency) measures the time it takes for data to travel from your device to a server and back, in milliseconds. Low ping means a more responsive connection. Under 20 ms is excellent, 20–50 ms is good for most activities, 50–100 ms is acceptable for browsing but may affect gaming, and over 100 ms can cause noticeable lag in video calls and online games. Run the dedicated ping test to also see jitter and packet loss.

Common causes include network congestion during peak hours, Wi-Fi interference or being too far from your router, outdated router hardware or firmware, too many devices sharing the same connection, background downloads or updates, and ISP throttling. Try restarting your router, moving closer to it, or connecting via Ethernet cable.

This test measures your connection in three steps. First, it sends small packets to multiple server regions and picks the one with the lowest latency. Then it downloads data from that server to measure download speed, and uploads data to measure upload speed. All testing happens in your browser — no app or plugin is needed.

This test gives a reliable snapshot of your current connection speed. Results may vary between tests due to network congestion, server load, Wi-Fi conditions, and other devices using your network. For the most accurate results, test over a wired Ethernet connection, close other tabs and applications, and run the test a few times.

Mbps (megabits per second) measures internet speed. MBps (megabytes per second) measures file transfer size. Since 1 byte equals 8 bits, divide Mbps by 8 to get MBps. For example, a 100 Mbps connection can download about 12.5 MBps, meaning a 100 MB file takes roughly 8 seconds.

Click Start above to run a full speed test. The test sends data to a server and measures how fast your connection can transmit it. Your upload speed is displayed in Mbps alongside download speed and ping.

Under 20 ms is excellent for competitive gaming. 20–50 ms is good for most online games. 50–100 ms is playable but you may notice occasional lag. Over 100 ms makes fast-paced games like first-person shooters and fighting games difficult.

Yes. This test measures whatever connection your device is using — WiFi or Ethernet. To test WiFi specifically, run the test while on WiFi, then compare with a wired connection. The difference shows how much speed your wireless setup loses.

Most internet plans are asymmetric, meaning download speed is much faster than upload. This is normal for cable and DSL connections. Other causes include network congestion, WiFi interference, background cloud syncing, or ISP throttling. If your upload is much slower than advertised, try restarting your router or testing on a wired connection.

Our in-browser CPU benchmark executes computationally intensive mathematical loops — including large prime number sieves, floating-point trigonometry, and cryptographic hashing — directly in JavaScript and WebAssembly. It clocks execution times to calculate millions of operations per second (MOps/s) across single-core and multi-threaded worker configurations.

MOps/s stands for Million Operations Per Second. It measures how many millions of integer and floating-point math instructions your processor can execute every second. Higher MOps/s scores indicate faster compilation times, snappier video rendering, and quicker web application response times.

Thermal throttling occurs when a CPU exceeds safe temperature thresholds (typically 90°C - 100°C) and automatically reduces its clock speed to prevent hardware damage. To detect it: run our CPU benchmark three consecutive times. If your score drops by 15% to 30% between the first and third run, your laptop cooling fan or thermal paste requires attention.

Yes. The benchmark inspects navigator.hardwareConcurrency to identify your CPU's available logical processor threads (e.g. 8 cores, 16 threads). In multi-core test mode, it spawns parallel Web Workers across every hardware thread to measure maximum multi-core processing throughput.

To optimize CPU responsiveness: 1. Clean out laptop cooling vents and heatsinks. 2. In Windows Power Options, select 'High Performance' or 'Ultimate Performance' plan. 3. Disable resource-heavy startup applications in Task Manager. 4. Close idle browser tabs and background applications before video calls.

No. Modern CPUs possess built-in firmware hardware protections (TJMax) that prevent damage. Furthermore, web browsers run inside sandboxed operating system processes with safety throttles, making online benchmarking 100% safe.

Choose how long the run should last, how many threads to load and at what intensity, then press start. The page opens one worker per thread, each running a tight arithmetic loop, and shows you what they get through. Keep the tab in front for the whole run — the browser throttles background tabs, and the readings stop meaning anything.

No, and no. The figure on screen is passes of one particular loop per second, produced by your browser's JavaScript engine. Another browser on the same machine gives a different number; the same browser after an update does too. Read the line against itself over the run, never against another machine.

No. Thermal and power protection sits in the hardware, far below the browser: a chip that gets too hot clocks itself down, and if that is not enough the machine switches off. Neither is damage. Expect heat, fan noise and, on a laptop, fast battery drain — and stop the run if you would rather not have those.

No. Web pages have no access to temperatures, clock speeds, fan speeds or the processor model on any platform. Run a local monitor beside this page: HWiNFO or Core Temp on Windows, Stats or iStat Menus on macOS, lm-sensors on Linux. This page gives you the load; the monitor gives you the numbers it cannot see.

Because the browser reports logical threads, not physical cores, and it is not always honest about those either. Safari clamps the figure, private and anti-fingerprinting modes clamp it further, and a hybrid chip counts its performance and efficiency cores in the same total. It is good enough to size the worker pool, and not good enough to quote as your core count.

The machine started at one pace and could not keep it. Heat is the usual reason, and on a laptop it points at dust in the fans, dried-out thermal paste, or a vent pressed into a soft surface. A power limit, a battery-saver profile, or another program taking cores look identical from inside a browser, so confirm with a temperature monitor before opening the case.

All threads to test cooling — that is what heats the whole package and makes the fans work. One thread to see the highest single-core boost. Which core the work lands on is up to the system, though — a web page cannot pin a worker to a particular core — so read a single-thread run as a statement about the chip, not about one core. The run panel shows every thread separately.

One minute is enough to hear the fans and confirm the load takes hold. Five minutes is the useful minimum for heat: most laptops throttle in the third or fourth minute, not the first. For a fault that only appears once the machine has been hot for a while, use the endurance preset and leave it running with the tab in front.

It should not. Every arithmetic loop runs in a Web Worker on its own thread, and the page itself only draws numbers. With every thread loaded the interface may feel slightly less crisp — everything is competing for the same cores — but scrolling, the controls and the stop button keep working. Stopping terminates the workers outright, so the load ends the moment you press it.

The GPU benchmark initializes an HTML5 WebGL2RenderingContext on an off-screen canvas and renders textured 3D geometric meshes with custom vertex and fragment shaders. It measures frame render delta times, vertex throughput, and shader shading capability to rate graphics acceleration performance.

Browsers synchronize their requestAnimationFrame loop with your monitor's physical refresh rate via Vertical Synchronization (V-Sync) to prevent visual screen tearing. If you are using a 60 Hz monitor, the benchmark will cap at 60 FPS. On 120 Hz, 144 Hz, or 240 Hz gaming monitors, it will scale to match the higher refresh rate.

To enable GPU hardware acceleration: 1. In Google Chrome or Microsoft Edge, go to Settings > System. 2. Toggle Use graphics acceleration when available to On. 3. Relaunch the browser. You can type chrome://gpu in your URL bar to verify that WebGL and Canvas are hardware accelerated.

Laptops with dual GPUs (Intel/AMD integrated graphics + NVIDIA RTX dedicated GPU) default web browsers to the power-saving integrated GPU. Our tester queries WEBGL_debug_renderer_info to reveal the active GPU. In Windows Settings > System > Display > Graphics, you can assign your browser to 'High Performance' to force dedicated GPU usage.

WebGL 1.0 is based on OpenGL ES 2.0, whereas WebGL 2.0 brings full OpenGL ES 3.0 feature parity to the browser. WebGL 2.0 adds 3D textures, uniform buffer objects, transform feedback, and multi-render targets, enabling console-grade 3D graphics inside modern web pages.

If WebGL fails to initialize: 1. Update your graphics drivers from NVIDIA, AMD, or Intel. 2. In Chrome, navigate to chrome://flags, search for Override software rendering list, and set it to Enabled. 3. Ensure your browser is updated to the latest version.

Pick a mode, press start and watch. Ramp up steps the load higher every few seconds until the frame rate can no longer keep up with your screen; artifact watch holds a steady load and shows high-contrast patterns for you to inspect. Nothing is installed and nothing leaves your device.

Because your screen only shows 60 pictures a second and your graphics card is waiting for it. That is a healthy result, not a limit of the card. What matters is the complexity level at which it finally drops below 60 — or below 144, or whatever your screen runs at.

No, and neither can any other web page. Browsers deliberately give no access to sensors, clock speeds, fan speeds or power draw, because that would identify your machine far too precisely. For temperatures you need a desktop tool such as your card vendor's own software, HWiNFO or GPU-Z.

Colored snow or speckles, checkerboard blocks, textures that smear or repeat wrongly, flashing and black frames, and geometry stretching off into nothing. On a good GPU the scene stays clean at every level. Anything that appears only under load and goes away when the test stops is worth taking seriously.

A lost graphics context under load is a genuine failure signal. Update your graphics drivers, remove any overclock or undervolt, make sure fans and vents are clean, and check that the power supply is up to the card. If it happens again quickly at low levels, the card itself may be failing.

No. The levels are settings of this one scene, and your result depends on your screen's refresh rate, the size of the window, your browser and your operating system's power settings. It answers “is my GPU behaving?”, not “is it faster than yours?”

A healthy, adequately cooled GPU is built to run at full load and will slow itself down long before it comes to harm. It will get hot and the fans will get loud. Stop the run if the device is uncomfortably hot or its vents are blocked, and do not run long tests on a laptop sitting on a duvet.

The browser asks for the high-performance GPU, but the operating system decides. On battery, or under a power-saving profile, it usually hands over the integrated chip instead. Look at the renderer name at the top of this page to see which one answered, then plug in or point the browser at the high-performance GPU in your system settings.

Yes, though phones throttle quickly and deliberately — a frame rate sliding after a minute is normal behavior on a phone, not a fault. Artifact watch is the more useful mode on mobile: keep the run short and stop it if the phone gets hot.

To check battery health online, open our Battery Test Online page on a supported browser (Chrome, Edge, Opera, Samsung Internet). The tool interfaces with the W3C Battery Status API to display current battery percentage, AC adapter charging status, charging time to 100%, and remaining discharge time.

Mozilla Firefox and Apple Safari disabled the Battery Status API due to privacy concerns regarding potential device fingerprinting across websites. Chromium-based browsers (Chrome, Edge, Brave, Opera) support the API with privacy safeguards. On macOS and iOS, you can also view battery health under System Settings > Battery > Battery Health.

Lithium-ion batteries experience the greatest chemical stress when fully discharged to 0% or kept at 100% full charge under high temperatures. The 80/20 rule recommends keeping your charge level between 20% and 80% during daily use. Enabling 'Battery Protection' or 'Optimized Battery Charging' can nearly double the cycle lifespan of your battery across 3 to 5 years.

The operating system battery management system (BMS) continuously monitors the milliampere (mA) current draw. It divides the remaining milliamp-hour (mAh) capacity by current power consumption to compute dischargingTime in seconds, which our tool formats into clear hours and minutes.

Video calls are exceptionally power-hungry because they activate the webcam sensor, keep the microphone powered, decode incoming 1080p video streams, encode your video via GPU/CPU, and power the display backlight simultaneously. Lowering screen brightness to 60% and enabling Hardware Acceleration significantly reduces battery drain.

Most modern laptop batteries are rated for 300 to 500 complete discharge cycles (roughly 2 to 3 years of daily use) before capacity drops below 80% of original design capacity. Premium laptops (such as Apple MacBooks) are engineered for up to 1,000 charge cycles.

Pick the load and start the run. Chrome and Edge read the percentage themselves; other browsers ask you to enter it. Keep the tab in front with the screen on — everything is saved as it goes.

No, and neither can any other web page: health, capacity, cycle count and voltage are not exposed to a browser on any platform. What this page measures is elapsed time against charge level, which is what actually compares two devices.

Safari and Firefox removed the Battery Status API over fingerprinting. The page switches to timing the run while you enter readings by hand; the chart, the projection and the exports are unchanged.

That is the case this page is built for. Every reading is saved as it arrives, so the run is offered back when the device returns, ending at the last reading before it died.

Yes, and in front. Background tabs are throttled and a locked phone freezes the page, which stops the load as well as the recording. The page keeps the screen awake while a run is going.

It is whatever the operating system reports, in whole percentage points, and that is itself an estimate — a poor one on a new battery. The timing is exact either way, which is why running to shutdown is the reliable method.

Heavy for runtime under stress, idle to catch a device that leaks charge doing nothing, light for something in between. What matters most is using the same one every time.

Yes, on a page of its own — one tab across. The same starting level with the same charger and cable is the only way to compare two devices.

In this browser, on this device, and nowhere else. Runs live in the browser's own storage so they survive a shutdown; nothing is uploaded.