How Much Storage Do 1080p, 4K, and 8K Videos Need?

Does Video Resolution Determine File Size?

No. Resolution is one of the factors that influence video storage, but it is not a file-size calculator by itself.

The standard dimensions commonly associated with these labels are:

1080p: 1920 × 1080

4K UHD: 3840 × 2160

8K UHD: 7680 × 4320

Those dimensions are defined in UHDTV standards and documentation. ITU identifies HDTV as 1920 × 1080, 4K UHDTV as 3840 × 2160, and 8K UHDTV as 7680 × 4320.

Because 3840 × 2160 contains four times as many pixels as 1920 × 1080, and 7680 × 4320 contains four times as many pixels as 3840 × 2160, it is reasonable to expect higher-resolution video to contain more visual information per frame.

But encoded file size does not have to scale in the same ratio.

Video codecs compress the picture, and the encoder decides how much data is used to represent it. MDN specifically notes that both resolution and frame rate affect encoded size, but also emphasizes that source content and codec configuration are major factors.

That is why:

4K does not automatically mean 4× the storage of 1080p

and:

8K does not automatically mean 4× the storage of 4K.

Those are pixel-count relationships, not guaranteed file-size relationships.

What Actually Determines Video Storage?

A useful way to think about video storage is:

resolution + bitrate + duration + codec + frame rate + audio + encoding settings → final file size

Each variable contributes differently.

Resolution

Resolution describes the dimensions of each video frame.

A 1080p frame contains fewer pixels than a 4K frame, and a 4K frame contains fewer pixels than an 8K frame.

Higher resolution can require more data because the encoder has more image information to represent. MDN states that higher resolution contributes to larger encoded video sizes, although the exact effect depends on the encoder and configuration.

But resolution alone says nothing about whether a particular video is encoded efficiently or aggressively compressed.

Bitrate

Bitrate tells you how much encoded data is being used over time.

This is one of the most useful numbers when estimating storage.

A video encoded at:

20 Mbps

can require much more storage than one encoded at:

5 Mbps

even when both have the same resolution.

MDN states that higher video bitrates inherently produce larger output files, while quality generally improves with higher bitrate up to the limits of the encoding setup.

Duration

Longer video means more time over which data is stored.

A five-minute file and a two-hour file could use completely different amounts of storage even when their resolution and bitrate are identical.

This is why “How much storage does 4K need?” cannot be answered properly without asking:

“For how long?”

Codec

A codec determines how the video is compressed and represented.

H.264, HEVC/H.265, VP9, and AV1 can produce different file sizes for comparable visual targets because their compression methods and encoding behavior differ.

MDN emphasizes that codecs have different strengths and weaknesses and that output size depends on both the source content and the codec configuration.

AOMedia describes AV1 as a codec designed for high-quality compression with greater efficiency than previous codecs, including high-resolution video. That is a design goal, not a promise that every AV1 file will always be smaller than every H.264, HEVC, or VP9 file.

Frame rate

Frame rate is the number of frames encoded or displayed per second.

All else being reasonably comparable, more frames per second can increase the amount of information the encoder must represent.

MDN explicitly notes that, assuming frame rate is not reduced during encoding, higher frame rates cause larger compressed video sizes. It also notes that motion complexity can make compression less effective.

That is why:

4K at 60 FPS

does not have to be the same size as:

4K at 24 FPS

even if both have the same width and height.

Audio

The final media file can contain audio in addition to the video.

If your video bitrate is:

10 Mbps

and your audio bitrate is:

128 Kbps

the combined media bitrate is approximately:

10.128 Mbps

The audio contribution is relatively small compared with high-bitrate video, but it still adds to the final file size.

This becomes more noticeable when video bitrate is low or when a file contains multiple audio tracks.

How to Calculate Video File Size

The basic bitrate formula

For a constant bitrate or a useful average bitrate estimate:

File size ≈ bitrate × duration

To make the units work:

file size in bytes ≈ bitrate in bits/second × duration in seconds ÷ 8

For decimal storage calculations, the result can then be converted to MB or GB.

This is an estimate, not a guarantee.

A one-hour example

One hour contains:

3,600 seconds

At:

5 Mbps

the calculation is:

5,000,000 × 3,600 ÷ 8

= 2,250,000,000 bytes

≈ 2.25 GB

At:

10 Mbps

the result is approximately:

4.5 GB

At:

20 Mbps

approximately:

9 GB

At:

