Updated: August 1, 2026
Quick answer: Keep the pixel dimensions, remove optional metadata, export from the clean master to a suitable format, and lower quality gradually while checking the details that matter. If the target remains unrealistic, make a separate smaller delivery copy instead of damaging the only original.
Sometimes the dimensions are part of the requirement: a marketplace expects a fixed canvas, a form accepts only a certain image size, or a design must remain crisp at a known resolution. In that case, resizing is not the first lever. You can still reduce megabytes by changing what data is stored and how efficiently it is encoded.
What You Can Change While Keeping Dimensions
| Lever | Changes pixel dimensions? | Potential benefit | Main risk |
|---|---|---|---|
| Remove optional metadata | No | Small to moderate | Deleting useful rights, color, or catalog data |
| Change format | No | Moderate to large | Compatibility or feature loss |
| Change lossless settings | No | Small to moderate | The file may remain too large |
| Use visually lossless encoding | No | Moderate to large | Fine detail or edges may change |
| Crop empty canvas | Yes | Can be large | Changes composition and requirements |
| Resize | Yes | Often largest saving | Less zoom or display detail |
If dimensions are truly fixed, focus on the first four rows. Keep an untouched master before testing.
Step 1: Check What “Dimensions” Means
“Keep the same dimensions” might mean pixel width and height, aspect ratio, or the visible canvas. Verify the requirement:
- Is the upload limit about megabytes or pixels?
- Is transparency required?
- Does the recipient need to zoom or print?
- Will a platform recompress the file anyway?
- Does the format need to be JPEG, PNG, or something else?
If a 3000×2000 image must remain 3000×2000, a 1200px export is not a valid solution even if it is much smaller. If only the aspect ratio matters, a different display copy may be acceptable.
Step 2: Keep the Master and Inspect the Current File
Record the current format, width, height, file size, color mode, alpha channel, and metadata. A “PNG photo” and a “JPEG photo” can have very different starting points. An already-optimized WebP may have little room left without visible change.
Do not repeatedly recompress the current delivery file. Return to the clean master for each candidate so you can separate the effect of the new export from earlier damage.
Step 3: Remove Optional Metadata
EXIF data may include GPS coordinates, camera information, timestamps, thumbnails, and editing history. For a public or casual sharing copy, removing data that is not required can lower the file size and reduce privacy exposure.
Keep metadata when it is part of a rights, color-management, catalog, or archival workflow. If the output looks different after metadata removal, the tool may also have changed the color profile; compare colors and preserve the profile when the destination needs it.
Step 4: Choose a More Efficient Format
Use the image content and destination together:
- Photograph: test WebP, AVIF, and JPEG at the same dimensions.
- Screenshot or flat artwork: test PNG and WebP; watch small text and edges.
- Transparency: use PNG or WebP; JPEG cannot retain alpha.
- Vector source: keep SVG when the destination supports it.
The MDN image format guide describes common capabilities and fallback considerations. Google’s WebP documentation notes that WebP supports both lossy and lossless modes, alpha, and animation. These facts make a format a candidate, not a guarantee.
If a file must remain JPEG or PNG for a receiving system, skip conversion and optimize within that constraint. If you control a website, use <picture> or a CDN fallback strategy rather than forcing every client to decode one modern format.
Step 5: Test Quality in Small Steps
Export from the master at the same dimensions with three visual targets:
- conservative;
- moderate;
- smaller, only if the destination has a strict limit.
For a photograph, a quality range around 75–85 may be a useful first test. It is not comparable across formats, and the correct setting changes with noise, texture, faces, text, and gradients.
Compare output bytes and inspect:
- fine texture and skin;
- small text and high-contrast edges;
- gradients and dark shadows;
- transparent boundaries;
- color and profile behavior.
Stop when the file is small enough for the actual requirement and the output still passes the destination-specific test. There is no benefit in reaching a smaller number that makes the asset unusable.
Why Some Files Will Not Shrink Much
Lossless compression works by encoding repeated or predictable patterns efficiently. A noisy photograph, film grain, or already-compressed file may contain little redundancy. If the current export has already removed metadata and uses a modern codec, further reduction usually requires changing visual detail or dimensions.
At that point, decide whether the constraint can change. A separate lower-resolution web copy, a crop, or a platform-specific variant may be more honest than pretending the original can remain identical at one tenth of its bytes.
If You Need an Exact Byte Ceiling
A hard limit such as 500KB or 1MB is a different goal from “make it smaller.” Set the ceiling, export a candidate just above it, reduce one variable, and recheck the visual acceptance criteria. Avoid a loop that repeatedly saves the same lossy file.
For target-size workflows, first remove metadata and choose the right dimensions and format, then adjust quality. LessMB’s exact-size guide covers the trade-off in more detail.
Website Delivery Still Matters
Keeping the source dimensions does not mean every visitor should download that source. A responsive page can offer several candidates while preserving the original pixel dimensions for a zoom or high-density display. Use srcset and sizes, and reserve the aspect ratio with width and height. Google’s image guidance and web.dev’s responsive image guidance explain this distinction.
<img
src="catalog-1600.webp"
srcset="catalog-800.webp 800w, catalog-1200.webp 1200w, catalog-1600.webp 1600w"
sizes="(max-width: 720px) 100vw, 720px"
width="1600"
height="1067"
alt="Blue backpack shown from the front"
/>
The browser chooses a delivery copy; the master remains available for a user who needs more detail.
Final Decision Checklist
- the fixed requirement is documented;
- original format, dimensions, and metadata were recorded;
- master is preserved;
- optional metadata was removed intentionally;
- candidate format supports transparency and compatibility needs;
- quality was changed gradually from the master;
- candidates were compared at 100% and at the real display size;
- the delivered copy was checked after upload;
- a separate responsive or smaller variant is used when appropriate.