Connecting a PlayStation 2 to a Modern TV for the Best Picture

Getting a PS2 to look right on a modern TV is not about buying the cheapest HDMI converter and calling it done. The PlayStation 2 library is dominated by 480i. That single fact decides everything about your cable and scaler choices. A flat-panel's internal processing treats 480i with the same algorithms it uses for broadcast television. That sounds fine until you see what it does to a game's sprite edges and text. You get combing artifacts, shimmer, and two to six frames of input lag, as measured by RetroRGB on unprocessed sets. The only way around this is to feed the display a clean progressive signal. You need an external scaler between the console and the TV. Three viable paths exist: a quality component cable into a RetroTINK 5X-Pro, an OSSC with its bob conversion, or an mClassic as a post-processor on top of a basic converter. Each path trades off flicker reduction, input lag, and sharpness differently. None of them work if you skip the 480i question.

Before you buy anything, understand the PS2's native output. The console outputs analogue component video (YPbPr) at up to 480p for games that support progressive scan, and 480i or 240p for everything else. The component port on the back of a slim or a fat PS2 carries those signals over three RCA jacks. A good cable from a maker like HD Retrovision or Retro Access is the only way to get a clean signal out of the console. The cheap HDMI converters do not scale anything. They are line-level devices that take the PS2's analogue output and repackage it as an HDMI signal. That means they pass 480i straight through to your TV's processor. This is the failure case. A PS2-to-HDMI converter that costs very little introduces no frame buffer of its own, but it leaves the conversion to the TV, which is exactly the problem you are trying to solve. The PS2's component versus HDMI question is really a question of whether you let a scaler handle the 480i conversion or trust the TV to do it. The TV always loses on lag and artifact removal.

The mClassic is a small HDMI dongle made by Marseille that promises to upscale and anti-alias any signal you feed it. In a PS2 mClassic setup, the chain is PS2 to a basic HDMI converter that outputs 480p, then that signal into the mClassic, then the mClassic into the TV. The mClassic's blue LED mode applies upscaling and anti-aliasing. The green LED mode only does anti-aliasing. Off is passthrough. The trade-off is that the mClassic is not a scaler in the sense of adding a frame buffer. It processes a 480p input and outputs a frame that is 1440p tall, but the active image area inside that frame is only 1080p upscaled by the mClassic's proprietary algorithm. Marseille's 1440p output claim is real in the sense that the frame is 1440p tall, but it is not a native render. The mClassic adds less than one millisecond of input lag, which is fine for most players. It cannot fix the 480i problem because it requires a progressive input to work at all. If you feed it 480i, it passes it through or fails to handshake with the TV. The mClassic setup is only worth it if you already have a way to force the PS2 to output 480p, like a GSM Selector or a game's built-in progressive mode. Even then, it is a post-processor, not a scaler.

How Interlaced Video Breaks on a Progressive Panel

The PS2 480i conversion question is the core of this whole page. 480i is an interlaced signal that draws odd lines first, then even lines, every 16.67 milliseconds at 60Hz. A modern TV has to process that signal to display it on a progressive panel. The quality of that processing determines whether you see smooth motion or a mess. The PS2's own behaviour makes this worse. It frequently switches between 240p and 480i within a single game, often during a menu or a cutscene. This resolution-switch blanking problem is a known issue documented by Shmups Forum testing. The console's sync signal dips in voltage during full-white frames. A scaler with a tight sync tolerance will drop the signal, blank the screen, and take a second or two to re-sync. The fix is a scaler with a frame lock speed that handles the switch without losing the signal.

The Three Approaches to Cleaning Up 480i

The RetroTINK 5X-Pro uses motion-adaptive processing, which reconstructs full resolution from 480i without flicker by comparing motion between fields. The OSSC uses bob conversion, which weaves the two fields together and causes visible horizontal jitter on moving objects. The TV's internal processor is usually bob or weave, which is why you get combing artifacts on fast motion. The only way to get acceptable 480i performance is to let a good scaler handle it.

