Why an always-on menu bar is the worst thing for an OLED screen

The macOS menu bar is the single worst thing on your screen for OLED burn-in because it combines all three risk factors at once: it is bright, it is high-contrast against the content below it, and it never moves. Burn-in is permanent, uneven pixel wear, and the pixels that wear fastest are the ones driven brightest for the longest in a fixed position. The menu bar is exactly that strip. On an OLED panel, a thin band of dimmer pixels can slowly etch itself across the top of the display.

That is the whole answer in three sentences. The rest of this post explains why each factor matters and why the menu bar specifically is so much riskier than the moving content below it.

What burn-in actually is

OLED displays light each pixel individually with an organic compound that dims as it ages. Drive a pixel hard for a long time and it ages faster than its neighbors. Burn-in is that differential aging made visible: a faint ghost of whatever sat in one place, showing through against a uniform color. It is permanent.

It is not the same as image retention, which is a temporary afterimage that fades once the pixels display something else. Retention is recoverable. Burn-in is the version you cannot undo. So when we talk about the danger of a static menu bar, we mean true burn-in: the slow path measured in cumulative hours, not the afterimage you sometimes see for a minute after a video pauses.

The three ingredients burn-in needs

Differential pixel wear accelerates when three things line up. The menu bar hits all three, which is why it stands out from almost everything else on a Mac desktop.

1. Brightness

The menu bar is one of the brightest regions on screen, especially in light mode, where it is a near-white bar across the top. On OLED, brightness maps almost directly to how hard each subpixel is driven, and harder-driven pixels age faster. A bright bar is a bar of fast-aging pixels.

Dark mode helps here, because a dark menu bar drives those pixels much more gently. That is real protection, not a placebo, and it is one reason a dark wallpaper and dark mode setup is the sensible default on an OLED Mac. But dark mode alone does not solve the problem, because of the next two ingredients.

2. High contrast against a moving background

Burn-in becomes visible as a difference between worn and unworn pixels. The menu bar sits above your desktop and your app windows, which change constantly. The bar itself does not. So you get a fixed strip of pixels with one wear history butting up against a region with a completely different one.

That contrast is what makes a ghost legible later. A uniform full-screen image that ages evenly leaves nothing to compare against. A static bar over ever-changing content leaves a crisp boundary, which is the worst case for showing wear.

3. It never moves

This is the one that makes the menu bar uniquely bad. Most of what you look at drifts. You scroll, windows open and close, video plays, even your wallpaper can rotate. The content layer of your screen spreads its wear around.

The menu bar does not move one pixel. The clock, the Wi-Fi icon, the Apple menu, your menu-bar app icons: same coordinates, every hour, every day. There is no averaging out. Whatever brightness it has is concentrated on the same pixels indefinitely. Concentration in one fixed location is the core mechanic of burn-in, and the menu bar is the most concentrated, most fixed element on the entire display.

Burn-in is not about how bright something is once. It is about the same pixels being driven the same way, in the same spot, for thousands of hours. The menu bar is the only part of your screen guaranteed to do exactly that.

Why the menu bar beats other static elements

Plenty of UI is static-ish. The Dock sits at the bottom, app toolbars hold still, a code editor's gutter barely moves. So why single out the menu bar?

• It is always present. The Dock can auto-hide. App chrome disappears when you close the app or go full screen. The menu bar, by default, is on top of everything, in every app, on every Space.
• It is uniform and edge-defined. The bar is a clean horizontal strip with a hard bottom edge. That geometry is exactly what makes wear show up as a visible band rather than diffuse haze.
• It is bright by default. In light mode it is close to white. Few other always-on elements are that bright.
• It owns the same row of pixels system-wide. Switch apps all day and the content below changes completely, but the top strip stays lit in place.

The Dock is a real secondary concern, which is why it is worth thinking about hiding the Dock too. But the Dock already auto-hides natively, and many people keep it hidden anyway. The menu bar is the element that is both high-risk and, by default, never out of the way.

Does this apply to your Mac?

Here is the honest part. Most Macs shipping today do not have OLED screens. Current MacBook Pro displays and the Pro Display XDR use mini-LED backlighting behind an LCD, which does not burn in the way OLED does. Apple uses OLED in iPhones and the Apple Watch, not in its current Macs or desktop displays. An OLED MacBook Pro has been widely rumored, but rumored is not shipping, so do not assume your built-in screen is at risk without checking. If you are not sure what panel you have, start with which Macs and Apple displays are actually OLED.

On the desktop, OLED almost always means an external monitor: panels from LG, Samsung, ASUS, Dough, and others, often QD-OLED, frequently used as a primary or gaming display. If you run a Mac into one of those, the menu bar gets painted across the top of an OLED panel all day, and the risk above is real and specific. That is also why the question of whether the menu bar causes burn-in comes up most among external-OLED users.

Why this is awkward to fix on a Mac

If only one of your displays is OLED, you would want to hide the menu bar on just that screen. macOS does not let you do that. It has a built-in setting under System Settings, Control Center, "Automatically hide and show the menu bar," but it is global: turn it on and the bar auto-hides everywhere, including your perfectly safe LCD. There is no built-in per-display menu-bar control. That limitation is its own topic, covered in why macOS can't hide the menu bar on just one display.

It is also worth being clear about what the popular menu-bar tools do and do not do. Bartender, Ice, Hidden Bar, and Dozer manage your menu-bar icons: they tidy, hide, and reorganize the status items you have added. They are good at that. But they do not remove the system menu bar itself, and they do not work per display, so they are not a burn-in fix for the bar as a whole.

If you want to address the static menu bar OLED risk on just the screen that needs it, that is the gap TuckBar exists to fill. You tag the OLED display, and TuckBar covers the menu bar there, either painting your live wallpaper over the strip so the bar simply vanishes or blacking it out to turn those pixels off entirely. The bar reappears when you move the pointer to the top, so you keep access to it. Your LCD keeps its normal menu bar.

The takeaway

Burn-in needs brightness, contrast, and a fixed position held for a long time. The menu bar delivers all three by design and never gets out of the way on its own. If you run a Mac into an OLED panel, the single most effective change you can make is to stop lighting that top strip the same way every hour of every day. Dark mode reduces the brightness. Getting the bar off the OLED entirely removes the problem.