by Alexa Ray Corriea

We’re in the eighth generation of home video game consoles, and of the three most popular options, two are not backward compatible. Nintendo’s Wii U offers access to its back catalog of Wii games through a separate console mode and to games from the company’s early days through the Virtual Console. But for the PlayStation 4 and Xbox One, owners have to count on remastered editions of their favorite older games or services like PlayStation Now if they want access to them on the newer machines.

It hasn’t always been this way, though. Previous console generations had the guts (literally) to run games from older hardware, but over time the cost of adding the extra technology to newer machines proved to be too high. Are we justified in feeling cheated out of consoles with backward compatibility? Or is it all just part of the industry’s evolution towards better, brighter experiences?

The history of backward compatibility

When we say something is backward compatible, it means that the object in question can work with input generated by an older product or piece of technology. If the new, most recent technology can receive, read, view or play input–like media–in older formats, then the product is backward compatible. In the case of consoles, when we talk about backward compatibility, we’re asking if the console can play games created for previous hardware in that console’s family. For example, early PlayStation 3 models could play PlayStation 2 and PlayStation 1 games, while the first run of the Nintendo Wii was compatible with GameCube games, memory cards, and even controllers.

The early years of video game consoles saw backward compatibility as a more common feature. But for some companies, it was harder than others.

Atari: The Atari 7800, released in 1986, was backward compatible with the Atari 2600 but not the console that directly preceded it, the 5200. This was because the 7800 included many of the same chips built into the original 2600. Users could put the 7800 into a “2600” mode that slowed down the console’s processor from 1.79 MHz to 1.19 MHz, which mirrored the 2600’s processor. In this mode, game data was accessed in 4K blocks rather than the 7800’s standard 48K blocks, allowing the newer Atari to read and play the older machine’s games.
Atari never released another true console with backward compatibility, but in 1987, the company launched the Atari XEGS, which could play the entire library of software developed for Atari’s 8-bit home computers. Additionally, the company developed but never released the Atari Jaguar II; the canceled project would have allowed users to play catridges for the original Atari Jaguar and Jaguar CD.


Sega: In 1983, Sega released the cartridge-based Sega Game 1000 in Japan; it would never be released outside of the territory. The company’s next machine, 1986’s Sega Master System, was built to be compatible with the SG-1000’s game cartridges. Following the Master System, Sega opted not to put the previous console’s chips in its next machine, the 1989 Sega Genesis, but instead made backward compatibility possible through a peripheral. Although the Genesis contained an 8-bit processor, this accessory, the Power Base Converter, had to be hooked up to the Genesis in order to play Master System games.

Sony: The PlayStation 2, which launched in 2000, allowed users to play PSOne discs, although PSOne memory cards were also required to access and store save data. PSOne controllers were also compatible with the hardware, although certain functions like the analog buttons were not available to use when playing PS2 games. Early PlayStation 3 models were backward compatible with both PSOne and PS2 games, and save files from PSOne and PS2 memory cards could be transferred to the PS3’s hard drive using a memory card adapter. When Sony debuted the PS3 Slim model in fall 2009, the company removed backward compatibility chips in order to make it a thinner piece of hardware. No PS3 models following the launch of the Slim have had backward capability.

Microsoft: The Xbox 360, 2005’s successor to the original Xbox, allowed for some backward compatibility but required several more complicated hoops to jump through. Unlike the PlayStation 2 and 3, players couldn’t put previous generation discs into the system and expect them to run. Playing Xbox titles on Xbox 360 required system software updates from Microsoft and emulation profiles. These emulation profiles were created for each individual game–there was no blanket solution for all Xbox titles–and could be downloaded straight to the console via Xbox Live or through and burned to a CD or DVD. Only Xbox 360s with the official Xbox 360 hard drive could run the emulation profiles.

In November 2007, Microsoft stopped creating emulation profiles for Xbox games. To date, there are 461 Xbox titles that are compatible with the Xbox 360. Any game without an official emulation will not work.


Nintendo: While Nintendo’s early consoles ran on their own media–with sizes and shapes of cartridges and discs varying between generations–it all came together with the Wii in 2006. Wii models made pre-2011 were fully backward compatible with Nintendo GameCube game discs, memory cards, and controllers. This was because the Wii hardware had ports for both GameCube memory cards, and peripherals and its slot-loading drive was able to accept and read the previous console’s discs. When playing a GameCube game, however, only GameCube functions were available, and only compatible memory cards and controllers could be used because the Wii’s internal memory would not save GameCube data. Online and LAN features of certain GameCube games were not available, however, due to the Wii not having serial ports for the GameCube’s Broadband and Modem Adapters.

The redesigned Wii Family Edition and Wii Mini, launched in 2011 and 2013 respectively, had this compatibility stripped out.

What’s the current situation?

Right now, Nintendo’s Wii U is the only console on the market with true backward compatibility. Wii software can be transferred to the Wii U and and accessed through Wii Mode by clicking on the “Wii Menu” home screen icon with a Wii remote. Speaking of which, Wii remotes and peripherals also work with the Wii U. In Wii Mode, games can be displayed on the GamePad screen, but Wii Remotes are still required to play them.

Additionally, Nintendo’s handheld lines also hold up in terms of backward compatibility. The Game Boy line read software from most previous incarnations of the handheld, with the exception of the Game Boy Micro. The company’s most current handheld, the Nintendo 3DS, can also play games from the Nintendo DS.

Neither of Sony’s current gaming hardware, the PS4 or PlayStation Vita, are backward compatible. The PS Vita cannot play the UMD discs of its predecessor, the PlayStation Portable, because there is no UMD reader; instead, the Vita utilizes small flash memory cards the size of SD memory cards. Compatible PSP games can, however, be downloaded from the PlayStation Network on PS Vita.

