CompressPhotosCompress photos

Compress photos for email Send the whole album in one email.

We size every photo so the set fits under your mail limit.

or drop them here · paste with Ctrl+V

Free · No sign-up · Photos stay on your device

A calm sea with the sun low over the horizonBefore · 3.4 MBAfter · 131 KB
96% smaller3000 × 2000 → 2560 × 1707 px

The rule on this page starts tighter than elsewhere: the whole set held to 18 MB, the long edge capped at 2560 pixels, strong quality, capture information removed. Change any of it in the rail. The total in the headline is what the set weighs, which is the number a mail server will apply its limit to.

Quality
Size per file
Long edge
Format
Metadata
Nothing chosen yet.Auto Encoded on this computer

Keyboard shortcuts

Ctrl/⌘ O
Choose photos
Ctrl/⌘ Enter
Compress (or re-run what changed)
Ctrl/⌘ S
Save the results
Ctrl/⌘ Z
Undo (recipe, own recipes, left out, names)
Ctrl/⌘ Shift Z, Ctrl Y
Redo
1 2 3 4
Light, Standard, Strong, Custom quality
G / T
Grid or table
P R E D
Photo, Recipe, Export, Device panel
[ ]
Move the ceiling line a step down or up
X
Leave the picked photos out, or put them back
Esc
Clear the selection
Space
Pause or resume a running job
\ (hold)
Show the original in the Photo panel
Arrows, Shift+Arrows, Enter
Move, extend, open in the sheet
?
This sheet

Shortcuts never fire while you are typing in a field.

Prepare a set of photographs for an attachment limit: one rule for all of them, and a measured total to check before you send.

What this does

Sending photographs by email fails in a specific way: the message is refused, or it sits in the outbox for four minutes and then is refused. The cause is almost never one enormous file. It is eighteen ordinary ones, each five megabytes, adding up to something no mail server was going to accept.

That makes it a set problem rather than a file problem. This page applies one rule to the whole selection and then tells you what the selection weighs. You compare that against the limit you are up against and either send it or tighten the rule and run it again — the originals are untouched either way, so a second pass costs nothing but time.

Setting the rule

  • The set total is the limit that matters: 18 MB of photos is about 24 MB once a mail program has encoded them, inside a 25 MB limit. Change it on the recipe bar.
  • Capping the long edge is doing most of the work. A 6000-pixel photograph attached to an email is 6000 pixels of nobody's benefit.
  • Strong quality is defensible here in a way it is not for an archive: the recipient is going to look at this on a screen, once, probably on a phone.
  • Capture information starts removed on this page only. A photograph sent outside the household is the one case where the metadata is a disclosure rather than a record.
  • The skip floor is lower here, because a 200 KB screenshot in an email batch is already small enough to leave alone.

What it will open

The same formats as everywhere else on this site: JPEG, PNG and WebP, identified from their leading bytes. Anything else in the selection is counted and reported, and nothing that cannot be handled is silently dropped from the total.

Screenshots are the common surprise. A PNG screenshot of a spreadsheet is often already small, and if it is under the floor it is left exactly as it was and passed through untouched — which is the correct outcome and is stated on its row rather than hidden in the arithmetic.

Questions about long jobs

What limit should I aim at?
Gmail stops at 25 MB for the whole message, and many other services stop between 10 and 25 MB, headers and encoding included. Attachments are encoded on the way out and grow by about a third, so aim the photos' total well under the limit. The safe reading is to treat the smaller figure as the real one, because the limit that matters is the recipient's server, not yours.
Why does this page start with the long edge capped?
Because a photograph attached to an email is going to be looked at on a screen. At 2560 pixels on the long edge it is still larger than almost any screen it will meet, and it is a third of the weight of the file the camera wrote.
Is capture information removed here?
On this page it starts switched on, because a photograph sent to a stranger carries the date, the camera and sometimes the location of the house it was taken in. Everywhere else on this site it starts off. Either way the row says what it weighed.
What does the set total do?
It holds the whole set under one size. Before each photo starts, it is given a share of what is left in proportion to its pixels and is compressed to fit that share; whatever it does not use goes back for the photos after it. The page starts at 18 MB because an attachment grows by about a third on the way out, so 18 MB of photos is about 24 MB in the message: inside Gmail's 25 MB. The meter under the skyline shows the set against 10, 20 and 25 MB, and Try on a sample projects the total before anything runs.
Can I keep each file under a size instead?
Yes, as a ceiling: set a maximum per file in the recipe, or drag the line on the skyline. Each photograph keeps the batch quality if it already fits and is searched down only if it does not; one that cannot get under is marked on its print. For an exact size per photo, switch the size to Target or Range in the recipe bar.

Other jobs

More ways to shrink a photo