50 Mbps

approximately:

22.5 GB

At:

100 Mbps

approximately:

45 GB

These numbers are mathematical bitrate examples, not claims that 1080p, 4K, or 8K normally uses those bitrates.

They simply give you a reusable storage-planning method.

Why real files vary from the estimate

Real files can differ because of:

variable bitrate changing scene complexity codec efficiency encoder settings audio multiple streams metadata container overhead variable frame rate differences between reported and actual source sizes

For a VBR file, the bitrate can change throughout the video rather than remaining at one fixed rate.

So the formula becomes especially useful when you know an average bitrate rather than treating it as an exact constant.

How Much Storage Does 1080p Video Need?

There is no single 1080p file size.

The correct answer is:

whatever the bitrate and duration require.

Short 1080p videos

Suppose a 1080p video happens to average:

5 Mbps

A ten-minute segment would require approximately:

5 × 600 ÷ 8

= 375 MB

before adding any separate audio bitrate and small overhead differences.

Now imagine another 1080p video averaging:

20 Mbps

The same ten minutes would require approximately:

1.5 GB

Again, both are 1080p.

The resolution did not change.

The storage requirement did.

One-hour 1080p video

At the purely mathematical examples above:

5 Mbps → about 2.25 GB/hour

10 Mbps → about 4.5 GB/hour

20 Mbps → about 9 GB/hour

These are bitrate-based examples.

They should not be described as universal 1080p storage requirements.

Long 1080p videos

Duration magnifies the difference.

A two-hour video at 10 Mbps is approximately:

9 GB

while four hours at the same bitrate becomes approximately:

18 GB

The resolution is unchanged.

Duration doubled.

Storage doubled.

That relationship is why duration deserves as much attention as resolution when planning a video library.

How Much Storage Does 4K Video Need?

4K also has no fixed storage requirement.

The same 4K resolution can be encoded at very different bitrates and with very different codecs.

Short 4K videos

Consider two purely illustrative one-minute 4K examples.

At:

10 Mbps

the video payload is approximately:

75 MB

At:

50 Mbps

the payload is approximately:

375 MB

Same resolution.

Five-times the bitrate.

Five-times the approximate payload size.

This is exactly why “4K = X GB per hour” is not a reliable universal rule.

One-hour 4K video

Using the same mathematical examples:

10 Mbps → about 4.5 GB/hour

20 Mbps → about 9 GB/hour

50 Mbps → about 22.5 GB/hour

100 Mbps → about 45 GB/hour

A 4K file at 10 Mbps can therefore be smaller than another 1080p file encoded at 20 Mbps.

That may seem surprising until you remember that bitrate controls the encoded data rate.

Long 4K videos

Long-form 4K accumulates storage quickly when bitrate is high.

For example:

50 Mbps × 2 hours

≈ 45 GB

That is a substantial amount of storage from a single video.

This does not mean all two-hour 4K videos will be 45 GB.

It means a 50 Mbps two-hour file mathematically contains about that much video payload before additional overhead and separate audio.

How Much Storage Does 8K Video Need?

8K needs the same kind of analysis.

The fact that 8K contains four times as many pixels per frame as 4K does not mean every 8K file uses exactly four times the storage. ITU defines the spatial resolutions, while the actual encoded size depends on compression and other parameters.

Short 8K videos

Imagine two illustrative 8K files:

20 Mbps

and:

100 Mbps

For one hour, those would mathematically correspond to:

9 GB

and:

45 GB

respectively.

Again, these are not “normal 8K file sizes.”

They are examples of how bitrate determines storage.

One-hour 8K video

The best question is not:

“How big is an 8K file?”

It is:

“What bitrate is the 8K file using, and how long is it?”

Once you know those two numbers, you have a much stronger estimate.

Long 8K videos

Large 8K collections can consume storage quickly because high resolution can be paired with high bitrate, high frame rate, demanding quality settings, or less aggressive compression.

Professional recording workflows can be especially storage-intensive.

The important point is that 8K itself is not the storage multiplier.

The encoded data rate is.

1080p vs 4K vs 8K Storage Comparison

The cleanest comparison is to use the same bitrate and duration.

For one hour at:

10 Mbps

all three hypothetical videos would have roughly:

4.5 GB of video payload

if the bitrate is truly the same.

That does not mean they would look equally good.

The 8K file would contain far more pixels per frame, so achieving useful quality at only 10 Mbps could require a very different compression strategy and may produce a very different visual result.

