For 1080p 60FPS cloud gaming, start with a stable stream in the 15 to 25 Mbps range, then adjust in small steps. Published provider requirements are higher than that because they describe the internet connection you need, not the video bitrate of the stream. Stable latency and low packet loss matter more than the biggest number.
Published by SensePC, which sells cloud gaming PCs. The 15 to 25 Mbps range is a practical starting rule of thumb, not a SensePC measurement. Provider figures below are quoted from their published requirements and should be re-checked before you rely on them.
Quick answer
| Question | Short answer |
|---|---|
| Starting bitrate for 1080p 60FPS | 15 to 25 Mbps, if your client lets you set one |
| Unstable stream? | Try 10 to 15 Mbps before raising anything |
| How much connection headroom? | Keep the stream well below your stable download speed (roughly half is a safe rule; Boosteroid advises about 30% below) |
| Data used at 25 Mbps | About 11.25 GB per hour, before overhead |
| What fixes stutter? | Wired Ethernet or strong 5 GHz Wi-Fi, a closer region, less competing traffic |
| What bitrate cannot fix | Low in-game FPS, a distant region, packet loss |
What bitrate is, and why it is not your internet speed
Bitrate is how much video data the stream uses each second, measured in Mbps (megabits per second). Internet speed is the most your connection can carry. A cloud gaming stream uses only part of it.
This distinction explains a common complaint: a fast speed test, yet a blurry or stuttering game. A speed test measures a short burst. It does not show jitter, packet loss, Wi-Fi interference, or other people using the connection. Mbps also means megabits, not megabytes, and mixing them up makes numbers eight times too big or small.
Start with a realistic 1080p 60FPS range
A practical starting point is 15 to 25 Mbps. Move toward 25 to 35 Mbps only if your connection is consistently stable and you play visually dense games such as open-world titles, where grass, rain, smoke and fast camera movement are harder to compress. If the stream freezes or input feels delayed, try 10 to 15 Mbps. A stable 15 Mbps stream usually feels better than a 35 Mbps stream that keeps hitting network limits.
What providers publish
Provider requirements describe the connection, not the exact stream bitrate. Per the research notes for this post:
| Service | Published figure for 1080p 60FPS | Note |
|---|---|---|
| NVIDIA GeForce NOW | 25 Mbps | Internet requirement. Also recommends wired Ethernet or 5 GHz Wi-Fi and lower latency for the best experience |
| Boosteroid | 24 Mbps minimum, 35 Mbps recommended (H.264) | Advises keeping bitrate about 30% below your connection speed |
Verify both against each provider's current requirements page before publishing. Figures change.
Step-by-step: match bitrate to your bandwidth
- Measure at your usual play time. Run speed tests in the evening if that is when you play. Note both download and upload.
- Check the service's published requirement for 1080p 60FPS.
- Leave headroom. Do not set the stream equal to your test result. Roughly half of stable download speed is a safe target. For example, a stable 50 Mbps connection suits a 20 to 25 Mbps stream.
- Fix resolution and frame rate first. Set 1080p and 60 FPS, then change only bitrate.
- Test in a demanding scene. Use fast camera pans, foliage, smoke and dark areas for 10 to 15 minutes, not a quiet menu.
- Adjust in small steps. If the image looks compressed but stable, raise by 3 to 5 Mbps. If you see hitching, delayed input or dropped frames, lower by 5 Mbps.
- Stop when it looks good. Choose the lowest setting that looks good in the games you play.
Important: many cloud services manage bitrate automatically. This guide does not claim that SensePC offers a manual bitrate slider. Where your client exposes no control, apply the same idea through the controls you do have: resolution, frame rate, connection quality, region and streaming mode.
How much data does 1080p 60FPS cloud gaming use?
Data per hour = Mbps ÷ 8 × 3,600 seconds ÷ 1,000. This is the theoretical stream data in decimal gigabytes before network overhead.
| Average stream bitrate | Approximate data per hour |
|---|---|
| 10 Mbps | 4.5 GB |
| 15 Mbps | 6.75 GB |
| 20 Mbps | 9 GB |
| 25 Mbps | 11.25 GB |
| 35 Mbps | 15.75 GB |
Real use varies with the stream's actual average bitrate, scene complexity and overhead. Internet data charges are separate from cloud PC compute and storage charges.
Bitrate vs. latency: which matters more?
They solve different problems.
| Symptom | Likely cause | First thing to try |
|---|---|---|
| Blocky motion, dark scenes banded or blotchy | Not enough bitrate or weaker codec efficiency | Raise bitrate in small steps if the stream is stable |
| Delayed controls | High latency or a distant region | Pick a closer region; use wired Ethernet |
| Periodic freezes or skips | Jitter or packet loss | Test over Ethernet; stop other traffic |
| Smooth stream but low FPS inside the game | The remote PC is rendering slowly | Lower in-game settings |
| Resolution drops suddenly | Stream reducing quality to recover | Lower bitrate; check bandwidth |
Higher bitrate can improve detail but cannot fix a distant server or a bad route. Low latency cannot fix every compression artifact either. Separate game performance from stream performance: bitrate can only deliver the frames the remote PC produces.
Stability before quality
- Use wired Ethernet for the device running the client, or a strong 5 GHz or 6 GHz Wi-Fi connection close to the router. See the Wi-Fi 6 vs. Ethernet guide.
- Avoid crowded 2.4 GHz, which is more prone to jitter.
- Pause large downloads, backups and uploads before a session.
- Use router QoS or traffic prioritization where supported.
- Lower the bitrate in shared homes. A slightly lower, steadier setting beats one that swings between excellent and poor.
Codec and game type
Newer codecs can keep more detail at the same bitrate, but support depends on your client, device, GPU and session setup. Use the best option your service and device support reliably, and do not force a setting that causes compatibility issues.
- Competitive shooters, racing and sports games: choose a moderate, steady bitrate and prioritize responsiveness.
- Slower single-player and visual-heavy games: can justify a higher bitrate if your network allows.
If your connection is unstable
Lowering bitrate is not a failure. For hotel Wi-Fi, shared flats or a laptop far from the router, dropping from 30 to 18 Mbps may remove the spikes. If stability remains poor, reduce resolution before frame rate for fast-input games, or reduce frame rate for slower games. The right trade-off depends on what you play.
SensePC settings that matter
SensePC users can start in the browser and switch to Performance Mode, which uses the native Amazon DCV client on supported Windows and macOS computers. SensePC recommends Performance Mode for latency-sensitive gaming, but results still depend on your network, region, configuration and game. Pick the closest of the 8 regions (SensePC suggests about 500 miles or less for gaming) and use the Session Live panel to watch stream quality, latency, bandwidth and FPS while you play. Test one change at a time. See SensePC cloud gaming PCs and pricing options.
SensePC has not published bitrate or latency benchmarks, so this guide gives none.
Frequently asked questions about 1080p 60FPS cloud gaming bitrate
1. What is the best bitrate for 1080p 60FPS cloud gaming?
A stable 15 to 25 Mbps is a practical starting range, but there is no single best number. The right value depends on the service, codec, game motion and network stability. Provider requirements such as 25 Mbps (NVIDIA) or 35 Mbps recommended (Boosteroid) describe the internet connection, not necessarily the stream bitrate. Adjust in small steps rather than choosing the maximum.
2. How much internet speed do I need for 1080p 60FPS cloud gaming?
Plan for at least the provider's published figure, with headroom. Published figures include 25 Mbps for NVIDIA GeForce NOW and 24 Mbps minimum with 35 Mbps recommended for Boosteroid's H.264 stream. Minimums are the floor, not a comfortable target, so allow for other devices, uploads and household traffic. Test your connection to the service's region, not only a generic speed test.
3. How do I match cloud gaming bitrate to my available bandwidth?
Measure your stable speed, then set the stream well below it. Check the provider's requirement, leave headroom (roughly half is a safe rule; Boosteroid suggests about 30% below), and lower the setting if performance is unstable. Change one setting at a time and retest in a demanding scene. If no bitrate control exists, use resolution, frame rate and region instead.
4. How much data does 1080p 60FPS cloud gaming use per hour?
At a sustained 25 Mbps, about 11.25 GB per hour before overhead. The formula is Mbps ÷ 8 × 3,600 ÷ 1,000. At 15 Mbps it is about 6.75 GB. Real use varies with variable bitrate, scene complexity and overhead.
5. Does a higher cloud gaming bitrate always improve image quality?
No. Gains diminish once the image is already clear, and extra bandwidth cannot fix poor rendering, a wrong resolution or an unstable network. Codec efficiency also matters. The provider may also manage bitrate automatically.
6. Which codec is best for cloud gaming: H.264, HEVC or AV1?
Newer codecs such as HEVC and AV1 can offer better compression efficiency, but results depend on the implementation and content. Hardware decoding support, device compatibility and processing overhead matter, and users often cannot choose manually. Confirm which codecs your service and device support before relying on one.
7. Why does cloud gaming look blurry even with fast internet?
Because compression, not speed, usually limits detail. Fast camera movement, smoke and dark scenes expose compression artifacts, and the stream may lower quality automatically. Check the stream's actual resolution, your display scaling and your in-game resolution. A low in-game render resolution looks blurry for a different reason than stream compression.
8. Should I lower bitrate or resolution when my connection is unstable?
Lower bitrate first if bandwidth is the problem and your client allows it. Lowering resolution reduces the visual information to encode, which helps when bandwidth is tight. Neither fixes packet loss or a poor route. Change one setting at a time and compare.
9. How can I reduce stuttering when playing cloud games at 1080p 60FPS?
Use wired Ethernet or a strong 5 GHz connection, close bandwidth-heavy apps and retest. Stutter often comes from jitter, packet loss or congestion rather than low bandwidth. First check whether the game itself is below 60 FPS on the remote PC. On SensePC, try Performance Mode on a supported computer, which can help responsiveness but cannot remove every network problem.
10. What matters more for cloud gaming: bitrate or latency?
It depends on the symptom. Bitrate affects image detail. Latency affects how quickly controls respond. High bitrate cannot fix a distant server, and low latency cannot fix compression artifacts. NVIDIA publishes latency guidance for GeForce NOW, but those values are not universal limits for every cloud PC.
11. How do packet loss and jitter affect cloud gaming quality?
They disrupt a real-time stream even when speed looks fine. Packet loss means data is missing and must be skipped or resent. Jitter is variation in how long packets take. Symptoms include freezes, skipped frames and inconsistent controls. Test over Ethernet, check router conditions, repeat at different times, and contact your ISP if the problem persists.
12. Is Ethernet better than 5 GHz Wi-Fi for 1080p 60FPS cloud gaming?
Usually yes, because a cable gives more consistent latency and avoids interference. Both NVIDIA and Boosteroid recommend Ethernet or 5 GHz Wi-Fi. A strong 5 GHz connection near the router can work well, but a faster Wi-Fi link does not automatically mean lower latency. Compare the two with the same game scene and the Session Live panel or your client's stats.
13. How can I optimize cloud gaming when other people use my internet connection?
Reduce competing traffic and leave headroom. Pause large downloads and uploads, schedule backups outside play time, and use router QoS where available. Test at different times to find congestion. A faster plan can help, but it will not fix every latency or routing issue.
14. How do I choose the right streaming settings for a rented cloud gaming PC?
Separate remote-PC hardware from local streaming settings. Check GPU, CPU, memory and the game's requirements, then choose a nearby region and a stable connection. Compare browser access with a native client where available. Bitrate controls vary by provider. Before paying, test game compatibility and connection quality. SensePC offers configurable cloud gaming PCs with browser access and Performance Mode, billed hourly, daily or monthly. See pricing options.
