Cropping and resizing are often grouped together because both can produce a smaller-looking image. They solve different problems.
Resizing changes the pixel dimensions of the image. Cropping removes part of the image area. If you need the same composition at a smaller width, resize. If you need a different composition or aspect ratio, crop. Many web workflows use both: crop first to establish the frame, then resize the crop to the required delivery dimensions.
Short version: resize changes scale; crop changes framing. Do not force a landscape image into a square by changing width and height independently. Crop it to a square or use a layout technique such as
object-fit: cover.
What resizing changes
Suppose a photo is 3000×2000 pixels. Resizing it proportionally to 1500×1000 keeps the full image and the original 3:2 aspect ratio. The composition is unchanged; the pixel grid is smaller.
Resizing is primarily useful for matching a source to the dimensions a layout can actually display. See the Image Resizing Guide for the full model.
What cropping changes
Cropping removes image area. If the same 3000×2000 photograph is cropped to a 2000×2000 square, pixels from the left/right sides—or another selected region—are discarded. The subject can become larger in the frame even before any resizing happens.
That means cropping is a composition decision. It can change emphasis, context, balance, and sometimes meaning. A group photo cropped around one person tells a different visual story from the original frame.
Crop first, resize second
When a destination requires a specific aspect ratio, a clean workflow is:
- start from the original;
- choose the crop that fits the destination ratio;
- position the subject deliberately;
- resize that crop to appropriate delivery dimensions;
- compress and export once.
This is better than resizing to an arbitrary width and then repeatedly trimming derivatives. Keep the crop decision attached to the original master whenever possible.
Why changing width and height independently is not cropping
If a 3:2 image is forced into a 1:1 box by changing the image data from 1500×1000 to 1000×1000, the pixels are distorted. Faces become narrower or wider, circles become ovals, and product proportions become inaccurate.
That is neither a proper crop nor a proportional resize. It is stretching.
MDN documents the same distinction in CSS. object-fit: fill can stretch content to fill a box. contain and cover preserve the image’s aspect ratio.
What object-fit: cover actually does
With object-fit: cover, the browser scales the image until the box is filled while preserving aspect ratio. Parts of the image that fall outside the box are clipped. The original image file is not permanently cropped; the browser is choosing which region is visible inside that layout box.
This is useful for card thumbnails, uniform grids, hero panels, and media tiles where every slot needs the same shape.
What object-fit: contain does
object-fit: contain keeps the entire image visible inside the box. If the ratios do not match, unused space remains on two sides. This is often a better choice for product imagery, diagrams, logos, or artwork where cutting off any part of the image is unacceptable.
Permanent crop vs CSS crop
A permanent crop can reduce transferred bytes because the excluded pixels are removed from the delivered resource. A CSS crop can be more flexible because the same source image can be reframed by different containers.
Which is better depends on the workflow:
- Use a permanent crop when the composition is editorially intentional, the image will repeatedly use the same ratio, or you want a smaller dedicated asset.
- Use CSS cover when a reusable image needs to fill many components and slight clipping is acceptable.
- Use art direction with
<picture>when different screen sizes need genuinely different crops rather than the same file clipped differently.
Art direction is more than responsive resizing
Responsive resizing answers: “Which resolution of this image should the browser download?” Art direction answers: “Should the composition itself change on this screen?”
MDN’s responsive image guide gives the classic example: a wide landscape image that works on desktop may make the subject too small on mobile. A tighter mobile crop can communicate better.
That can be implemented with <picture> and media-specific sources, while srcset can still provide multiple resolutions within each art-directed crop.
Common crop ratios
There is no universal set, but common interface requirements include:
- 1:1 for square cards, profile imagery and many product grids;
- 4:3 for balanced editorial and product imagery;
- 3:2 for photography derived from common camera proportions;
- 16:9 for video-like hero and media compositions;
- 3:1 or wider for shallow banners.
The ratio should come from the design system, not from an assumption that one ratio is always better. Our aspect ratio guide explains the geometry and implementation.
How cropping affects quality
Cropping itself does not necessarily reduce the quality of the pixels that remain, but it can leave you with too few pixels for the intended display size. If a small region is cropped from a large source and then enlarged aggressively, softness becomes visible.
After cropping, check the resulting pixel dimensions against the display slot. The remaining crop must still contain enough intrinsic pixels for the intended use and likely screen density.
Worked example: product photo across three placements
Imagine one original 4000×3000 product photograph.
Product detail page: keep the full 4:3 composition, then create responsive widths such as 800, 1200 and 2000 pixels.
Square collection card: crop a 1:1 version around the product, then resize that crop to the card’s responsive source widths.
Wide homepage hero: use a 16:9 or wider art-directed crop that leaves negative space for text. On mobile, a second tighter crop may be necessary so the product remains visible.
One source image can therefore generate several intentional compositions without ever stretching the product.
How to choose: crop or resize?
- If the composition is correct and only the pixel count is excessive: resize.
- If the destination needs a different shape: crop, then resize.
- If the same resource must fill variable boxes and clipping is acceptable: use cover.
- If the entire image must always remain visible: use contain.
- If mobile and desktop need different framing: use art direction.
Try the resize part locally
Use the image tool to set target dimensions and encode the delivery output locally in your browser. When a different composition is needed, create the crop in an editor first, then use the tool to generate the final web dimensions and format.
Frequently asked questions
Does cropping reduce image dimensions?
It can. Cropping removes part of the pixel grid, so the remaining width and/or height may be smaller. But the defining change is the visible frame, not simply the dimensions.
Does resizing crop an image?
Not when the aspect ratio is preserved. Proportional resizing keeps the entire composition. If software fills a differently shaped box and cuts off the edges, a crop or cover operation is also happening.
Should I crop before resizing?
Usually yes when the destination ratio differs from the original. Establish the intended composition from the best source, then resize that crop to its delivery dimensions.
Is object-fit: cover the same as permanently cropping the file?
No. It crops the visible presentation inside the element while the underlying source file remains unchanged.
Sources and further reading
- MDN: object-fit
- MDN: Fill a box with an image without distorting it
- MDN: Responsive images and art direction
Image Resizing & Dimensions
A practical series on choosing, resizing, cropping, and delivering the right image dimensions for the web.
- Image Resizing: The Complete Guide to Dimensions, Resolution and Aspect Ratio
- How to Resize an Image Without Losing Visible Quality
- Crop vs Resize: What’s the Difference?
- Aspect Ratio Explained: How to Resize Images Without Stretching Them
- Best Image Size for a Website: Hero, Banner, Blog and Content Images
- Best Hero Image Size for Desktop and Mobile
- Pixels vs Resolution vs File Size: What Actually Matters on the Web?
- Does DPI Matter for Web Images? The 72 DPI Myth Explained