How Many Photos Can 32GB Hold? The Answer at Three Levels of Detail

A 32 GB memory card holds roughly 3,600 top-quality JPEGs from a 24-megapixel camera, or about 1,120 RAW files from that same camera. Those are Canon's own published figures for the EOS R100, measured on a 32 GB UHS-I card at 8.4 MB per fine JPEG and 27.2 MB per RAW. Nikon's table for the 20.9-megapixel Z50II gives 2,100 fine JPEGs or 763 lossless NEF files on a card of the same size. Phone photos run smaller: SanDisk's own working average of 3.5 MB per photo puts about 8,500 images on 32 GB.

The answer at three levels of detail

Level one is one sum you can do standing at a counter. A 32 GB card gives you about 30,000 MB to write to. Divide that by your average file size in megabytes. Ten megabytes a frame gives 3,000 frames. Thirty gives 1,000. That is the entire model, and for most people it lands close enough to plan a day around.

Level two is the manufacturer's own table for your camera, which beats any generic chart because it was measured on that sensor, on a 32 GB card.

| Camera and setting | Resolution | Average file | Photos on a 32 GB card | |---|---|---|---| | Canon EOS R100, JPEG Large Fine | 6000 × 4000 (24.1 MP) | 8.4 MB | 3,600 | | Canon EOS R100, C-RAW | 6000 × 4000 | 15.8 MB | 1,930 | | Canon EOS R100, RAW (CR3) | 6000 × 4000 | 27.2 MB | 1,120 | | Nikon Z50II, JPEG/HEIF fine, Large | 5568 × 3712 (20.9 MP) | 10.0 MB | 2,100 | | Nikon Z50II, JPEG/HEIF normal, Large | 5568 × 3712 | 5.7 MB | 4,200 | | Nikon Z50II, NEF lossless compressed | 5568 × 3712 | 24.4 MB | 763 | | iPhone, Apple ProRAW at 12 MP | 12 MP | about 25 MB | about 1,200 | | iPhone, Apple ProRAW at 48 MP | 48 MP | about 75 MB | about 400 |

The Canon rows come from the EOS R100 instruction manual. The Nikon rows come from the Z50II reference guide, measured with a SanDisk 32 GB card and a 16–50mm lens, dated July 2024. The ProRAW sizes are Apple's own.

Level three is your own average, taken off your own card after a real afternoon of your own shooting. It is the only number that survives contact with the way you actually photograph, and it takes about four minutes to get. Instructions are further down.

Why a 32 GB card never has 32 GB on it

Card makers count in round decimal gigabytes, and SanDisk prints the rule in its own product disclosures: 1 GB = 1,000,000,000 bytes, actual user storage less. So a 32 GB card leaves the factory holding 32,000,000,000 bytes. Your computer and your camera count in binary, where a gigabyte is 1,073,741,824 bytes. Divide one by the other and 32 GB becomes 29.80. Formatting takes a little more for the file tables, and the card reserves some for wear management, which is what "actual user storage less" discloses. Most 32 GB cards report about 29.7 GB free straight out of the packet.

I have had this conversation across a demonstration table more often than any other. The audiobook players I put into people's hands take SD cards, and a caller who has just fitted a brand new 32 GB card and heard the machine announce twenty-nine point seven is, quite reasonably, sure they have been sold a dud. Nothing is faulty. Two counting systems have met, and only one of them was printed on the box.

Two makers, two ways of counting the same card

This one is worth checking on a calculator, because it explains a good deal of disappointment.

Canon divides straight. 8.4 MB per fine JPEG at 3,600 shots multiplies back to 30,240 MB, which is the whole card. Every row of Canon's table lands near 30,000 MB: 15.8 × 1,930 is 30,494, and 27.2 × 1,120 is 30,464.

Nikon does not. Ten megabytes a frame at 2,100 frames comes to 21,000 MB, roughly two-thirds of the card. Lossless NEF is starker still, at 24.4 MB against 763 frames, or 18,617 MB. Nikon's stated file size and Nikon's stated frame count do not multiply back to the card.

I read that gap as deliberate headroom, and Nikon's footnote supports the reading without confirming it: the number of pictures varies with the scene recorded. A frame full of foliage or gravel compresses badly and lands well above the average. A frame of flat overcast sky lands well below. Canon publishes the average and lets you do the division. Nikon publishes the average and then quotes a count that would still hold on a bad day. Shooting Canon, expect fewer frames than the table on detailed subjects. Shooting Nikon, expect more.