Now reverse the example.

Suppose:

1080p = 5 Mbps

4K = 10 Mbps

8K = 50 Mbps

Then the one-hour payloads are approximately:

1080p → 2.25 GB

4K → 4.5 GB

8K → 22.5 GB

This is a much more useful way to compare storage than assigning a fixed number of gigabytes to each resolution.

Why Two Videos With the Same Resolution Can Have Very Different File Sizes

This is one of the most important ideas in video storage planning.

Different bitrates

This is the biggest obvious difference.

Two 4K files at 10 Mbps and 50 Mbps cannot have the same one-hour payload size.

Different codecs

H.264, HEVC/H.265, VP9, and AV1 use different compression technologies.

MDN notes that codec algorithms and configuration can produce different output quality and size.

HEVC is designed to provide greater compression efficiency than H.264 in relevant use cases, while AV1 was designed with greater efficiency than previous codecs as one of its goals. But neither statement means a particular file will always be smaller in every real-world comparison.

Different frame rates

A 4K video at 60 FPS represents more frames per second than a 4K video at 24 FPS.

MDN notes that higher frame rate generally increases compressed size when it is not reduced during encoding.

Different durations

An hour of 4K and ten minutes of 4K obviously do not require the same storage.

Different quality settings

Two files can have the same resolution, frame rate, and codec yet use different encoder quality settings.

A higher-quality encode may use more data and produce a larger file.

MDN explicitly describes quality settings as affecting both visual fidelity and encoded size.

Different audio tracks

One video may include:

one stereo audio track

while another may include:

multiple languages multiple audio variants commentary tracks

The video resolution has not changed, but the total media file can become larger.

How Bitrate Changes Video Storage

Bitrate is often the most useful storage-planning number because it directly describes encoded data over time.

Consider a one-hour video:

5 Mbps → 2.25 GB

10 Mbps → 4.5 GB

20 Mbps → 9 GB

50 Mbps → 22.5 GB

100 Mbps → 45 GB

The relationship is nearly linear for constant bitrate calculations.

Double the bitrate for the same duration:

20 Mbps → 40 Mbps

and the video payload approximately doubles.

That makes bitrate a much more useful storage predictor than saying:

“This is 4K.”

Resolution still matters because it influences how much image information has to be encoded and what bitrate may be needed for a desired visual result.

But it does not determine the final number by itself.

How Duration Changes Video Storage

Duration has a direct relationship with encoded data.

At 10 Mbps:

30 minutes → about 2.25 GB

1 hour → about 4.5 GB

2 hours → about 9 GB

4 hours → about 18 GB

This is just the same bitrate formula applied to different durations.

It is also why a long 1080p recording can use more space than a short 4K clip.

For example:

1080p, 20 Mbps, 2 hours

≈ 18 GB

while:

4K, 10 Mbps, 30 minutes

≈ 2.25 GB

There is nothing contradictory about that.

The files have different durations and bitrates.

How Codec Efficiency Changes Video Storage

Codec efficiency changes how effectively the available bitrate is converted into visual quality.

H.264

H.264 is an extremely widely used video codec.

It is supported in many environments and remains a practical format when compatibility matters.

Its wide adoption, however, does not mean that H.264 is always the most storage-efficient option.

MDN lists H.264 as a common web codec and identifies MP4 as a supported container.

H.265 / HEVC

HEVC, also called H.265, was designed to improve compression efficiency compared with earlier standards such as H.264.

That can allow a similar visual target to be represented with less data in suitable encodes.

But the result depends on the encoder, settings, source material, profile, and playback support.

MDN notes both its compression advantage and the compatibility/licensing considerations around HEVC.

VP9

VP9 is an open video codec developed by the WebM Project.

Google's technical documentation describes VP9 as a video compression technology with multiple bitrate modes and support for high-quality and ultra-HD use cases.

Again, there is no rule that:

“VP9 files are always smaller.”

Encoding mode and content still matter.

AV1

AV1 is a newer open codec designed for high compression efficiency.

AOMedia specifically describes AV1 as designed to provide high-quality video compression with greater efficiency than previous codecs and as suitable for high-resolution content such as 4K and 8K.

That makes AV1 attractive for storage and streaming efficiency in compatible workflows.

But “designed for efficiency” should not be turned into “every AV1 file is always smaller than every competing file.”

How Frame Rate Affects Storage

Frame rate is another reason resolution-only calculations fail.

