A practical guide to your next decision
A practical field guide to image size, composition and file weight. Read from start to finish, or jump straight to the decision you need to make.
Worked example and sample files
A PNG can grow after resizing because file size depends on how well its pixel patterns compress. Interpolation creates new edge colors, and a browser encoder can choose a different compression strategy from the original tool. Removing pixels does not mathematically guarantee fewer bytes. A previously optimized or palette-based PNG may become a larger full-color export.
Work through an example
Resize a 640 × 480 graphic to 320 × 240 and compare exact bytes in the result. If it is larger, enable lossless PNG optimization and process again from the source. The optimized file is used only when it is smaller than the native export.
- Open the relevant tool below and choose a supported image. Check the original dimensions and bytes before changing anything.
- Set the dimensions and fitting mode for your destination. Enable enlargement only if you accept that it cannot restore missing detail.
- Process the image, switch between Original and Result, and check the final pixel dimensions and exact bytes. If a target is not met, change an allowed constraint and run again.
Check before you download
A JPEG quality slider cannot compress PNG in this editor. If lossless optimization is insufficient, fewer pixels or a deliberate format change are the remaining options. Preserve transparency when you need it; JPEG removes it.
Try the files yourself
The following original geometric illustration and exports are supplied with this project. These are actual files, not estimated savings. The exported examples use JPEG quality 85. Your own images will have different byte counts; compare details as well as weight.
| Result | Width × Height | File size |
|---|---|---|
| Original | 4032 × 3024 | 225354 bytes |
| Try a sample image | 1200 × 900 | 36438 bytes |
| Fit within bounds | 1440 × 1080 | 41113 bytes |
| Fill & crop | 1920 × 1080 | 44272 bytes |
| Add padding | 1920 × 1080 | 44602 bytes |
Choose your next step
Exported images remove EXIF, GPS and XMP metadata. Processing uses SDR/sRGB.
Compare the encoding path, not just the pixel count
A heavily optimized palette PNG and a full-color browser export are not identical storage strategies. Resampling can also introduce intermediate colors along edges. Record the original dimensions and bytes, then compare the exported dimensions and bytes. If pixels decreased while weight increased, the observation is consistent with a changed representation; it is not proof that the resize failed.
Use the optional optimizer as a controlled second step. Verify that it preserves the decoded output and inspect the actual saving. If the destination allows a different format, test that as a separate candidate and check alpha and text. If PNG is compulsory, stay within that constraint and revise dimensions only when allowed.
Why a resized PNG can become heavier
Resizing changes pixel values along edges and gradients. A compact source may use a palette, while a browser export may use a fuller color representation. The original may also have been carefully optimized. Fewer pixels therefore do not guarantee fewer stored bytes. Compare the real source and output sizes rather than assuming a particular saving from the scale percentage.
Try the optional lossless optimizer when PNG is required. “Lossless” describes the optimization of the already exported PNG: it must preserve that image’s decoded pixels. It does not undo changes introduced by resizing, and it does not guarantee a smaller file for every input. If the optimized export is not smaller, retaining the valid native output is preferable to claiming a saving that did not happen.
Transparency needs a format and a background decision
Transparent space is not white space. An alpha channel records how opaque each pixel is, including soft edges around a logo or illustration. PNG and static WebP outputs can retain this channel. JPEG cannot: the image must be composited onto a background. Choose that background deliberately, especially when the final page is dark or the artwork has pale lettering.
Inspect edges against both light and dark surfaces. A logo that looks correct on white can reveal a halo on navy. Padding has the same choice: keep its empty space transparent, or fill it with a chosen color. Once alpha has been flattened into an opaque file, switching the extension back to PNG cannot reconstruct the missing transparency. Return to the transparent original instead.
Pixels describe the image; bytes describe the file
A 1920 × 1080 image has 2073600 pixels, regardless of whether it is stored as JPEG, PNG or WebP. That count describes its decoded grid. The download’s byte count describes the compressed representation of that grid. A flat illustration and a grainy photograph can share the same dimensions while producing very different file weights. Texture, noise, alpha and encoding settings all change what the encoder has to store.
This distinction explains two common surprises. A smaller image can still weigh more after it is re-encoded with different settings. A tiny compressed file can still need substantial memory when decoded. Evaluate dimensions, stored bytes and visual detail separately. None of those measurements can stand in for the other two.
The concepts behind this page
These relationships explain why changing one setting can affect another. Use them to identify which constraint matters most for your image.
- PNG
- A supported lossless output that can carry an alpha channel.
- File size in bytes
- The amount of data in the encoded download, measured after processing.
- Pixel dimensions
- The width and height of the decoded image grid.
- Alpha channel
- Per-pixel opacity, including partially transparent edges.
- JPEG
- A supported photographic output with lossy encoding and no transparency.
- Static WebP
- A supported still-image format with transparency and quality-controlled export.
- Padding
- Added canvas space around an image whose proportions stay intact.
- Encoding quality
- A JPEG/WebP setting that trades compression against visible artifacts.
- Encoding quality influences the encoded File size in bytes.
- JPEG flattens instead of retaining an Alpha channel.
- PNG can preserve an Alpha channel.
- Static WebP can preserve an Alpha channel.
Questions worth asking before you export
Why did my transparent logo get a solid background?
JPEG cannot retain alpha, and disabling transparency also flattens it. Choose PNG or static WebP with transparency enabled, starting from the transparent original. Converting an already opaque JPEG back to PNG cannot recover alpha.
Why is a smaller PNG heavier than its source?
Resampling, palette differences and encoder settings can change storage efficiency. Compare actual bytes and try the optional lossless optimizer. Fewer pixels alone do not guarantee a smaller encoded file.
Does quality 100 make the export lossless?
No. JPEG quality 100 is still an encoding setting, not a promise of identical source pixels. Resizing itself also changes the grid. Preserve the original when you need an unchanged archive.
Sources and how to verify the examples
The numerical examples on this page come from explicit geometry calculations and the project’s synthetic files. Hypothetical byte counts illustrate acceptance rules; downloadable sample counts describe those specific files. The references below explain the underlying formats and browser export API, not a guaranteed saving or acceptance by another service.
Ready to prepare your image?
Keep the original, choose one clear requirement, and inspect the exported file. A useful result meets its destination’s rules and keeps the details that matter.
Back to the image tools