The basic idea
In cloud gaming, the game does not run on the device in front of you. It runs on a powerful computer in a remote data centre. That computer draws each frame, compresses the picture into video, and sends it over the internet. Your device only decodes and shows the video, and sends back your button presses and movements.
This is why the approach can work on modest hardware such as a basic laptop, a phone, or a small streaming box: the heavy work of running the game and drawing the graphics happens elsewhere. Nothing about the game itself changes. What changes is where it runs.
The loop, step by step
Each moment of play goes through a repeating loop:
- You press a button. Your device records the input.
- The input travels over the internet to the remote machine.
- The game processes it and draws a new frame.
- The frame is encoded into compressed video, using the same family of techniques described in the piece on stream bitrate.
- The video travels back to you.
- Your device decodes and displays it.
All six steps must happen quickly, and then happen again for the next frame, many times a second. A stable result needs the whole loop to stay fast and consistent.
How this differs from watching a stream
The video technology is similar to a broadcast, but the purpose differs. In a broadcast, as explained in the article on game streaming, a delay of several seconds is acceptable because viewers only watch. In cloud gaming, the video is your live view of a game you are controlling, so the delay has to be small enough that controls still feel responsive. That is a much stricter demand, and platforms typically use settings and delivery methods built for low delay instead of the buffering that suits viewing.
Where delay comes from
Delay in cloud play is the sum of several parts: the time to capture input, the trip to the data centre and back, the game’s own processing, encoding, and decoding on your device, plus the display itself. Some of these are small, and the network trip is often the part that varies most.
Key network ideas apply directly:
- Distance. The farther you are from the data centre, the longer the round trip. Services therefore operate many locations, and availability depends on where you live.
- Ping time. The measured round-trip time to a server gives a rough sense of the trip, though it does not capture everything. What ping really measures is a narrower thing than total delay.
- Packet loss and jitter. If data goes missing or arrives unevenly, the picture can stutter or break up, and the system may need to lower quality to recover.
- Wi-Fi. Wireless links add variability, so a wired connection is often steadier.
All of these combine into the input latency you feel. People differ in how sensitive they are to it, and so do games. A slow strategy or turn-based game tolerates delay better than a fast shooter or a game that rewards precise timing.
Bandwidth and quality
Your connection must also carry the video continuously. Higher picture quality needs more data per second, and a connection that cannot sustain it forces the service to lower the quality, producing blur or blocky patches during fast motion. A data cap, if you have one, matters too, since cloud play streams video for as long as you play. Services publish their own recommendations, and these change, so check the current requirements before relying on any figure you have seen elsewhere.
What you gain
- Lower hardware needs. The device in front of you needs only to decode video and accept input.
- Quick starts. There may be no large download or installation, since the game already sits on the remote machine.
- Flexibility. The same game can often be reached from several kinds of devices.
- Access to demanding games. Visual features such as ray tracing may be available without owning hardware that can handle them, depending on the service.
What you give up
- Dependence on the connection. A weak or unstable link directly harms the experience, and without internet you cannot play.
- Added delay. Even a good connection adds some latency compared with playing locally.
- Compressed picture. The image has been through video compression, so it can look slightly softer than a game rendered directly on your own device.
- Limited choice. Services offer particular libraries, and a game you own elsewhere may not be available. Ownership and access rules vary between services.
- Service lifetime. If a service closes or removes a game, you may lose access. This links to wider concerns about game preservation and server shutdowns.
Remote play versus cloud gaming
A related idea is streaming from a machine you own, for example from a console or PC at home to a phone or laptop in another room or elsewhere. The principle is the same, with video sent over a network and controls sent back, but the “remote machine” is yours, not a data centre. Cloud gaming usually means the machine is provided by a service. Home streaming tends to work best on your own local network, where delay is lower.
Is it right for you?
It depends on circumstances more than on technology alone. Cloud play often suits people with a steady, fast wired or strong wireless connection, a nearby service location, and games that do not demand split-second timing. It may suit them less if their connection is variable, or if they care about the sharpest possible picture and the lowest possible delay. A free trial, where one is offered, is a reasonable way to test it on your own network before committing.