Consider two otherwise comparable videos:

4K at 24 FPS

and:

4K at 60 FPS

The second contains 2.5 times as many displayed frames per second.

That does not mean its final compressed file must be exactly 2.5 times larger.

Modern codecs exploit similarities between frames, and different content can compress differently.

But MDN confirms the general relationship: higher frame rates tend to increase compressed size when the frame rate is retained during encoding.

Fast motion can also make compression more difficult.

MDN notes that greater motion creates larger inter-frame differences and typically makes compression less effective.

So:

resolution + frame rate + motion

can all influence storage.

Does 4K Always Need More Storage Than 1080p?

No.

It is generally true that higher-resolution video can require more data to encode at a comparable visual target.

But a specific 4K file can be smaller than a specific 1080p file.

For example:

1080p at 20 Mbps for 1 hour

≈ 9 GB

4K at 10 Mbps for 1 hour

≈ 4.5 GB

The 4K file is smaller because its encoded bitrate is lower.

That does not mean the 4K image will necessarily look better.

It means:

resolution and storage are related, but bitrate controls how much encoded data is actually being used.

Does 8K Always Need Four Times the Storage of 4K?

No.

8K has four times the pixel count of 4K under the standard 7680 × 4320 and 3840 × 2160 dimensions.

But file size depends on encoded data.

For example:

4K at 50 Mbps for 1 hour

≈ 22.5 GB

8K at 20 Mbps for 1 hour

≈ 9 GB

The 8K file is actually smaller in this mathematical example.

That would not prove that 8K is “more efficient” or “better.”

It simply demonstrates that bitrate and duration determine the amount of encoded data stored.

How Much Free Storage Should You Have Before Downloading a Large Video?

Do not treat the displayed file size as an exact instruction to have exactly that much space available.

A safer principle is:

expected output size + sensible free-space margin

The reason is simple.

The browser, app, operating system, and other background activity may need storage too.

On Windows, Microsoft provides storage tools that show available drive space and recommends checking storage before dealing with low-space conditions. Windows also provides Storage Sense and Cleanup recommendations for managing temporary and unnecessary files.

You do not need a universal “keep exactly 20% free” rule for video downloads.

Instead:

check available space compare it with the expected file size leave room for normal device operation avoid starting a huge download when the target drive is nearly full

For very large 4K or 8K files, it is also worth deciding whether the file actually needs to remain on the internal drive.

MediaFetches Storage and File-Size Limits

The current MediaFetches configuration was reviewed directly from the project files.

There are several important distinctions between the source video's size estimate, the server-side job file, and the final local copy on the user's device.

Maximum individual output

The current/default MediaFetches configuration sets:

2,147,483,648 bytes

which is exactly 2 GiB.

The implementation passes that value to yt-dlp as its maxFilesize setting.

When yt-dlp reports that the source is larger than that configured ceiling, MediaFetches currently surfaces:

“That file is larger than this server allows. Please try a lower quality.”

This is a current/default configuration value, not a permanent promise that every future deployment will have the same limit.

The limit is also enforced through the downloader's maximum-file-size setting rather than by using resolution as a proxy for size.

Configured READY-file storage quota

The current/default configuration is:

8,589,934,592 bytes

which is 8 GiB.

This deserves careful wording.

The actual quota-enforcement function does not simply count every byte in the temporary directory.

It filters for jobs that are:

READY

and have a known:

sizeBytes

It then sums those READY files and, when the configured total is exceeded, removes the oldest READY jobs first until the calculated READY total is back under the configured threshold, with one edge case where a single remaining READY file larger than the quota is not evicted because the loop requires more than one READY job.

So the technically accurate description is:

MediaFetches currently has an 8 GiB configured READY-file quota enforced over completed READY job files.

It should not be described as:

“The server can never use more than 8 GiB.”

Active downloads and intermediate files are handled separately by the job/download process and are not included in that quota calculation.

That distinction matters when discussing storage planning.

Finished-file retention

The current/default finished-job TTL is:

30 minutes

After a job becomes READY, its expiresAt is set to 30 minutes in the future.

The janitor runs every:

5 minutes

and removes expired jobs and their associated files.

The exact moment a file disappears can therefore be later than the theoretical expiration timestamp because cleanup happens during the sweep.

Why resolution alone cannot predict whether a download will fit

MediaFetches itself shows quality options based on the source's reported heights.

Its configured ladder includes:

