To make an image fit a 20 KB, 50 KB or 100 KB limit, set that byte cap in the KB image tool, select the required format and pixel dimensions, and inspect the downloaded result. Compression can reduce quality or dimensions. No fixed number of pixels is guaranteed to fit every photo at the same KB.

For an exam or government form, check your notification and the current upload instructions first. A green local size check confirms a property of the export, not acceptance by the receiving portal.

Read all the requirements together

Write down the accepted format, maximum bytes, optional minimum bytes, width and height. Also note any rules for background, recency, signatures or live capture. A small JPEG can still be the wrong image for the form.

Check whether dimensions are exact or a range. A requirement for 200×230 pixels is different from a maximum of 200×230. Crop and resize settings should reflect that distinction.

The form preparation guide explains how to read the current notification. A preset is a starting point and does not replace the instructions for your application cycle.

KB and pixels measure different things

Pixels describe width and height. Bytes measure the file's encoded data. Two 600×600 images can have different file sizes because a smooth signature background and a detailed photograph need different data to encode.

This site uses 1024 bytes for its KB setting. The decimal SI prefix kilo means 1000; binary prefixes such as KiB distinguish 1024. A portal may label its units loosely. NIST's binary-prefix reference explains the distinction.

When close to a portal's cap, leave room below it and inspect the file size in bytes where possible. If a nominal 50 KB upload fails, check its actual bytes and the error before trying unrelated changes.

Crop before chasing a smaller number

Remove irrelevant surroundings while preserving the required subject and margins. A photograph of a signature might contain a table, shadow and paper edges that are not needed. Cropping those away can simplify the delivery image.

Do not crop so tightly that letters or the subject are cut off. A technically small file with missing content is not an improvement. For a form, follow its composition instructions rather than a generic social-media crop.

Start from the original instead of a screenshot of a gallery preview. A screenshot can contain fewer useful pixels and extra interface elements. It is not a reliable method for reaching a byte cap.

Choose quality and dimensions deliberately

For JPEG, the tool searches for an encoding that fits the cap. If the workflow permits reducing dimensions, it may reduce them when quality alone is insufficient. Read the actual output dimensions; do not assume they remain unchanged.

If a form requires exact dimensions, use that option and verify the download. A very demanding byte cap may still require an unacceptable visual compromise. Do not submit an unreadable image just because its byte count fits.

There is no universal rule that JPEG quality 80 halves the bytes, or that quality 60 is invisible. Different content and browser encoders produce different results. Compare the subject, thin strokes and smooth areas in your own image.

Set the cap on your phone

  1. Open the 20 KB, 50 KB or 100 KB page, or type another cap in the general KB tool.
  2. Confirm the unit and choose the accepted output format.
  3. If required, select exact dimensions and enter the notification's width and height.
  4. Enter a minimum size only when the instructions require one and the format supports the option.
  5. Select the original file, adjust the crop, and inspect the result.
  6. Download, reopen it, and confirm the actual dimensions and size before choosing it on the portal.
Try it on your own photoSocial-ready photos, smaller files, nothing uploaded
Compress a photo

Browser file sharing and download locations vary. Keep a clear filename so that the correct photo and signature are easy to distinguish. The image is processed locally by this tool; the later form submission is a separate upload to the portal.

Understand minimum-size padding

The JPEG minimum-size option adds comment data when an encoded image is below the requested minimum. It does not alter the decoded picture and does not restore detail. It increases the file's bytes.

This can create a local file in a specified range, but not every receiving system treats files the same way. A portal may inspect structure, remove comments, re-encode an image or reject it for another reason. Padding is not a guarantee and should not be used to evade a rule.

If the portal rejects a padded file, follow its instructions or support guidance. Keep the original and do not repeatedly alter an already compressed copy while guessing.

Why a small file can still fail

  • The output format does not match the accepted list.
  • Width or height is incorrect, even though bytes fit.
  • A required minimum is not met.
  • The photo is in the signature slot or an old file was selected.
  • The image content does not meet the current notification.
  • The portal requires live capture rather than a prepared photo.

Inspect the downloaded file and the portal's own preview. A local pass only proves the property actually checked. It does not prove identity, recency, legibility or compliance with every application rule.

What this cannot do

A compressor cannot guarantee a full-resolution photograph at 20 KB, restore focus or improve a signature merely by adding bytes. A simple graphic may fit easily; a textured photograph may need a significant compromise.

Keep the original and treat the small output as a delivery copy for one use. For technical details of variable-quality browser export, see the HTML canvas specification. The platform's own instructions decide which output it accepts.

Checklist

  • Check your notification and current upload instructions.
  • Record format, bytes and required dimensions.
  • Crop without removing required content.
  • Inspect readability and actual output dimensions.
  • Treat minimum padding as bytes, not better quality.
  • Check the portal preview after uploading.
  • Keep the original and the accepted delivery copy.

Editorial review: 20 October 2026. Numerical photo-size predictions and universal portal-acceptance promises were removed.