How do you get a photo under an upload size limit?

An upload limit doesn't always mean you need a smaller picture. Here's how to reduce the file size, keep the dimensions you need, and check the photo before you send it.

FluffyBench · 6 min read · Reviewed October 21, 2026

What must your photo upload satisfy?

Think of file size as your photo's packed weight, and pixel dimensions as the picture's width and height. An upload can check both, plus the file type.

Bytes measure packed file weight; pixels describe width and height; the format determines the file type. Lower quality changes packed bytes; resizing changes the picture grid; conversion changes the type. PNG has no lossy Quality slider. — A smaller file still needs the right dimensions and an accepted file type. How these image results were measured · Photo: Jeremy McKnight, Unsplash License, via Unsplash.

Follow the destination's stated cap, dimensions and accepted types. If it asks for JPG, a smaller AVIF won't meet that rule. Lower quality stores less detail without reducing the pixel grid; resizing changes the grid itself.

Can you reduce file size without shrinking the photo?

Yes. Saving a JPG as a more compressed JPG can keep its width and height.

Original: 1,240,605 bytes. Saved JPG: 79,598 bytes. Both are 1,600 × 1,200 px. Small context photos mark matching crops; the foam is coarser in the saved copy. — FluffyBench's JPG converter took this waterfall JPG from 1.2 MB to 79.6 KB under a 100 KB cap, with its pixel dimensions unchanged. Matching rock-and-whitewater crops show fine foam texture becoming coarser. · Photo: Jeremy McKnight, Unsplash License, via Unsplash.

Doing it in FluffyBench

FluffyBench's JPG converter can lower quality to meet a per-file cap while keeping Size on Original. The walkthrough uses a JPG destination; the To menu also offers AVIF and WebP when your upload accepts them.

The Limit each file's size control sets a ceiling, not an exact byte count for the saved copy. A result below the number you entered still meets that byte rule, and the cap applies separately to every photo if you add several at once.

Here's the job from choosing a photo to saving a copy. The 100 KB setting is an example; use your upload's cap.

Step 1. Choose a type the upload accepts in To, add your photo with Choose images, and open Settings.
1. Keep JPG if the upload requires JPG.
2. Choose images adds your photo.
3. Settings opens the controls.
Step 2. Keep Size on Original. Enable Limit each file’s size and enter your cap in KB per file.
1. Original keeps width and height.
2. Enable the file-size limit.
3. 100 means a 100 KB cap here.
Step 3. Click Settings again to close the phone panel, then press Convert. Wider screens keep Settings alongside the workspace.
1. Click the gear again to close Settings.
2. Convert uses your selected settings.
Step 4. Read the completed file’s dimensions and size, then choose Download to save your copy.
1. Read the output dimensions and size.
2. Download saves the finished JPG.

Need one photo under a file-size cap?

Open FluffyBench's JPG converter

Use Limit each file's size to make a copy with an accepted output type.

Is your smaller photo ready to upload?

Use these three checks on your downloaded copy before you send it.

Step 1: inspect the downloaded photo at its intended display size; the illustrated full photo and foam crop show where to look. Step 2: compare its bytes, dimensions and type with the upload requirements, keeping your original until you're happy. Step 3: try the upload and read its acceptance or error message. — Passing the file-size rule is one part of getting a usable upload. · Photo: Jeremy McKnight, Unsplash License, via Unsplash.

What if a full-size photo still won't fit?

The quality setting has a lower end. If FluffyBench's JPG converter can't meet your cap there, an accepted format change or fewer pixels gives it another way to reduce the file size.

At 10 KB, full-size JPG and WebP stayed over the cap. An AVIF at 1,600 × 1,200 px and a JPG resized to 800 × 600 px fit.

Source and both saved outputs with full-image context, locators and matching crops. Source and AVIF patches are 30 px square; the resized JPG patch is 15 px square. Each is enlarged eightfold. — Both saved crops lose fine foam detail; the resized JPG crop has also lost nearly all its color. The crops share the same magnification, so the resized patch is smaller. · Photo: Jeremy McKnight, Unsplash License, via Unsplash.

If your upload permits fewer pixels, the extra Dimensions and file-size settings below use the same JPG workflow you've already seen.

Step 1. Choose Dimensions and the width and height the upload allows. Keep aspect ratio avoids stretching; the file-size cap stays enabled.
1. Dimensions enables Width and Height.
2. Set Width 800 and Height 600; keep aspect ratio checked.
3. Enable Limit each file's size and enter 10 KB per file.
Step 2. Retained JPG result: the smaller grid fits the cap, with coarser detail.
1. The retained JPG meets this cap at the smaller dimensions.

If the upload requires the original dimensions and JPG, neither of those alternatives meets its rules. You'll need a less detailed source photo or a different limit from the destination.

Need one resize rule for a batch?

Open FluffyBench's Image Space Saver

Apply the same dimensions and output type to several photos.

How we reviewed

Reviewed October 21, 2026

Results measured 2026-10-15 on build: e9741d65 in Chromium 153.0.8010.12. The input is a 1,600 × 1,200 px JPG of 1,240,605 bytes. Center-cropped from the staged Unsplash 2400 by 1600 JPEG and encoded as JPG at quality 96 with 4:4:4 chroma sampling using sharp 0.35.5. Each successful output was downloaded from the local FluffyBench JPG converter, then checked by file length and decoded dimensions.

The walkthrough is a fresh illustration of the current controls, separate from the dated measurements. The main output row is an illustration, not a new measurement record. The resize branch ends with an illustration of the retained JPG and its recorded properties.

The measurements use one prepared waterfall photo; results depend on the photo and settings.

Target size was enabled at decimal 100 KB, 50 KB and 10 KB. JPG, AVIF and WebP fit the first two caps at the original dimensions. Resized JPG used 800 × 600 px at the largest and smallest caps; the middle cap used 560 × 420 px.

One KB here means 1,000 bytes. Some uploads use 1,024 instead; 100,000 bytes is below 102,400 bytes.

The main comparison marks a wider rock-and-whitewater region and shows the same crop in both files. Complete-file byte counts and dimensions are printed with each panel; no new encoding measurements were added.

The tight-cap panels use the recorded 30 px square region and the matching 15 px square resized region, enlarged 8 times without smoothing. The locator uses a contrasting outline to keep the small patch visible.

The retained files establish exact byte counts and dimensions; the crops show the visual tradeoff.

Image credits

A large waterfall surrounded by trees in a forest — Jeremy McKnight. Unsplash License. Derived from the staged 2,400 × 1,600 Unsplash JPEG: center-cropped and encoded as the measured 1,600 × 1,200 JPG input, then converted to a 1,200 × 900 WebP display copy. The photo callout marks the matching rock-to-whitewater edge used by all four local converter outputs.