Much has been said about the yellowing of plastic on old consoles, but it’s clear the displays on old handhelds have their own issues here.
DS, PSPs, PS Vitas, Wii U GamePads and Nintendo Switch systems have been found to be impacted by this, where the edges of the panel have a yellow hue, one that does not match the pixel structure in terms of how it spreads out.
This was originally brought up on the DS thread last year but there still doesn’t seem to be a definitive conclusion about what causes it and what could fix it. So I thought it’d be worth starting a thread where we compile knowledge and resources.
Resources:
GBA Temp: DSi LL De-Yellowing Experiment
VG Collect: Yellowing screens of moderns handhelds
Reddit PSP board: Yellowing on PSP 3000 screen?
The cause
cause doesn’t seem clear. After reading through the above three resources, the yellowing could be caused by a number of factors that either directly cause the yellowing or lead to aging of components that cause the yellowing:
- humidity
- glue melting
- layers of the LCD separating, creating uneven light diffusion
- UV light/heat damage (I think this is more related to the polariser on reflective displays like GB Pocket)
- plastic diffusor over the backlight
- cigarette smoke
Possible fixes
1) Leaving the displays on for extended periods: For DSi XL/LL owners who have systems impacted, leaving the displays on over an extended period of time, preferably with the pixels set to rgb 255 255 255 (white) will reduce the amount of yellowing on them after a number of hours. In the GBA Temp thread above, one user mapped out the deyellowing profile of 5 separate systems left on for up to 58 days.
2) Replacing the light guide plate: As detailed in August 2025 by a user in the GBA Temp thread, swapping the light guide plate in from another system fixed the problem.
As for my personal systems, the two European DSi LLs that I have owned since 2013 and 2018 respectively have yet to develop any yellowing.
But a white DSi LL I just received from Japan yesterday does have this issue, and fix 1) has yet to deliver a noticeable improvement after 24 hours:
Eager to hear your thoughts on this!