clientgallery.io

File size

Why Are My Photo Files So Big?

Four things decide how large a photo file is. Two of them you can change without losing anything a client would ever see. One of them you should not touch at all.

Updated September 2026

The question usually arrives at a bad moment. A drive is full, an upload is crawling, or a client says the gallery will not finish loading on their phone. The file sizes look absurd next to what the job actually is: a few hundred pictures of a family in a park.

A photo file is big for reasons that are easy to name once you know where to look. This page walks the four of them, in the order they matter, then splits them into what you can change without consequence and what you should leave alone. The last part is the one that usually fixes the problem for good: the file you archive, the file a client proofs from and the file you hand over at the end are three different files, and most storage and upload pain comes from treating them as one.

Start with the format, because it decides everything else

The single biggest factor is whether you are looking at a camera RAW file or a JPEG. Adobe states that RAW files will be between two and six times larger than a JPEG file. That is not a small tax. It is the difference between a shoot that fits on a drive and one that does not.

The reason is what each format is for. Adobe describes RAW files as lossless, unprocessed and uncompressed, capturing the data from your camera sensor. Nothing has been thrown away yet, because nothing has been decided yet. The camera's JPEG is the same capture after the camera has made those decisions for you, and Adobe states that it undergoes a lossy compression process on the way.

Adobe is direct about the trade. It calls size the main drawback of shooting RAW, and notes that the files can require additional camera and computer storage space. So the first answer to why your files are big is often simply that they are RAW files, and that is the format working as designed.

FormatWhat Adobe states about itWhere it belongs in your workflow
Camera RAWLossless, unprocessed and uncompressed; two to six times larger than a JPEGYour archive, on your own drives
JPEGSupports up to 24-bit colour and uses lossy compressionProofing, client viewing and final delivery

Bit depth: how much room each pixel gets

Bit depth is how much information the file keeps for each pixel. Adobe states that JPEGs are 8-bit and that RAW files can be 12 and 16-bit. More bits per pixel means more data stored per pixel, across every pixel in the frame.

This is why a RAW file feels disproportionately heavy even at the same pixel dimensions. It is carrying a wider description of every point in the image, which is exactly what gives you room to recover a sky or lift a shadow later.

Bit depth is not a setting to shave for storage reasons. You keep the depth while you are editing and you let the export decide what the client receives. Adobe states that a JPEG supports up to 24-bit colour, which is what a delivered photograph is viewed in.

Compression: the lever you are allowed to pull

Compression is where your export settings live, and it is the one place you can genuinely reduce file size on purpose. Adobe describes what JPEG compression does: it reduces file size by changing the colour values and blocking together groups of pixels.

That has a limit, and Adobe names it. When dealing with very heavily compressed images, the quality will suffer. Adobe's own advice on the subject is to not compress photos or images any more than you need to.

In practice this means compression is a per-destination decision, not a global one. A proof a client scrolls on a phone can take real compression and lose nothing the client would ever notice. A file that is going to a print lab should not be squeezed at all. The mistake is picking one export setting and using it for both.

Pixel count, explained plainly

The fourth factor is how many pixels are in the frame. We are going to explain this one in our own words rather than attribute it, because the published sources we checked discuss pixel count in terms of quality rather than in terms of bytes.

Adobe does state that the number of pixels in a file is directly related to image quality. Adobe also names the operation that changes pixel count: when you add or subtract pixels, that is called resampling, with downsampling for decreasing the count and upsampling for increasing it.

Our own reasoning follows from there. A file is a description of its pixels, so a frame described by more of them has more to store. That is why downsampling an export is an effective way to make a delivered file smaller, and it is also why upsampling is never a fix for anything. Adobe describes the Resample control as what "allows you to adjust the print size and resolution independently, which changes the number of pixels in the image", so a print dimension typed in with resampling switched off is a label rather than a change to the file.

Phone photos are a separate story

If the large files in question came off an iPhone rather than a camera, the format question has a different shape. Apple documents HEIF as the photo format and HEVC as the video format, and states that they offer better compression than JPEG and H.264, so they use less storage space.

Apple states that High Efficiency is the default capture behaviour on supported models. The alternative, Most Compatible, captures in JPEG or H.264 format instead. So a phone that is filling up with unexpectedly large photo files may simply have been switched to Most Compatible at some point.

There is a second trap worth knowing. Apple documents that when you transfer media to a computer over USB, files may be converted automatically to JPEG and H.264, and that enabling Keep Originals prevents that conversion so the original files transfer instead. If your imported phone photos are bigger than the ones on the phone, an automatic conversion on import is a reasonable place to look first.

What is safe to change, and what is not

Here is the whole question compressed into a decision. Read the right-hand column before you touch anything.

ChangeWhat it costsVerdict
Compress the exports a client views on screenNothing visible at sensible settingsSafe, and the first thing to do
Downsample exports meant for screensPixels the screen was never going to showSafe for viewing copies
Delete duplicate exports of the same editNothing, if the master is intactSafe, and usually overdue
Compress a file going to a print labQuality suffers when compression is heavyDo not
Upsample to make a file look higher resolutionSize, with nothing gainedDo not
Delete the RAW files to free a driveEvery future re-edit of that shootNever

One more rule that follows from Adobe's description of JPEG as a lossy format. If you need a smaller delivered file, go back to the master and export again at the size you want. Re-exporting a JPEG from a JPEG puts the image through a lossy process a second time for no reason, when the original is still sitting on your drive.

The real fix: three files, three jobs

