- Photos that need to fit a CMS or template's maximum pixel size
- Screenshots or camera photos far wider or taller than a slide or widget allows
- Preparing an image for a destination that names dimensions, not kilobytes
Fit a pixel ceiling, not a byte one
Resize an image to fit the frame.
This is not a file-size tool. Name the maximum width and height and FileFit scales the whole photo down to fit inside them, aspect ratio intact, without ever cropping, stretching, or enlarging it.
Exact-size image engine
Set the ceiling. We find the fit.
Why this ceiling
When the number you were given is a pixel size
A CMS, a slide template, or a widget that says '1920×1080 recommended' is not describing a file-size ceiling — a small JPEG can still be far too many pixels wide. This tool solves the actual constraint directly: it computes the largest size that fits inside your width and height limit and stops there, so nothing gets cropped out and nothing gets stretched to fill space it shouldn't.
Dimensions shrink; quality does not have to
Because there is no byte ceiling to chase, FileFit does not trade away visual quality to hit a target — it fixes the pixel size first, then encodes at a quality high enough that resizing is the only visible change. The one exception is the file itself: the result is never allowed to be larger than the original you dropped in, even though shrinking pixels usually shrinks bytes anyway.
- The result's width and height are at or under the ones you asked for
- Nothing in the frame was cropped — the whole original photo is still visible
- The subject still reads clearly at the new, smaller size
A measured result
Compression is an action.
Compatibility is an outcome.
Inspect
We verify the file signature, dimensions, format, and size before planning a change.
Search
The engine tests dimension and quality combinations instead of applying a generic preset.
Validate
The output is checked independently against the actual byte limit before it is called ready.
Adaptive exact-size engine
Every byte has a job.
A percentage slider cannot know your upload limit. FileFit starts with the constraint, preserves a high visual-quality floor, then uses the available byte budget as fully as the image allows.
- 01Decode safelyTrue file type, real dimensions
- 02Find the scaleLargest useful pixel area
- 03Refine qualityIterative search, not a preset
- 04Prove the resultSize, format, image, privacy
Before you drop a file
Nothing vague.
Does this crop or stretch my photo to hit the exact size?
No. FileFit preserves the original aspect ratio and scales the whole image down to fit inside your width and height limit — the result may be narrower than your maximum on one axis if the photo's proportions call for it, but nothing outside the original frame is cut, and nothing is stretched out of shape.
What if my photo is already smaller than the size I set?
It is left at its original size. This tool only ever scales down to fit inside a limit — it will not enlarge a smaller photo up to your target, since that only adds blur, not real detail.
Will the resized file also be smaller in size?
Almost always, since fewer pixels usually need fewer bytes to encode — but that is a side effect here, not the goal. If you need a specific byte ceiling instead of a pixel one, use one of the exact-size tools; they solve the opposite problem.
Does the image upload anywhere?
No. The image is decoded, resized, encoded, and checked inside your browser. Network transfer for the image is zero bytes.
What happens to GPS and camera metadata?
It is not copied into the new JPEG. The result contains the rendered image pixels, which also avoids spending the size budget on invisible data.
Which image formats can I start with?
FileFit accepts JPG, PNG, HEIC, WebP, and AVIF images and produces a standard JPEG result. iPhone HEIC photos work directly. It checks the file signature instead of trusting only the filename extension.