Know where it will appear
Choose a target based on the layout and display size. A hero image and a small card rarely need the same dimensions.
Set a maximum width for an image, keep its aspect ratio and optionally convert it to WebP, AVIF, JPEG or PNG in the same step. Files stay on your device.
Images are processed locally in your browser and are not uploaded to a PixoSift image-processing server.
Estimate a suitable width, apply it in the optimizer and check the actual exported dimensions before using the file.
Choose a target based on the layout and display size. A hero image and a small card rarely need the same dimensions.
Set a maximum width. PixoSift calculates the height from the source ratio and does not enlarge smaller images.
Check dimensions, clarity and file size. Resizing creates a separate output; the original image on your device is not overwritten.
PixoSift does not overwrite the original file. It creates an output copy to download, so you can keep the source at full size.
The output has fewer pixels when reduced, and lossy conversion can introduce additional visual changes. Do not replace your original master with a resized copy; check the output at its intended display size first.
An image that is much wider than the area where it will appear can add unnecessary bytes to a page. Resizing to a suitable maximum width can reduce file size while keeping the image proportions intact.
PixoSift offers presets for 1920 px, 1280 px, 1024 px and 640 px, plus a custom width. These are starting points rather than universal rules: choose dimensions based on the layout where the image will be displayed.
A full-width desktop banner may need a larger image than a small card or mobile placement. The best width depends on the page layout, responsive behavior and display density. For production websites, also consider responsive image markup such as srcset and sizes when serving multiple variants.
These are practical starting points, not hard rules. Adjust them to the actual display size and verify the exported file.
Try WebP around quality 80–88. Resize to the largest width the layout genuinely needs; compare fine textures, gradients and faces.
If quality is the priority, test a higher setting and compare the file size rather than assuming a target percentage.
Keep the original vector file if you have one. For raster exports, PNG is useful when lossless edges matter; WebP may be smaller and supports transparency.
Inspect transparent edges against both light and dark backgrounds. Avoid JPEG when transparency must be retained.
Start with PNG for lossless reproduction, or test high-quality WebP if size matters.
Zoom in on small lettering, icons and thin lines. Lossy artefacts can be more visible on sharp edges than in photos.
Use the target component's rendered width as a guide. The 1920, 1280, 1024 and 640 px presets are starting points, not guarantees.
For responsive sites, you may need several variants plus srcset and sizes, rather than one file for every screen.
Enter an image's current dimensions and a target maximum width to estimate the output. This calculator runs in your browser and does not inspect or upload any file.
Estimated output dimensions
1280 × 960 pxThe aspect ratio is preserved. This is an estimate before encoding; it does not predict the final file size.
No. The tool calculates the new height from the original aspect ratio when it resizes an image.
The maximum-width control only resizes images wider than the selected width; smaller images are not upscaled.
Yes. You can queue and process up to 50 images in one batch.
Yes. Select the output format and the maximum width before running optimization.