Most photographers do not have a file size problem. They have a filing problem that shows up as a file size problem. A single shoot naturally produces three kinds of file, and they have nothing in common except the picture.

  • The archive file. The RAW, or the layered master. Big by design, never sent to anyone, kept on your own storage. Its whole job is to still exist in five years when a client comes back.
  • The proof. The file a client scrolls, compares and picks from. It needs to load instantly on a phone and be sharp enough to judge. It does not need to be printable, and it should not be.
  • The delivery file. The finished, full-resolution export the client keeps. Large, but only handed over once, and only for the frames that were actually chosen.

Once those three are separated, the storage maths stops being frightening. You are not hosting an archive. You are hosting a set of proofs, and moving a delivery across once.

How clientgallery.io splits the same three files

Our plan is one price, 10 $ a month or 100 $ a year, and the split above is built into how it works rather than sold as tiers.

Photos you upload are compressed in the browser into proof JPEGs of about 0.6 MB each before they are hosted, and they stay hosted for as long as the account exists. That figure is the reason a gallery of several hundred frames opens quickly on a client phone: the client is never loading your masters. Under fair use a gallery holds up to 1,000 photos, a paid account holds 250 GB of proofs, and a free account holds 5 GB.

Full-resolution delivery is a separate mechanism on purpose. You upload one full-resolution ZIP per gallery, it stays live for 3 days per handoff, and you can re-upload it any time the client needs it again, within 100 GB of standing ZIPs per account. The heavy files exist for the handoff and then stop consuming anything.

What we do not do is just as relevant to an archiving question. We host JPEGs. We do not warehouse RAW files and we do not host master video. If you were hoping a gallery platform would double as your backup, it should not, and ours does not pretend to. Your masters belong on storage you control, with a copy somewhere else.

Sources

  • Adobe, JPEG vs. RAW (RAW two to six times larger than JPEG; JPEG 8-bit, RAW 12 and 16-bit; RAW lossless, unprocessed and uncompressed; lossy compression process). Fetched 23 September 2026.
  • Adobe, RAW vs. JPEG (RAW captures uncompressed sensor data; size is the main drawback of shooting RAW). Fetched 23 September 2026.
  • Adobe, RAW file format (RAW size can require additional camera and computer storage space). Fetched 23 September 2026.
  • Adobe, JPEG file format (up to 24-bit colour and lossy compression; heavily compressed images suffer in quality; compression changes colour values and blocks groups of pixels). Fetched 23 September 2026.
  • Adobe, How to compress an image (do not compress photos or images any more than you need to). Fetched 23 September 2026.
  • Adobe, How to increase image resolution (number of pixels is directly related to image quality; adding or subtracting pixels is resampling, with downsampling and upsampling; what the Resample control does to print size, resolution and pixel count). Fetched 23 September 2026.
  • Apple, Using HEIF or HEVC media on Apple devices (HEIF is the photo format and HEVC the video format; better compression than JPEG and H.264; High Efficiency is the default on supported models; Most Compatible captures JPEG or H.264; USB transfer may convert automatically unless Keep Originals is enabled). Fetched 23 September 2026.

Frequently asked

Why are RAW files so much bigger than JPEGs?

Adobe states that RAW files will be between two and six times larger than a JPEG file, because RAW is lossless, unprocessed and uncompressed while the camera's JPEG has already been through a lossy compression process. Adobe also states that JPEGs are 8-bit while RAW files can be 12 and 16-bit, so each pixel is described with more data.

Can I compress my photos without ruining them?

Yes, for files a client views on a screen. Adobe describes JPEG compression as reducing file size by changing colour values and blocking together groups of pixels, and warns that when images are very heavily compressed the quality will suffer. Adobe's advice is to not compress photos any more than you need to, so compress viewing copies and leave print files alone.

Should I delete my RAW files to free up space?

No. The RAW is the only file that still holds everything the sensor recorded, and Adobe describes it as lossless, unprocessed and uncompressed. Deleting it saves space today and costs you every future re-edit of that shoot. Free space by removing duplicate exports and by hosting proofs rather than masters.

Why did my iPhone photos get bigger after I imported them?

Apple documents that when you transfer media to a computer over USB, files may be converted automatically to JPEG and H.264, and that enabling Keep Originals prevents that conversion so the original files transfer instead. Apple also states that High Efficiency, which captures HEIF and HEVC, is the default on supported models, while Most Compatible captures JPEG or H.264 instead.

Does making an image smaller in inches make the file smaller?

Not on its own. Adobe states that adding or subtracting pixels is an operation called resampling, and describes the Resample control as what allows you to adjust the print size and resolution independently, which changes the number of pixels in the image. With resampling off you are relabelling. Reducing the pixel count is downsampling, which is the change that actually reduces what the file has to store.

How big are the photos in a clientgallery.io gallery?

Photos you upload are compressed in the browser into proof JPEGs of about 0.6 MB each before they are hosted, and they stay hosted for as long as the account exists. Under fair use a gallery holds up to 1,000 photos, a paid account holds 250 GB of proofs and a free account holds 5 GB.

How do I deliver full-resolution files if the gallery holds compressed proofs?

Full-resolution delivery is a separate paid mechanism. You upload one full-resolution ZIP per gallery, it stays live for 3 days per handoff and can be re-uploaded any time, within 100 GB of standing ZIPs per account. We host JPEGs and do not warehouse RAW files or master video, so your archive stays on storage you control.

Your client galleries, under your name

Branded galleries, client selections and a Lightroom Classic workflow. Start with your first gallery, then compare the current plan. Full-resolution delivery is a separate handoff with its own limits and conditions.

Create your studio

Related guides

Why Are My Photo Files So Big?