When someone asks for the best PS2 video cable, the answer is component video (YPbPr). The PS2's component output is the highest quality analogue signal the console can produce, carrying YCbCr 4:2:2 colour space in the digital domain and YPbPr in the analogue domain. A good component cable from HD Retrovision is built with proper shielding. This matters because the PS2's analogue signal is susceptible to noise and ghosting. The alternative is RGB SCART. The PS2 can output this via a SCART cable with composite video sync or luma sync depending on the manufacturer, but RGB is not supported over the component port for 480p without a sync-on-green signal. The PS2's 480p over RGsB is supported by the RetroTINK 5X-Pro and the OSSC via their component inputs. Generic HDMI converters do not support it because they require separate sync. So the best PS2 video cable is a component cable. The second best is an RGB SCART cable if you are using a scaler that accepts it. The PS2's D-Terminal output, which is a Japanese-region only connector, carries D1 (480i) and D2 (480p) and is electrically identical to component. The same rules apply.

If you want the best possible PS2 on a modern TV, buy the RetroTINK 5X-Pro. It accepts component, S-Video, composite, and RGB SCART. It uses motion-adaptive processing to handle 480i without the flicker that plagues simpler scalers. The 5X-Pro has a menu system, profile saving, and CRT simulation filters that make a 240p signal look like a consumer tube television. Input lag measured by RetroRGB is under 0.25 milliseconds at 480p, which is effectively zero, and about 1.5 frames at 480i with motion-adaptive processing enabled. That half-frame penalty is the cost of reconstructing full resolution from interlaced video. It is worth it because the alternative is a bob-processed mess. The 5X-Pro also handles the PS2's 240p/480i resolution switches gracefully, with a frame lock speed that re-syncs in a fraction of a second. Shmups Forum testing confirms this is the key to avoiding blank screens on games like Silent Hill 2. The 5X-Pro outputs up to 1440p over HDMI, which is a clean 1080p signal for most TVs. It supports the PS2's 480p over RGsB via the component input. The only downside is the price. For a PS2 on a modern TV, it is the reference.

The Open Source Scan Converter is the other high-end option, but it comes with a serious caveat for PS2 owners. The OSSC is a line multiplier with no framebuffer. It adds zero lag in the traditional sense, measured in microseconds rather than milliseconds. It takes a 480p signal and line-doubles it to 960p, or line-doubles 240p to 480p. The result is razor-sharp pixels with no processing artifacts. However, the OSSC only accepts RGB SCART, component video, and VGA. It has no composite or S-Video input, so you are locked into the console's best analogue output. More importantly, the OSSC's bob conversion for 480i is its Achilles heel. Bob conversion weaves the two interlaced fields together, which causes horizontal jitter on moving objects because the image is shifted by one scanline every field. For a game like God of War that runs at 480i, the OSSC produces a visible flicker that is fatiguing to play. The OSSC also struggles with the PS2's 240p/480i resolution switches because it has no frame buffer to smooth the transition. You get a blank screen for a second or two. The OSSC is the right choice for 240p games on retro consoles. For a PS2 on a modern TV, the 480i-heavy library makes the RetroTINK 5X-Pro the better buy. The OSSC Pro adds a framebuffer and motion-adaptive processing, but it costs more than the 5X-Pro and is overkill for most players.

For a cheaper path, the GBS-Control is a community-developed firmware that runs on a GBS-8200 VGA scaler board. It adds motion-adaptive processing and accepts component video. That is enough for a PS2 on a modern TV if you are willing to tinker. The GBS-Control's motion-adaptive processing works, but it exhibits chroma artifacts on fast-moving red objects. The interface is not user-friendly. You flash the firmware, wire a control board, and configure it via a serial terminal. The RetroRGB site has a full guide, but it is not for a beginner. If you want a simple stopgap, the mClassic is the only plug-and-play option that works with a PS2, but only if you force 480p with the GSM Selector or a game's progressive mode. The mClassic and GBS-Control serve different purposes. Both are compromises. The GBS-Control is the best budget solution if you are technical. The mClassic is the best budget solution if you are not. The failure case is buying a generic composite-to-HDMI converter. It treats the 240p signal as 480i video, applies weave conversion, and adds two frames of lag. That is the single worst thing you can do for a PS2 on a modern TV.

