Resizing vs Compressing: Which One Actually Shrinks the File
The quality slider and the width box feel like two ways to ask for a smaller file. They are not. One of them throws away pixels. The other stores the pixels that remain with less precision. On a camera photo, the first move is almost always the one that gets you under the limit without a ruined sky.
They are different operations
Resizing changes how many pixels exist. Compressing, in the way the quality slider uses the word, changes how coarsely those pixels are stored. You can do either without the other. A 6000-pixel JPEG at quality 70 is still a 6000-pixel image, and it is still the wrong file to put in a 400-pixel column. A 800-pixel PNG of a photograph has few pixels and a lossless container, so it can be larger than a gentler JPEG of the same 800 pixels.
People reach for the slider first because it is the control that looks like "smaller." On a camera original, the dimensions are the control that moves the size. The slider is how you stop the resized file from looking cheap.
The pixel arithmetic
Take a 6000 ร 4000 photo. That is 24,000,000 pixels. Shorten the long side to 1920 and keep the aspect ratio: the scale is 1920 รท 6000 = 0.32, so the new height is 1280. The new count is 1920 ร 1280 = 2,457,600 pixels, which is 10.24% of the original. You removed about nine tenths of the pixels before any quantizer ran.
Halving both edges quarters the count, because area scales with the square of the edge. A 4000-pixel side and a 2000-pixel side are not "a bit smaller." They are four times different in pixels. This is why a modest change to the width box beats a dramatic shove of the slider.
The decoded bitmap is larger than the file. RGBA is 4 bytes a pixel. The 6000 ร 4000 frame is 96,000,000 bytes, about 92 MB, while it sits decoded in memory, even if the JPEG on disk was 8 MB. Phones feel that. It is also why a batch of full-size camera files stalls a laptop that shrugged at the same photos once they were 1600 pixels wide. File size and memory size are not the same number.
JPEG bytes do not fall in exact proportion to the pixel count. A smaller image has less to quantize, and the camera file was already compressed, so you should not promise yourself "10% of the pixels means 10% of the megabytes." You should expect a large drop, and you should read the size the studio shows. The point of the arithmetic is to decide which knob to turn, not to predict the byte count to three digits.
Order: crop, resize, then quantize
Each lossy save is a new approximation. If you drop the slider on the 6000-pixel file, upload that to a site, and the site scales it to 1200 pixels, the photograph has been quantized twice and the first file was still huge on the wire. Resize from the camera original to the pixel size you will display, then encode once. Image Studio does both in the same export: the width and height fields set the canvas, and the slider is applied as that canvas is encoded. Set the dimensions before you judge the slider.
Cropping is the third operation, and it is not resizing. A crop throws away pixels outside the frame and keeps the ones inside at their original spacing, until you also set a target width. A square crop of a landscape is a framing decision. It saves bytes only because the frame contains fewer pixels, and only if you do not then scale that crop back up.
The studio will scale to the width and height you type. If both numbers are filled in and they do not match the crop's aspect ratio, the export is stretched to that exact box. There is no "maintain aspect ratio" checkbox in the current Image Studio. Set the side you care about, and make the other side match the crop. The aspect-ratio preset buttons (1:1, 4:5, 16:9, 9:16, free) control the crop frame, not the encoder.
Screens are CSS pixels. Printers are physical inches.
Browsers lay out images in CSS pixels. The DPI number stored in a JPEG is ignored for that layout. A 1920 ร 1080 image tagged at 300 DPI and the same pixels tagged at 72 DPI display at the same size on a page. Changing DPI metadata without changing the pixel dimensions does not make a lighter web image. Do not hunt for a DPI field in the studio. There isn't one, and it would not do this job.
Retina and other high-density screens show more than one device pixel per CSS pixel. A column that is 800 CSS pixels wide looks sharper if the image is about 1600 pixels wide on a 2ร screen. It does not look sharper if the image is 6000 pixels wide. Extra pixels past about 2ร, sometimes 3ร on a phone, cost bytes and decode time and do not create detail the screen can show. The slot-by-slot table is in Compressing Images for Core Web Vitals.
Print is the case where inches matter. A 4 ร 6 inch photo at 300 pixels per inch needs 1200 ร 1800 pixels. At 150 ppi, which is often acceptable for a large print seen from a few feet away, it needs 600 ร 900. Those pixels are the image. The DPI tag is only a hint to the printer about how large to draw them. If you resize a print file down to 800 pixels on the long side, you have given up the print, no matter what the tag says. Keep a print-sized export and a screen-sized export as two files.
PDF pages add one more unit. A PDF point is 1/72 inch, and the PDF Suite builds an image page whose point size equals the pixel size. A 2400 ร 3000 image becomes a page of 2400 ร 3000 points, which is about 33 ร 42 inches, not a letter page. How to handle that is in Images to PDF, and PDF Pages Back to Images.
Upscaling does not invent detail
If the crop is 800 pixels wide and you type 2400, the studio will resample upward. The file gets heavier and the picture gets softer or blockier. It does not recover the texture the camera never captured, or that an earlier resize threw away. Export at the size you have, or go back to the original and crop again.
The resampling the studio does use, when you do need a smaller image, is the browser's high-quality image smoothing on the cropped canvas. That is a normal downscale. It is not a reason to downscale in three hops (6000 to 4000 to 2000 to 1200). One hop from the original to the final size keeps the interpolation honest.
A concrete pass through the studio
- Drop the camera JPEG on Image Studio. Note the pixel size the crop box starts from. That number is the budget you are spending down.
- Decide the destination. A blog column at 2ร is often a 1600-pixel-wide WebP. An email under a 2 MB cap often starts at a 1600-pixel JPEG. A full-page print at 300 ppi is a different, larger file. Write the width down before you touch quality.
- Set that width. Set the height only if it matches the crop. If the crop is 3:2 and the width is 1600, the height is 1067, not a round 1000, unless you are willing to crop or stretch.
- Then set the format and the slider. Photographs: WebP or JPEG around 80. Screenshots: PNG, and the slider will not change the PNG.
- Look at the preview size. If the file is still too heavy, reduce the width by a few hundred pixels and look again. If the file is small enough and the sky is already blocking, you resized too little and crushed too much. Put the slider back and shorten the edge.
- Download. The filename includes the width, which is how you will tell this derivative from the next one. Keep the camera file.
Social networks publish their own pixel recipes and then recompress. Use the sizes in Crop and Resize for Instagram and Social, and still do the resize yourself so their recompress starts from a clean 1080-pixel file instead of a 6000-pixel one.
If the "too big" complaint is a mailbox or a form, the cap and the Base64 margin are in Shrink Photos for Email and Upload Limits. The slider advice on its own, including chroma subsampling, stays in the JPEG guide.
Frequently Asked Questions
Does changing the DPI metadata make a web image smaller?
No. Browsers lay images out in CSS pixels and ignore the JPEG DPI tag. Fewer pixels means a smaller file. A different tag on the same pixels does not.
What if I fill in both width and height?
The studio scales the crop to those exact dimensions. If the two numbers do not match the crop's aspect ratio, the picture is stretched. There is no separate lock-ratio checkbox. Set one side and keep the other in proportion.
Should I upscale a small image for a retina screen?
Only if you accept a softer picture and a heavier file. Upscaling does not recover detail. Export at the pixels you have, or go back to a larger original.
How wide should a photo be for a normal article column?
Often about 1600 pixels wide if you want it sharp on a 2ร screen in a column near 800 CSS pixels. The slot-by-slot table is in the Core Web Vitals guide. A 6000-pixel file does not look sharper in that column.
Set the width, then the slider
Type the pixel size the destination needs. Match the other side to the crop so the export is not stretched.
Open Image Studio