If a person were recorded in true 8K continuously from birth to age 89, the result would sit far outside the world of normal hard drives. Even a relatively compressed 8K implementation already lands in petabytes over a full life. Higher-quality compressed 8K quickly climbs into the tens of petabytes, professional-grade workflows cross into exabytes, and fully uncompressed edge-case scenarios become so large that the right comparison is no longer a laptop or a NAS box, but physical infrastructure.
Table of Contents
The number starts with the format, not the resolution
Samsung defines consumer 8K as 7,680 × 4,320 pixels, or roughly 33 million pixels per frame. That sounds precise enough to settle the question on its own, but it does not. Storage depends on resolution, frame rate, bit depth, chroma subsampling, codec choice, and compression level. In other words, “8K” tells you how many pixels exist in a frame, not how many bytes a lifetime of those frames will require.
The timespan is part of what makes the thought experiment explode. Eighty-nine mean solar years contain about 2.81 billion seconds. Once any serious 8K bitrate is stretched across that many seconds without interruption, the total stops being intuitive very quickly.
Even compressed 8K becomes a storage problem
Take a relatively conservative real-world example first. Samsung’s support documentation for the Galaxy S20 says its 8K mode supports 7,680 × 4,320 at 24 fps, uses HEVC, and produces files of about 600 MB per minute. Extend that rate across 89 years nonstop and the total comes to roughly 28.09 petabytes, or about 28,086 terabytes. That is not a rounding error away from ordinary storage. It is already infrastructure-scale.
YouTube’s current guidance shows why the range broadens so quickly. For 8K uploads, it recommends 80–160 Mbps for standard frame rates and 120–240 Mbps for high frame rates. Over 89 years, those rates translate to about 28.09 PB, 56.17 PB, 42.13 PB, and 84.26 PB respectively. That is the believable compressed range for a lifelong 8K archive before stepping into professional post-production or uncompressed capture.
The physical comparison helps. A 28.09 PB archive would need roughly 1,404 drives of 20 TB each. A 56.17 PB archive would need about 2,809 such drives. At 84.26 PB, the number rises to roughly 4,213 drives. That is why the phrase “store it on hard drives” stops sounding practical here. It is technically true and strategically absurd.
From megabytes to ronnabytes
How data grows from everyday files to a planet-scale 8K archive: A few megabytes feel trivial. A few gigabytes still sound familiar. Even terabytes are now ordinary enough to live on a desk or in a backpack. Then the scale breaks. Once you move into petabytes, exabytes, and beyond, data stops feeling like something stored on devices and starts feeling like something that demands buildings, power, cooling, land, and logistics. That is the scale this article is really describing.
| MB | Megabyte | The scale of ordinary digital life. A single image, a simple document, or a short audio file can live here. |
| GB | Gigabyte | The unit most people know best. Phones, apps, films, and laptop storage are often measured in gigabytes. |
| TB | Terabyte | The point where storage starts to feel serious for an ordinary user. External drives, home backups, and media libraries often live in this range. |
| PB | Petabyte | The point where consumer storage stops making intuitive sense. Petabytes belong to major archives, enterprise systems, and very large video collections. |
| EB | Exabyte | A scale associated with infrastructure rather than personal technology. At this level, storage starts to resemble an industrial problem. |
| ZB | Zettabyte | A global-scale unit used to describe huge digital ecosystems, internet-scale systems, and vast flows of information. |
| YB | Yottabyte | A quantity so large that it becomes difficult to picture in human terms. It belongs to extreme comparisons, not ordinary storage planning. |
| RB | Ronnabyte | One of the largest official SI units. In this article, it marks the point where data becomes so vast that it can be compared to the physical surface of the planet. |
Each step in this sequence is 1,000 times larger than the one before it. That is why the climb from megabytes to ronnabytes is not a gradual increase. It is a collapse of ordinary intuition. By the time the number reaches petabytes, it has already left consumer reality behind. By the time it reaches ronnabytes, the right comparison is no longer a hard drive, a server room, or even a data center. It is geography.
Professional workflows push the total into exabytes
The professional end of the spectrum makes the picture even harsher. Apple’s ProRes white paper lists Apple ProRes 422 HQ at about 220 Mbps for 1920 × 1080 at 29.97 fps. Blackmagic RAW, meanwhile, offers constant-bitrate options such as 5:1, 8:1, 12:1, and 18:1, which is a reminder that cinema workflows are built around deliberate compression choices rather than a single universal data rate.
If you scale Apple’s 1080p ProRes 422 HQ figure linearly by pixel count to 8K UHD, a rough 8K30 equivalent lands at about 3.52 Gbps, which across 89 years becomes roughly 1,235.77 PB, or about 1.24 exabytes. If you then scale that same estimate up to a rough 8K60 equivalent, the lifetime total rises to about 2,474.01 PB, or 2.47 exabytes. That is not an official Apple 8K specification. It is a reasoned extrapolation. But it captures the real point cleanly: once you move into serious production-grade 8K, exabytes stop looking hypothetical.
The uncompressed ceiling breaks intuition
Once compression disappears, ordinary intuition fails almost immediately. Assume standard 8K UHD at 7,680 × 4,320, running at 60 fps. In an uncompressed 10-bit 4:2:0 signal, each frame would contain about 62.21 MB, and the stream would run at roughly 3.73 GB every second. Carried across 89 years, that becomes about 10.48 exabytes.
Raise the signal to 10-bit 4:2:2, and the lifetime total climbs to about 13.98 exabytes. Move again to a mastering-grade 12-bit 4:4:4 signal at the same 8K and 60 fps, and the number reaches roughly 25.16 exabytes. This is where the thought experiment changes character. It is no longer about whether a person could buy enough storage. It is about how much physical infrastructure would be needed to keep the archive alive, powered, cooled, copied, and protected.
When data outgrows the room
The most extreme version of the thought experiment comes from a real current camera benchmark. Blackmagic says its URSA Cine platform can capture 8K 2.4:1 at 8,192 × 3,408 up to 224 fps. If you imagine storing that stream completely uncompressed in 12-bit 4:4:4 over 89 years, the archive rises to roughly 79.04 exabytes. That is not just “a lot of footage.” It is an amount of data so large that it has to be pictured spatially, not digitally.
To make that tangible, take a real desktop machine rather than an abstract drive. Dell sells a Pro Tower configuration with a 256 GB SSD, and Dell’s owner’s manual gives the chassis dimensions as 324.3 mm high, 154 mm wide, and 293 mm deep. On that basis, a 13.98-exabyte archive would require about 54.6 million such desktop towers. A 25.16-exabyte archive would need around 98.3 million. The extreme 79.04-exabyte scenario would demand about 308.7 million towers.
Set only those 308.7 million towers on the floor using nothing but their footprint, and they would cover about 13.93 square kilometres. Line them up side by side using only their 154 mm width, and the row would stretch for roughly 47,546 kilometres. That is the moment the number becomes real. An uncompressed 8K record of one human life does not belong in the language of external SSDs anymore. It belongs in the language of land use.
When data outgrows the planet
Now scale the same extreme scenario to a hypothetical world of 8.3 billion people, exactly as a thought experiment. At 79.04 exabytes per person, humanity would generate about 656.01 ronnabytes of data over 89 years. The prefix matters here: under the International System of Units, ronna means 10²⁷. That means the total is also about 656,013.6 yottabytes, 656,013,615.8 zettabytes, 656,013,615,760.0 exabytes, or 656,013,615,760,045.9 petabytes.
Put differently, if you tried to store that archive on the same 256 GB desktop towers, you would need around 2.56 quintillion computers. Even if you counted only the footprint of each machine on the floor and ignored cables, aisles, power, cooling, maintenance, walls, and every other real-world requirement, those towers would occupy about 115.63 billion square kilometres. NASA Earthdata says Earth has more than 57 million square miles of land, which is roughly 147.63 million square kilometres, so this storage footprint would be about 783 times Earth’s land surface.
We live in a data age so vast that most people still do not realise how quickly information turns into physical space, said Jan Bielik, CEO & Founder
That quote lands because this is the hidden lesson inside the arithmetic. Data often feels abstract because most people interact with it through streaming apps, cloud icons, and percentages on a phone screen. But once recording is pushed to its logical extreme, data stops feeling weightless. It becomes area, hardware, energy, logistics, and cost. In that sense, an uncompressed 8K archive is not merely a media file problem. It is a problem of physical reality.
What the honest answer really is
The honest answer is no longer the old terabyte-scale one. For an 89-year nonstop 8K recording, the believable range starts at roughly 28 petabytes even on a relatively compressed mobile-style implementation, rises to roughly 28–84 petabytes for current compressed 8K upload-grade ranges, climbs to around 1.24–2.47 exabytes in a professional ProRes-style inference, and reaches roughly 10.48–79.04 exabytes in uncompressed scenarios depending on the exact signal and frame rate you choose. If the question is meant in practical human terms rather than cinema engineering terms, the most useful conclusion is simple: a true lifelong 8K archive belongs in petabytes at minimum, and very quickly in exabytes once quality assumptions get serious.
The archive would also be a security liability
A lifelong 8K archive would not merely be a storage problem. It would also be a privacy and security risk of unusual magnitude. Under the GDPR, video that relates to an identifiable person is personal data, and if that footage is processed for the purpose of uniquely identifying someone, it can become biometric data, an even more sensitive category. The European Data Protection Board’s guidance on video devices makes the broader point clear: recording people at scale has to meet tests of necessity, proportionality, and transparency, not just technical feasibility. The GDPR itself adds the harder limits that matter here most: purpose limitation, data minimisation, storage limitation, and appropriate security of processing. In plain terms, a complete lifelog would not just be an archive of a human life. It would be a concentrated map of habits, relationships, locations, routines, vulnerabilities, and identity signals. That means the bigger the archive becomes, the more dangerous its misuse, leakage, repurposing, or analysis becomes.
The archive would demand a living infrastructure
A lifelong 8K archive at this scale would not survive as a pile of disks in a room. It would require a living infrastructure built around redundancy, integrity checks, migration, and operational resilience. Over decades, storage media age out, hardware fails, formats change, and the archive has to be copied forward without losing fidelity or trust. The real challenge would not be creating the first copy. It would be preserving the archive across generations of hardware, software, and failure events. Modern large-scale storage systems are designed around exactly that logic: redundant copies across separate locations, durability controls, and infrastructure that can tolerate the loss of hardware or even an entire facility. In practical terms, a true 8K lifelog of this size would demand not just capacity, but continuous verification, replacement cycles, secure decommissioning of retired media, and resilient power behind the storage itself. That is the moment the idea stops looking like personal archiving and starts looking like critical infrastructure.
Author:
Jan Bielik
CEO & Founder of Webiano Digital & Marketing Agency
Sources
Samsung Smart TVs with 8K Resolution
Official Samsung page used for the 8K definition of 7,680 × 4,320 pixels and roughly 33 million pixels.
https://www.samsung.com/levant/tvs/tv-buying-guide/what-is-8k-tv/
Meet the unprecedented 8K video with Galaxy S20
Official Samsung support page used for the 8K mobile example of 7,680 × 4,320 at 24 fps, HEVC, and 600 MB per minute.
https://www.samsung.com/sg/support/mobile-devices/meet-the-unprecedented-8k-video-with-galaxy-s20-plus-s20-ultra/
YouTube recommended upload encoding settings
Official YouTube support page used for current 8K upload bitrate guidance.
https://support.google.com/youtube/answer/1722171?hl=en
Apple ProRes
Official Apple white paper used for the ProRes 422 HQ reference bitrate of approximately 220 Mbps at 1920 × 1080 and 29.97 fps.
https://www.apple.com/final-cut-pro/docs/Apple_ProRes.pdf
Blackmagic RAW
Official Blackmagic page used for the constant-bitrate examples of 5:1, 8:1, 12:1, and 18:1 in professional workflows.
https://www.blackmagicdesign.com/products/blackmagicraw
Blackmagic URSA Cine
Official Blackmagic page used for the extreme 8K 2.4:1 capture benchmark at 8,192 × 3,408 and up to 224 fps.
https://www.blackmagicdesign.com/products/blackmagicursacine
Dell Pro Tower Desktop
Official Dell product page used for the real-world 256 GB desktop storage example.
https://www.dell.com/en-us/shop/desktop-computers/dell-pro-tower-desktop/spd/dell-pro-qct1250-desktop
Dell Pro Tower QCT1250 Owner’s Manual
Official Dell manual used for the desktop chassis dimensions of 324.3 × 154 × 293 mm.
https://www.dell.com/support/manuals/en-us/dell-pro-qct1250-desktop/dell-pro-tower-qct1250-owners-manual/dimensions-and-weight
Land Surface
Official NASA Earthdata page used for the land-area reference of more than 57 million square miles.
https://www.earthdata.nasa.gov/topics/land-surface
SI prefixes
Official BIPM reference used for the SI definition of ronna as 10²⁷ and the related large-number prefix ladder.
https://www.bipm.org/en/measurement-units/si-prefixes
General Data Protection Regulation
Official EUR-Lex text of the GDPR used for the definitions of personal data and biometric data, as well as the principles of purpose limitation, data minimisation, storage limitation, and security of processing.
https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng
Guidelines 3/2019 on processing of personal data through video devices
Official European Data Protection Board guidance used for the privacy implications of large-scale video recording and the need for necessity, proportionality, and transparency in video-based processing.
https://www.edpb.europa.eu/sites/default/files/files/file1/edpb_guidelines_201903_video_devices_en_0.pdf
Security Guidelines for Storage Infrastructure
Official NIST publication used for the argument that storage at this scale must be treated as managed infrastructure with security, integrity, and lifecycle controls rather than passive capacity.
https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-209.pdf
Object Storage Classes – Amazon S3
Official AWS documentation used for the infrastructure example of redundant storage across a minimum of three Availability Zones and extremely high durability design.
https://aws.amazon.com/s3/storage-classes/
Data Center – Our Controls
Official AWS trust documentation used for the point that storage media must be managed across their full lifecycle and securely decommissioned when no longer useful.
https://aws.amazon.com/trust-center/data-center/our-controls/
Resilient Power Best Practices for Critical Facilities and Sites
Official CISA guidance used for the point that infrastructure at this scale depends on resilient power planning rather than ordinary consumer assumptions about uptime.
https://www.cisa.gov/sites/default/files/2023-01/CISA%20Resilient%20Power%20Best%20Practices%20for%20Critical%20Facilities%20and%20Sites.pdf
