Screen Flicker Test

Introduction

The DeviceHub Screen Flicker Test provides controllable flash patterns so users who intentionally study flicker, such as comparing whether a brightness level feels PWM-like, can do so in a browser tab. This page leads with a strong photosensitivity / epilepsy caution: flashing content can trigger seizures or severe discomfort in susceptible people. If you have photosensitive epilepsy, a history of seizure risk from flashes, or feel unsure, do not run this test. Move away if patterns begin unexpectedly. Parents should not let children play with flash controls. For everyone else who still chooses to proceed, start at the mildest settings, keep sessions short, and stop at the first hint of headache, eye pain, nausea, or aura. DeviceHub patterns are software flashes subject to display refresh and rAF scheduling, they are not a laboratory photodiode PWM duty-cycle analyzer. Prefer Refresh Rate, Frame Skip, and Motion Blur Tests when your question is smoothness or clarity without intentional flashing. Intentional flashing is a narrow diagnostic niche, and a serious safety topic, so DeviceHub leads Screen Flicker Test with a strong photosensitivity / epilepsy caution rather than burying warnings under marketing. Flashing content can trigger seizures or severe discomfort in susceptible people; if you have photosensitive epilepsy, a history of seizure risk from flashes, or feel unsure, do not run this test, and move away if patterns begin unexpectedly. Parents must not let children play with flash controls, and nobody should run patterns on shared public displays or screen-share them without explicit consent from every viewer, including remote call participants. Users who still knowingly proceed, for example to compare whether a brightness level feels PWM-like, should start at the mildest settings, keep sessions short, and stop at the first hint of headache, eye pain, nausea, or aura. Software flashes are subject to display refresh and rAF scheduling; they are not a laboratory photodiode PWM duty-cycle analyzer, and DeviceHub will not pretend otherwise. Prefer Refresh Rate, Frame Skip, and Motion Blur Tests when your question is smoothness or clarity without intentional flashing, those remain rAF-influenced visual/timing aids, not hardware analyzers, but they avoid deliberate strobing. Permissions stay none; leaving the page is enough to stop patterns. Esports venues and classrooms should treat this URL as restricted content: post the photosensitivity warning at the door mentally before anyone fullscreen-strobes a wall display. If your actual question is whether Hz stuck or frames hitch, leave this page and use Refresh Rate or Frame Skip instead, those avoid intentional flashing while still disclosing rAF and compositor limits.

What this tool does

Controls may adjust frequency, duty, or color of flashes after warnings and confirmations. Persistent banners remind users of medical risk. The tool does not diagnose PWM hardware, prescribe filters, or claim to cure flicker headaches. It does not upload recordings of your session. If your goal is dead pixels or color, use those safer static tools instead. Controls may adjust frequency, duty, or color of flashes only after warnings and conscious opt-in affordances. Persistent banners remind users of medical risk throughout. The tool does not diagnose hardware PWM, prescribe medical filters, or claim to cure flicker headaches. It does not upload session recordings. If your goal is dead pixels, color, or uniformity, use those safer static tools instead of inventing a reason to flash. Fullscreen increases risk because flashes fill more of the visual field, another reason mild starts and quick exits matter.

When to use it

Only when you knowingly need to observe software flicker behavior and you have considered photosensitivity risks for yourself and anyone who can see the screen. Do not use this as entertainment. Do not run it on shared public displays. Prefer non-flashing display tools for routine monitor inspection. Prefer Refresh Rate Test for Hz estimates (rAF-based, not a hardware analyzer). Only when you knowingly need to observe software flicker behavior and you have considered photosensitivity risks for yourself and anyone who can see the screen. Do not use this as entertainment, as a party trick, or as a stress toy. Prefer non-flashing display tools for routine monitor inspection. Prefer Refresh Rate Test for Hz estimates (rAF-based, not a hardware analyzer) and Frame Skip for hitching without strobe patterns. Workplace wellness policies may forbid flashing content on open floors, follow them.

How it works

The browser toggles colors or opacity on a timer or rAF tick to create flashes. The panel’s own backlight PWM may interact with perceived flicker, but DeviceHub cannot meter that with a diode. OS compositor and vsync affect regularity of software flashes. No camera permission is required. Fullscreen increases risk exposure because the flash fills vision, another reason warnings matter. Remote viewers on a call could also be affected, do not share flashing screens without consent. The browser toggles colors or opacity on a timer or rAF tick to create flashes; the panel’s own backlight PWM may interact with perception, but DeviceHub cannot meter that with a diode. OS compositor and vsync affect regularity of software flashes, another honesty limit beside the medical caution. No camera permission is required. Remote viewers on a call can be affected; never share flashing screens without warning and consent. Increasing intensity to “force” a measurement when you cannot see flicker is explicitly unsafe and discouraged. Phone rolling-shutter bands are not a substitute for careful human stopping rules.

Step-by-step instructions

1. Read every photosensitivity and epilepsy warning on the page; if you or nearby viewers are at risk, leave without starting patterns.
2. Ensure bystanders consent or cannot see the display, then opt in only if appropriate.
3. Begin with the mildest flicker settings for a brief moment; stop immediately if you feel any adverse symptoms.
4. If you continue, change one control at a time briefly, never maximize intensity “for fun.”
5. When finished, or at any discomfort, exit fullscreen and navigate away so flashing stops.
6. No special permission revoke is required; leaving the page is enough.

Common problems

Ignoring warnings because “I usually tolerate games” is unsafe, pattern frequency matters. Phone cameras rolling-shutter can show flicker bands that eyes barely notice, or miss PWM entirely. Increasing flash rate beyond comfort to chase a measurement is explicitly discouraged. Confusing Frame Skip stutter with PWM flicker leads people here unnecessarily; try non-flash tools first. Ignoring warnings because games usually feel fine is unsafe, pattern frequency and duty cycle matter. Confusing Frame Skip stutter with PWM flicker leads people here unnecessarily; try non-flash tools first. Chasing a photodiode-style reading with brighter software flashes is a misuse of the page. Bystanders behind you can still be affected by a fullscreen strobe, check your surroundings. Children mimicking creators online may not read disclaimers; adults must supervise or block access.

Privacy explanation

Flash patterns run locally. DeviceHub does not record medical reactions or upload flicker sessions. No camera permission is requested. Leaving the page stops patterns. Do not screen-share flicker tests without warning participants, photosensitivity risk extends to remote viewers. Flash patterns run locally; DeviceHub does not record medical reactions or upload flicker sessions as health data. No camera permission is requested. Leaving the page stops patterns immediately. Do not screen-share without warning participants, photosensitivity risk extends to remote viewers and is part of the privacy/safety story, not a footnote. Facilitators running demos for hardware PWM education must obtain consent from everyone in the sightline, including people entering mid-session. Facilitators must brief every person in the sightline before any flash begins, including colleagues who walk in mid-session. If your actual question is smoothness or clarity, prefer Refresh Rate, Frame Skip, and Motion Blur Tests so you avoid intentional flashing entirely. Software flicker here cannot certify a panel’s backlight PWM duty cycle; photodiode meters and manufacturer specs remain the hardware path for that claim.