BRYME TECH
SEPTEMBER 2026 · THE TOOL DESKPractical technology. No theatre.
THE BRYME

First-hand · verified against the real thing

How many hours of video fit in a gigabyte: the streaming numbers the services publish

In one line: The SD/HD/4K data ranges as the providers themselves state them, the quality setting that is the whole steering wheel, and the app's hidden habits.

The plan-reading page taught households to read the five numbers of a bundle; this page supplies the multiplier that turns those into hours - because 'how long will this data last' is decided not by the phone or the network but by a quality menu most people have never opened. The honest service numbers are published, boring and stable, and knowing them converts the month's data from a mystery into a budget.

The ranges, as the platforms state them

  • Standard definition: the streaming services' own help pages put a typical hour in the few-hundred-megabyte range - the rough arithmetic the desk uses is 'several hours per gigabyte', which is why the mobile plan's daily video habit is survivable at SD on even a modest bundle.
  • High definition: the same published figures put HD at roughly a gigabyte to a few gigabytes an hour depending on the app and the scene - fast motion (the football, the action film) costs more than a talk show because there is more change to compress, which is the entire explanation when the match 'eats the data' faster than the podcast did.
  • 4K/UHD: the published top-tier ranges run several gigabytes per hour and up - at which point a single movie can cost the whole month of a budget bundle, which is why the desk treats 4K as a wifi-only luxury on metered connections, not a default.

The exact figure for your app is on your app's own support page (they all publish it in megabytes-per-hour phrasing) - this page deliberately prints ranges rather than a table because codecs improve and tiers change, and a stale number here is worse than a live one there.

The steering wheel: the quality setting

Every major app has a data-saver or quality menu (the phone's settings on some, the account page on others) with exactly the positions that matter: auto, the capped lower tier, and the unrestricted top tier. The desk's practical frame: auto is the expensive choice - it optimizes for picture, not for your plan, and it is why the metered household that 'barely watched anything' finds the month spent. Capping at the SD/medium tier is not a downgrade the commute will notice on a six-inch screen; the difference shows on the television, which is precisely the place to save the HD figures for the wifi hour. The second setting people forget is downloads: pre-caching a film or a playlist on the office's or home's wifi is the free upgrade to every evening, and the apps all carry it in plain sight - the data math that matters is 'what downloaded it', not 'what streamed it'.

The hidden taps, so the numbers above are honest

Autoplay (trails and feeds rolling data at full quality while you scroll) lives in settings and defaults to generous; background app updates on mobile data belong in the phone's OS switch; cloud-synced photo libraries are the quiet gigabyte-haul the backup page already covered - the sync that uploads the year of photos on mobile data does it during the match you are watching, and the phone's own data meter reports both under 'system'. The monthly audit is five minutes in that same meter: the app-by-app ledger the phone keeps - the usage that surprises everyone is rarely the video app.

The verdict, as a rule

Learn your apps' published hours-per-gigabyte once; cap the commute tier, save the HD for the television and the wifi window; download ahead when you have the chance; and let the phone's own data meter, not the advertisement, tell you what the month actually cost. The bundle is finite in a way the plan-reading page already argued; the quality menu is the faucet - the households that survive the month on the same data as the ones that do not are separated by one setting three menus deep.

Next

Related on this desk.