Compress an image under 1MB

The optimiser below targets 1MB with Preserve dimensions and a 5% safety margin, so the file aims slightly under the limit for strict validators.

CompressProcessed locallyInstantNo account

Choose a target: 50KB · 100KB · 200KB · Under 1MB

Drag & drop your image

or click to browse files

Supports: JPEG, PNG, WEBP, AVIF (max 100MB)

  • Processed locally
  • No image upload
  • No account required
  • Images not stored by PictureConvert

Why 1MB matters

A 1MB (1024KB) ceiling is a frequent general-purpose upload and email attachment limit. Many websites, document portals, and mail systems reject larger binaries even when the photo still looks fine on screen. This page preloads Smart Optimizer at 1MB, preserves dimensions by default, and applies a small safety margin because some systems measure limits after their own re-encoding.

  • Email attachments that must stay under a 1MB mailbox rule
  • Website and CMS uploads with a one-megabyte maximum
  • Document portals and case-management systems
  • General “keep it under a megabyte” sharing requests

Advice for a 1MB target

  • Preserve dimensions often works at 1MB for photos that are already web-sized; enable Allow resizing only if the tool reports the target is out of reach.
  • A 5% margin targets about 972KB so picky validators are less likely to reject a file sitting at 1,024,000 bytes.
  • Email clients and portals sometimes quote “1MB” loosely — if uploads still fail, drop to 900KB custom or keep the margin at 10%.
  • Batch many files with Bulk Compressor after you know settings that work for one image.
  • Do not promise lossless results — JPG/WebP/AVIF trade detail for size even under 1MB.

Worked examples

These illustrations use realistic starting points. Image complexity varies — do not expect identical bytes or dimensions on your file.

Email attachment from a DSLR export

Starting dimensions
5000×3333
Starting file size
4.8 MB (JPG)
Output format
JPG
Resizing needed
Yes
Approx. result dimensions
about 2400×1600
Approx. result size
about 900–970 KB

With a 5% margin the effective target is under 1MB. Resizing was required for this large export; smaller sources may not need it.

CMS blog image

Starting dimensions
2000×1125
Starting file size
1.6 MB (JPG)
Output format
WebP
Resizing needed
No
Approx. result dimensions
2000×1125
Approx. result size
about 700–950 KB

Shows a case where preserve-dimensions mode can succeed at 1MB after a format/quality search. Outcomes vary with noise and detail.

Format recommendations

  • JPG — default for email and legacy portals.
  • WebP — great for websites when the stack accepts it.
  • AVIF — strong compression for modern browsers that can encode and display it.
  • PNG — fine for UI graphics under 1MB; heavy photos should usually convert.

Common problems

  • File is 1.02MB and still rejected — enable a safety margin or custom target slightly below 1MB.
  • Preserve dimensions fails on a 20MP RAW-derived JPG — turn on Allow resizing or resize to 2000px on the long edge.
  • Email compresses again and ruins quality — attach the already-optimised file and avoid client “image optimisation” if you can.
  • Need transparency under 1MB — prefer WebP over PNG for photographic alpha.

Open the general Smart Optimizer for any target, or continue in Compress.

Frequently asked questions

Why start with a 5% safety margin?

Some uploaders reject files at or microscopically over the stated limit after server-side re-encoding. Aiming slightly under 1MB reduces those false failures.

Will I always need to resize for 1MB?

No. Many images already near web resolution fit under 1MB with quality and format changes alone. Resizing is the fallback when preserve-dimensions mode cannot reach the target.

Is 1MB the same as 1024KB?

This tool’s 1MB preset uses 1024×1024 bytes. If a system means 1000×1000 bytes, use a custom target or a larger safety margin.

Are my files uploaded?

No. Exact-size compression runs locally in your browser on PictureConvert.