Skip to main content

Image Resize

Resize an image to the specified dimensions. Drag the handle in the bottom-right corner to resize interactively. All processing happens in your browser — no data is sent to any server.

After processing, chain to:

Drop an image or click to select

Supported formats: image/* · Max size: 50MB

How to use

  1. Drag & drop your image

  2. Set width/height (px or %); lock the aspect ratio if you like

  3. Download the resized image

Resizing is usually forced by a specification: a photo that must be an exact pixel size, a social header that has to fit, article images that should share a width. Often only one dimension is specified — "800px wide" — and working out the other one by hand every time is tedious.

OFFiler keeps the aspect ratio locked by default, so typing one number fills in the other. It runs in the browser and previews the result immediately. Below: what the resize actually does, how the output format is decided, and when to resize rather than compress.

What happens inside

The image is redrawn at the requested pixel size

The resize allocates a canvas at the width and height you asked for and draws the source image into it. The browser's rendering engine handles the interpolation, which gives smooth results when scaling photographs down. With the aspect-ratio lock on, entering a width computes the height from the original proportions.

You can also enter dimensions larger than the original, but enlarging does not create detail that was never captured — edges come out soft. If you need a large version for print, the reliable answer is to go back to a larger source.

The output keeps the input's format

The resized image is written back in the same format as the input: feed it a JPEG and you get a JPEG, feed it a PNG and you get a PNG, with the extension matched accordingly. This avoids the classic surprise of "I only resized it and now everything is a heavyweight PNG".

If you want to change format as well, resize first and chain the format converter afterwards.

Resize or compress?

If the pixel count is excessive, resize first

Resizing and compressing attack file size differently. A 4000×3000 phone photo displayed 800px wide on a blog carries more than twenty times the pixels it will ever show. Lowering the quality in that state still spends bits on pixels nobody sees.

Resize down to the dimensions you actually need first, then compress if it is still too big. For visible quality per byte, that order wins.

Metadata does not carry over

Because the image is redrawn through a canvas, EXIF (capture time, camera model, GPS) and ICC profiles do not survive the resize. That is convenient from a privacy standpoint and inconvenient if you wanted to keep the capture data. Files are handled up to 50 MB each.

Chaining around the resize

Crop first, then hit the exact size

For something like a social avatar — "square, at this exact size" — resizing straight away distorts the picture. Crop the region you want as a square first, then resize to the required dimensions, and the subject keeps its proportions while the specification is met.

Specs and limits

Input formats
Any image the browser can display (JPEG, PNG, WebP, …)
Size limit
50 MB per file
Output format
Same format as the input
Aspect ratio
Lock is optional; when on, one dimension fills in the other
Upscaling
Possible, but adds no real detail
Discarded
EXIF, ICC colour profile
Network
No file upload; all processing in-browser

Frequently asked questions

Does enlarging improve quality?
No. Upscaling can't add detail beyond the original resolution and may look soft. Downscaling preserves quality well.
Can I match SNS recommended sizes?
Yes, specify exact pixels. To also reduce file size, chain into Compress Image afterward.

Where this tool fits

Step-by-step guides that combine this tool with others, organized by what you're trying to do.