You can avoid the 480i problem entirely by using the PS2's GS Mode Selector (GSM), a homebrew application that forces supported games to output 480p or 240p. GSM runs from a memory card or a hard drive. It patches the video mode in real time. Compatibility is title-dependent. Some games work perfectly. Others crash. Some go into FMV desync because the cutscenes are encoded at a different resolution. Forcing 480p also changes the sharpness of 2D elements, which can make text smaller and harder to read on a large TV. GSM is a free tool, so try it. Do not rely on it as your primary solution. A forced 480p signal is still analogue. You still need a scaler or a converter to get it to HDMI. The RetroTINK 5X-Pro or OSSC will handle it fine. The PS2's BIOS version 2.00 and later supports a 480p system menu, but that does not affect game output. GSM is a great addition to a signal chain, not a replacement for it.

The physics of input lag are simple. A frame at 60Hz is 16.67ms. Any processing step that buffers a full frame adds at least that much. The RetroTINK 5X-Pro at 480i adds about 1.5 frames, which is the cost of motion-adaptive processing. The OSSC adds microseconds because it is a line multiplier, but the TV then adds its own scaling lag. The mClassic adds less than 1ms but does not touch 480i. Chroma subsampling is another factor. The PS2 outputs YCbCr 4:2:2 in the digital domain, but component video is analogue, so the scaler has to convert it. Most scalers output 4:4:4 over HDMI, which preserves colour detail. Cheap converters may subsample to 4:2:0, which blurs red and blue edges. HDMI handshake issues are a real failure mode, especially with the mClassic. A newer TV may refuse to negotiate HDCP with the dongle. The only fix is a different converter or scaler. HDMI cable certification also matters. Use a certified high-speed cable rated for 18Gbps.

Does the mClassic work with a PS2 without a scaler? No. The mClassic requires a 480p input. You need a PS2 HDMI converter that outputs 480p or a GSM Selector forced progressive mode. Feeding it 480i causes a handshake failure or a purple tint on some TVs.

Will a cheap HDMI converter damage my PS2? No, but it will not help. A basic converter just converts analogue to digital without scaling. Your TV's processor handles 480i, adding lag and combing artifacts. It is not a fault, just a useless step for picture quality.

Is the GBS-Control as good as the RetroTINK? No. The GBS-Control is a budget option with motion-adaptive processing, but it shows chroma artifacts on reds and requires tinkering. The RetroTINK 5X-Pro has better motion handling, a menu system, and zero lag at 480p. It is the reference.

Why does my PS2 game flicker on the OSSC? The OSSC uses bob conversion for 480i, which weaves fields and causes jitter. That flicker is inherent to bob. The only fix is a scaler with motion-adaptive processing, like the RetroTINK 5X-Pro.

The single most practical thing you can do is buy an HD Retrovision component cable and a RetroTINK 5X-Pro. Plug the PS2 into the 5X-Pro before it reaches your TV. That chain gives you motion-adaptive processing, zero-lag at 480p, and a clean 1080p output that your TV will not mangle. The failure case that most often goes wrong is buying a generic HDMI converter and being surprised that the image looks like a smeared version of what you remember. That converter has no processor, no scaler, and no solution for the PS2's 480i output. Skip it. Skip the OSSC unless you play only 240p games, because the 480i flicker will make you quit. The RetroTINK 5X-Pro is the only option that does not compromise. It is the one upgrade that makes a PS2 on a modern TV look like a console from the future, not the past.

The OSSC's bob conversion causes a horizontal jitter on God of War's 480i output that the RetroTINK 5X-Pro eliminates at 1.5 frames of lag, measured by RetroRGB in 2021.