What “refresh rate” means for LED walls (and transparent LED)

For TVs/monitors, refresh rate often means “frames per second displayed.”

For LED walls, the term is commonly used differently: it relates to how the LEDs are switched on/off to create brightness via PWM, and it’s often expressed as thousands of Hertz (e.g., 3840 Hz, 7680 Hz).

That matters because your camera doesn’t continuously see light like your eye. It samples exposure in discrete windows (shutter), and many sensors read out line-by-line (rolling shutter). When the sampling window doesn’t line up with LED timing, you see artifacts.

Why cameras see banding when your eyes don’t

Rolling shutter + scan mux mismatch (the #1 cause)

LED panels often use multiplexing/scan mux: only some rows (or groups) are lit at a time, rapidly cycling so the human eye integrates it.

Cameras, especially rolling shutter cameras, may capture different parts of the frame at slightly different times. If during the shutter-open period the camera “collects” a different number of LED scan cycles in different sensor rows, you get bright/dark bands. In practice, a mismatch between camera shutter timing and the panel’s scan mux period often leads to scan-line artifacts.

“It gets worse when we dim it”

This is common for transparent LED storefronts: day mode is bright; night mode is dim to avoid glare.

At low brightness, PWM pulses become narrower, and timing artifacts can become more visible on camera—especially in dark or mid-gray content. Scan ratio and driver behavior affect available time for refresh and PWM behavior, and artifacts can appear as bands when different sensor sections catch different numbers of pulses.

A note on human comfort (why “invisible flicker” still matters)

Even if flicker isn’t consciously perceived, it can still contribute to discomfort (e.g., fatigue, eyestrain) for some people under certain modulation conditions. It’s a useful reminder that “looks fine” isn’t always “is fine.”

The specs that actually matter (and why “3840 Hz” is not a magic spell)

1) Refresh rate (PWM refresh): typical 3840 Hz or 7680 Hz

In many LED wall contexts, 3840 Hz and 7680 Hz are commonly cited as “typical” refresh values. Higher refresh generally reduces the chance of visible banding/flicker across more shutter settings—especially for broadcast/multi-camera demands.

Transparent LED reality check:
Many transparent LED products advertise 3840 Hz as a “high refresh rate.” That’s often adequate for casual smartphone filming if scan ratio + PWM behavior + processor timing are decent. But for professional cameras, fast shutter, panning shots, or dim content, you may still see artifacts unless the whole timing chain is designed for on-camera use.

2) Scan ratio (multiplex): the hidden lever

Scan ratio describes how many lines (rows/groups) the driver IC controls in sequence. A lower scan ratio (e.g., 1:8 vs 1:16) generally means the panel has more time to increase refresh rate and/or PWM behavior, reducing artifacts.

If your supplier can’t tell you scan ratio (or dodges the topic), that’s a procurement red flag for any “camera-friendly” requirement.

3) Timing control / shutter sync / genlock-capable processing

Some processors can tune panel refresh timing to camera shutter settings (or at least allow better synchronization). With shutter-sync/genlock-capable systems, you can reduce artifacts like scan-mux lines and exposure instability—especially when the camera isn’t open long enough to capture a complete PWM cycle.

For live broadcast or multi-camera (even two cameras filming the same storefront for different angles), synchronization features become far more valuable.

Transparent LED screen for building at day

Practical camera settings: what to do on site today

You can reduce artifacts without changing hardware—sometimes.

Step 1: Lock your frame rate to the region

If you’re in 50 Hz power regions, start with 25 fps or 50 fps.
If you’re in 60 Hz power regions, start with 30 fps or 60 fps.

This isn’t because the LED wall “runs on mains frequency,” but because many camera and lighting environments end up harmonizing better when you stay consistent with local standards. (Still: test is king.)

Step 2: Use shutter angle thinking (more stable than random shutter fractions)

At 24 fps, a 180° shutter corresponds to ~1/48 exposure.

Safe starting points (field defaults)

24 fps → 180° (≈ 1/48)
25 fps → 180° (≈ 1/50)
30 fps → 180° (≈ 1/60)
50 fps → 180° (≈ 1/100)
60 fps → 180° (≈ 1/120)

