What cloud gaming actually is
Cloud gaming means the game never runs on your device. It runs on a server — a datacenter rack with a strong GPU, or your own console in the living room — and what reaches your screen is a compressed video feed, updated sixty times a second. Your inputs travel the other way: every button press and stick movement is sent upstream, applied to the game on the server, and the result comes back down as new frames. Your laptop, tablet, or TV is a thin client. All the heavy lifting happens somewhere else.
Most services fall into one of three models, and the differences matter:
- Datacenter streaming with a subscription catalog. You pay a recurring fee and play from a rotating library, the way video streaming services rotate films. Titles can leave the catalog.
- Datacenter streaming of your own library. You buy games on a regular storefront and the service streams them to you from its own hardware. Ownership rules are set by the storefront; streaming is the delivery method.
- Home streaming. Your own console or PC renders the game and sends it across your local network to another screen. Latency is usually far lower than datacenter streaming because the signal never leaves the house, but the host machine still needs the horsepower.
In all three cases you are really renting three things: a graphics card somewhere else, a video encoder, and a network path between you. Everything about the experience — good or bad — follows from those three rentals.
Where the milliseconds go
Latency is the whole ballgame, so it is worth understanding exactly where it accumulates. On a local PC, the path from pressing a button to seeing the result — input to photon — takes roughly 20 to 40 milliseconds: input reads, simulation, rendering, and the display's own scan-out. Cloud gaming adds several stages on top:
- Input upload — your button press travels to the datacenter. Distance sets the floor: nearby regions add a few milliseconds, distant ones 30 or more.
- Server-side render and encode — the server renders the frame, then a hardware video encoder compresses it in real time, typically single-digit milliseconds.
- Network transit — the compressed frame travels to you. This is usually the largest and most variable component; it depends on routing, congestion, and your connection's stability, not just raw speed.
- Client decode — your device decompresses the frame, again single-digit milliseconds on modern hardware.
- The normal display chain — the same scan-out and processing a local game would have.
A well-placed session on a good connection typically lands 20 to 40 milliseconds above local play. A distant region or a congested evening can add 80 to 150. That spread is why the same service can feel flawless one night and unplayable the next.
How much of this matters depends entirely on the game. Slow-paced genres — turn-based strategy, RPGs, adventure and puzzle games, most sims — absorb 50 or 100 milliseconds without the player noticing anything but a slightly soft camera. Precision genres absorb nothing: in competitive shooters, fighting games, and rhythm games, 50 milliseconds is the difference between hitting your shot and watching it whiff. The general rule: the faster the camera and the tighter the timing window, the more cloud latency costs you.
One more physical fact worth internalizing: the region your session runs in is usually assigned automatically from your location, and you cannot tune your way past the speed of light. If the nearest datacenter region is 2,000 kilometers away, no router setting will recover that round trip. Distance is a fixed cost you accept or avoid.
Compression, bitrates, and what they do to the picture
Games are the hardest thing a video codec can be asked to compress. Film has motion blur, controlled lighting, and frame-to-frame similarity; a game at 60 fps redraws nearly every pixel every frame — grass, particles, rain, screen shake — and much of that detail is essentially random noise to an encoder. This is why cloud gaming bitrates dwarf film streaming: a 4K film might need 15 to 25 megabits per second, while a 4K game stream wants roughly double that to look clean.
Approximate figures for typical service tiers:
| Stream quality | Typical bitrate | Data used per hour |
|---|---|---|
| 1080p, 60 fps | 10–25 Mbps | about 4.5–11 GB |
| 1440p, 60 fps | 25–40 Mbps | about 11–18 GB |
| 4K, 60 fps | 35–50 Mbps | about 16–22 GB |
Two consequences follow. First, data caps are a real constraint: four evening sessions of 4K streaming can consume most of a 250 GB monthly cap. Second, the compression is adaptive. When the network wobbles, the encoder does not fail — it degrades. Bitrate drops, and the picture shows it: blocky patches during particle-heavy explosions, color banding in dark scenes, smeared detail during fast pans. Notice the ordering: quality decays before latency does. The service hides connection trouble from the frame rate first and from your inputs last, which is why a session can look merely "soft" while your aim has quietly gotten worse.
The connection that matters: stability beats bandwidth
Bandwidth is the easy part. Every service's requirements — 15, 25, 35 megabits — are numbers almost any modern connection clears. What actually separates a good cloud gaming connection from a bad one is stability: jitter (variation in packet arrival time), packet loss, and congestion behavior.
- Use ethernet whenever you can. Wi-Fi adds contention from every other device in the house, interference from neighbors and appliances, and retransmission delays. A controller-length ethernet cable to the router is the single cheapest upgrade to cloud gaming quality. If Wi-Fi is unavoidable, use the 5 GHz band at close range.
- Watch for bufferbloat. When someone else's upload saturates the line, your inputs and their acknowledgments queue behind bulk traffic and latency multiplies. This is fixable at the router with SQM-style queue management.
- Respect congestion hours. ISP networks are shared. The same session that is flawless at 10 a.m. can fall apart at 9 p.m. when the neighborhood streams. If your play hours are peak hours, judge the service during peak hours.
- Treat mobile connections as variable. 5G home internet can be excellent or unusable depending on cell congestion; a phone hotspot works but rate-adapts hard. Neither is a stable baseline.
The honest test is not the service's built-in speed check. It is two hours of a demanding free-tier game, wired, at your real play time, watching for both artifacts and input feel.
What you still need, and what you never install
Cloud gaming removes the graphics card requirement, not the system requirements. What you still need: a stable connection, a display, and a controller — and the display matters more than people expect, because a TV in "vivid" mode with heavy processing can add as much input lag as the streaming path itself. Enable your display's game mode.
What disappears is equally concrete: there are no 100 GB downloads, no patch queues, no storage juggling. The server installs and patches everything. The tradeoffs sit on the same shelf:
- Library access depends on the model. Subscription catalogs rotate, and a title leaving takes your save progress with it unless the save also lives in a storefront cloud you control. Bring-your-own-library services stream what you own, but ownership disputes belong to the storefront, not the streaming platform.
- Cheaper tiers come with strings. Session length limits, queue waits at peak, and weaker virtual GPUs are how the tier structure pays for the datacenter. Premium tiers buy stronger hardware, ray tracing, and higher resolutions.
- No local files means no local modding. Single-player modding, community patches, and tweaks that assume access to the install directory are off the table on datacenter streams.
When streaming is the right call
Cloud gaming earns its keep in specific situations, and it is worth being honest about which ones apply to you:
- You want to play demanding games without buying hardware. A several-hundred-dollar GPU decision can wait while you test whether a monthly fee covers your actual usage.
- You play across many screens. TV, tablet, a work laptop, a phone in a hotel — no local install can follow you that way.
- Your library is locked behind downloads. A 130 GB release becomes playable in seconds instead of an overnight download, and patches happen whether you are there or not.
- Your hardware is below the game's requirements but your connection is excellent. A premium-tier stream can run max settings better than a mid-range PC can.
- Your line is uncapped. On unlimited fiber, the data usage table above stops mattering and the math tilts further toward streaming.
When it is not
- You play competitively. Every millisecond of the round trip is a handicap in ranked shooters and fighting games, and none of it is tunable away.
- Your connection is capped, shared, or unstable. Data caps make 4K streaming expensive, and an unreliable line turns every session into a lottery.
- You play offline at all. Flights, rural connections, outages — a streamed library is unreachable exactly when you have time to play.
- You already own capable hardware. For you, streaming adds latency and a subscription fee in exchange for nothing.
If you want to go deeper on the connection side, 365Finds' network guides cover router buffering, packet loss versus jitter, and Wi-Fi versus wired trade-offs in detail.