Audited ·Last updated 28 Jul 2026·4 citations·Tier 2·0 uses

Image File Size Calculator

Work out photo file size from pixel dimensions, bit depth, channels and compression — plus how many fit on a card and what a shoot will need.

Image File Size Calculator

What do you need?
Recorded pixel width. The Canon EOS R6 default here records 5472 × 3648, which Canon lists as approximately 20.1 effective megapixels.
px
Recorded pixel height. Use the full-resolution figure, not a cropped export, if you are trying to predict what the camera writes to the card.
px
Bit depth
Channels
Uncompressed ÷ stored. 1 means none. Derived from Canon's published EOS R6 table: JPEG Large Fine is about 8.4:1, JPEG Large Normal about 15.4:1, lossless RAW about 1.6:1 and C-RAW about 3.1:1. Ignored when you are solving for the ratio.
:1
The size of a real file from this camera, in megabytes. Only used when you are solving for the compression ratio. Canon publishes 7.1 MB for an EOS R6 JPEG Large Fine.
MB
How many frames you expect to take. A wedding is typically 1,500–3,000; a studio session a few hundred; a sports fixture several thousand.
As the manufacturer quotes it. Card capacities are decimal gigabytes (1 GB = 10⁹ bytes), which is why a 64 GB card shows as 59.6 GiB in an operating system that counts in binary.
GB
Answer
5472 × 3648 (20 MP), 8-bit, 3-channel at 1:1 compression is 59.89 MB per image (57.11 MiB), or 24 bits per pixel. Uncompressed the same frame would be 59.89 MB.
The solved quantity stated in the terms of the mode you chose, with the uncompressed size alongside so the compression is visible rather than implied.
File size
59.8856 MB
File size (binary)
57.1113 MiB
File size in bytes
59,885,568 B
Uncompressed size
59.8856 MB
Bits per pixel
24
Compression ratio
1:1
Resolution
19.9619 MP
Images per card
1,068
Storage for the shoot
29.9428 GB
Cards and caveats
A 64 GB card holds 1068 of these images and 500 frames come to 29.94 GB. Card capacities are quoted in decimal gigabytes (1 GB = 10⁹ bytes), so a card your operating system calls 59.6 GiB is the same card. Treat this as an upper bound: filesystem overhead, embedded previews and metadata all take a slice, and the compression ratio itself moves with the picture — a frame of blue sky compresses far harder than autumn woodland.

Background.

This calculator answers the question a camera's own display never quite does: how big will these files be, and will they fit? It works from pixel dimensions, bit depth, channel count and a compression ratio, and it reports the uncompressed size alongside the stored size so the compression is visible rather than implied. It is not a download-time calculator — it produces a file size from parameters rather than taking one as an input.

The uncompressed part is a definition, not an estimate. An image is width × height × channels × bit depth bits, divided by eight to get bytes. There is nothing to look up. The trap is the channel count: a JPEG or a TIFF has three channels because it stores a red, green and blue value for every pixel, but a Bayer raw file has only one, because the sensor records a single value per photosite and the demosaic that invents the other two happens later, in software. Set channels to 3 for a raw file and you will overstate the uncompressed size by a factor of three, and any compression ratio you derive from it will be nonsense.

The compressed part is genuinely uncertain, which is why compression ratio is an input on this page rather than a hidden table. How well a codec does depends on the codec, the quality setting, and — most of all — the picture. A frame of clear blue sky and a frame of autumn woodland from the same camera at the same setting can differ by more than two to one, and Canon's own file-size table carries the footnote "file size, number of possible shots, and maximum burst vary depending on shooting conditions". What this page can do is give you real anchors instead of folklore. Canon publishes, for the 20.1 MP EOS R6 at 5472 × 3648: JPEG Large Fine 7.1 MB, JPEG Large Normal 3.9 MB, RAW 21.8 MB and C-RAW 11.2 MB. Divide those into the corresponding uncompressed bitmaps and the ratios fall out — 8.4:1, 15.4:1, 1.6:1 and 3.1:1 — and the compression-ratio mode on this page lets you do the same with a file from your own camera.

The third mode is the practical one. Give it a frame count and a card size and it returns the storage a shoot needs and the number of cards, using decimal gigabytes the way card manufacturers do. That is also why the results show both MB and MiB: a 64 GB card is 64 × 10⁹ bytes to the manufacturer and 59.6 GiB to your operating system, and neither is lying.

Below the widget you will find the identity written out, three worked examples computed by hand against Canon's published figures, why raw compression ratios above about two should make you suspicious, and an honest list of what the arithmetic leaves out.

What is image file size calculator?

