Eliminating Dynamic Ghosting on Outdoor LED Screens

Nobody wants to see a ghostly trail behind every moving car on their outdoor LED billboard. Ghosting — that smear or faint afterimage that lingers when content changes quickly — is one of the most persistent complaints with outdoor LED displays. It is not just annoying. It destroys perceived image quality more than poor brightness ever could.

The good news is that ghosting is not some mysterious flaw you just have to live with. It comes from identifiable physical and electrical causes, and each one has a concrete fix.

Why Ghosting Happens More Outdoors Than Indoors

The Parasitic Capacitance Problem

Every LED module has tiny capacitors built into the PCB traces whether you designed them or not. These are parasitic capacitances, and they store electrical charge. When a row of LEDs switches off, that stored charge does not disappear instantly. It leaks out slowly, keeping the LEDs dimly lit for a fraction of a millisecond longer than they should be.

That tiny delay is enough for your eye to register a faint trail behind moving objects. Outdoor screens run at higher brightness levels, which means higher currents, which means more charge stored in those parasitic capacitances. The problem scales with brightness. A screen running at 6000 nits will ghost worse than one running at 3000 nits if the drive electronics are identical.

The row traces and column traces both contribute. Row line parasitic capacitance causes column-direction ghosting. Column line parasitic capacitance causes row-direction ghosting. You end up with a smear that follows the scan direction, which is why fast-scrolling text looks like it has a comet tail.

Scan Timing Mismatches and Switching Delays

Outdoor LED panels use multiplexed scanning. The screen does not light every pixel at once. It lights one row at a time, cycling through all rows in a fraction of a second. If the turn-off delay of the driving transistor does not match the turn-on delay, some rows stay lit slightly longer than others.

Driver ICs have propagation delay variations between channels. A typical IC like the TLC5947 can have channel-to-channel timing skew of plus or minus 15 nanoseconds. That sounds trivial until you realize that at a 1/16 scan rate, each row only gets about one millisecond of on-time. A 15 nanosecond skew becomes a noticeable brightness difference between rows, and that difference manifests as ghosting in dynamic content.

Hardware-Level Ghosting Elimination

Bleeder Circuits and Charge Discharge Paths

The most direct fix for parasitic capacitance ghosting is giving that stored charge somewhere to go. A bleeder resistor placed across the LED anode and ground creates a discharge path. When the row line switches off, the residual charge drains through the resistor instead of leaking slowly through the LED.

A typical implementation uses a 1k ohm bleeder resistor in parallel with a 100 picofarad acceleration capacitor. The resistor pulls the voltage down fast. The capacitor handles the initial surge so the resistor does not waste power during normal operation. This combination can reduce visible ghosting from a rating of 3.8 down to 1.2 on standard visibility scales.

Some designs go further and use active discharge circuits built into the driver IC itself. Chips like the MBI5153 include built-in charge discharge paths that automatically clear parasitic capacitance at the end of each row cycle. This is cleaner than adding discrete components because the discharge timing is synchronized perfectly with the scan clock.

Current Elimination Techniques in Driver ICs

Current elimination (sometimes called current ghosting removal) works differently. Instead of draining charge after the fact, it prevents the wrong pixels from receiving current during row transitions.

During the time when row N is switching to row N plus 1, the column lines for row N plus 1 should not yet be active. But parasitic capacitance on the column lines can couple enough voltage to dimly light LEDs that should be off. Current elimination circuits actively charge or discharge the column parasitic capacitance to a voltage that keeps those LEDs firmly below their turn-on threshold.

Driver ICs with this feature built in, such as the D7258, D4973, or 5922, handle this automatically. The result is a clean row transition with no dim afterglow on the following row.

Upgrading to BCM or FPGA-Based Drive Systems

Traditional 8-bit PWM driving gives you 256 brightness levels. At low brightness, the steps between levels are large, and ghosting becomes visible because the pixel cannot settle cleanly between levels.