The main reason PlayStation 4 and Xbox One can’t play older games games is because both consoles use an entirely different kind of chip with a different instruction set. While older PlayStations and the Xbox 360 used PowerPC chips, the PS4 and Xbox One completely changed the guts of the system by using an x86-64 architecture, which is closer to Intel and AMD CPUs.

For PS4, Sony’s PlayStation Now service, currently in open beta, does allow users to stream PS3 games, but requires a subscription fee.

Speaking with GameSpot during the PS4’s launch in November 2013, PS4 architect Mark Cerny said that, while the plan for PS3 was to put PS2 hardware in every console, the move was impossible with PS4.

“Software emulation is very hard to do unless you have 10 times the frequency of the previous console,” Cerny said. “Software emulation is not about the overall performance that can be achieved by having a great number of processing units. It’s about being able to do things quickly. You’re trying to emulate your previous hardware, and that takes you a certain number of operations to emulate whatever it was doing. So, PlayStation 1 is emulatable on PlayStation 2 because there was an increase in the frequency of the CPU and GPU to something like a factor of 10. And the same thing is true between the PlayStation 2 and PlayStation 3. The PlayStation 2 is something like 300 Mhz; PlayStation 3 about 3.2 Ghz — about 10 times as much. But even so, it’s very, very hard to do.”


“The world we’re in now, though, frequency has stopped increasing,” he added. “For example, if you look at your PC, the frequency of the CPU hasn’t changed much in the last ten years. And that makes emulation just really hard to do.”

Microsoft’s Xbox One is also not compatible with its predecessor’s media. Nor can you use the Xbox 360’s Kinect with the Xbox One; you must purchase the updated version of the peripheral. There is no PlayStation Now equivalent for Xbox One.

How do you make something backward compatible?

The more advanced the technology used for consoles becomes, the more difficult–and more expensive–it is to add the hardware or software necessary for backward compatibility. Consoles with more features will likely be pricier, and a current generation console with a the previous generation’s chipset would be wildly expensive; think of a PS4 or Xbox One with another $200 tacked on to account for the additional parts. This is one reason why Sony and Microsoft have shied away from including backward compatibility in their current consoles.

But just what does it take to make something backward compatible? There are two ways to go about implementing the feature: hardware implementation and software emulation. Either you have the exact hardware needed to run previous generation games, or you’re using the full power of the new hardware to emulate the previous generation’s software.

The best way to add backward compatibility to a console is to include the important pieces of the previous generation machine’s guts, like the CPU, GPU, and sound chips. For example, the Wii was able to play GameCube games because it was essentially a more powerful version of the GameCube. The PlayStation 2 also had the original PSOne chipset built in.

The other way, emulation, is a little trickier, and there are two different ways to make things work.


Dynamic recompilation ensures the most compatibility. This process takes code that has been written for one chip and, as the code goes through the CPU, translates it into code that the native hardware can interpret. This method may give hardware the best way to emulate software, but you need really strong hardware in order for dynamic recompiling to reproduce a 1:1 experience performance-wise.

Another way to emulate software is to add another layer of software that is written to mimic the hardware a code has been written for. This is the most common form of emulation because it doesn’t drastically affect a game’s performance. A good example of this is Microsoft’s approach to emulating Xbox games for the Xbox 360; individual emulation software was written for each compatible game. That’s the slight drawback: one emulation software can’t be created for multiple titles, so the code has to be created separately for each game needing compatibility. The downloadable PSOne games Sony has released for PS3 and Vita come with emulation code tailored to that specific game, which is why we haven’t seen every PSOne Classic released at once for any of the newer consoles. This is also how Nintendo is handling game releases for the Wii U Virtual Console.

For the Xbox 360, some games had additional compatibility updates to fix problems, but not all of them received these patches. Many Xbox games still have problems running on the 360, compatible or not.

The PS2 had a more powerful graphics system than its predecessor that could do parallel processing. When running a PSOne game on PS2, the timing between the hardware’s parallel processing and the running software had to be exactly right, or the game would break. Later, slimmer PS2s used software emulation for PSOne games, and as a result only supported certain titles.

What do Microsoft and Sony have to say now?

Last fall, Sony’s vice president of Sony Network Entertainment Eric Lempel stated in an interview with Game Informer that PlayStation Now could see the addition of PS4, PS2 and PSOne games in the future.

“In our plans going forward we’re looking at everything so there’s the real possibility that you’ll see PlayStation 1, PlayStation 2, and PlayStation 4 titles available,” he said. “Right now it’s just PlayStation 3, but these are all options for the future.”

Around the same time, head of Xbox Phil Spencer said Microsoft have heard fans’ cries for backward compatibility, and that something was in the works for Xbox One.

“Back compat is always a hot topic at the turn of a generation, and I get why, especially on [Xbox 360] so many people bought so much digital content and it means that a lot of us, we’re holding on to our 360s,” Spencer said. “I get the question. I totally respect the question. There’s nothing I can say about it right now, but I’ll just say ‘I hear you.’ I definitely hear you and I’ll continue to try to work to build something that can help people out.”

We reached out to Sony and Microsoft for comment on their plans to bring backward compatibility to current consoles. However, neither company could share any information at this time, other than reiterations of what we already know. A representation from Sony said the company’s long-term goals for PlayStation Now include bringing PS1 and PS2 games to service, but for now they are focused on PS3.

So this is where we are today: current consoles are not backward compatible, but with the recent rise in re-releases and remasters of previous generation games, we technically can play older games on newer consoles. The downside of this is the cost, as all of these remasters require an additional purpose. Moving forward, it seems that this is the likeliest way publishers will ensure we’ll be able to play their older games for years to come.

Leave a Reply