2160p, 1440p, 1080p, 720p, 480p, 360p, 240p, 144p

and it can also surface non-standard source heights when the extractor reports them.

The important point is that the UI does not turn resolution into a universal file-size formula.

When source metadata contains a usable filesize or filesize_approx, the quality selector can show an approximate size using the ≈ symbol.

For merged video/audio options, the project's estimation logic can combine reported video and audio sizes.

If the source provides no reliable size information, the interface intentionally avoids inventing a number.

That is exactly the right behavior for storage planning: an estimate is useful when the source provides evidence, but a fabricated “4K = X GB” number would be misleading.

One additional MediaFetches accuracy point is important for 8K.

The current homepage describes video saving as going up to 4K, and the primary named quality ladder ends at 2160p. The backend can surface non-standard source heights, but the current interface does not present a dedicated, clearly named 8K product tier. Therefore:

this article's 8K storage examples are general video-storage examples, not a guarantee that every 8K source is selectable through the current MediaFetches interface.

How Much Storage Should You Reserve for a Video Library?

The best way to plan a library is to estimate from your actual content instead of buying storage based on resolution labels alone.

A few short videos

A small collection of short 1080p clips may fit comfortably on modest storage.

The important question is the total duration and average bitrate.

Long 1080p videos

Long recordings can become substantial even at moderate bitrates.

For example:

10 Mbps × 10 hours

would be about:

45 GB

of video payload.

4K video collections

4K collections benefit from planning by average file size.

If ten one-hour videos each average approximately 9 GB, the collection is already around:

90 GB

before considering additional copies or other files.

8K video collections

8K needs especially careful planning because high-resolution workflows can pair large frame sizes with high bitrates.

Do not assume that a single example predicts the entire collection.

Look at the actual bitrate and duration of the content you are collecting.

How to Reduce Storage Without Immediately Deleting Videos Choose a lower resolution when appropriate

If a video will mainly be watched on a smaller screen, you may not need the highest resolution available.

That is a decision about practical use, not a statement that lower resolution is always better.

For a deeper explanation of resolution choices, see our guide to video resolutions.

Choose a suitable quality level

When a source offers several quality options, compare the available resolution and approximate size.

A smaller option may be more practical when the highest-quality version would consume disproportionate storage for your use.

Avoid unnecessary duplicate copies

Two identical 4K files do not give you twice the quality.

They give you twice the storage usage.

Keep duplicates when they serve a purpose such as backup or editing, but remove accidental duplicates.

Move older videos to external storage

For large libraries, an external HDD or SSD can keep your main device from becoming crowded.

The important step is to verify that the copied file exists before deleting your original.

Use cloud storage for selected archives

Cloud storage can make sense for videos that you want available across devices without keeping every archive on the internal drive.

It should be treated as another storage location rather than a magic solution to unlimited storage requirements.

Common Storage Planning Mistakes Assuming every 4K video has the same size

They do not.

Using resolution as a file-size calculator

Resolution describes frame dimensions, not the complete encoded data rate.

Ignoring video duration

A two-hour 1080p file can use more storage than a short 4K clip.

Ignoring bitrate

Bitrate directly controls how much encoded data is represented over time.

Confusing bitrate with resolution

These are different properties.

Resolution = pixel dimensions

Bitrate = encoded data rate

Planning storage based on one sample file

One 4K file tells you something about that particular encoding.

It does not establish a universal 4K file size.

Ignoring free space needed by the device

A drive with just enough theoretical room for the video is not necessarily a comfortable storage situation.

Leave sensible headroom.

Quick 1080p vs 4K vs 8K Storage Guide

For storage planning, think this way:

1080p

Often practical when you want a good balance between visual detail and storage, but the actual size still depends on bitrate and duration.

4K

Can provide more spatial detail, but storage varies dramatically with bitrate, frame rate, codec, and content.

8K

Contains substantially more pixels per frame and can demand significant storage in high-quality workflows, but there is still no universal GB-per-hour figure.

The fastest practical calculation is:

bitrate × duration ÷ 8

Then account for:

audio + container/metadata + real encoding behavior

That gives you a much better estimate than searching for a universal “4K file size.”

Frequently Asked Questions

How much storage does a 1-hour 1080p video need?

There is no universal number.

At a purely mathematical video bitrate of:

5 Mbps → about 2.25 GB

10 Mbps → about 4.5 GB

20 Mbps → about 9 GB

