What this calculator does
The Storage Needed for Photos & Videos Calculator estimates how much disk, cloud, or memory-card space your media library requires. By combining the number of photos, the average size of each photo, the total minutes of video, and the data rate per minute of video, it returns a single total in gigabytes (GB) — perfect for choosing an SD card, external drive, or cloud plan before you run out of room.
How to use it
Enter four values: the number of photos you expect to keep, the average size of one photo in megabytes (MB), the total length of your video footage in minutes, and how many MB each minute of video consumes. The calculator multiplies and sums these, then divides by 1024 to convert megabytes to gigabytes. It also breaks down how much space photos versus videos take so you can see what dominates your storage.
The formula explained
The math is straightforward:
$$\text{Total GB} = \frac{\text{photos} \times \text{MB per photo} + \text{video minutes} \times \text{MB per minute}}{1024}$$We use 1024 MB per GB (the binary convention used by most operating systems). Typical references: a smartphone JPEG is roughly 2–5 MB, a high-resolution RAW photo 20–50 MB, 1080p video about 100–130 MB/min, and 4K video roughly 350–400 MB/min.
Worked example
Suppose you have 1,000 photos averaging 4 MB each, plus 60 minutes of 1080p video at 100 MB/min. Photo storage = \(1{,}000 \times 4 = 4{,}000\) MB. Video storage = \(60 \times 100 = 6{,}000\) MB. Total =
$$10{,}000 \text{ MB} \div 1024 \approx 9.77 \text{ GB}$$A 16 GB card would comfortably hold this with room to spare.
Typical File Sizes by Photo and Video Format
Before you can size a drive you need a realistic average file size. The figures below are nominal defaults for consumer and prosumer cameras — the sizes a device tends to produce at its factory settings — not measurements of your own library. Real files vary a lot with scene detail: a photo of a blue sky compresses to a fraction of a photo of autumn leaves, and a locked-off interview shot uses far less bitrate than handheld footage of moving water.
| Image type | Typical size each | Notes |
|---|---|---|
| Phone JPEG, 12 MP | 2–5 MB | Most common smartphone default |
| Phone HEIC, 48 MP | 3–8 MB | HEIC packs more pixels into a similar size |
| JPEG from a mirrorless/DSLR, 24–45 MP | 8–20 MB | Fine/large quality setting |
| RAW, APS-C or full-frame | 20–50 MB | 14-bit uncompressed sits at the top of the range |
| Scanned photo or TIFF, 300–600 dpi | 30–80 MB | Uncompressed 16-bit scans can exceed this |
| Video format | Approx. MB per minute | Approx. GB per hour |
|---|---|---|
| 720p30 | 45–60 | 2.6–3.5 |
| 1080p30 | 90–130 | 5.3–7.6 |
| 1080p60 | 160–200 | 9.4–11.7 |
| 4K30 | 350–400 | 20.5–23.4 |
| 4K60 | 440–500 | 25.8–29.3 |
| ProRes, log or other intraframe codecs | 1,500–6,000 (1.5–6 GB) | 90–360 |
Codec matters as much as resolution. At equal perceived quality, HEVC/H.265 produces roughly half the file size of H.264 — so a phone set to "High Efficiency" may record 4K30 near 350 MB/min while the same phone in "Most Compatible" (H.264) mode lands closer to 700 MB/min. If you know your camera's bitrate in megabits per second, convert it directly rather than using a table value:
$$\text{MB per minute} = \frac{\text{Mbps} \times 60}{8}$$
A 100 Mbps 4K mode therefore writes about \(100 \times 60 \div 8 = 750\) MB per minute — well above the table's consumer figures, which is normal for cameras with a high-bitrate "All-I" or "Fine" setting. The most accurate approach is always to check a handful of your own existing files and use their average as the input.
Storage Needs Across Common Scenarios
The table below runs five realistic libraries through the same formula:
$$\text{Total GB} = \frac{ (\text{Photos} \times \text{MB each}) + (\text{Minutes} \times \text{MB per minute})}{1024}$$
Video rates used: 1080p30 at 110 MB/min, 4K30 at 375 MB/min, 4K60 at 470 MB/min. The last column adds 20% headroom and then rounds up to the next capacity actually sold — remembering that a card's advertised size is decimal, so it delivers roughly 7% less than its label.
| Scenario | Photos | Video | Photo GB | Video GB | Total GB | +20% headroom | Suggested size |
|---|---|---|---|---|---|---|---|
| Casual phone user, one year | 2,000 × 3 MB | 30 min 1080p30 | 5.86 | 3.22 | 9.08 | 10.9 | 32 GB |
| Family vacation | 800 × 4 MB | 60 min 4K30 | 3.13 | 21.97 | 25.10 | 30.1 | 64 GB card |
| Wedding shoot, RAW + video | 2,500 × 30 MB | 90 min 4K30 | 73.24 | 32.96 | 106.20 | 127.4 | 256 GB |
| Video creator, one month | 200 × 5 MB | 300 min 4K60 | 0.98 | 137.70 | 138.67 | 166.4 | 256 GB |
| Scan & archive project | 10,000 × 8 MB | none | 78.13 | 0.00 | 78.13 | 93.8 | 128 GB |
Two details are worth pulling out of the table. The wedding row needs 127.4 GB after headroom, which looks like a 128 GB card — but a 128 GB card offers only about 119 GiB of usable space, so it would overflow mid-day. That is the single most common sizing mistake, and the reason the suggestion jumps to 256 GB. The creator row shows the opposite lesson: the stills are rounding error (under 1 GB) while 4K60 footage accounts for 99% of the requirement. Whenever a project includes more than a few minutes of high-resolution video, sizing the drive is really a video question, and refining your MB-per-minute figure matters far more than refining the photo count.
Choosing Your Drive or Card Size
The calculated total is the floor, not the answer. Use these steps to turn it into a purchase:
- Add 15–20% headroom. You will shoot more than planned, edits and exports create second copies, and catalog software writes previews and sidecar files that can add 5–15% on their own. Multiply your total by 1.2 before shopping.
- Round up to a capacity that exists. Cards and drives are sold at 32, 64, 128, 256 and 512 GB, then 1, 2 and 4 TB. There is nothing between them, and the per-gigabyte price usually falls as you go up a tier — buying one size larger is often only slightly more expensive.
- Account for decimal-versus-binary shrinkage. A 1 TB drive reports about 931 GiB, and a 128 GB card about 119 GiB. If your headroom-adjusted figure lands within ~10% of a capacity label, take the next size up rather than gambling on the margin.
- Keep SSDs below about 80% full. Flash drives need free blocks for wear levelling and garbage collection; a nearly full SSD can slow down noticeably on sustained writes, which is exactly when you are offloading a card. Treating 80% as your practical ceiling means dividing your requirement by 0.8 — a 400 GB library really wants a 500 GB or larger SSD.
- Plan for the 3-2-1 backup rule. Three copies of the data, on two different types of media, with one copy offsite. This multiplies your requirement — a 500 GB library implies roughly 1.5 TB of total capacity across working drive, local backup and cloud or offsite disk. Budget for that up front; a single drive holding the only copy of a library is a single point of failure, and consumer drives do fail.
- Check write speed, not just capacity, on memory cards. Capacity determines how long you can record; sustained write speed determines whether you can record at all. Under the SD Association's Video Speed Class marking (an international specification, used worldwide), V30 guarantees 30 MB/s sustained and is the usual minimum for 4K, while V60 and V90 (60 and 90 MB/s) are needed for high-bitrate 4K, 8K, or 10-bit and All-I codecs. Always confirm the minimum class your specific camera lists for the mode you intend to shoot.
A useful sanity check while shooting: divide the card's usable space by your MB-per-minute rate to get recording time. A 128 GB card (≈119 GiB ≈ 122,000 MB usable) at 4K60's ~470 MB/min holds roughly 260 minutes — about four and a quarter hours, before any stills. Knowing that number stops you from discovering the limit halfway through an event.
Finally, two habits that reduce the storage question rather than answering it: switch the camera to HEVC/H.265 and HEIC if your editing software supports them, which roughly halves new files at the same quality; and cull before you archive, since deleting obvious rejects on import typically removes 20–40% of a shoot's frames at no cost to the final work.
FAQ
Should I use 1000 or 1024 MB per GB? This tool uses 1024 (binary GiB) to match how Windows, macOS, and most devices report free space. Drive manufacturers often advertise 1000, so real usable capacity is slightly lower.
How big is a typical photo? Compressed phone JPEGs are about 2–5 MB; RAW files can be 20–50 MB. Use the size shown in your gallery for accuracy.
Should I add a buffer? Yes — leave 10–20% free for the operating system, future shots, and editing scratch files to keep performance smooth.