Resize, convert, or compress? A practical workflow for web images
A smaller image file is only useful if it still works in its intended layout. Dimensions, format, transparency, and compression solve different problems. This guide follows a fictional 2400 × 1600 product photograph through a web preparation workflow and explains what to inspect before replacing the original.
Start with the display requirement
Check the space where the image will appear. A card displayed at 600 × 400 CSS pixels has a 3:2 aspect ratio. A 1200 × 800 image can provide two image pixels for each CSS pixel at that size. That is a design choice, not a universal export rule: responsive images may need multiple sizes and the actual layout may crop differently on mobile.
Keep your source file. Work on a copy and choose a useful output name, such as product-card-1200.webp. Repeatedly recompressing an already lossy image can compound artifacts; returning to the original makes it easier to compare export settings fairly.
Crop for composition, then resize for dimensions
Cropping removes part of the picture. Resizing changes its pixel dimensions. If your source has the wrong shape, crop to the intended aspect ratio first, leaving room around the subject. Check that text, faces, or product details are not pushed against the edges.
Use Image Resizer to reduce the 2400 × 1600 source to 1200 × 800 while preserving its ratio. The result has 960,000 pixels instead of 3,840,000: one quarter of the pixel count. Its file size will not necessarily fall by exactly 75%, because encoding and image detail also matter.
Avoid upscaling a small image merely to satisfy a dimension target. Resampling can add pixels, but it cannot recreate original detail that the source never contained.
Choose a format for the content and destination
Photographs and textured illustrations are often suitable for lossy compression. Screenshots with small text, crisp logos, and diagrams may benefit from lossless output. Transparency is a separate requirement: check whether the destination needs a transparent background and whether your selected format and conversion preserve it.
PNG to WebP provides a way to compare a PNG source with a WebP export. Inspect fine edges and transparency after conversion. Converting a JPEG to PNG does not recover details already lost in the JPEG; the PNG can also be larger. Use that conversion when a downstream application requires PNG, rather than treating it as a quality upgrade.
Compare compression with a clear stopping point
Open the resized file in Image Compressor and compare the downloaded result with the source at its intended display size. Look at text, gradients, hair, and high-contrast edges. These often expose artifacts sooner than large flat areas.
Record the original and result byte counts. If a 400 KB file becomes 160 KB, the saving is (400 − 160) ÷ 400 × 100 = 60%. That arithmetic describes this export, not a guaranteed saving for other images. Already optimized files may shrink little or even grow with a different encoder.
Choose the smallest acceptable result for your use case. There is no single quality setting that works equally well for a photograph, screenshot, transparent logo, and detailed chart.
Verify the downloaded file in the actual page
Reopen the export and check its format, dimensions, orientation, and background. Inspect it on a mobile-sized layout as well as a desktop-sized layout. Canvas-based conversions may not retain source metadata or behave like a professional color-managed photography workflow, so retain originals for archival or print use.
For the website itself, write meaningful alternative text when the image conveys information, and use an empty alt value for purely decorative images. Set dimensions to reserve layout space. File optimization and accessible presentation are separate steps; completing one does not complete the other.
UtilBrix processes these files in your browser. The current limits are 25 MB per file, 20 files per selection, 40 million pixels, and 10,000 pixels on the longest allowed dimension. Large decoded images can still exceed a mobile browser’s available memory, so process smaller batches when necessary.
Try the tools in this guide
- Image Compressor — Smaller images, ready to share. No uploads needed.
- JPG to PNG — Convert your JPEG images into PNG files.
- PNG to WebP — Create lightweight WebP images from PNG files.
- Image Resizer — Get the right image size for your next project.
- Crop Image — Crop, rotate, and flip to find the perfect frame.
References
Found a mistake? Send the page address and a non-sensitive example to support@utilbrix.com.
Explore more practical guides