These are examples, not fixed 1080p standards.

How much storage does a 1-hour 4K video need?

Again, it depends on bitrate.

For example:

10 Mbps → about 4.5 GB

20 Mbps → about 9 GB

50 Mbps → about 22.5 GB

The correct number for a real file depends on its actual encoding.

How much storage does a 1-hour 8K video need?

There is no universal 8K storage figure.

For illustration:

20 Mbps → about 9 GB

50 Mbps → about 22.5 GB

100 Mbps → about 45 GB

These are bitrate-based calculations, not claims about normal 8K recordings.

Is 4K always four times larger than 1080p?

No.

4K UHD has four times the pixel count of 1080p, but encoded file size does not have to be four times larger.

Bitrate, duration, codec, frame rate, audio, and encoder settings all matter.

Is 8K always four times larger than 4K?

No.

8K UHD has four times the pixels per frame of 4K UHD, but file size depends on the encoded data rate and other factors.

Does bitrate affect video storage?

Yes.

For the same duration, higher bitrate means more encoded data and therefore a larger file.

Does FPS affect video file size?

Yes.

All else being comparable, higher frame rates generally increase compressed video size because more frames have to be represented. MDN explicitly documents this relationship.

Does codec affect video file size?

Yes.

Different codecs use different compression methods and can achieve different quality/size trade-offs.

Why are two 4K videos different sizes?

Possible reasons include:

different bitrates different durations different codecs different frame rates different encoder settings different motion complexity different audio tracks How much free storage should I have before downloading 4K?

Have more free space than the expected final file size.

There is no universal extra-storage multiplier that applies to every device and workflow.

If the source estimate is close to your available free space, choose a smaller available quality or move other files first.

Can a 4K video be too large for MediaFetches?

Yes.

The current/default MediaFetches downloader configuration uses a 2 GiB maximum-file-size ceiling through yt-dlp's maxFilesize setting.

When yt-dlp reports an oversized file, the current user-facing message is:

“That file is larger than this server allows. Please try a lower quality.”

The practical consequence is that a source can be 4K yet still be unsuitable for the current configured limit if the particular encoding is too large.

Can an 8K video exceed MediaFetches' file limit?

Yes.

Any source whose relevant download exceeds the configured maximum can encounter the same file-size restriction.

Also remember that the current MediaFetches homepage does not advertise a dedicated 8K quality tier, so the article's 8K examples should be treated as general storage-planning guidance rather than an assurance of 8K availability.

Does higher resolution always mean better quality?

No.

Higher resolution provides more pixel dimensions, but perceived quality also depends on source quality, bitrate, codec, encoding quality, display, viewing distance, and other factors.

A heavily compressed 4K video can look worse than a well-encoded 1080p video.

Sources and references

• MDN video codec guidance
• ITU Recommendations

Related MediaFetches guides

For related guidance, see video resolution guide and video bitrate guide.

Final Takeaway

The most important thing to remember is:

Resolution is not file size.

1080p, 4K, and 8K describe different frame dimensions.

They do not tell you how many gigabytes the finished video will occupy.

For storage planning, start with:

FILE SIZE ≈ BITRATE × DURATION

Then account for:

codec + frame rate + audio + encoding settings + content complexity + container/metadata

That is why two 1080p videos can have very different sizes.

It is why two 4K videos can have very different sizes.

And it is why an 8K file is not automatically four times the size of a 4K file.

For practical planning, examples such as:

5 Mbps × 1 hour ≈ 2.25 GB

10 Mbps × 1 hour ≈ 4.5 GB

20 Mbps × 1 hour ≈ 9 GB

50 Mbps × 1 hour ≈ 22.5 GB

100 Mbps × 1 hour ≈ 45 GB

are far more useful than pretending that every resolution has one fixed storage requirement.

For MediaFetches users, there is another useful layer:

the source's approximate file size → the server's configured size limit → the server's temporary READY-file storage → your device's local free space

are separate things.

The current/default MediaFetches configuration has a 2 GiB individual downloader limit, an 8 GiB READY-file quota, a 30-minute finished-file TTL, and a 5-minute cleanup sweep. These are deployment configuration values, not permanent universal guarantees.

The central lesson is simple:

When planning video storage, think in bitrate and duration first, then use resolution, codec, frame rate, audio, and encoding settings to understand why the real file may differ.

That approach works for 1080p, 4K, 8K, and essentially any other resolution because it is based on how video data is actually stored.