Why photo attachments keep bouncing
Modern phone cameras produce images 4,000 pixels wide or more, weighing several megabytes each. Attach five or six and you sail past the 20–25 MB ceiling most mail providers enforce, so the message bounces or crawls into the recipient’s inbox. The fix isn’t a desktop app or a cloud-transfer link — it’s smaller dimensions. A photo resized to around 1,200 pixels on its long side still looks sharp on any screen while weighing a small fraction of the original; the extra pixels a full-resolution photo carries are simply invisible in an email window.
Step by step
- Open the Resize Image tool on SafeFileConvert in whatever browser you already use. It behaves the same on Windows, Mac, Linux, and Chromebooks, and there’s no download, extension, or sign-up involved.
- Set a maximum width in pixels; around 1,200 px suits most email photos. Aspect ratio is preserved automatically, and any image already smaller than your limit keeps its original dimensions — the tool never stretches a picture upward, since upscaling only adds blur.
- Pick an output format and a quality level. JPEG with the quality slider around 80% is a sensible default for photographs; the slider runs from 10 to 100% and affects JPEG and WebP, while PNG is lossless, so with PNG the dimensions do all the work.
- Drop the whole batch onto the dropzone. Each image reports its new dimensions and file size as it finishes, and you can keep queuing more files while earlier ones are still processing.
- Download the resized photos individually, or grab everything as one ZIP and attach that to your message.
Resizing is not the same as a KB cap
Smaller dimensions and lower quality both shrink files, but neither guarantees a specific kilobyte figure. For email that’s fine — you only need the total to be noticeably lighter, and the per-file size readout confirms it. If you’re instead facing a form with a hard rule like “under 200 KB,” the compress-image-to-exact-size tool on this site is built for exactly that job: it adjusts compression until each file lands beneath the number you type.
Everything happens on your own computer
The decoding, scaling, and re-encoding all run on a canvas inside a Web Worker — a background thread of your own browser. No photo crosses the network at any point, so family pictures and work screenshots stay on your machine until you attach them to an email yourself. The background thread has a practical benefit too: the page stays responsive while a large batch grinds through, instead of freezing until the work is done.