top of page

The Truth About LED Flicker: Why Phone Cameras Mislead You (and What Actually Matters)

  • Writer: Unwired Connect
    Unwired Connect
  • Feb 16
  • 4 min read
The Truth About LED Flicker: Why Phone Cameras Mislead You (and What Actually Matters)

Understanding Real vs. Camera-Induced Flicker — A Technical Guide from a Manufacturer’s Perspective


If you’ve ever filmed a spinning car wheel and watched it appear to move backwards, you’ve experienced how cameras can distort reality. A similar illusion happens when you point your phone camera at an LED light and see dark bands or “flicker.”

Most people assume:


“If my phone shows flicker, the LED driver is faulty.”


But this is a misconception — one that causes unnecessary panic, incorrect product conclusions, and bad purchasing decisions.


In this blog, we’ll break down the difference between actual human-visible flicker and camera-induced artifacts, explain why phone cameras are completely unreliable for evaluating driver quality, and clarify when “camera-friendly” drivers do — and do NOT — matter.


This article is written from the lens of deep hardware experience at Unwired Connect, where we design and manufacture LED drivers, firmware, and wireless controls in-house.


1. Why LED Lights Flicker on Phone Cameras (But Not to Your Eyes)


Why LED Lights Flicker on Phone Cameras (But Not to Your Eyes)

LEDs do not glow continuously. They turn ON and OFF rapidly — far faster than human eyes can perceive — using PWM (pulse-width modulation) or current modulation.

To your brain, this looks like steady light.

But a phone camera works differently:

  • It uses a rolling shutter

  • It scans the image line by line

  • It samples light asynchronously

    (not in sync with the LED’s PWM frequency)

So when the LED driver pulses light, the camera slices that pulse into visible stripes.


The result?


Flicker that isn’t actually there — exactly like the car wheel illusion.

This is why:

Phone-camera flicker ≠ , human-visible flicker, phone-camera flicker, ≠ low driver quality


2. The Flicker That Actually Matters (and How It Is Properly Measured)


There is a type of flicker that affects humans — but it has nothing to do with what your phone sees.

Real physiological flicker comes from:

  • Low-frequency modulation (below ~100 Hz)

  • Deep ripple in the LED current

  • Poor power factor correction

  • Low-quality driver design

It can lead to:

  • Headaches

  • Eye strain

  • Fatigue

  • Stroboscopic effects

This flicker is measured using:

  • A photodiode + oscilloscope

  • IEC metrics such as:

    • Flicker Percentage

    • Flicker Index

    • Pst LM (IEC TR 61547-1)

NOT a phone camera.Never a phone camera.


oscilloscope test

3. Why High Power-Factor Drivers Look “Worse” on Camera


This surprises many engineers:

A high-PF, high-quality LED driver will often look more flickery on a phone camera.

Why?

Because high PF (Power Factor) designs intentionally allow controlled power-line ripple — by design — to achieve efficiency and lower harmonics.

Phone cameras capture this ripple as banding.

Meanwhile:

Cheap, low-PF, capacitor-heavy drivers look perfect on camera(because giant capacitors smooth out visible ripple)

But those same drivers suffer from:

  • Shorter lifespan

  • Higher thermal stress

  • Poor PF

  • High inrush current

  • Increased risk of field failure

So “camera-perfect” lighting often indicates worse engineering, not better.


4. PWM Is NOT the Same as Flicker


Another myth:

“If a driver uses PWM, it flickers.”

Not true.

PWM above ~5 kHz is fully invisible to the human eye. Modern LED drivers (including UWC) operate at 20–40 kHz.

Humans cannot see this. Cameras can.

So:

Banding on camera ≠ flicker for humans. Banding on the camera ≠ problem


5. Why Relying on the Phone Cameras Creates Real Engineering Problems


This misunderstanding forces engineers to “solve” a problem that does not exist.

Many manufacturers end up:

  • Adding unnecessary bulk capacitors

  • Reducing power factor

  • Increasing component stress

  • Lowering product life

  • Increasing costs

  • Compromising thermal performance

All because a client insists: “My phone shows flicker — fix it.”

This is bad engineering driven by bad diagnostics.


6. The Only Times Camera-Flicker Actually Matters


There are situations where camera banding is a real issue:

  • Professional photography studios

  • Broadcast sets

  • Slow-motion filming

  • High-end retail showrooms with video walls

For these, “camera-friendly” LED drivers exist with:

  • High-frequency modulation schemes

  • Synchronization techniques

  • Flicker reduction tuning

  • Specialized dimming curves


But a common misconception is:

“Camera-friendly drivers = better quality for humans.”

This is incorrect.

Camera-friendly drivers are optimized for camera sensors, not for human biology.

For 99% of spaces — homes, offices, retail, commercial — these specialty drivers provide zero additional human benefit.


7. Practical Rule of Thumb (Share With Your Clients!)


✔ If you can see a flicker with your naked eye → real problem

✔ If only your phone camera shows flicker → not a real problem

✔ If someone reports headaches/eye strain → measure with proper instruments

✔ Never judge flicker by a smartphone


“A camera sees time differently than a human eye. Don’t design LED drivers for cameras.”


8. Why Manufacturers Like Unwired Connect Care About This Topic


The Indian smart lighting market is flooded with imported, rebranded hardware. Most traders don’t control:

  • Driver design

  • Firmware

  • PWM frequency

  • Ripple control

  • EMI/EMC performance

  • Component sourcing

  • Thermal engineering

So they cannot explain why their product flickers on phone cameras — or doesn’t.


At UWC:

  • Every product is designed in-house

  • Firmware is developed and controlled internally

  • PWM, ripple, and dimming curves are deliberately engineered

  • Field failures are <0.1% across deployments

  • All drivers are stress-tested for Indian voltage conditions

This is why UWC products behave predictably in real lighting environments — and why we actively educate the market about such misconceptions.


9. Final Takeaway — And Why This Matters Now


Phone cameras have become the default “test equipment,” but they were never meant to evaluate LED drivers.

Using them leads to:

  • Incorrect assumptions

  • Wrong purchasing decisions

  • Engineering compromises

  • Misinformed customer claims


The right way to measure flicker is with proper photometric tools, not smartphones.

If you need:

  • Human-safe, low-flicker drivers

  • Camera-optimized drivers

  • High-PF commercial-grade drivers

  • Wireless control drivers (Casambi / Tuya / Meshle / AIML / BLE Mesh / Zigbee)

  • Technical consultation on flicker or dimming


UWC can help — backed by deep engineering, not rebranding.


Want to understand flicker the right way?


📩 Reach out to UWC for a technical session on flicker, dimming, and driver selection.


We’re happy to educate, clarify, and guide — because good engineering starts with good understanding.

Comments


  • Whatsapp
bottom of page