Guide

Image Compression for Photographers

By the Smol team11 min read

Start here: Lightroom Classic and Capture One already do most of this. Both export JPEG at a chosen quality, resize on the long edge, and let you decide which metadata travels. If your delivery runs through either one, your compression problem is an export-preset problem, and the useful thing this page can give you is the numbers to set those presets against.

The part that is worth reading carefully is metadata. Stripping metadata removes your IPTC Copyright Notice, Creator and Credit Line along with the camera serial number, and most tools that advertise “strips metadata for privacy” do not distinguish between the two. Ours strips by default. That is the wrong default for a photographer and we would rather you know before you run it on 600 files.

We build Smol, a Mac compression app. It reads RAW (CR2, NEF, ARW, DNG) but does not develop it, and it is not a Lightroom replacement. Every platform and lab spec below was read from the vendor’s own documentation on 26 September 2026 and is quoted.

What does your client gallery platform actually accept?

Wildly different things, and two of them will re-encode your file without telling you in the upload dialog.

PlatformPer-file capFormatsDoes it touch your file?
Pixieset100 MB JPEG/PNG, 85 MB GIF, 100 MB RAW on select plansJPEG, PNG, GIF, RAW. No TIFF. Print products are JPEG only“Original resolution files provide the photo exactly as uploaded, with no compression or resizing.”
ShootProof50 MB and 100 MPJPEG only, sRGB requiredResizes the gallery display copy above 3,000 px, stores your original untouched
Pic-Time100 MB, 12,000 × 12,000 pxJPEG and GIF only. No PNG, no TIFF, no RAWPlan-dependent JPEG optimizer may recompress. “this does not alter dimensions or dpi”
SmugMug500 MiB and 4 gigapixels, RAW 3 GBJPEG, GIF, PNG, HEIC. No TIFF. Prints are JPEG onlyOver the limit it will “resample it … or recompress it”. HEIC originals are discarded
CloudSpot150 MB, 18,000 px long edge, 250 MPFree plan JPEG only; paid plans add PNG, TIFF, PSD, Ai, GIF, PDFDelivers the original file type, but “any resizing will result in the file being converted … as a JPEG”
Read from each vendor's own help documentation on 26 September 2026. Article timestamps range from February to September 2026.

Two details worth acting on. SmugMug converts HEIC on upload and does not keep the original: “We don’t retain a copy of the original HEIC file, so if you try to download the original at a later date, you’ll receive a high-quality JPEG instead.” If a phone is your second camera, convert HEIC yourself first. And CloudSpot is the only one of the five that accepts TIFF, which matters for 16-bit deliverables.

Pixieset publishes its download rungs, a useful check on what is worth uploading: “high-resolution (3600px or original resolution) or web size (640px, 1024px, or 2048px)”. If the client’s top tier is 3,600 px, a 6,000 px upload buys storage cost and nothing else.

Which metadata has to survive the export?

Your copyright fields. This is where generic compression advice actively harms photographers: “strip metadata” is treated as an unambiguous good in every web-performance article ever written, and for a photographer it deletes the record of who made the picture.

The current IPTC Photo Metadata Standard is version 2025.1, revision 1, dated 26 November 2025. The fields that carry rights information, with their exact official names:

IPTC propertyXMP nameWhat the standard says it holds
Creatordc:creator“the name of the photographer, but in cases where the photographer should not be identified the name of a company or organisation may be appropriate”
Copyright Noticedc:rights“any necessary copyright notice … should identify the current owner of the copyright”
Credit Linephotoshop:Credit“The credit to person(s) and/or organisation(s) required by the supplier of the image to be used when published”
Creator’s Contact InfoIptc4xmpCore:CreatorContactInfo“all necessary information to get in contact with the creator of this image”
Web Statement of RightsxmpRights:WebStatement“URL referencing a web resource providing a statement of the copyright ownership and usage rights”. Labelled “Copyright Info URL” in tools
Digital Source TypeIptc4xmpExt:DigitalSourceType“The type of the source of this digital image”. Added 2009; vocabulary updated 2022 to describe AI-generated content
IPTC Photo Metadata Standard 2025.1 rev 1 (2025-11-26). Creator, Copyright Notice and Credit Line are IPTC Core; Digital Source Type and Web Statement of Rights are IPTC Extension.

Version 2025.1 added four properties for AI-generated content: AI System Used, AI System Version Used, AI Prompt Information and AI Prompt Writer Name. Editorial clients will start asking about those.

Lightroom Classic gets this right, with options that are not obviously named. Adobe’s own export documentation lists four choices in the Metadata panel’s Include menu: Copyright Only, Copyright & Contact Info Only, All Except Camera Raw & Camera Info (everything except EXIF camera data such as Exposure, Focal Length and Date Time), and All.

