What Average File Sizes Really Look Like in 2026

Updated on December 12, 2025

The Numbers Have Changed More Than You Think

Every few years, someone publishes a "typical file size" chart that gets copy-pasted across the web until it quietly becomes obsolete. The photo sizes listed were calibrated for 12-megapixel smartphones. The video figures assumed H.264. The app sizes assumed nobody was shipping neural-engine weights on-device. None of that reflects 2026 reality.

So let's actually look at what files weigh today — pulling from device benchmarks, platform transparency reports, codec adoption data, and the kind of firsthand poking around that most roundups skip.

Photos: The Quiet Explosion Nobody Talks About

The average consumer smartphone in 2026 ships with a main sensor between 50 MP and 200 MP. Even mid-range Android devices from brands like Samsung and Xiaomi are capturing at 50 MP by default. Apple's iPhone 16 Pro shoots at 48 MP for the standard lens and up to 4K ProRes stills in some modes.

What does that actually mean for file size?

  • JPEG (standard smartphone, 12–24 MP effective output): 4–8 MB per photo. Most phones still downsample to ~12 MP for JPEG to keep sharing sizes manageable.
  • HEIC (Apple default since iOS 11, now universal): 2–5 MB for equivalent quality — the compression advantage is real and measurable.
  • RAW / DNG (full-resolution, no compression): 25–80 MB per frame. A 200 MP sensor produces a DNG that sits comfortably above 50 MB.
  • ProRAW (Apple's computational RAW): Typically 25–45 MB, depending on scene complexity and whether the multi-frame capture pipeline merged frames.

The practical takeaway: if you're a casual photographer syncing HEIC files, you're probably moving 3–4 MB per shot. If you're a serious photographer shooting uncompressed DNG on a high-resolution mirrorless body like a Sony A1 or Canon EOS R5 Mark II, expect 85–120 MB per frame. That's not a rounding difference — it's a 30x spread within a single category.

Music: Streaming Won, But Local Files Are Bigger Than Ever

Streaming dominates consumption, but local music files haven't gone away — they've gotten heavier. Here's the current landscape:

  • MP3 (320 kbps, standard quality): A 4-minute track lands at roughly 9.2 MB. This has been stable for years.
  • AAC (256 kbps, Apple/Spotify default for downloads): Around 7–8 MB for the same track, with arguably better perceived quality at lower bitrate than MP3.
  • FLAC (lossless, CD quality / 16-bit 44.1 kHz): 25–35 MB per track. A full album can easily hit 350–450 MB.
  • Hi-Res FLAC (24-bit 96 kHz or 192 kHz, available on Tidal, Qobuz, Amazon Music HD): 80–200 MB per track. A single album at 24/192 can exceed 2 GB.
  • Dolby Atmos / spatial audio tracks (MKA/AC4 containers): These vary wildly — from 15 MB for a compressed Atmos mix down to a lossless Atmos master that can exceed 300 MB for a 5-minute track.

The shift toward lossless and spatial audio formats, particularly as Apple Music and Tidal push them to mainstream listeners, means anyone building storage calculators or converter tools needs to account for a much wider range than "a song is about 4 MB."

4K Video: The Codec Split That Determines Everything

This is where file size conversations get genuinely complicated, because "4K video" can mean a 500 MB vacation clip or a 50 GB professional master — both technically accurate, both describing the same resolution.

The decisive variable is codec and bitrate:

  • H.264 / AVC (legacy streaming, YouTube 4K): YouTube's 4K stream runs at 35–68 Mbps. A 10-minute video encoded at 40 Mbps = approximately 3 GB.
  • H.265 / HEVC (modern streaming default): Equivalent quality to H.264 at roughly half the bitrate. A 10-minute 4K HEVC file at 20 Mbps ≈ 1.5 GB.
  • AV1 (YouTube's 4K standard since 2023, Netflix adopting): Further compression gains — similar quality to HEVC at 15 Mbps. Same 10-minute video ≈ 1.1 GB.
  • ProRes 4K (professional production, iPhone 16 Pro cinematic mode): 4K ProRes HQ at 24fps runs at approximately 2,500 Mbps. Ten minutes of footage = roughly 185 GB. This is not a typo.
  • BRAW / R3D (cinema RAW formats from Blackmagic / RED cameras): Bitrates vary by compression ratio selected, but 4K BRAW at 3:1 compression (a common production choice) runs about 600–900 MB per minute of footage.

For casual users, 4K video recorded on an iPhone or Android device in the standard HEVC mode runs about 400–800 MB per minute depending on frame rate. 4K at 60fps is approximately double 30fps, all else equal. If you're building a storage calculator, these are the numbers that actually matter for the 2026 smartphone user.

PDFs: Deceptively Variable

People think of PDFs as small, and text-only PDFs are. But the category spans an enormous range:

  • Text-only document (a report, a novel, a legal brief): 50–300 KB is typical. A 200-page text PDF rarely exceeds 1 MB.
  • Scanned document (image-based PDF, no OCR): 300–800 KB per page at standard scanner resolution (200 DPI). A 20-page scanned contract can hit 10–15 MB.
  • High-DPI scanned archival document (400–600 DPI): 1–3 MB per page. A 50-page manual becomes 50–150 MB quickly.
  • PDF with embedded high-resolution photos (product catalogs, photography portfolios, coffee table books): 50–500 MB is common. Some design-heavy PDFs from agencies exceed 1 GB.
  • PDF/A (archival standard) with embedded fonts and ICC color profiles: Adds 10–20% overhead compared to equivalent standard PDF.

The practical rule: if someone tells you their PDF is "huge," ask whether it's scanned or image-heavy. A scanned document is essentially a photo album in disguise, and its file size behaves accordingly.

Apps and Software: The New Heavyweight Category

App sizes have grown faster than any other category, driven by on-device AI models, higher-resolution assets, and framework bloat.

  • Simple utility apps (weather, flashlight, unit converter): 10–60 MB on iOS; 5–40 MB on Android. The gap has narrowed as Android improved its asset pipeline.
  • Social media apps (Instagram, TikTok, X, Snapchat): 100–400 MB on device, but these apps also cache aggressively — total on-device footprint (app + data + cache) often exceeds 2–5 GB for active users.
  • Mobile games (mid-tier): 500 MB–2 GB initial install, plus additional asset downloads post-install. AAA mobile titles like Genshin Impact exceed 20 GB of on-device storage after full download.
  • Desktop productivity apps: The Microsoft Office suite installation is approximately 4–6 GB on Windows. Adobe Creative Cloud's full suite exceeds 30 GB. Final Cut Pro on macOS sits at roughly 3.8 GB.
  • AI-integrated apps with on-device models: This is the new heavyweight. Apps shipping local LLM inference (Apple Intelligence features, Google Gemini Nano, on-device translation) add 1–8 GB of model weights to their footprint. Some developer tools with bundled code models exceed 10 GB installed.

The on-device AI shift is genuinely new as of 2025–2026 and hasn't been reflected in most "average app size" discussions. If you're building anything that estimates storage needs for users, treat AI-capable apps as a separate category with dramatically higher storage requirements.

Putting It Together: What "Average" Actually Means in 2026

If someone asks what a typical file size is in 2026, the honest answer is that the category matters far more than ever before. The range within each file type has expanded, not contracted, as formats have multiplied and quality ceilings have risen.

Here's a practical reference sheet for the most common use cases:

  1. Casual smartphone photo (HEIC): 3–5 MB
  2. Professional RAW photo: 40–120 MB
  3. Streamed music track (AAC): 7–9 MB
  4. Lossless hi-res music track (FLAC 24/96): 80–150 MB
  5. 1 minute of casual 4K smartphone video (HEVC): 400–600 MB
  6. 1 minute of 4K ProRes (professional): 15–20 GB
  7. Text-only PDF, 50 pages: 200–500 KB
  8. Scanned PDF, 50 pages: 15–40 MB
  9. Typical mobile social app: 150–350 MB
  10. AAA mobile game (fully downloaded): 5–25 GB

The lesson for anyone converting, compressing, or estimating file sizes in 2026 is to always ask two questions first: what's the source format, and what was the capture or encoding quality? The answers will move your estimate by an order of magnitude more reliably than any rule of thumb from three years ago.