A form wants 100 KB and your photo is 4 MB? Learn how resizing, compressing and changing format differ, which size suits each destination, and the exact order of steps that cuts kilobytes without visible damage.
You can reduce image file size in three ways: lower the pixel dimensions (resizing), lower the compression quality, or switch to a more efficient format. Taking a 4 MB, 4000 × 3000 phone photo down to 1600 pixels wide and saving it at around quality 80 typically lands it between 200 and 450 KB, with no difference you can see on a screen. When a form sets a hard limit such as 100 KB, cut the dimensions first and the quality second. And if a photo was accidentally saved as PNG, converting it to JPG alone can save several megabytes.
Each step has its own tool: the image resizer for dimensions, the image compressor for quality and target sizes, PNG to JPG for photos stuck in the wrong format, and the image cropper for trimming wasted edges. For a website, JPG to WebP gives the same look in fewer bytes. Below is when to use each one, and in which order.
The space a photo takes on disk is roughly the product of two things: how many pixels it has, and how many bytes each pixel costs after compression. Dimensions set the first; quality and format set the second. Every shrinking technique turns one of those three dials.
Halve the width and the height and you are left with a quarter of the pixels, and roughly a quarter of the weight. The 12 megapixels a phone captures are far more than any screen needs.
| Dimensions (px) | Pixel count | Share of 12 MP | Typical use |
|---|---|---|---|
| 4000 × 3000 | 12,000,000 | 100% | Camera output, printing |
| 2000 × 1500 | 3,000,000 | 25% | Archive copy, large displays |
| 1600 × 1200 | 1,920,000 | 16% | Email, website content |
| 1080 × 810 | 874,800 | 7.3% | Social media feeds |
| 600 × 800 | 480,000 | 4% | Application-form portraits |
In JPG and WebP, the quality number controls how aggressively fine detail is rounded off. In practice, the difference between 95 and 80 is almost invisible at normal viewing size, yet the file typically shrinks by close to half. Below about 70, banding creeps into flat areas such as sky, and smudges appear around text. The compressor's default of 82 is a safe starting point for most photos.
The same photo saved as PNG weighs several times more than as JPG, because PNG is lossless and cannot squeeze the natural grain of a photograph. Pictures saved from screenshots are often bloated for exactly this reason. Files also carry EXIF metadata with the camera model, the date and sometimes the location; on small images that can amount to a few kilobytes or more. The compressor strips metadata, which helps both size and privacy.
A popular tip says to “set the photo to 72 DPI”. DPI is a printing hint stored inside the file; it does not change the number of pixels, so it does not change the weight either. Two 1600 × 1200 files at 300 and 72 DPI are the same size. To shrink a file you have to reduce the pixels themselves.
| Method | What it does | Effect | When to choose it |
|---|---|---|---|
| Resizing | Reduces the pixel count | Largest saving, proportional to dimensions | The image will be viewed on a screen |
| Compression | Adjusts quality at the same dimensions | Typically 30–70% smaller | Dimensions are fixed by a rule |
| Changing format | PNG to JPG, JPG to WebP | Huge on photographic PNGs; 25–34% with WebP | Wrong format, or publishing on the web |
| Cropping | Removes unneeded edges | In proportion to the area removed | The subject fills only part of the frame |
| Stripping metadata | Deletes EXIF information | A few KB up to tens of KB | Before sharing, always |
These methods stack, and they work best in sequence: crop first, then resize, then change format if needed, and compress last. Compressing first means spending quality again at every later step.
At each step the file is uploaded, processed within that request, sent back and not stored. Uploads are limited to 24 MB per file, which phone photos stay comfortably under.
An application portal asks for “JPG, max 100 KB”, and you have a 4 MB portrait at 4000 × 3000 pixels. First crop a vertical 3:4 area, for example 2250 × 3000 pixels. Then set the width to 600 in the resizer; the height follows at 800. At this point the file usually sits between 100 and 200 KB. Finally enter 90 KB as the target in the compressor. The target is an approximation rather than a guarantee, so if the result still overshoots, set the quality by hand to around 70. At 600 × 800, that setting does not visibly damage a face.
Windows reports sizes in base 1024: it calls 1024 bytes a KB and 1024 KB an MB. macOS Finder and some websites count in base 1000. The difference is small, but it can get a file that sits right on the limit rejected. Aiming about 5% below the cap, say 90–95 KB for a 100 KB limit, removes the ambiguity.
| Destination | Suggested dimensions | Target size | Note |
|---|---|---|---|
| Application form, ID photo | Whatever the form specifies | The form's limit (often 100–500 KB) | Read the form's own rules |
| Email attachment | Long edge 1600–2000 px | 300–800 KB per photo | Attachments grow by about a third |
| Website content image | Display width, doubled for sharp screens | Typically 100–300 KB | WebP goes lower still |
| Social media | 1080 px wide is commonly cited | The platform recompresses anyway | Upload a high-quality JPG |
Attachments are converted to text with Base64 before they travel, and that adds roughly 33% to their size: 15 MB of photos becomes more than 20 MB on the wire. Many mail services cap the total attachment size of a message somewhere around 20–25 MB. If you are curious, encode a small file with the Base64 encoder and compare the output length with the original. The practical rule for sending ten photos: resize each to 1600 pixels and save at quality 80.
Resize to at most twice the width the image occupies on the page; for an 800-pixel content column, 1600 pixels is plenty. Then compress, and convert to WebP where you can. A common target is a few hundred kilobytes for large hero images and 100–200 KB for images inside an article.
Job, exam, scholarship and visa portals usually combine three rules: a format (mostly JPG), dimensions in pixels or centimetres, and a maximum file size. Satisfy them in that order. If your iPhone saves photos as HEIC and the portal refuses them, Settings > Camera > Formats > Most Compatible makes the phone shoot JPG from then on.
A reduction you cannot see on screen can show up on paper. A 4 × 6 inch print needs around 1200 × 1800 pixels, so a photo cut down to 600 pixels will look soft at that size. Send the original to the printer.
Yes. The tools run in a mobile browser: open the page, tap the upload area and pick a photo from your gallery. The processed file lands in your downloads, with no app to install.
Compression results depend on content; the same quality setting can give 60 KB on a simple photo and 140 KB on a busy scene. That is why the target works approximately. If the result is over the limit, reduce the dimensions a little more.
No. Discarded pixels and detail do not come back, which is why reductions should always be made on a copy.
For the formats themselves, read what is WebP and what is AVIF; for choosing between photo and graphic formats, see PNG vs JPG; and for the effect on page speed, continue with image compression and web performance.