The control worth knowing about is separate from that menu. Remove Location Info “removes GPS metadata from photos, even if All Except Camera Raw & Camera Info or All is chosen from the pop-up menu.” It is an override, not another toggle, which is exactly what you want: full IPTC rights data out, GPS coordinates of the client’s house gone, one checkbox.

Capture One exposes the same idea as removals in the Process Recipe. Its documentation names five: “Rating and Color Tag, Copyright, GPS Coordinates, Camera Metadata (EXIF), and All other metadata (IPTC)”, with everything except ratings and colour tags included by default.

One command tells you what actually came out, the same one we use in what EXIF data actually contains and removing EXIF data on Mac:

exiftool -G1 -a -s -Creator -Copyright -CopyrightNotice \
  -Credit -By-line -GPSPosition -SerialNumber export/*.jpg

Note how thoroughly the same information is duplicated: in one test file the photographer’s name appeared three times, as EXIF Artist, IPTC By-line and XMP dc:creator. Clearing one does not clear the others, which cuts both ways.

Does your copyright survive once the photo is online?

Often not, and the standards body that defines the fields has measured it. IPTC has run a recurring test on whether platforms preserve embedded metadata, in 2013, 2016 and Spring 2019. The 2016 round’s finding was blunt: “Ten sites removed at least some metadata when images were downloaded to a desktop environment” and “Only one social media site, Behance, received favorable results for retaining and displaying embedded data.”

Note the age. Spring 2019 is the most recent systematic study IPTC lists, so treat per-platform results as historical. The durable conclusion is structural: embedding your Copyright Notice is necessary and not sufficient, because you do not control the re-encoder at the other end.

One gallery vendor documents its behaviour, and only one. Zenfolio extracts IPTC on upload and states that “Unlike EXIF data, which is not supported by Zenfolio, IPTC is not recorded automatically by your camera”, listing five fields it recognises: Headline, Object Name, Caption, Keywords and Copyright notice. Pixieset, ShootProof, Pic-Time, SmugMug and CloudSpot say nothing about metadata in their file-requirement documentation; we checked, and the word does not appear.

The print copy should barely be compressed at all, and the labs say so themselves in language that surprises people.

Bay Photo’s file preparation guidelines are explicit: “We recommend that you DO NOT resize your files for ordering.” They publish no maximum file size. They constrain everything else: JPEG, TIFF or PNG with JPEG preferred, 8-bits per channel only (“16 or 32 bit files will become corrupted when imported into our systems”), RGB only, layers flattened, alpha channels removed, colour profile embedded, and “a resolution of 200-300 PPI at print size”.

WHCC gives the single most useful number in this whole article for anyone wondering how hard they can push JPEG for print: “We recommend saving your files at a JPEG quality of 10 or higher in Photoshop, 90% in Lightroom, or the equivalent in your editing tool.” They print most products at 300 DPI and resize submissions automatically, they accept P3 as well as Adobe RGB and sRGB, and engraving files need at least 1,200 PPI.

CopyLong edgeQualityColourMetadata
Print lab submissionNative. Do not resizeJPEG 90% in Lightroom or higher, or TIFFEmbedded profile, 8-bit, RGBAll, including IPTC rights
Client gallery originalNative, or the platform’s top download tierJPEG 85–90%sRGB unless the platform accepts moreAll except GPS
Client gallery web tierWhat the platform serves (640–2048 px on Pixieset)Platform’s choice, usuallysRGBPlatform-dependent, usually lost
Your own portfolio siteMatch the CSS slot, 2× for RetinaAVIF or WebP, quality 65–80sRGBCopyright Only
Stock agency submissionNative, above the minimum megapixelsHighest. Adobe Stock: “Don’t: Compress files too much”sRGBTitles and keywords preserved

The stock row has hard numbers behind it. Adobe Stock requires JPEG in sRGB, a 4 MP minimum, 100 MP maximum and 45 MB maximum file size, and preserves titles and keywords added in Lightroom or Bridge. Shutterstock also sets a 4 MP floor, caps browser uploads at 50 MB, and converts everything to JPEG on approval. A 45 MB ceiling alongside “Don’t: Compress files too much” is a narrow target on a 60-megapixel file, and one of the few places a real file-size control beats a quality slider.

Where does a compression app fit if Lightroom already exports?

In the gaps, and the gaps are specific. Three of them come up repeatedly.

Formats your developer will not write. For a portfolio site you want AVIF or WebP, and at matched quality the difference is not small: on our Kodak test image, measured for the compressor roundup, 91,868 bytes of JPEG became 63,206 as WebP and 48,230 as AVIF. On a screenshot-style image the AVIF was 66% smaller while scoring higher on SSIM.

A hard file-size target. Lightroom’s export panel does offer Limit File Size To for JPEG, which Adobe documents as specifying “a maximum file size for the exported file”. Outside JPEG there is nothing. Smol’s neural encoder takes a targetKb between 4 and 4,096 for AVIF, WebP, JPEG or PNG. Asked for an AVIF under 100 KB from a 352,861-byte JPEG, it returned 51,140 bytes.

Mixed piles that are not a catalogue. The folder someone AirDropped you, phone HEICs from the second shooter, a contract PDF, forty screenshots for a tutorial. None of it belongs in a catalogue and all of it needs the same treatment.

The default you must change. Smol’s image defaults are quality 75, a 2,000 × 2,000 fit ceiling, and metadata stripping on. For a web asset that is correct. For your own work it deletes your Copyright Notice, Creator and Credit Line along with the camera serial. Turn it off before the first batch, and verify with the exiftool line above rather than trusting the setting.

One limit stated plainly: we read RAW, including CR2, NEF, ARW and DNG, and we do not develop it. No white balance, no highlight recovery, no lens profile. Pointed at untouched RAW you get a JPEG made from the camera’s own interpretation, which is not what you shot RAW for.

When is Smol the wrong tool for photography work?

Four cases, and the first covers most professional delivery.

Your delivery runs through Lightroom or Capture One. Build an export preset and stop. It resizes, sets quality, chooses which metadata travels, and it is already open. An export preset is also reproducible in a way a drag-and-drop pass is not.

The files are going to a print lab. Bay Photo tells you not to resize. WHCC resizes for you at 300 DPI. Compression is the wrong instinct at the point where you are paying for ink.

You want provably lossless optimization. ImageOptim is free and the only tool in our roundup that produced pixel-identical output, verified at absolute error zero. On a 30-file batch it saved 5.8%, which is what honest lossless looks like.

You need RAW development, culling, or a catalogue. We are none of those things and will not become them.

Where a local app earns the $29: AVIF and WebP for your own site, a real byte target, phone and screenshot piles that never enter a catalogue, and a Finder right-click for the one-file-right-now case. Nothing is uploaded, which matters when the folder is a client’s wedding. Smol is $29 once. Adjacent guides: every method for compressing images on Mac and converting HEIC on Mac. For the privacy side of the same operation, see stripping GPS from photos.

The sibling vertical pages: web developers, real estate listings, podcasters and legal and HR teams.

Frequently asked questions

Does compressing a photo remove my copyright information?

It can, and many tools do it by default. Your rights information lives in IPTC fields including Creator, Copyright Notice, Credit Line and Web Statement of Rights, and a generic strip-metadata setting removes them along with the camera serial. In Lightroom Classic choose Copyright Only or Copyright & Contact Info Only in the export Metadata panel, then verify with exiftool.

How do I remove GPS from client photos but keep my copyright?

In Lightroom Classic, set the export Metadata Include menu to All Except Camera Raw & Camera Info or All, then tick Remove Location Info. Adobe documents that this checkbox removes GPS metadata even if those menu options are chosen, so it acts as an override. Capture One exposes a separate GPS Coordinates toggle in the Process Recipe metadata list alongside Copyright and Camera Metadata.

What JPEG quality is safe for a print lab?

WHCC recommends saving at a JPEG quality of 10 or higher in Photoshop, 90% in Lightroom, or the equivalent. Bay Photo goes further and recommends you do not resize files for ordering at all, targeting 200 to 300 PPI at print size, 8 bits per channel, RGB only, layers flattened and the colour profile embedded. Print is the wrong place to economise on bytes.

What is the file size limit for uploading to a client gallery?

It varies. Pixieset accepts JPEG and PNG up to 100 MB, ShootProof 50 MB and 100 megapixels, Pic-Time 100 MB at up to 12,000 by 12,000 pixels, CloudSpot 150 MB, and SmugMug 500 mebibytes. Formats differ more than sizes: ShootProof is JPEG only, Pic-Time takes JPEG and GIF only, and CloudSpot alone accepts TIFF.

Do photo platforms strip metadata from uploads?

IPTC has tested this periodically, and its 2016 round found that ten sites removed at least some metadata when images were downloaded to a desktop, with only Behance scoring favourably. The most recent systematic IPTC study is Spring 2019, so treat per-platform results as historical. Among gallery hosts, Zenfolio is the only one that documents its policy: it reads and retains IPTC and does not support EXIF.

Can Smol replace Lightroom for exporting client galleries?

No, and it is not trying to. Smol reads RAW including CR2, NEF, ARW and DNG but does not develop it, so there is no white balance, highlight recovery or lens correction. What it adds is AVIF and WebP output for your own site, a hard file-size target between 4 and 4096 KB, and mixed folders that never enter a catalogue.

Keep reading