Compress an image under 200 KB

MakeFileWork searches for the highest quality that stays below the limit, verifies the result and only reduces dimensions when necessary.

1Choose a file
✓ Private by design

Prepare my file

One file at a time · up to 40 MB · no account needed

✓ Processed in your browser whenever possible✓ Your file is not stored
Common requirement shortcuts
Need something different? Describe it here
Optional — leave blank to check the file
More options

How upload requirements become measurable checks

Upload portals often reject files because of a combination of maximum size, format, dimensions or document properties. MakeFileWork interprets measurable constraints and applies transformations it can verify rather than treating an error message as permission to degrade the file unnecessarily.

Verification before download

After transformation, the output is checked again against the known limits. The goal is to satisfy a concrete condition —such as a KB/MB ceiling or exact dimensions— rather than simply create a different file that may still be rejected by the destination portal.

Quality versus compliance

An aggressive limit may require compression, format conversion or resizing. When a workflow can remove searchable text, transparency, metadata or other capabilities, MakeFileWork treats that as an explicit trade-off instead of silently presenting it as an improvement.

If the portal rejects the result again

Paste the new rejection message and rerun the workflow with the additional requirement. Repeated blind compression or conversion is discouraged because each unnecessary transformation can reduce quality without addressing the actual rejection condition.

Why websites reject images over 200 KB

Upload forms often enforce file-size limits. Kilobytes are not the same as pixel dimensions, so MakeFileWork preserves dimensions first and adjusts image quality. If that is not enough, it progressively reduces resolution until the file fits, while respecting any minimum or exact dimensions you ask for.

Privacy

JPG, PNG and WebP are processed locally in your browser.