An image file's size has two components: how much information the pixels represent, and how efficiently the format stores it. The first is exact. A digital image is a rectangular array of samples, each sample carrying a fixed number of bits per channel, so the information content is width × height × channels × bit depth bits — 19,961,856 pixels × 3 channels × 8 bits for a 20 MP RGB image, which is 478,884,544 bits or 59,885,568 bytes. That figure is what an uncompressed TIFF or BMP writes, and it is the denominator of every compression ratio. The second component is the codec. Lossless formats (PNG, TIFF with LZW or ZIP, lossless raw) reconstruct every original sample exactly and therefore achieve only what the image's own redundancy allows — typically 1.2 to 2 times on photographic content, which is why a lossless raw file compresses far less than people expect. Lossy formats (JPEG, HEIF, AVIF, JPEG XL in lossy mode) discard information the eye is unlikely to miss and can achieve ten or twenty times, at a quality cost that grows with the ratio. JPEG, standardised as ISO/IEC 10918-1, works by transforming 8 × 8 blocks into frequency coefficients, quantising them by an amount the quality setting controls, and entropy-coding the result — a process whose output size depends entirely on how much high-frequency detail the picture contains. That is the fundamental reason no calculator can predict a JPEG's size from its dimensions alone, and why this page asks you for a ratio or lets you measure one. Two conventions matter for the storage arithmetic. Card and drive capacities are decimal: a 64 GB card holds 64 × 10⁹ bytes. Operating systems and file managers usually count in binary, where a gibibyte is 2³⁰ bytes, so the same card shows as 59.6 GiB. NIST's guide to the SI covers both prefix families, and the difference — about 7 % at the gigabyte scale — is enough to matter when you are deciding whether a shoot fits.

How to use this calculator.

  1. Choose what you need. "File size" predicts a file from its parameters; "compression ratio" measures what your camera is really doing from a file you already have; "shoot storage" turns a frame count into cards.
  2. Enter the recorded pixel width and height. Take these from the camera's specification or from an existing file's properties, not from the marketing megapixel number, which is usually rounded and sometimes counts photosites that are never written out.
  3. Set the bit depth. JPEG is always 8 bits per channel. Most full-frame cameras record raw at 14 bits, many crop and older bodies at 12, and medium format at 16. HEIF stills are typically 10.
  4. Set the channel count carefully. Use 3 for RGB, 4 for RGBA or CMYK, and 1 for grayscale — and 1 for a Bayer raw file too. If you are computing a raw file's size and you chose 3, everything downstream will be wrong by a factor of three.
  5. For the file-size mode, enter a compression ratio. Use 1 for genuinely uncompressed output. For a camera JPEG at best quality, around 8 is a reasonable starting point derived from Canon's published table; for lossless raw, around 1.6.
  6. For the compression-ratio mode, enter the size of a real file from your camera instead. The calculator will tell you the ratio and the bits per pixel it implies — which is the most useful diagnostic on the page, because it is measured rather than assumed.
  7. For the shoot-storage mode, enter your frame count and card capacity. Then double the result if you shoot raw + JPEG, and double it again if you back up to a second drive in the field.
  8. Treat every storage figure as an upper bound. Filesystem overhead, the embedded JPEG preview inside every raw file, and metadata all take a slice, and the compression ratio itself moves with what you photograph.

The formula.

B_unc = W × H × C × D ÷ 8 · B = B_unc ÷ R · bpp = 8B ÷ (W×H) · n = ⌊capacity ÷ B⌋

The uncompressed size is a definition:

B_unc = W × H × C × D / 8 bytes

For a 5472 × 3648 frame that is 19,961,856 pixels. At 3 channels and 8 bits each: 19,961,856 × 3 × 8 / 8 = 59,885,568 bytes = 59.885568 MB. The bits-per-pixel figure for an uncompressed file is then exactly C × D — 24 for 8-bit RGB — which is the arithmetic self-check built into this page.

Compression divides:

B = B_unc / R bpp = 8B / (W × H)

and the compression-ratio mode inverts it: R = B_unc / B_observed.

The ratios you can trust are the ones you derive from published figures rather than remember. Canon's EOS R6 specification lists, at 5472 × 3648: JPEG Large Fine 7.1 MB, JPEG Large Normal 3.9 MB, RAW 21.8 MB, C-RAW 11.2 MB. Working those out:

8-bit RGB uncompressed = 59.885568 MB ÷ 7.1 = 8.43 : 1 (2.85 bits per pixel) JPEG L Fine ÷ 3.9 = 15.36 : 1 (1.56 bits per pixel) JPEG L Normal

14-bit single-channel raw = 19,961,856 × 14 / 8 = 34,933,248 B = 34.933248 MB ÷ 21.8 = 1.60 : 1 RAW (lossless) ÷ 11.2 = 3.12 : 1 C-RAW (lossy)

