How do you size proof images so a client proofing gallery loads fast on any connection?

What a proof actually has to do

A proof has one job: let the client decide whether a frame is worth finishing. That means they need to see expression, whether the eyes are open and sharp, whether the composition works, and whether one near duplicate beats another. It does not need to be print ready, it does not need to survive a hundred percent zoom, and it does not need to carry the full detail of the file you will eventually retouch. Sizing proofs starts with accepting that the selection decision is made at screen size, not at pixel level. Related: Streamlining Client Proofing After a Shoot

Uploading full resolution files instead is tempting because it feels safer, but it moves the cost onto the client. A gallery of large originals scrolls slowly, stalls on hotel wifi, and burns through a mobile data plan while someone flicks through frames in a parking lot. Slow galleries produce fewer picks and more abandoned sessions, and a client who gives up halfway through the grid tends to come back with vaguer feedback. Speed is not a technical nicety here, it is part of the quality of the decision you get back.

Keep reading: Streamlining Client Proofing After a Shoot, Why Image Numbers Over Email Fail, Setting Client Expectations for Selections. See how Framepickr helps you photographer client proofing galleries with print-order markup.

A working range for the long edge

For most proofing work, a long edge somewhere between 1600 and 2400 pixels covers the realistic viewing situations. A typical laptop shows a single image in a lightbox at roughly 1200 to 1800 CSS pixels wide, and high density displays render that with about twice the pixel data, so a file near 2000 pixels on the long edge looks crisp without being wasteful. Around 2048 is a comfortable middle that photographers tend to settle on after experimenting. Related: Why Image Numbers Over Email Fail

Going much higher rarely changes a selection. A 4000 pixel proof usually costs three or four times the bytes of a 2000 pixel one and gives the client no new information about whether they like the shot. Going much lower creates its own problems: below about 1200 pixels, judging critical focus and fine expression gets genuinely hard, and you start receiving messages asking for a bigger version of a frame the client is unsure about. Those messages cost more time than the bandwidth ever saved. Related: How Many Proofs to Show a Client

Compression and color settings do more work than pixel count

Pixel dimensions get the attention, but JPEG quality usually decides the file size. Exporting at a quality setting around 70 to 80 typically lands proofs between roughly 200KB and 600KB depending on the scene, and the visible difference against a maximum quality export is close to invisible on a screen at normal viewing distance. Busy frames with foliage, confetti, or heavy grain compress worse than clean studio backgrounds, so check a few of the noisiest images from a session rather than judging by one portrait.

Convert to sRGB before export, every time. Wide gamut files can render flat or oddly desaturated in some browsers and messaging apps, which produces the worst kind of client email: one that says the photos look dull when the files are fine. Apply a small amount of output sharpening after the resize, because downsizing softens detail, and strip metadata you do not need while keeping copyright and contact fields. If you watermark proofs, remember the mark adds contrast edges that compress poorly, so re-check file sizes after adding it. Related: Protecting Your Images While Sharing Them

Thumbnails, load order, and the phone reality

The grid and the lightbox are two different problems. A grid should be built from a separate small derivative, typically a few hundred pixels on the long edge, so the whole page paints quickly and the client can scan the session in seconds. The full proof loads only when an image is opened. Lazy loading below the fold and quietly preloading the next image while the client looks at the current one make a gallery feel instant even when the total payload is large.

Do the arithmetic before you send the link. A gallery of four hundred proofs at half a megabyte each is around two hundred megabytes if someone opens every frame, which is fine over home wifi and unpleasant on a weak cellular signal. The only reliable test is the real one: open a full gallery of the size you actually deliver on your own phone with wifi turned off, scroll it, open ten images, and see how it feels. If you are patient with it and still notice the wait, your client will not be patient at all.