Streaming video is the single largest consumer of mobile data for most people, and the figures involved are large enough that one weekend of viewing can decide which cost tier a monthly bill lands in. On a usage-based tariff such as the one offered by https://naked.net, where the price steps up at defined thresholds, knowing the hourly consumption of a streaming app is not trivia but budgeting. The numbers vary by a factor of twenty between the lowest and highest quality settings, and the difference is entirely under the viewer's control.
Netflix publishes data usage by quality setting rather than by resolution alone, because the two are not identical. The setting determines the bitrate ceiling; the actual bitrate varies with scene complexity.
| Quality setting | Typical resolution | Data per hour | Hours per 5 GB | Hours per 20 GB |
|---|---|---|---|---|
| Low or Save Data | Up to 480p | About 0.3 GB | About 16 | About 66 |
| Medium | Up to 720p | About 0.7 GB | About 7 | About 28 |
| High, standard definition | 480p to 576p | About 1 GB | 5 | 20 |
| High, full high definition | 1080p | About 3 GB | About 1.6 | About 6.6 |
| High, ultra high definition | 2160p with HDR | About 7 GB | Under 1 | About 2.8 |
| Automatic on mobile data | Adaptive | Roughly 0.25 to 0.6 GB | 8 to 20 | 33 to 80 |
The practical reading of this table is the jump between rows four and five. Moving from 1080p to 4K roughly doubles consumption while the visual gain on a phone screen is close to zero. On a six-inch display held at arm's length, most viewers cannot distinguish 1080p from 4K at all, and many cannot distinguish 720p from 1080p.
Three factors move the actual figure.
Scene complexity. Modern codecs allocate bits where they are needed. A static dialogue scene in a dim room consumes a fraction of what a snow-covered action sequence does. Across a full film these average out, but a single hour of a visually busy title can exceed the published figure by 30 percent.
Codec. Netflix serves AV1 to devices that support it, and falls back to HEVC or H.264 elsewhere. AV1 delivers comparable quality at roughly 20 to 30 percent lower bitrate. An older phone may therefore consume noticeably more data for the same title at the same resolution.
Adaptive bitrate. The player continuously measures throughput and steps the quality up or down. On a congested cell, quality drops and so does consumption. On a strong connection with the setting on automatic, the player will climb to the highest level the setting permits.
Netflix is not unusual. The pattern holds across video platforms, and the outliers are worth knowing.
| Service or activity | Data per hour | Note |
|---|---|---|
| YouTube at 1080p | About 1.5 to 2.7 GB | Varies strongly with frame rate; 60 fps costs considerably more |
| YouTube at 480p | About 0.5 GB | Adequate on a phone screen |
| Short-form vertical video feeds | About 0.8 to 1.5 GB | Autoplay and preloading inflate this well beyond expectation |
| Music streaming at high quality | About 0.07 to 0.15 GB | Lossless tiers reach 0.5 GB and above |
| Video call, one to one | About 0.5 to 1.5 GB | Group calls scale with participant count |
| Voice call over an app | About 0.03 GB | Negligible against any allowance |
| Turn-by-turn navigation | About 0.005 to 0.01 GB | Offline maps reduce this to near zero |
| Social feed browsing with autoplay | About 0.15 to 0.4 GB | Disabling autoplay cuts this by more than half |
Two entries surprise people. Navigation, widely blamed for large bills, is among the cheapest activities on the list. Short-form vertical video, treated as a casual filler activity, is among the most expensive, because the feed downloads several clips ahead of the one being watched and discards what is skipped.
Downloading an episode over Wi-Fi and watching it offline uses zero mobile data. Downloading over mobile data uses the same volume as streaming the same title at the same quality, with one difference: a download completes once, while a rewatch streams again.
For anyone who rewatches, or who watches the same title across a commute in several sessions, downloading over Wi-Fi is the single largest saving available. Netflix offers two download qualities, standard and high, roughly corresponding to 0.5 GB and 1 GB per hour for a typical episode.
Downloads expire. Most titles remain playable for a limited period after download and a shorter one after playback begins. That constrains how far ahead a trip can be prepared.
A worked example for someone deciding whether their viewing habits fit inside a given cost tier:
- Count actual viewing hours on mobile data, not total viewing. Time spent watching at home on Wi-Fi does not count. A typical commuter watches on mobile only during travel, perhaps 45 minutes each way, four days a week: about 24 hours a month.
- Multiply by the per-hour figure for the chosen setting. At Medium quality, 24 hours is roughly 17 GB. At Save Data, the same 24 hours is roughly 7 GB.
- Add the other traffic. Messaging, email, navigation, and social browsing for a moderate user total roughly 3 to 5 GB a month.
- Compare the total against the tier boundaries of the tariff. With naked.net, the relevant thresholds are 250 MB, 5 GB, 20 GB, 50 GB, 70 GB, 100 GB, and 200 GB. Landing at 22 GB rather than 19 GB costs five euros more for the month.
- Decide which lever to pull if the figure sits just above a boundary. Dropping Netflix from Medium to Save Data on the commute removes about 10 GB, which moves the example from 22 GB down to 12 GB and back below the 20 GB line.
- Set the app limit rather than relying on discipline. Netflix has a per-profile mobile data setting with an explicit Save Data option and a Wi-Fi-only option. Configure it once instead of remembering each session.
- Verify after one full month by comparing the operator's usage figure against the estimate. Device counters and network counters differ by a few percent because the network also counts protocol overhead.
Step five is where the money is. On a tiered tariff, a small behavioural change near a boundary is worth far more than the same change made deep inside a tier, where extra consumption is free until the next threshold.
- Set Netflix mobile data usage to Save Data or Wi-Fi only, per profile. The setting does not sync across profiles on the same account.
- Disable autoplay of previews. The browsing interface plays trailers automatically, consuming data before anything is chosen.
- Turn off autoplay for the next episode. It is the main cause of overnight consumption when a viewer falls asleep.
- Download over Wi-Fi in standard quality rather than high, unless the content will be viewed on a tablet.
- Restrict background app refresh for streaming apps, which fetch artwork and recommendation data periodically.
- Cap YouTube quality manually. The app defaults to automatic and will select 1080p at 60 frames per second on a good connection.
Yes, roughly double, but the visible benefit on a phone screen is minimal. 4K is also restricted to specific plans and devices. On mobile data, there is no practical reason to allow it.
Spatial and high-bitrate audio tracks add a modest amount, typically under 10 percent of the total for a video stream. Compared with the difference between video quality settings, it is not the lever to pull.
Playback of a downloaded title uses no data, but the app still communicates for licence validation, progress synchronisation, and recommendations. The volume is small. Larger unexpected usage usually comes from the app fetching a fresh stream because a download expired.
A two-hour film at 1080p is roughly 6 GB, at 720p roughly 1.4 GB, and at Save Data quality roughly 0.6 GB. The same film in 4K approaches 14 GB, which exceeds many monthly allowances on its own.
Pausing stops new segment requests within a few seconds, but the player has already buffered ahead, typically 30 to 120 seconds of content. That buffered data is counted whether or not it is watched.
The file is the same size at the same quality. The difference is indirect: a faster connection lets adaptive bitrate climb to a higher quality level than a congested LTE cell would sustain, so consumption rises. Fixing the quality setting manually removes this effect.
Streaming data usage is not a fixed property of an app but a consequence of one setting. The same hour of viewing costs 0.3 GB or 7 GB depending on a menu choice that most people never open.
On a plan with fixed monthly cost tiers, that choice translates directly into money. Twenty-four hours of commute viewing is 7 GB at Save Data and 17 GB at Medium, and those two figures sit in different price brackets on most tiered tariffs.
The reliable approach is to set the app limit once, download over Wi-Fi whatever is planned in advance, and check the operator's usage figure after the first full month against your own estimate. After that, the monthly bill stops being a surprise and becomes a number you chose.