Resize Icons and Assets

Normalize image dimensions for reusable app and web assets.

Recommended Sizes

128 × 128

Small Icon

200 × 200

Thumbnail

256 × 256

Standard

512 × 512

Large

Use Cases

App IconsFood Menu IconsCharacter LibrariesWebsite AssetsDesign Systems

How It Works

Choose a Preset

Select from the existing presets to match the target asset size and usage.

Fit Mode

Choose "contain" to fit within bounds or "cover" to fill the entire area.

Quality Control

Adjust WebP quality from 70 to 90 for the right balance of size and clarity.

Reusable Output

Keep dimensions and compression consistent across repeat exports from one source image.

Sizing and framing tips

Leave breathing room

Small icons need padding. If the subject touches the edge, it can look cropped in app grids or circular masks.

Use square output for libraries

Square presets make mixed food, sticker, and character assets align in a shared UI library.

Do not use one size for everything

Use compact sizes for lists and larger exports only when you need a source for later editing or high-density screens.

For consistent icon and thumbnail sizes

ByteCut helps turn one source image into consistent square assets for app icons, menu thumbnails, design systems, and reusable UI libraries.

What this solves

Normalize mixed source images into consistent output dimensions.
Use square presets such as 128, 200, 256, and 1024 pixels.
Export lightweight WebP assets ready for web and app interfaces.
Use padding to keep the subject visible instead of cropping important edges.

Making a mixed pile of images look like one set

Consistent canvas, inconsistent subjects

Exporting everything at 256 pixels does not make a grid look tidy. What breaks the rhythm is the subject inside the square: one illustration fills the frame edge to edge, the next floats with a wide margin, a third sits off-centre. Square fitting measures where the actual subject is and centres it on the canvas, so the set reads as deliberate even when the sources came from different places and different artists.

Pad rather than crop

When a source is not square, something has to give. Cropping to fill guarantees the frame is full but quietly cuts off whatever sat near the edge — the handle of a pan, the tip of a hat, a logo descender. Padding keeps the whole subject and adds transparent space instead. For icon and thumbnail work, padding is almost always the safer default, since a slightly smaller subject is a much cheaper mistake than a clipped one.

Stray pixels move the whole frame

A single faint speck left over in a corner counts as part of the image, and a naive bounding box will stretch to include it. The visible result is a subject shoved off to one side for no apparent reason. ByteCut measures the dominant subject and ignores small detached specks when it decides where to centre, which is why a cutout with a little leftover noise still lands in the middle of the square.

Pick sizes from where the asset is displayed

A menu thumbnail repeated forty times down a page and a source asset you will re-crop next quarter have opposite requirements. Small presets keep list pages fast; the large preset gives you headroom to reuse the file later. Exporting everything large because it feels safer makes list pages heavy for no visible gain, and every one of those files gets downloaded by every visitor.

Enlarging does not create detail

Resizing down discards information cleanly; resizing up cannot put back what was never captured. A 128 pixel source pushed to 1024 becomes a soft, slightly mushy version of itself, and it will look worse next to assets that started large. When a set has to include one low-resolution source, either find a bigger original or set the whole set to a size the weakest member can actually support.

Image resize FAQ

Can I make a square icon from a rectangular image?

Yes. ByteCut fits the image into a square preset with padding so it can be reused as an icon or thumbnail.

Which size should I use for menu thumbnails?

Food 200px is a good lightweight default. Use Large when you need a bigger source for later editing.

Can I keep transparency after resizing?

Yes. Cleanup outputs preserve transparent backgrounds when exported.

Is this only for icons?

No. The same sizing flow works for menu thumbnails, small product assets, UI previews, and reusable image libraries.

All processing runs locally in your browser. No files are uploaded.

Resize Images