Reading Paths

Ports & Emulators

What does it take to bring a game from an old platform into a modern browser?

Explore the differences between ports, emulators, and recreations, including practical examples of hardware simulation, browser integration, graphics translation, and compatibility.

Follow a button press

Say you press Jump at the edge of a platform. In a port, the browser reports the input and the adapted game reads it on its next update. Original code may still handle collision and movement, while new or translated code passes the result to a browser graphics API.

In an emulator, the same action becomes a button on a virtual controller. The original program reads the emulated device and issues the drawing commands it was built to use. The emulator translates the behavior of those commands into an image the browser can present.

Where the work happens

A port needs an implementation of the services the program expects, such as file access and a main loop that yields to the browser. For a console emulator, the hard work often includes keeping the original components in sync. A timing difference can affect one game even when others on the same console appear to work.

A recreation is another approach. A developer can write a new implementation from the game's documented format or observed behavior. Some recreations read assets supplied by the player. The project's documentation should make clear which parts of the original are reused and what files are required.

What a game listing can tell you

Look for the name of the engine or emulation core, game version, controller support, and where saves are stored. That information helps you compare two playable editions of the same title.