How long does it take for a static menu bar to burn into an OLED?

There is no single number. How long OLED burn-in takes from a static menu bar depends on how bright the bar is, how many hours a day it sits unchanged, how high-contrast its content is, and which panel you own. On a dim panel at moderate brightness you might never see it. On a bright panel running many hours a day with a high-contrast bar, faint permanent wear can show up in months rather than years.

Anyone who gives you a clean answer like "400 hours" is guessing. Burn-in is gradual, cumulative pixel wear, and the rate is set by a handful of variables you can actually control. This post walks through each one so you can estimate your own risk instead of trusting a scare number.

First, what we are actually measuring

It helps to be precise about the failure mode, because the timeline is completely different depending on which one you mean.

OLED burn-in is permanent. Each subpixel is its own organic light emitter that dims slightly the more it runs. When part of the screen (like the menu bar) is consistently brighter than the rest, those subpixels age faster, and the difference becomes a faint ghost that never fully clears. This is differential wear, and it does not reverse.

Image retention is temporary. A static image can leave a short-lived afterimage that fades on its own within seconds to hours once the content changes. That is not burn-in, and it is not what we are timing here. For the full distinction, see OLED burn-in vs image retention.

Image retention is a timing question of seconds to hours. Burn-in is a wear question of months to years. The menu bar is dangerous precisely because it pushes you from the first into the second.

The variables that decide your timeline

Think of burn-in as a slow accumulation, like sun fading on a curtain. Four factors set how fast it builds.

1. Brightness

This is the biggest lever. OLED wear rises steeply with luminance, so running a panel near full brightness ages those bright menu-bar pixels far faster than running it dim. A white menu bar at high brightness is close to the worst case the panel can experience. The same bar at low brightness in a dark room may wear so slowly you never notice it. Doubling your brightness does not just double the risk. It is worse than that.

2. Hours per day at the same content

Burn-in is cumulative, so more hours of an unchanging bar means more wear. The menu bar is uniquely bad here because it never moves and is visible in almost every app, so its on-screen time tracks your total screen time. A wallpaper or a window scrolls, gets covered, and changes. The menu bar does not.

3. Content and contrast

What sits in the bar matters. A light menu bar over a dark wallpaper creates a sharp, high-contrast boundary, and high-contrast static edges are exactly what produces visible ghosting. Static text and icons that hold the same screen positions (a clock, fixed status icons) add their own localized wear. Dark Mode lowers the average brightness of the bar and softens the contrast, which slows things down, but it does not stop it, because even a dark bar is still static.

4. The panel itself

Not all OLEDs age at the same rate, and most ship with built-in mitigations. Many OLED monitors and TVs run pixel-shifting, logo-dimming, and periodic compensation cycles that slow or partially mask wear. Panel chemistry differs too, and some newer stacks are more resistant than early OLEDs. This is why two people with the same habits on different displays can get very different outcomes, and why knowing whether your display is even OLED matters before you worry at all.

Do you even have an OLED to worry about?

Worth a reality check, because the timeline is moot on the wrong panel. As of mid-2026, most shipping Macs and Apple displays are not OLED. Current MacBook Pro screens and the Pro Display XDR use mini-LED LCD, which does not suffer organic-emitter burn-in the way OLED does. Apple's OLED panels ship in iPhone and Apple Watch, not in the desktop displays people stare at all day.

On the Mac, OLED almost always means an external monitor, the LG, Samsung, ASUS, and Dough panels that have made OLED desktop displays common. If you run one of those, the static menu bar is a genuine, ongoing concern. If you are on a mini-LED MacBook Pro or an LCD external, you can relax about burn-in specifically. An OLED MacBook Pro has been widely expected, but treat any future Apple OLED laptop as unconfirmed until it actually ships.

So what is a realistic estimate?

Combine the variables and you get a range, not a date.

• Lower risk: a modern OLED monitor, moderate brightness, Dark Mode, mixed daily use, the panel's own compensation running. Visible menu-bar ghosting may take years, if it ever becomes noticeable.
• Higher risk: high brightness, a light menu bar over a dark wallpaper, eight or more hours a day in the same apps, an older or compensation-light panel. Faint permanent wear can become visible in months.

The honest takeaway is that the menu bar is the single most consistent burn-in stressor on a Mac, because it checks every bad box at once: bright, static, high-contrast, and on-screen nearly all the time. For why it outranks even your wallpaper or the Dock, see why an always-on menu bar is the worst thing for an OLED screen.

Why prevention beats guessing

Here is the practical problem with timelines: by the time burn-in is visible, it is permanent. You cannot undo it, only stop adding to it. So the smart move is not to calculate exactly how many months you have. It is to remove the stressor before any of it accumulates. Every hour the static bar is not on screen at full brightness is an hour of differential wear you simply skip.

macOS gives you one built-in tool, under System Settings > Control Center > Automatically hide and show the menu bar. It helps, but it is global (you cannot apply it to just your OLED while leaving the bar on your LCD), and the bar still reappears constantly on hover and when you move between apps. There is no native way to hide the menu bar on one display only. It is also worth being clear that icon managers like Bartender, Ice, Hidden Bar, and Dozer organize the icons in your menu bar. They do not remove the system bar itself, so they do little for burn-in.

This per-display gap is the specific problem TuckBar exists to solve. You tag only the displays you want protected, and it covers the menu bar by painting your live wallpaper over it (so the bar simply disappears) or by dimming or blacking it out, reveals it on hover when you actually need it, and can untuck on a timer. Mixed OLED-and-LCD setups get protection where it matters and a normal bar everywhere else.

You do not need to know your exact burn-in countdown. You need to keep that bright, static rectangle off the panel that can be permanently damaged by it. Remove the stressor and the timeline question stops mattering.