SendShrink makes oversized photos fit real upload limits. The free browser tool checks or compresses a JPEG, PNG, or WebP locally with no account or upload. The iPhone app adds Photos-first batches, combined size budgets, saved recipes, and native save/share while keeping originals untouched. A ChatGPT/MCP version handles one image interactively. Output is best effort: a destination may also enforce dimensions, format, or metadata.
Large photos often fail at the last step: an email limit, a support form, or a chat that refuses the attachment.
I built SendShrink around the destination rather than a vague quality slider. You choose a send goal, see the approximate result, then create a smaller copy locally on the iPhone. Originals stay untouched, and the same flow works for repeat batch jobs.
The current tradeoff is deliberate: the estimate is approximate because the final encoded size depends on the image. I prefer showing that uncertainty instead of promising an exact byte target the app may miss.
Which destination or file-size preset would save you the most time?