Note what the raw line depends on. If you set channels to 3 instead of 1, the "uncompressed" raw figure becomes 104.8 MB and the implied ratio 4.8:1 — and a lossless ratio of 4.8 on photographic data is not achievable, which is how you know the channel count was wrong. A raw file holds one number per photosite; the other two colours per pixel are interpolated later.

Storage, finally:

images per card = ⌊ capacity_bytes / B ⌋ shoot storage = B × frames / 10⁹ GB

with capacities in decimal gigabytes because that is how they are sold. The results also show mebibytes, 2²⁰ bytes, because that is what most operating systems display when they write "MB".

What this leaves out: container overhead and metadata, which add tens of kilobytes to a JPEG and often one to several megabytes to a raw file thanks to the embedded full-size JPEG preview; chroma subsampling, which throws away colour resolution before JPEG's transform even runs, so "3 channels" overstates what the encoder is really given; and the dominant factor of all — picture content. Canon's own table is footnoted "file size, number of possible shots, and maximum burst vary depending on shooting conditions", and it is not being coy.

A worked example.

Example

Take Canon's own published figure and see what it implies. The EOS R6 records 5472 × 3648, which Canon lists as approximately 20.1 effective megapixels, and its specification table gives a JPEG Large Fine file as 7.1 MB. Start with the bitmap: 5472 × 3648 = 19,961,856 pixels, and at 3 channels of 8 bits each that is 19,961,856 × 3 = 59,885,568 bytes, or 59.885568 MB — 57.11 MiB if your file manager counts in binary. The stored file is 7,100,000 bytes, so the compression ratio is 59,885,568 ÷ 7,100,000 = 8.4345870423 to one. In other words Canon's default JPEG discards about 88 % of the data. In bits per pixel that is 7,100,000 × 8 ÷ 19,961,856 = 2.845426798 bits, against the 24 an uncompressed 8-bit RGB pixel occupies — under three bits to describe a full-colour pixel, which is a fair summary of why JPEG changed photography. The storage consequences follow immediately: a 64 GB card holds ⌊64,000,000,000 ÷ 7,100,000⌋ = 9,014 of these frames, and a 500-frame session comes to 7,100,000 × 500 ÷ 10⁹ = 3.55 GB. Compare that with shooting the same session uncompressed, where the same card would hold 1,068 frames and the session would need 29.94 GB. Now try the raw line as a cross-check, because it is where people go wrong. Set the bit depth to 14, the channels to 1 and the actual size to Canon's published 21.8 MB. The uncompressed figure becomes 19,961,856 × 14 ÷ 8 = 34,933,248 bytes = 34.933248 MB, and the ratio is 1.6024425688 to one — a modest, believable number for lossless compression of photographic data. Had you left the channel count at 3, the calculator would have reported an uncompressed size of 104.8 MB and a lossless ratio of 4.8:1, which is not achievable and is the signal that the setting is wrong. A Bayer raw file stores one value per photosite; the missing two thirds of the colour information is invented by the demosaic later.

compression Ratio1
channels3
bit Depth8
height Px3,648
shot Count500
width Px5,472
storage Capacity G B64
known File Size M B7.1
solve ForcompressionRatio

Frequently asked questions.