What actually sets your average file size

Four things, ordered by how far they move the number.

1. Format. RAW against JPEG is roughly a threefold difference on the same body, 27.2 MB against 8.4 MB on the R100, with Canon's C-RAW sitting between them at 15.8 MB.
2. Compression inside the format. Nikon's fine, normal and basic JPEG at Large size run 10.0, 5.7 and 2.3 MB, from the same sensor at the same resolution. That is nearly four times the frames at the bottom setting.
3. Resolution. 6000 × 4000 pixels on the Canon, 5568 × 3712 on the Nikon. Dropping the Nikon from Large to Medium takes a fine JPEG from 10.0 MB to 6.8 MB.
4. Scene detail. Nobody controls this one, and everybody blames the card for it.

How to find your camera's own average photo size

Four minutes, once, and you can stop reading capacity charts.

1. Format a card in the camera, then shoot a normal session on it. Not a test wall. The subjects you genuinely photograph.
2. Read the frame count off the camera. Say it comes to 214.
3. Put the card in a computer, select the DCIM folder, and read its total size in megabytes. Say 1,930 MB.
4. Divide the megabytes by the frames. 1,930 ÷ 214 is 9.0 MB a frame.
5. Divide 30,000 by that. About 3,300 frames on a 32 GB card, for you, shooting the way you shoot.

Write the answer on the card's plastic case in fine marker. I have been up from this desk twice already this morning for no reason I could name, which is a fair indication of how much of my attention is available for remembering a four-digit number, and precisely why the marker wins.

32 GB in a camera against 32 GB in a phone

The two are not the same quantity, and the search results that sit them side by side cause real confusion.

A 32 GB card in a camera is 30,000 MB of photographs and nothing else at all. A 32 GB phone is an operating system, every installed app, years of messages, downloaded music, and then whatever is left over for pictures. Apple's tech specs carry a footnote saying available space is less and varies, and iOS with its built-in apps takes several gigabytes before you press the shutter once. Settings, then General, then iPhone Storage shows the real figure on your handset, and on a 32 GB phone it is common to find well under 20 GB genuinely free.

No iPhone has ever accepted an SD card, so the question of how many photos 32 GB holds on an iPhone is really a question about free space. Apple does publish two hard numbers for it. A ProRAW file is about 25 MB at 12 megapixels and about 75 MB at 48 megapixels, so 30 GB of free space is about 1,200 ProRAW frames, or about 400 of the 48-megapixel ones. Ordinary HEIF photos are far smaller, and Apple publishes no average for them. I think that is the honest position rather than an omission, because the resolution setting and the scene move it too much to quote a single figure.

SanDisk publishes no photo count for its 32 GB cards either. The only average it commits to print is tucked inside a transfer-speed footnote, where a 4.1 GB batch is described as photos averaging 3.5 MB each. Thirty gigabytes at that rate is about 8,500 pictures.

Why the card fills sooner than you planned

Bursts go first. The R100 fires at about 6.5 frames a second. Hold the shutter down for fifteen seconds of fine JPEGs and you have written roughly 100 frames, about 840 MB, before the thought has caught up with the finger. Canon rates the buffer at about 100 JPEGs, 17 C-RAW frames, or 6 RAW frames, and six RAW frames is under a second of holding the button.

RAW plus JPEG together is the quiet one. Every press writes 35.6 MB on the R100. Your 3,600-frame card has become an 840-frame card, and the setting is often on by default.

Video is the big one, which is why the related searches about video keep turning up next to this question. The per-minute estimates Apple prints under each option in Settings, Camera, Record Video run about 60 MB a minute for 1080p at 30 fps, 170 MB for 4K at 30 fps, and 400 MB for 4K at 60 fps. Set against 30,000 MB, that is roughly eight hours, under three hours, and seventy-five minutes. One afternoon at 4K 60 empties the card. Those estimates shift by phone model, so read the ones on your own screen rather than mine.

The card is nearly full: what to move and what to delete

Copy first, verify second, format third. In that order, every time.

