How to Compress PNG or JPG to 100KB, 200KB, or 50KB

The practical answer

To compress an image under 100KB, start with the pixels, not the quality slider. If the file is a phone photo, resize the long edge to roughly 800-1000 px, export as JPG at about 70-80 quality, then check the downloaded file size. For a 200KB limit, start around 1200-1600 px and quality 75-85. For a 50KB limit, use the portal's required pixel dimensions first, then lower JPG quality only as much as needed.

That order matters. A 4032 x 3024 phone photo contains more than 12 million pixels. A 1000 x 750 copy contains 750,000 pixels. If the destination is a form thumbnail, profile image, ID upload, or small document attachment, fewer pixels usually looks better than crushing the original with a very low quality setting.

Also, most upload pages do not want a file that is exactly 100.0KB. They want a file that is below a maximum. Aim a little under the cap - for example 92-95KB for a 100KB limit or 185-195KB for a 200KB limit - because some portals count kilobytes as 1000 bytes and others display 1024-byte KiB values.

Read the upload rule before touching the photo

The size error message is only part of the rule. Before compressing, check the upload page for five details:

• Maximum file size: 50KB, 100KB, 200KB, 500KB, 1MB, or another cap.
• Allowed formats: JPG/JPEG is safest. Some forms allow PNG. Fewer accept WebP or AVIF.
• Pixel dimensions: A portal may require 600 x 600, 413 x 531, 1200 x 1600, or a maximum width.
• Aspect ratio: Square, portrait, document scan, banner, or freeform.
• Content rules: ID and passport photos may require a plain background, no filters, no retouching, and a clear face.

If the form gives both pixel dimensions and a KB limit, set the dimensions first. Then compress the correctly sized copy. If you compress first and resize later, the final export may land over the limit again.

Starting settings for common KB targets

These are starting points, not promises. A simple headshot on a plain background compresses much smaller than a photo with leaves, fabric, text, noise, or a busy street behind it.

When the upload page accepts WebP, try WebP after JPG if the file is still too large. Google's WebP documentation reports that lossy WebP files can be smaller than comparable JPEGs at equivalent quality, but compatibility still decides the final choice for forms.

Choose the format before lowering quality too far

Format changes are often cleaner than extreme quality changes.

• Use JPG for forms: JPG works almost everywhere and is the safest choice for government portals, school systems, job boards, and older upload widgets.
• Use WebP for websites: WebP is a practical web format when the CMS, browser target, or delivery pipeline accepts it. It often reaches 100KB or 200KB with fewer visible artifacts than JPG.
• Use AVIF only when accepted: AVIF can create very small files, but many non-web upload forms reject it. Do not use AVIF for a strict form unless the form explicitly lists AVIF.
• Avoid PNG for photos: PNG is lossless, which is useful for screenshots, logos, diagrams, and transparency. It is usually the wrong format for a camera photo under 100KB.
• Convert HEIC first: If the source is an iPhone HEIC and the portal wants JPG or PNG, convert to JPG before chasing the KB target.

Resize first when the image is far too large

PhotoTools' Compress tool changes quality and output format; it does not change pixel width or height. If your source is a full camera photo, use the Resize tool first, then compress the resized copy.

For a normal portrait or document upload, these long-edge sizes are realistic:

• 500-700 px: Very small 50KB targets, signatures, thumbnails, and simple headshots.
• 800-1000 px: Most 100KB forms where the image will only be reviewed on screen.
• 1200-1600 px: Most 200KB profile photos, university forms, marketplace listings, and application uploads.
• 1600-2000 px: Website images where quality matters more and the target is closer to 500KB or 1MB.

If the portal requires exact dimensions, do not use a rough long-edge value. Enter the required width and height in the Resize tool, keep the aspect-ratio lock on unless the portal explicitly wants a fixed crop, export the correctly shaped copy, then compress that file.

How to use PhotoTools for a 100KB or 200KB limit

Use this workflow when the upload page gives a strict file-size cap and you want to keep the image private:

1. Keep your original file untouched.
2. If the photo is larger than the destination needs, open Resize, set the target pixels, and download the resized copy.
3. Open Compress and drop in the resized JPG or PNG.
4. Choose the output format. Pick JPG for form compatibility; pick WebP only when the destination accepts WebP.
5. Set quality to 80 and click Compress all.
6. Read the card: PhotoTools shows the original size, output size, and percentage saved after compression.
7. If the result is still over the limit, go back to the original or resized copy, lower quality to 70, and run another export.
8. Stop as soon as the downloaded file is comfortably below the cap and still looks clear.

Do not repeatedly compress the already-compressed download. Re-encoding a JPG again and again compounds artifacts. If the first attempt is too large, return to the original or to the clean resized copy and export a new version with a lower quality setting.

Recipe: compress a JPG to under 100KB

For a form photo, product thumbnail, or job application profile image:

1. Resize the long edge to 900 or 1000 px unless the portal gives exact dimensions.
2. Export as JPG.
3. Start at 80 quality.
4. If the file is 110-130KB, try quality 72-75.
5. If the file is still over 100KB, reduce the long edge by another 150-200 px before pushing quality below 60.

The result should still look clean at normal viewing size. If the face, label, or document text looks waxy at 100% zoom, the image probably has too many pixels for the byte budget. A smaller image at higher quality often looks better than a large image at quality 35.

Recipe: compress a JPG to under 200KB

