Image Resizer
Batch resize by pixels, percent or presets, and finally SEE the crop before you download: visual crop frame, movable focal point, honest quality behavior, safe memory limits and one ZIP. Everything runs in your browser.
Drag images here or browse
JPG, PNG, WebP, GIF · up to 20 files · 80 MB and 50 MP per image · resized locally, files never leave your browser
With the lock on, set one dimension and the other follows each image automatically. Unlock and fill both to force exact dimensions.
50 percent halves both dimensions. Values above 100 need Allow upscaling turned on.
Image sizes that matter in 2026
Resize to the size a slot actually displays. The presets above cover the common targets: WordPress featured images at 1200x628, Open Graph link previews at 1200x630, Instagram squares at 1080x1080 and stories at 1080x1920, X headers at 1500x500, YouTube thumbnails at 1280x720, and 400x400 profile pictures. Platform rendering changes over time, so treat exact numbers as current guidance rather than eternal law; the aspect ratio is what matters most, and the crop preview shows you precisely what each ratio keeps.
Oversized images are also the most common page-speed problem: shipping a 4000-pixel photo into a 800-pixel slot wastes bandwidth and Largest Contentful Paint. Resize to roughly the display size (or 2x for high-DPI screens), then run the result through the Image Converter for WebP or AVIF if the page budget is tight.
What this resizer refuses to hide
Most resize tools are honest about dimensions and silent about everything else. This one surfaces the rest: whether your file was re-encoded or kept byte-identical, what format the output actually is, that a JPG matte replaced transparency and with which color, that an animated GIF would lose its animation before you confirm it, that a result came out under the preset because upscaling is off, and that metadata was stripped. Every one of those is shown on the file's own row, not buried in a help page.
Image resizer FAQ
Does resizing reduce image quality?
Honest answer: downscaling discards pixels by definition, and JPG or WebP output is re-encoded, which is lossy. What this tool does is keep the loss invisible: multi-pass high-quality scaling instead of one abrupt jump, quality control for lossy formats, and a true no-change path, when dimensions and format stay identical, your original file is kept byte-for-byte with metadata intact. Tools promising fully lossless resizing are describing something that does not exist.
How does the crop preview work with presets?
Presets like 1080x1080 have a fixed shape your photo usually does not match. In Fill mode the image covers the whole preset and the overflow is cropped; the preview shows exactly which area survives, and you move the kept area by dragging the focal dot, using arrow keys, or typing focus percentages, per file. Fit mode instead shrinks the whole image inside the box without cropping, and Stretch distorts to the exact size. Nothing is cut without you seeing it first.
What are the file limits, and why do they exist?
Up to 20 files, 80 MB and 50 megapixels per image, and requested dimensions up to 8192 px. The megapixel limit is a memory guarantee: a decoded image costs width x height x 4 bytes plus working copies, so one 100 MP panorama would need roughly 800 MB and can freeze a phone browser. Files over the limits are refused with the math shown, instead of crashing your tab.
What does "Same format" mean exactly?
JPG stays JPG, PNG stays PNG, WebP stays WebP, re-encoded at your quality setting when dimensions change. GIF is the exception: resizing produces a still PNG, and animated GIFs are flagged and require an explicit "first frame" confirmation instead of being silently flattened. The resolved output format is shown on every row before you download.
What happens to transparency when converting to JPG?
JPG has no alpha channel, so transparent areas must become a color. This tool composites them onto a background you choose, white by default, black or any custom color, instead of leaving the result to browser-dependent black. The matte is applied in the actual output, not just the preview.
Are my photos uploaded? What about EXIF and location data?
Nothing is uploaded; decoding, cropping, scaling and encoding all run in your browser. Orientation from EXIF is applied to the pixels first, so phone photos stay upright. Re-encoded outputs have EXIF metadata removed, including GPS location and capture date, which is stated in the tool because it matters both ways: privacy win, but keep your originals if you need the metadata. The no-change path keeps the original file untouched.
Why did my image come out smaller than the preset?
Because upscaling is off by default: enlarging a small image cannot add detail, only blur. When your source is smaller than the preset, the tool produces the largest sharp result at the preset's aspect ratio and labels it, instead of silently inflating pixels. Tick "Allow upscaling" if you need the exact size regardless.
More free tools: Resize to 1200x630 · Instagram Resizer · YouTube Thumbnail · WordPress Sizes · Image Converter · Image Compressor · Favicon Generator