“I've owned a 65" LG OLED TV since 2020. I love the picture quality. But, as I watch a lot of cable news, the banners and Headshots have burned into the screen, basically ruining the picture! Has LG fixed the OLED burn-in problem?”
Answer This Question
1-2 of 2 Answers
It's not so much an issue with LG as it is with the settings you have disabled. There are many features available that are automatically enabled or that you can turn on to ensure the screen has automatic dimming, as well as screensavers that activate when you're not using the TV. These features help prevent static images from being displayed for too long. For example, the screensaver is always moving, and you can customize it. If you disable the turn-off features and leave a still image on the screen for too long, all OLEDs can experience burn-in. The technology has improved in recent LG TVs; you just need to research which settings can help prevent burn-in, and you'll find guides to assist you. Additionally, there are several AI features, such as the dimming function I mentioned, that can help with this issue.
Sorry, there was a problem. Please try again later.Hello there! Thank you for sharing your experience with your OLED65C3PUA. It's great to hear that you love the picture quality, but we understand how frustrating screen burn-in can be, especially with prolonged viewing of static content like news banners. While LG has made improvements in the technology to reduce the risk of burn-in in newer OLED models, including advanced pixel-shifting techniques and screen savers, it's important to note that some risk still exists with static images over long periods. To minimize the potential for burn-in, it’s recommended to vary your viewing habits, use the “Screen Saver” mode, and take advantage of the “Logo Luminance Adjustment” feature available in the settings. If you have further concerns or need assistance, please feel free to send us a private message on Social Media @LGUSSupport. Our team is here to help! Thank you for reaching out! —Avril
Sorry, there was a problem. Please try again later.