Binary Code Modulation (BCM) changes the game. Instead of one PWM cycle per frame, BCM splits each frame into multiple weighted time slots. For 4-bit BCM, you get 15 time units per frame, and each bit controls whether the LED fires during its weighted slot. This gives effectively 16 brightness levels per bit plane, resulting in much smoother transitions and dramatically less ghosting at mid-to-low brightness.

On larger installations with complex content, FPGA-based controllers push this even further. An FPGA can achieve row switching delays below 50 nanoseconds compared to 1.2 microseconds on an MCU-based system. That sevenfold improvement in timing precision means every row turns off exactly when it should, with no overlap and no residual charge buildup.

Signal Chain and Refresh Rate Optimization

Matching Refresh Rates Across the Entire Chain

Ghosting often happens because the sending card, receiving card, and panel refresh rates are not locked together. If your sending card outputs at 60 Hz but the panel is running at a slightly different rate due to clock drift, frames get dropped or repeated, and the visual result is a stuttery ghost.

Lock everything to a master clock. Modern synchronization protocols keep all receiving cards aligned to the same clock source with microsecond precision. When every pixel on every module updates at the exact same instant, ghosting from timing jitter disappears.

The panel refresh rate itself matters. Higher refresh rates mean each frame is displayed for less time, which reduces the window during which ghosting can accumulate. Moving from 1920 Hz to 3840 Hz does not eliminate ghosting by itself, but it gives the PWM more cycles per frame to render clean transitions, which makes the remaining ghosting far less visible.

Signal Integrity and Cable Quality

Long cable runs between the sending card and the first receiving card introduce signal degradation. The data edges get rounded, and timing margins shrink. By the time the signal reaches the last module in a daisy chain, the row clock might be delayed by hundreds of nanoseconds compared to the first module.

Use star topology cabling for large installations. Every receiving card gets the data signal at virtually the same time. If daisy chain is unavoidable, use differential signal lines with proper termination, and keep cable runs under 15 meters per segment.

High-quality HDMI or DVI cables between the media player and sending card also matter. A bad cable introduces jitter that the sending card interprets as frame timing errors, which cascade into visible ghosting on the panel.

Operational Practices That Prevent Ghosting Over Time

Temperature-Compensated Timing Adjustment

LED driver ICs change their switching speed with temperature. At 5 degrees Celsius, turn-off delays can stretch to 200 nanoseconds or more. At 40 degrees, they shrink. If your panel runs the same timing parameters year-round, ghosting will be terrible in winter and barely noticeable in summer.

Modern control systems use NTC temperature sensors on the panels to adjust PWM timing in real time. Every 5 degrees of temperature change triggers a recalibration of the row switching delays. This keeps ghosting performance consistent regardless of weather.

Avoiding Static Content for Extended Periods

This one sounds obvious but gets ignored constantly. If you display the same static image for more than two hours, charge imbalance builds up in the pixel capacitors. When you finally switch to moving content, the pixels that were stuck at high brightness take longer to settle at their new values. The result is a ghost of the previous static image overlaid on the new content.

Rotate content regularly. Even switching between two static images every 30 minutes prevents the charge buildup that causes persistent ghosting. For installations that must show static content, enable a pixel shift function that moves the entire image by one or two pixels every few seconds. This spreads the charge load evenly across all pixels and prevents localized ghosting.

Periodic Recalibration of Drive Currents

As LEDs age, their forward voltage drops. The driver ICs compensate by adjusting current, but the compensation is not always perfect across all channels. After a year of outdoor operation, channel-to-channel current mismatch can reach 3 percent or more, and that mismatch shows up as ghosting in gradients and smooth color transitions.

Recalibrate the drive currents at least twice a year. Measure the output of every module with a photometer, generate per-module correction curves, and upload them to the control system. This takes an afternoon but eliminates a huge chunk of ghosting that would otherwise require a service call to diagnose.