How much data YouTube uses per hour

YouTube uses roughly 0.3 GB an hour at 360p, roughly 1 GB an hour at 720p and roughly 2 GB an hour at 1080p — which means the same clip, at the same length, can cost nearly seven times as much without you noticing anything different. Every number here is a planning estimate rather than a measurement from your handset, and it shifts with the kind of footage too: a talking head costs less than a travel video where the camera never stops moving.

The thing most people get wrong is assuming they chose the resolution. By default the app chooses it, from the speed it measures at that moment. Land somewhere with a strong signal and it reads that as permission to serve you something sharper, and spends accordingly without asking. That is why a good-signal day can cost more than a sluggish one for exactly the same amount of watching.

Rough figures, quality by quality

Read the table and you can see that the decision that matters happens once — when you choose what to pin the quality at — not each time you choose a video. The gap between 360p and 1080p is the gap between a trip with data left over and a trip that runs dry on day three, and on a six-inch screen the difference your eye notices is far smaller than the difference your plan notices.

Pinning the quality down for good

This is the single highest-value switch on this page. It takes under a minute and it applies to every video you watch for the rest of the trip. The path is the same on iOS and Android, which is a relief, because most apps are not like that.

1. 1Open the settingsTap your profile picture at the top right, choose Settings, then open Video quality preferences.
2. 2Set the mobile-network rowOpen On mobile networks and set it to Data saver if you want the cheapest option. Because the two rows are independent, you can still let it run at higher picture quality whenever you are on Wi-Fi at the hotel.
3. 3Listen audio-only while you moveIf you are using YouTube for podcasts or music, pin it to 144p and put the phone in your pocket. Almost no picture gets pulled down and you are left with roughly 50–100 MB an hour of audio.
4. 4Download on Wi-Fi before you leave the roomIf you have Premium, download the long stuff at the hotel, and in Settings > Downloads switch on Download over Wi-Fi only so the app never finishes a download over mobile data.

Shorts are their own category

Shorts do not always obey the same quality setting as ordinary videos, and because they play end to end with no gaps, their rate looks more like a short-video feed than like YouTube as you知 it — somewhere around 1–1.5 GB an hour. If Data saver is on and the data still seems to vanish, count the minutes you spend in Shorts before you look anywhere else.

• A reminder in Digital Wellbeing or Screen Time does more for your data than any quality setting, because the largest variable is simply how many minutes you watch.
• To avoid Shorts entirely, open videos from your Subscriptions tab or straight from a link rather than scrolling the home feed.
• Turn off Autoplay next video on the player screen so the app does not keep going after you put the phone down and doze off.
• Switch off Background App Refresh for YouTube on iOS, or Background data on Android, to stop it fetching while the app is closed.

How much to set aside for YouTube

It depends what YouTube is for on this trip. If it is background audio on a train or the walk back to the hotel, pin it to 144p and set aside roughly 1 GB for the week. If it is your main evening entertainment, pin it to 360p and set aside roughly 3–4 GB. If you pin nothing and let the app decide, budget at least roughly 10 GB and expect that it may still not be enough.

The most useful thing you can do is convert the gigabytes you have into hours you can actually watch, because "5 GB" tells nobody anything, while "roughly fourteen hours at 360p" tells you immediately whether it covers a seven-day trip.

Wi-Fi versus cellular: does the starting quality really differ

Left to decide for itself, YouTube tends to open a clip at a higher quality on a strong, steady Wi-Fi connection and step down if speed drops, while on cellular it more often starts lower and climbs only if the connection can support it. That is why pinning quality under Settings > Video quality preferences makes such a visible difference on either connection: it removes the ramping-up step that otherwise spends data before you have decided the picture even needs to be that sharp.

Another common misunderstanding is casting to the room television. Cast properly via Chromecast with the TV on the same Wi-Fi, and the television pulls the stream from the internet itself, using not a single bit of your cellular data; the phone is acting only as a remote control. Use screen mirroring instead of a true cast, though, and the phone remains the thing doing the streaming and pushing the picture to the TV, which spends the phone's own data exactly as if you were watching on the handset. The distinction matters most if the room TV cannot join the hotel Wi-Fi and you end up feeding it from a phone hotspot instead.

Common traveller mistakes with YouTube

The single most common mistake is downloading clips for offline viewing and then leaving them too long. Videos downloaded through YouTube Premium expire and need periodic reconnection to renew, so if the app has not been opened with a connection for a while, a download can refuse to play at the exact moment you need it on the train, forcing a live stream instead of the offline viewing you planned.

• Do not leave background play running unattended. Continuing to play while you switch apps or lock the screen is a genuine ongoing stream, not audio quietly paused in the background.
• Scrolling the home feed for a long time without tapping anything still costs data, because every thumbnail has to load to be shown, and some clips autoplay a short preview as you scroll past.
• The comments under a video carry profile pictures and sometimes attached images that need loading too. Scrolling a long comment thread regularly is another slice of data separate from the video itself.
• If signed in on more than one device, check that quality is pinned on each one separately, because Video quality preferences is stored per device, not per account.

Budgeting a realistic day of YouTube while traveling

The per-hour figures mentioned earlier shift a great deal depending on whether you watch one long video continuously or hop between many short ones. An hour spent on a single long video and an hour spent opening a dozen shorter clips back to back do not use the same amount of data, because every time you switch to a new clip it has to start buffering again, unlike a single video that buffers smoothly the whole way through.

Another variable is whether you watch directly on the phone or cast to a TV. As mentioned, Chromecast uses the TV's own connection, so a day spent mostly casting barely touches phone data at all, while a day spent watching directly on the phone accumulates in line with actual viewing hours. This distinction affects the daily total more than changing resolution does.

Because the gap between a light day and a heavy day is this wide, the more workable approach is to decide in advance whether that day will mostly be direct phone viewing or casting, and set the resolution to match that decision, rather than letting the app choose resolution on its own as the day goes along.

If you are not sure how far the real number has drifted from what was expected, both iOS and Android already show data usage broken down per app. On iOS, go to Settings > Cellular and scroll to YouTube; on Android, go to Settings > Network & internet > Data usage. Checking it once mid-trip lets you adjust behavior for the rest of the trip in time, before data runs out faster than planned.

The figure on that screen counts from the last billing cycle, not a single day, so it helps to note it at the start of the trip and check again after a couple of days, giving a real sense of how much YouTube averages per day on this specific trip rather than relying on a generic figure that may not match actual viewing habits.

Turn gigabytes into hours of watching