Why is my raw file so much smaller than the calculator's uncompressed figure?
Two reasons, and the first is usually the channel count. A raw file is not an RGB image: the sensor has a colour filter array with one filter per photosite, so the file stores one number per photosite, not three. Set channels to 1 for any Bayer raw file. For a 20 MP camera at 14 bits that is 19,961,856 × 14 ÷ 8 = 34.9 MB rather than the 104.8 MB you get by wrongly assuming three channels. The second reason is that almost all raw files are compressed even when they are described as uncompressed — Canon's lossless RAW comes out at 21.8 MB against that 34.9 MB bitmap, a ratio of about 1.6:1, which is roughly what lossless entropy coding achieves on photographic data. If you compute a lossless ratio much above 2, check the channel count before believing it. Note also that raw files carry an embedded full-size JPEG preview plus maker notes, which can add one to several megabytes that this pixel arithmetic does not include.
Why does my 64 GB card show as 59.6 GB on my computer?
Because the two are counting in different bases and both are correct. Storage manufacturers use decimal SI prefixes, where a gigabyte is 10⁹ = 1,000,000,000 bytes, so a 64 GB card really does hold 64,000,000,000 bytes. Most operating systems count in binary, where the natural unit is 2³⁰ = 1,073,741,824 bytes, and many of them display that unit with the label "GB" even though its correct name is the gibibyte, GiB. 64,000,000,000 ÷ 1,073,741,824 = 59.6, hence the discrepancy. It grows with scale: about 2.4 % at the kilobyte, 4.9 % at the megabyte, 7.4 % at the gigabyte and 10 % at the terabyte. This calculator reports both — decimal MB, which is what camera manufacturers publish, and binary MiB, which is what your file manager shows — so you can reconcile the two rather than wonder which is lying.
Can this predict how big my JPEGs will actually be?
Only as well as your compression ratio estimate, and that is an honest limitation rather than a shortcoming of the arithmetic. JPEG's output size depends on how much high-frequency detail the picture contains, because the codec quantises frequency coefficients and entropy-codes what survives — a frame of clear blue sky produces very few surviving coefficients and a frame of autumn woodland produces a great many. Two frames from the same camera at the same quality setting can differ by more than two to one. Canon's own file-size table is footnoted "file size, number of possible shots, and maximum burst vary depending on shooting conditions" for exactly this reason. The reliable way to use this page is the other way round: shoot a few representative frames, put one of their sizes into the compression-ratio mode, and use the ratio it derives for planning. That is a measurement of your camera on your subject matter rather than a guess.
What is a good bits-per-pixel figure?
It depends entirely on what the file is for, but the scale is useful to know. Uncompressed 8-bit RGB is exactly 24 bits per pixel by definition. A camera JPEG at its highest quality lands around 2.5 to 3.5 — Canon's EOS R6 JPEG Large Fine works out at 2.85 — and that is generally regarded as visually indistinguishable from the original at normal viewing sizes. A well-optimised web image sits between 0.5 and 1.5 bits per pixel; below about 0.5 the blocking and ringing artefacts of JPEG become visible on smooth gradients, though newer codecs such as AVIF and JPEG XL hold up considerably further down. Lossless raw sits around 8 to 9 bits per pixel for a 14-bit sensor. Bits per pixel is a more useful comparison than compression ratio when you are comparing different cameras, because it normalises out the resolution and the source bit depth.
Should I plan storage for raw + JPEG?
If you shoot both, yes, and the arithmetic is simply additive: run the calculator once for each and add. Canon's published pairs make the point — RAW + Large Fine JPEG on an EOS R6 is 21.8 + 7.1 = 28.9 MB per frame, about a third more than raw alone. Beyond the frames themselves, three things routinely blow a storage plan. Backing up in the field doubles everything. Editing raw files generates sidecars and, if you round-trip to TIFF or PSD, full 16-bit RGB files that are several times the raw size — a 20 MP 16-bit RGB TIFF is 119.8 MB before any layers. And most photographers under-count their frames: sports and wedding shooters routinely take two to three times what they planned. A defensible rule is to compute the honest figure here and then buy twice it.
How does this differ from the download time calculator?
Direction. This page produces a file size from image parameters — pixels, depth, channels and compression. The download time calculator takes a file size as an input and tells you how long it will take to move over a given connection. They chain naturally: work out here that a 500-frame raw shoot is 10.9 GB, then take that number to the download page to find out how long uploading it to a client gallery will take on your connection. Neither can do the other's job. This one has no notion of bandwidth and that one has no notion of pixels.

References& sources.

  1. [1]Canon Inc. EOS R6 Product Manual — Specifications. Source of every default and every compression anchor on this page. Gives the image sensor as 'Approx. 35.9×23.9 mm' with 'Max. approx. 20.1 megapixels' effective pixels, and the still-image file-size table at 5472×3648: JPEG Large (Fine) 7.1 MB, JPEG Large (Normal) 3.9 MB, RAW 21.8 MB, C-RAW 11.2 MB, with the caveat 'File size, number of possible shots, and maximum burst vary depending on shooting conditions.'
  2. [2]National Institute of Standards and Technology. NIST Special Publication 811, Guide for the Use of the International System of Units, Appendix B.9. The authority for the SI decimal prefixes used by storage manufacturers and for the IEC binary prefixes (kibi, mebi, gibi) that operating systems display. This is the basis of the MB / MiB and GB / GiB distinction reported by this calculator.
  3. [3]International Organization for Standardization / International Electrotechnical Commission. ISO/IEC 10918-1:1994, Information technology — Digital compression and coding of continuous-tone still images: Requirements and guidelines — the JPEG standard. Cited for the fact that JPEG is a lossy, quality-parameterised codec whose output size depends on the frequency content of the picture, which is why compression ratio is an input on this page rather than a table of constants.
  4. [4]International Organization for Standardization (2019). ISO 12232:2019, Photography — Digital still cameras — Determination of exposure index, ISO speed ratings, standard output sensitivity, and recommended exposure index. Cited for the bit-depth framing used here: what a camera's 12- or 14-bit raw capture represents in tonal levels per photosite, as against the 8 bits per channel a JPEG carries.

In this category

Embed

Quanta Pro

Paid features are coming later.

  • All 590 calculators remain free
  • No billing is enabled
Coming soon