“Make the image smaller” means three different jobs. Compressing reduces bytes. Resizing changes pixel dimensions. Converting changes the file format. Using the wrong one wastes time and can wreck quality—especially when a portal rejects a 6 MB photo that is already only 800 pixels wide because it is still an uncompressed PNG.
This guide helps you pick the right ToolsInFlow tool on the first try.
The three jobs in plain language
| Job | What changes | Typical tool |
|---|---|---|
| Compress | File size (KB/MB), mostly by quality/encoding | Compress Image |
| Resize | Width × height in pixels | Resize Image |
| Convert | Format: JPG, PNG, WebP, SVG, etc. | Converters / to WebP |
You often combine them: resize a 4000 px phone photo down to 1600 px, then compress, then convert to WebP for a website.
Decision tree
- Portal says “max 500 KB” and the photo is already a reasonable width → compress first.
- Portal says “max 2000 px on the long edge” → resize first, then compress if still heavy.
- Site or CMS wants WebP → convert after you are happy with dimensions and quality.
- You need transparency → stay on PNG (or WebP with alpha where supported); do not flatten to JPG unless you accept a solid background.
- You need a scalable logo → JPG to SVG / Image to SVG, not compress.
When compression is enough
Compression shines for camera JPGs that are sharp but heavy. Social uploads, job portals, and WhatsApp-bound images often need fewer bytes, not fewer pixels.
Watch for:
- Soft text on screenshots—raise quality or resize less aggressively
- Banding in gradients—stop crushing quality
- Repeated compress cycles—always start from the original when possible
Read the longer walkthrough: How to compress an image without losing quality.
When you must resize
A 12 MP photo emailed into a form that displays at 400 px wide is wasted bandwidth. Resize to the display size (or 2× for sharp screens), then compress lightly.
Resize also fixes “dimension too large” errors that compression alone cannot fix. If width is 6000 px, no quality slider will satisfy a “max 2000 px” rule.
Crop first when the subject is tiny in a wide frame—Crop Image then resize—so you do not spend pixels on empty walls.
When conversion is the real fix
- PNG product shot with no transparency needed → PNG to JPG or WebP for size
- JPG logo that must stay sharp on retina headers → consider SVG tracing if the graphic is flat
- WebP rejected by an older email client → WebP to JPG
- Mixed gallery formats → standardize to WebP for web, keep JPG masters offline
Format guides: JPG vs PNG vs WebP and JPG to SVG converter free.
Example workflows
University portal, 2 MB limit, photo is 5 MB at 4032 px: Resize long edge to ~2000 px → compress to under 2 MB → upload. Converting to PNG would make this worse.
Shopify-style product image, needs transparent background: Remove background → export PNG → compress carefully or use WebP if the stack supports alpha.
Blog hero that feels slow on mobile: Resize to content width (for example 1600 px) → convert to WebP → keep JPG fallback if your theme needs it.
Flat logo only available as JPG: Try SVG conversion; if the trace is noisy, keep a high-quality PNG instead of forcing SVG.
Mistakes that look like “the tool failed”
- Converting a photo to PNG and wondering why the file grew
- Compressing a 200 px icon until it looks blocky instead of exporting a clean asset from design software
- Resizing upward to “add quality”—upscaling does not invent detail
- Chaining five compress passes on the same download
How to read portal error messages
- “File exceeds 2 MB” → compress (and resize if the photo is still multi-thousand pixels wide).
- “Image dimensions too large” → resize; compression will not change width/height enough.
- “Invalid file type” → convert to the listed type (often JPG or PDF), not another random format.
- “Upload failed” with no detail → open the file locally, check size and type, try a smaller resize, then retry.
Write down what the portal accepted when it works. That note saves the next upload for the same site.
A simple default for phone photos
For most forms that want a photo of a document or a headshot: crop → resize long edge to about 1600–2000 px → compress until under the MB limit → upload. Convert only when the form names a format. That default prevents the two classic failures: enormous PNGs and tiny, over-crushed JPGs.
Related ToolsInFlow tools
Pick the job by the error message and the destination—not by whichever button you used last week. One clear step (or two in the right order) beats a pile of random exports.