A 200KB cap gives you more room, so avoid over-compressing:

1. Resize the long edge to 1200-1600 px.
2. Export as JPG at 80-85 quality.
3. If the file lands around 220KB, lower quality to 75-78.
4. If the background is busy and the file is still large, resize to 1200 px instead of driving the quality slider too low.

Use 200KB when the image must still be inspectable: application portraits, small product photos, scanned certificates, classroom submissions, and CMS uploads where viewers may zoom in slightly.

Recipe: get a visa or passport photo under 50KB

Identity-photo uploads are different because file size is not the only rule. The crop, face position, background, expression, and lighting matter more than the byte count.

Start with the official pixel dimensions from the portal. If it says 600 x 600, make a 600 x 600 file. If it says a minimum and maximum, stay inside that range. Then export as JPG around 70 quality and check the size. If it is still over 50KB, lower to 60-65 or reduce dimensions only if the portal allows it.

Do not fix a bad official photo with beauty filters, AI sharpening, face retouching, background replacement, or heavy color edits. Plain resizing and compression are file preparation. Altering the face or background is a compliance risk.

Recipe: compress a signature or scanned form to 20KB

Small signature uploads fail for a different reason: people compress a whole phone photo of the paper instead of the signature itself.

Crop first. Remove desk, table, shadows, and blank paper. A tight crop can reduce the file more than any compression setting. Then resize the crop to 300-500 px wide and export as JPG around 55-65 quality. If the form allows PNG and the signature is simple black text on white, PNG may stay crisp, but it can also exceed the cap. Try both and keep the smaller readable file.

Before uploading, zoom to normal screen size and confirm the strokes are not broken. A 12KB file that makes the signature unreadable is not a win.

What to do with PNG screenshots and transparent images

A screenshot with text, a logo, or a transparent graphic is not the same as a photo.

Keep PNG when the image needs transparency, crisp UI text, or exact flat colors. If the portal only cares about a small preview and accepts WebP, WebP can reduce a screenshot a lot while keeping edges cleaner than JPG. Use JPG for screenshots only when the form accepts JPG and the text remains readable after export.

For transparent PNG files, remember that JPG has no transparency. Exporting to JPG will flatten the transparent area to a background color. If the image is a logo or overlay asset, keep a clean PNG master and create a flattened upload copy only when the destination requires JPG.

Why your file is under the limit but still rejected

If the final file says 96KB and the portal still refuses it, check these issues before compressing again:

• Wrong extension: The portal wants .jpg or .jpeg, not .webp, .avif, .heic, or a renamed file.
• Wrong dimensions: The KB size is fine, but the pixel width or height is outside the allowed range.
• Wrong aspect ratio: A square photo was required, but the image is portrait or landscape.
• File is too close to the cap: Your computer shows 100KB, but the portal counts exact bytes. Export to 92-95KB instead.
• Progressive or unusual encoding: Some older portals reject perfectly valid images. Re-export as a simple JPG from a browser tool.
• Filename problem: Remove special characters, emoji, very long names, and spaces. Use something like photo.jpg.
• Visible content problem: For ID photos, the file can be technically valid but rejected for shadows, crop, expression, glasses, background, or edits.

How to judge quality quickly

Do a thirty-second review before uploading:

1. Open the final downloaded file, not the preview.
2. Check the exact file size in Finder, Windows Properties, or the upload dialog.
3. View it at the size the reviewer will probably see.
4. Zoom to 100% once and look at eyes, text, logo edges, gradients, and skin texture.
5. If you see blocky squares, halos, smeared details, or unreadable text, use fewer pixels and a higher quality setting instead of lowering quality again.

For website images, also check the image inside the layout. A 100KB file can still look bad if the browser has to upscale it into a large hero slot. For a small form upload, normal viewing size matters more than pixel-peeping.

Privacy and metadata notes

PhotoTools processes compression in the browser. The tool decodes the image, draws the pixels to an OffscreenCanvas, then exports a new JPG, WebP, AVIF, or original-format file with the selected quality. MDN documents that canvas export can specify both output type and quality for formats that support lossy compression.

Because the output is created from canvas pixels, camera metadata is usually not copied into the new file. That can remove GPS coordinates, camera model, timestamps, and editing software tags. If the file is sensitive, verify the finished download with a metadata checker instead of assuming every hidden field is gone.

What not to do

• Do not take a screenshot of the photo just to make it smaller; screenshots often add blur, change color, and create a worse source.
• Do not message the image to yourself through a chat app as a "compressor"; many apps resize unpredictably and strip useful detail.
• Do not compress the only copy of the original. Keep the full-resolution source and make upload copies from it.
• Do not use the lowest possible quality setting first. Try a sensible resize before going below quality 60.
• Do not use WebP, AVIF, or HEIC for a form that only lists JPG/JPEG/PNG.

Quick recap

For strict KB targets, use this order:

1. Read the upload rule: size, format, dimensions, and content requirements.
2. Resize first if the photo has far more pixels than the destination needs.
3. Use JPG for maximum form compatibility; use WebP or AVIF only when accepted.
4. Start around quality 80, then step down only as needed.
5. Aim below the cap, not exactly on it.
6. Check the downloaded file size and visual quality before uploading.

Technical sources checked

This article was reviewed against the current PhotoTools compression and resize implementation, MDN's OffscreenCanvas convertToBlob() documentation, MDN's image file type guide, Google's WebP documentation, and web.dev's Learn Images course.