Phone cameras now shoot 12–48 megapixel photos that weigh 5–15 MB each. Emails bounce over 25 MB, and most online forms — job applications, insurance claims, marketplace listings — cap uploads at 2–5 MB per file. The result is a daily, avoidable failure: a photo that won't send, a form that rejects the file, a website that crawls. The fix is to right-size images before you send them, and it takes seconds once you know the numbers.
The two levers: dimensions and compression
File size is driven by two things: the number of pixels and how efficiently they're encoded. Resizing reduces pixels; compression reduces how many bytes each pixel costs. For most purposes you need both — a 4000 px photo compressed aggressively still starts at several MB, while the same photo resized to 1600 px and compressed normally lands around 300–800 KB. The order matters: resize first, then compress, because compressing a 4000 px image then shrinking it wastes the effort on pixels you're about to throw away.
The numbers that work
- Email attachments — resize to 1600 px on the longest edge and compress to JPG quality ~80. A photo that was 8 MB becomes 400–800 KB, emails instantly, and looks identical on any screen.
- Job applications and portals — check the stated limit (commonly 2–5 MB), then target half of it. Resize to 1200–1600 px and compress to be safe.
- Websites — a 2000 px hero or 1200 px content image at moderate compression is the sweet spot; anything larger is wasted bandwidth for most layouts.
- Print — don't resize below 300 DPI at the printed size. A 6-inch-wide print needs 1800 px; keep the original for anything going to a printer.
Keep the original
Never overwrite your only copy with a resized one. You can always downscale again later, but you can never recover the pixels you've thrown away. Save resized versions as new files, and keep the camera original in a folder.
A practical example: a real-estate agent needs to send six room photos to a client. Each camera original is ~9 MB — 54 MB total, dead on arrival in Gmail's 25 MB limit. Resizing each to 1600 px and compressing to quality 80 brings them to ~500 KB each: 3 MB total, under any limit, and the client can't tell the difference on a phone or laptop. That's the entire job of image resizing for everyday life.
Right-size an image now
ForgePlug's Image Resizer handles longest-edge resizing and social presets, and Image Compressor shows a live before/after size comparison — both in your browser, no uploads.
Open Image ResizerWhy "quality 80" means something different in every tool
The JPEG quality slider isn't a standardised measurement — it's not defined by the file format, only by convention. Each piece of software maps its own 0–100 scale to its own internal compression settings, so "quality 80" in one compressor can produce a visibly different result, at a different file size, than "quality 80" in another. Treat the number as relative within one tool, not as a portable setting to replicate elsewhere — compare the actual output visually and by file size rather than assuming the same number means the same thing everywhere.
The sideways-photo bug
Phone cameras frequently save a photo's actual pixel data in landscape orientation regardless of how the phone was physically held, then store a separate EXIF "orientation" flag that tells a viewer to rotate the image on display. Most modern software reads that flag correctly and shows the photo right-side up — but some resizing and compression tools ignore it, process the raw landscape pixel data as-is, and bake in the wrong orientation. The photo looked correct in your gallery app but comes out genuinely sideways after processing. If a batch of resized images comes out rotated, this EXIF handling — not the resize settings — is almost always the cause.