Then test:

Fast pans across the transparent LED
Mid-gray content (the “worst case”)
Dimming down to your night setting

Step 3: If you see bands, adjust shutter in “clean multiples”

Banding often improves when shutter speed becomes a better match (or multiple) of the LED timing cycle. In practice, mismatched relative frequencies between LED PWM/refresh behavior and camera shutter can produce flicker and rolling bands—so structured testing is essential.

If your processor supports true shutter-sync/genlock workflows, use them. Otherwise, you’re hunting for a “lucky” shutter value—possible, but not scalable.

Evidence-backed reference table: artifact → root cause → fix

What you see on camera	Likely root cause	Fast fixes	System-level fixes
Rolling dark horizontal bands moving	Rolling shutter sampling vs LED PWM/scan mux mismatch	Try 180° shutter; adjust shutter speed; avoid extreme fast shutter	Lower scan ratio panels; processor with timing/shutter-sync; genlock workflow
Thin “scan lines” / mux lines	Scan mux period mismatch with shutter window	Slight shutter change; reduce pan speed	Shutter-sync features; better scan ratio; higher refresh headroom
Flicker only when dimmed	PWM pulse scarcity at low luminance; timing instability	Raise LED brightness and reduce camera ISO; avoid ultra-low brightness	Panels/driver design that maintains stable low-luminance PWM behavior; better scan ratio
Looks fine to eye, awful on phone	Phone rolling shutter and auto-exposure fighting PWM	Lock exposure in phone/pro camera app	Improve timing chain; higher refresh; better processing

What to demand in your RFQ (transparent LED / LED film)

If “camera-friendly” matters, your RFQ must include measurable acceptance, not marketing adjectives.

Minimum spec questions (ask and require written answers)

Refresh rate (Hz) at intended configuration
Scan ratio (e.g., 1:8, 1:16) and why
Supported processor/controller ecosystem and whether it supports genlock/timing tuning
On-camera notes at low brightness (your night mode)
Recommended camera settings from the supplier (if they can’t provide any, that’s telling)

The engineering mindset we use for supplier validation is aligned with what we outline in:

Technology & Quality

Acceptance testing (simple, brutal, effective)

FAT (Factory Acceptance Test)

Gray ramp + 20–50% gray screen test (banding reveal)
Solid color test patterns
Record a short video at 24/25/30/50/60 fps with 180° shutter
Dimming sweep: 100% → your night setting (record at each step)

SAT (Site Acceptance Test)

Repeat the above on the actual glass with real cable routing and final brightness
Add a pan/tilt test across the screen (fast motion triggers issues)

For projects where the screen must look clean on camera for marketing content, include a documented reference in your project file alongside your solution category choice:

Projects & Case Studies

Transparent LED screen for building at night

Transparent LED-specific notes (why these projects surprise teams)

Transparent LED is usually “spec’d for daylight,” but filmed at night

Storefront transparent LED is often sold on brightness and transparency. On camera, the real battle is often night mode, because:

you dim heavily to keep glass premium-looking,
content shifts to dark backgrounds (logo, minimalism),
and cameras amplify low-luminance artifacts.

That’s why scan ratio + low-luminance behavior matter as much as headline refresh rate.

Film vs cabinet transparent LED: different risk profile

If you’re deciding between solution types:

Film can be visually elegant, but the on-camera outcome still depends on timing chain + controller + commissioning quality—not just the film itself.

A quick “do this first” checklist (field operator version)

Set camera to 25/50 fps (50 Hz regions) or 30/60 fps (60 Hz regions)
Start at 180° shutter
Test: mid-gray + pan across screen
If banding appears: change shutter angle slightly (e.g., 172.8°, 144°, 216°), retest
If artifacts persist across many shutter angles: you likely need better timing control (processor features) or a different panel/scan ratio

Closing: the buying rule that saves budgets

If your project will be filmed—storefront marketing, product launches, influencer content, livestreams—treat “camera-friendly” as a system requirement: