Mind Forge All tools
Visual attention

Flicker Change-Blindness Test

Two scenes alternate with a gray blank between them. Spot the change. It's harder than it sounds — without a continuous visual reference, your brain may literally not notice that an object moved, changed color, or disappeared.

What makes this one different

We include a "scene degradation" mode where parts of the scene are obscured with noise during each blank, making the change harder to spot. That exposes how much of your change-detection is actually attention versus peripheral vision.

Trial 0 / 10
Mean RT —
Miss rate —
Press Space as soon as you spot a change.
Ad slot.

Results

Found
—
Missed
—
Mean RT
—

History

No sessions yet.

What problem does it solve?

Change blindness is one of the most counterintuitive findings in cognitive psychology. Despite the rich visual detail around us, our visual system encodes surprisingly little of it. When a continuous reference is removed (a blink, a saccade, a flicker), large changes can go entirely unnoticed.

The phenomenon has practical implications: distracted driving, witness reliability, even UI design. Training attention is one way to reduce change blindness — and this task simulates the experience directly.

Who is this for

How to interpret your results

Miss rate of 30–50% on clean mode is normal — change blindness is real. Below 20% means you're unusually attentive or using a strategy (e.g., fixating on the change region).

Mean RT under 2 seconds is fast. Over 4 seconds is slow.

Limitations

  • The classic Rensink & O'Regan demonstrations used real photographs; we use abstract colored grids. The principle is the same but the absolute difficulty differs.
  • Display refresh rate affects flicker timing. Most users will see 60 Hz; high-refresh monitors may make it slightly easier.
  • Your eyes naturally make saccades every ~250 ms. The flicker simulates what happens at each saccade boundary.

FAQ

What does the noise mode do?

During each gray blank, random noise covers parts of the scene. This adds a "where was that?" cost — you have to remember the layout from before the noise. Most people miss more changes in noise mode.

Should I stare at the center?

Yes. Peripheral attention is what change blindness mostly defeats. Looking at the change region "cheats" the task — try to detect changes without moving your eyes.

How do I use Flicker Change-Blindness Test step by step without mistakes?Follow the order given in the usage section: Two nearly-identical scenes alternate. A blank flash separates them. Find the change before attention drifts. The step-by-step part matters less than the unit check that sits inside it. Confirm every unit matches the thing you are actually trying to measure before you press calculate - that single check catches more wrong answers than any other habit, and it costs about ten seconds.
What are the common mistakes when using Flicker Change-Blindness Test?Most common mistakes come down to four habits: entering 20 when the field expects 0.2 because the field is a percentage; leaving a field blank and accepting the default without checking what it stands for; changing one input and reading a result that was calculated before the change; and quoting the output as an exact figure when the page describes it as a reference estimate. Press calculate again after any edit, and treat the number as a reference point rather than a final answer.
How do I read the result from Flicker Change-Blindness Test?Read the final figure first, then come back to this section for the conditions behind it: Miss rate of 30–50% on clean mode is normal — change blindness is real. Below 20% means you're unusually attentive or using a strategy (e.g., fixating on the change region). Mean RT under 2 seconds is fast. Over 4 seconds is slow. Keep two things apart: the number itself, which comes from the values you typed, and the assumptions it depends on, which decide whether that number is meaningful. The page sets out what a higher or lower result means for your case, so check that direction as well as the magnitude.
Can I act on the Flicker Change-Blindness Test result directly?Treat it as one reference sheet before you decide, rather than as the answer itself: The classic Rensink & O'Regan demonstrations used real photographs; we use abstract colored grids. The principle is the same but the absolute difficulty differs. Display refresh rate affects flicker timing. Most users will see 60 Hz; The output describes a magnitude under the conditions you entered. It does not include what it actually costs to act, what might change while you act, or how the other side behaves. Before you commit, compare the result against reality and note which assumptions do not hold where you are.