Estimate image file sizes from resolution, bit depth, and format. Compare JPEG, PNG, WebP, AVIF, and RAW sizes with compression ratios.
Understanding image file sizes is essential for web developers, photographers, and anyone working with digital media. An uncompressed 4K image at 24-bit color takes up nearly 24 megabytes, but JPEG compression can reduce this to under 2 MB with minimal visual quality loss. Our Image File Size Calculator estimates the storage requirements for any resolution and format combination.
Enter your image dimensions, bit depth, and color channels, then see the uncompressed size alongside estimated sizes for JPEG, PNG, WebP, AVIF, and RAW formats. The calculator accounts for typical compression ratios at different quality levels and shows how format choice impacts file size, loading speed, and storage requirements.
Whether you're optimizing images for web performance, planning storage for a photo library, estimating bandwidth for an image-heavy application, or choosing between modern formats like WebP and AVIF, this calculator provides the data you need. It also includes common resolution presets from smartphone cameras to 8K displays, making it easy to plan your image pipeline.
Plan storage requirements, optimize web image formats, and understand the tradeoffs between quality and file size across different image formats. Keep these notes focused on your operational context. Tie the context to the calculator’s intended domain. Use this clarification to avoid ambiguous interpretation. Align this note with review checkpoints. Apply this where interpretation shifts by use case.
Uncompressed Size = Width × Height × Channels × (BitDepth / 8) bytes JPEG Size ≈ Uncompressed / (10-40) depending on quality PNG Size ≈ Uncompressed / (2-5) depending on content WebP Size ≈ JPEG Size × 0.70-0.85 AVIF Size ≈ JPEG Size × 0.55-0.75
Result: 24.88 MB uncompressed → ~2.07 MB JPEG @ 80%
3840×2160 at 8-bit RGB = 24,883,200 bytes uncompressed. At JPEG quality 80, typical compression ratio is ~12:1, yielding approximately 2.07 MB. WebP would be ~1.66 MB and AVIF ~1.24 MB for equivalent visual quality.
JPEG (Joint Photographic Experts Group) has been the dominant web image format since the late 1990s. It excels at photographs with smooth color gradients but struggles with sharp edges and text. Quality settings range from 1-100, with 75-85 being the practical sweet spot for web use. At quality 100, JPEG files can be larger than PNG with no visual benefit.
PNG (Portable Network Graphics) uses lossless compression, preserving every pixel. It's ideal for screenshots, diagrams, logos, and images with transparency. PNG files are typically 3-5× larger than JPEG for photographs but can be smaller for images with large areas of solid color. PNG supports 8-bit and 16-bit color depth plus full alpha transparency.
WebP, developed by Google, offers both lossy and lossless compression in a single format. Lossy WebP is typically 25-35% smaller than JPEG at equivalent quality. Lossless WebP is typically 26% smaller than PNG. It supports animation (replacing GIF) and alpha transparency. All modern browsers support WebP as of 2023.
AVIF (AV1 Image File Format) is the newest contender, based on the AV1 video codec. It offers approximately 50% savings over JPEG and supports HDR, wide color gamut, and both lossy and lossless modes. The main tradeoff is encoding speed — AVIF is significantly slower to encode than WebP or JPEG, making it better suited for static content that's encoded once and served many times.
Camera megapixels have exploded from 2MP in early digital cameras to 50-200MP in modern smartphones and 61-100MP in professional cameras. A single 50MP RAW file takes 50-100 MB of storage. At 1000 photos per event, a wedding photographer might generate 50-100 GB of RAW files in a single day.
For web delivery, consider that global average internet speed is approximately 50 Mbps. A 2 MB image takes about 0.3 seconds to download, while a 10 MB image takes 1.6 seconds. Google recommends that total page weight stays under 1.5-3 MB for good user experience, making image optimization crucial for any image-heavy website.
The current best practice for web images is a multi-format pipeline: generate AVIF, WebP, and JPEG versions of each image, then use the HTML picture element to serve the smallest supported format to each browser. Combined with responsive images (srcset) that serve appropriate resolutions based on viewport and device pixel ratio, this approach can reduce image bandwidth by 60-80% compared to serving original JPEGs. Tools like Sharp (Node.js), Squoosh (CLI/web), and Cloudflare Image Resizing automate this pipeline.
Resolution (total pixels), bit depth (bits per channel), color channels (RGB=3, RGBA=4), and compression format/quality. Content also matters — simple images compress better than complex ones.
Lossy (JPEG, lossy WebP) permanently discards data to achieve smaller files. Lossless (PNG, lossless WebP) preserves every pixel exactly. For photos, lossy is usually preferred; for screenshots and graphics, lossless is better.
WebP typically achieves 25-35% smaller files than JPEG at equivalent visual quality. It also supports transparency (alpha channel) and animation. WebP is supported by all modern browsers.
AVIF (AV1 Image File Format) is the newest competitive format, offering 30-50% smaller files than JPEG. It supports HDR, wide color gamut, and transparency. Browser support is growing but not yet universal.
Yes, file size scales roughly linearly with pixel count. A 50MP image is approximately 5× larger than a 10MP image in the same format and quality. But compression efficiency also depends on image content.
For web images, 8-bit is standard. For professional photography and editing, 16-bit preserves more tonal information (especially in shadows and highlights). 10-bit and 12-bit are common for HDR displays and cinema.