• Copy the whole DCIM folder to the computer. The whole folder, not a selection of images.
• Open several of the copied files from the computer's own drive. A copy nobody has opened is not yet a backup.
• Format the card in the camera rather than in the computer. Camera formatting writes the structure the camera expects, and the SD Association gives away its own SD Memory Card Formatter tool for the same reason.

Leave the folders and index files sitting alongside the images alone. Deleting pictures through the computer while the camera's index survives is how a card ends up reporting free space the camera then refuses to use.

One preference, which I will own as a preference. Weeding frames one at a time on a camera's rear screen is where the mistakes happen, and it is considerably worse for a hand that shakes. A dedicated trash button with a physical confirm beats a swipe on a touchscreen, and I will take the button every time. If your camera offers only the touchscreen, do the weeding on the computer after the copy, where a wrong tap is recoverable.

When a bigger or a faster card is the right answer

Two different problems, two different answers, and people buy the wrong one all the time.

Bigger, for video. This is where 32 GB stops making sense, and the reason sits in the standard rather than the capacity. The SD Association defines SDHC as over 2 GB up to 32 GB on FAT32, and SDXC as over 32 GB up to 2 TB on exFAT. FAT32 cannot hold a single file larger than 4 GB. At the 170 MB a minute Apple quotes for 4K at 30 fps, a clip reaches that ceiling around twenty-three minutes in and the camera splits the recording. At 4K 60 it happens at ten minutes. For long single takes, 32 GB is the wrong tier, and 64 GB is a different file system rather than simply more room.

Faster, for stills. Speed changes nothing about how many photos fit. It changes how quickly the buffer drains between bursts. The SD Association's UHS Speed Class 3 and Video Speed Class 30 both guarantee 30 MB a second sustained; V60 and V90 guarantee 60 and 90, and need a UHS-II card in a UHS-II slot to deliver it. A stalling six-frame RAW burst is a speed problem. A card that says full is not.

Since it will come up: for stills I would rather carry two 32 GB cards than one 64 GB, because a card failure then costs half a day instead of all of it. For video I would not buy 32 GB at all.

Keeping a running number across future shoots

One line per shoot in a notes app: the date, what you photographed, frames taken, gigabytes used. After four or five entries you will hold a personal megabytes-per-frame figure for weddings, or for birds, or for the Saturday market, and those three will not match each other. That figure beats every capacity chart on the internet, this one included, because it was measured on your camera, at your settings, on your subjects.

Common questions people actually ask

How many GB do I need for 500 photos?

For 500 fine JPEGs from a 24-megapixel camera at 8.4 MB each, you need about 4.2 GB. For 500 RAW files at 27.2 MB, about 13.6 GB. For 500 phone photos at SanDisk's 3.5 MB working average, about 1.8 GB. Multiply your own average file size by 500, then add a fifth for headroom.

Is 32 GB enough for photos?

For stills, yes, for most people. A 32 GB card holds around 3,600 best-quality JPEGs or 1,120 RAW files from a 24-megapixel camera, by Canon's figures. It stops being enough if you shoot RAW plus JPEG together, fire long bursts, or record 4K video onto the same card.

How many photos can 32 GB hold on an iPhone?

No iPhone accepts an SD card, so this is a question about free space. Apple publishes 25 MB for a 12-megapixel ProRAW file and 75 MB at 48 megapixels, giving roughly 1,200 or 400 photos per 30 GB free. Ordinary HEIF photos are much smaller; check Settings, General, iPhone Storage for your real figure.

How many photos can 32 GB hold on a Canon camera?

Canon's EOS R100 manual gives 3,600 Large Fine JPEGs at 8.4 MB each on a 32 GB card, 1,930 C-RAW files at 15.8 MB, and 1,120 RAW files at 27.2 MB. Other Canon bodies publish the same style of table in their manuals; a higher-resolution sensor gives proportionally fewer frames.

How many videos can 32 GB hold?

Using the per-minute estimates Apple shows in Settings, Camera, Record Video, 32 GB holds roughly eight hours of 1080p at 30 fps, under three hours of 4K at 30 fps, or about 75 minutes of 4K at 60 fps. On a 32 GB SDHC card, FAT32 splits any single clip at 4 GB.

How can I find my camera’s average photo size?

Shoot a normal session on a freshly formatted card. Note the frame count on the camera, then copy the DCIM folder to a computer and read its total size in megabytes. Divide the megabytes by the frames. That is your average. Divide 30,000 by it for frames per 32 GB card.