File size is only one validation rule

You compressed the image to 196KB, selected it in the form, and still received an error. This usually means the portal is checking something besides file size. Image validators may inspect the real format, pixel dimensions, aspect ratio, color profile, filename and even whether the file can be decoded by an older library. Work through the checks below in order rather than repeatedly reducing quality.

Upload error diagnostic table
What you seeLikely causeFirst fix to try
“Invalid format”The real codec does not match the accepted extensionExport a genuine JPG, PNG or WebP rather than renaming the file
“Invalid dimensions”Width, height or aspect ratio is outside the ruleCrop and resize to the exact pixels before compression
“File too large” below 200KBThe portal uses a stricter byte calculationSet a 190KB target to create more margin
Generic “upload failed”Filename, session, browser or portal problemUse a short filename, reload and try a current browser

1. Confirm the real file format

Changing a filename from photo.webp to photo.jpg does not convert the image. The internal file remains WebP and a validator can detect the mismatch. Use the compressor’s output format menu to create a genuine JPG when the portal says JPG or JPEG only. If the result card reports WebP, do not rename the extension and expect it to pass.

2. Check width, height and aspect ratio

A size limit measured in KB is separate from pixel dimensions. A portal may require 600 × 600 pixels, a 3:4 portrait ratio or a width between 300 and 1000 pixels. Compression can reduce dimensions when necessary, but it does not force one exact shape. Crop and resize to the required dimensions first, then run the final 200KB compression.

Do not stretch a portrait into the required shape. Cropping maintains natural proportions. For identity images, keep the head position and background requirements in mind while making the crop.

3. Leave room below the maximum

Some systems label the limit as 200KB but enforce 200,000 bytes, while a computer may display 200KB using 1,024-byte units. A file close to the edge can therefore appear compliant locally and fail remotely. This compressor keeps a safety margin automatically. If a particularly strict form still rejects the result, enter 190KB and try again.

4. Simplify the filename

Older systems can reject spaces, multiple periods, accented characters, emoji or long filenames. Rename the download to something simple such as profile-photo.jpg. Keep a single extension and avoid punctuation other than hyphens or underscores. This change does not affect image quality or file size.

5. Remove unusual color and metadata conditions

Professional editing tools can save JPEG images with CMYK color, unusual embedded profiles or progressive settings that an outdated validator does not handle. Re-encoding as a standard browser-generated JPG converts the pixels into a widely supported form and removes most nonessential metadata. If the source came from print production software, JPG output is a useful compatibility reset.

6. Distinguish image errors from form errors

Try the file in a different current browser. Reload the form, clear a stale selected file and choose the result again. An expired session, browser extension or incomplete form field can produce a generic “upload failed” message unrelated to the image. If every valid image fails, the portal itself may be unavailable.

Fast diagnostic: create a standard JPG below 190KB with a short filename. If that still fails, inspect dimensions and the portal session before compressing the image more aggressively.

Final upload checklist

Keep the high-quality original after a successful upload. Future systems may request a different crop, format or file-size range, and exporting again from the original produces better results than compressing an already reduced image.

When several application images need the same settings, use the batch compression workflow. If the destination rules are unclear, start with the online form preparation guide.