Image Resizer

How to Resize Images Online

1. Choose Your Files: Drag and drop images onto the page or click "Choose photos" — up to 50 at once. The first photo opens in the editor and the rest line up as thumbnails below it; with two or more photos open, "Add more" adds files to the same batch.
2. Set the New Size: In Resize, type a "Width" or "Height" in pixels or percent — with "Keep aspect ratio" on, the other side follows — or pick a "Size preset" (percent of original, a long edge such as 1600 px, a target height, or a platform size such as an Instagram post, which crops to fill that exact size). Decimals like 12.5 % work. The size applies to every photo in the batch.
3. Pick the Output Format (Optional): "Save as" keeps "Same as original" or saves as JPG, PNG, WebP or another format. For JPG, WebP and AVIF output, the "Quality" slider (40–100) trades file size against detail. Resize, Crop, Rotate and Flip all work in the same session, and "Undo" steps back.
4. Download: Click the Download button, which names the output format (for example "Download PNG"), for one photo, or "Download all (.zip)" for a batch — "Download one by one" saves the files separately. Most images are processed right in your browser and are not uploaded; a file your browser can't decode, such as EPS or camera RAW, is either processed on our servers and deleted automatically afterward, or skipped with a note. No sign-up, no watermark.

Why Resize an Image?

Most photos straight out of a phone or camera are 4000–8000 pixels wide — far larger than any screen, social platform, email attachment, or print job actually needs. Resizing trims a 12 MB iPhone HEIC down to a 400 KB JPG that loads instantly, fits Gmail's 25 MB attachment cap, and won't blow past Discord's 20 MB free upload limit. It's the single biggest lever for page-load speed on image-heavy sites — Google's Core Web Vitals routinely flag oversized images as the dominant LCP cost.

• Social media uploads — Instagram crops anything wider than 1080 px; Facebook re-compresses large uploads aggressively. Resizing before upload gives you a sharper final post than letting the platform downscale.
• Email and messaging — Gmail caps attachments at 25 MB total, Outlook.com at 20 MB, Discord at 20 MB on the free tier (raised from 10 MB in August 2026). One 4K phone photo can blow the budget; resizing to 1920 px wide fixes it.
• Web and blog publishing — Most blog content areas display at 800–1200 px wide. Serving an 8000-px source forces the browser to download megabytes it will immediately discard. WordPress, Ghost, and most CMS platforms compress further on upload — start with a right-sized image instead.
• E-commerce listings — Shopify recommends 2048×2048 px for product photos; eBay accepts up to 9000 px on the long side but recommends 1600 px. Etsy crops to 2700×2025. Match the platform target before uploading.
• Passport and ID photos — US passport is 2×2 inches (600×600 px at 300 DPI per State Department spec). UK gov.uk requires at least 600×750 px and 50 KB–10 MB. Schengen and most EU countries use 35×45 mm. Match the country before submitting.
• Print at known DPI — A 6×4 inch print at 300 DPI needs 1800×1200 px; an 8×10 needs 2400×3000. Anything less prints soft. Resize to the pixel size the print needs; the DPI tag itself is set by your print or layout software.

Social Media Image Size Cheat Sheet (2026)

Verified against Buffer's May 2026 guide and platform recommendations.

Common Size Targets

Format-Specific Resizers

Every format page opens this same editor; files of that format are saved in their own format by default (HEIC is saved as JPG, because browsers can't write HEIC): Resize JPG · Resize PNG · Resize WebP · Resize HEIC · Resize TIFF · Resize GIF · Resize AVIF · Resize BMP. For lossy compression after resizing, see the image compressor. To change format without resizing, use the image converter.

Frequently Asked Questions

Will resizing reduce image quality?

Downscaling (making an image smaller) preserves perceived quality very well — you're discarding data the screen wasn't going to show anyway. Upscaling (making it larger) always reduces sharpness because the resizer has to invent pixels; interpolation can't recover detail that was never captured. The editor lets you enlarge (up to 16,384 px on a side and 120 megapixels) and says how many times larger the result is. For best results, always resize from the largest source you have rather than from a previously downscaled copy.

Does resizing keep transparency (alpha channel)?

Yes, when the output format supports it. PNG, WebP, AVIF, TIFF, ICO and PSD output keep transparency; GIF keeps only 1-bit transparency, so soft edges and shadows become hard-edged. JPG, BMP and PPM have no alpha channel: transparent pixels are filled with white, and the editor says so and offers a "Keep PNG" button.

What's the best format to output for the web?

WebP if your audience runs current browsers — it produces files roughly 25–35% smaller than JPG at equivalent quality and is supported in Chrome (32+), Edge (18+), Firefox (65+), and Safari (16+), with partial support in Safari 14–15.6 (caniuse data). Fall back to JPG for legacy compatibility, or AVIF for even smaller files at the cost of slightly slower decoding. For graphics with transparency or hard edges (logos, screenshots, line art), stick with PNG.

Can I resize a batch of images to the same dimensions?

Yes — drop up to 50 images at once (a mixed batch works too). The size, format and quality you set apply to every file in the batch; "Download all (.zip)" saves every resized result in one ZIP (a very large batch is split into ZIP parts of at most 1.5 GB), and "Download one by one" saves them separately.

How do I resize for a specific file size (e.g., "under 100 KB")?

Resizing only reduces pixel count; file size is a function of pixels × encoding quality. This editor sets size, format and the "Quality" slider (JPG, WebP, AVIF), not a KB target, so resize to a sensible dimension first (e.g., 1080 px wide) and then run the result through the image compressor, which has a target-file-size control. Many passport sites cap photos at 240 KB or 1 MB — the two-step resize-then-compress flow gets there without guesswork.

What's the difference between resize, crop, and compress?

Resize changes the pixel dimensions of the entire image proportionally (or with a forced ratio if you unlock it). Crop discards pixels from the edges to change framing or aspect ratio — the remaining pixels keep their original resolution. Compress keeps pixel dimensions the same but re-encodes at lower quality to shrink the file. They're often combined: crop to the right aspect, resize to the platform target, compress to fit the size cap. Use crop image for the second step.

Does DPI matter when I resize an image?

DPI only matters for print; screens ignore it and draw by pixel count. This editor sets pixel size, not a DPI value, so work out the pixels you need instead: inches × 300 for photo prints (a 6 × 4 in print = 1800 × 1200 px), about 150 per inch for posters and banners seen from a distance, and the platform's pixel size for web and social. Your print or layout software then sets the DPI.

Will EXIF metadata (camera info, GPS, dates) survive a resize?

JPG output keeps the camera, date-taken and GPS tags of a JPG or HEIC source; the Orientation tag is reset to normal because the pixels are already turned upright. PNG, WebP and the other outputs do not carry that EXIF block. There is no remove-location switch, so if you need to strip GPS before posting publicly, save as PNG or WebP or check the file in an EXIF viewer after resizing. Many social platforms (Instagram, Facebook, X) strip metadata server-side regardless, but email attachments and direct uploads do not.

Can I resize RAW camera files (CR2, NEF, ARW, DNG)?

Yes, either here or after one conversion step. RAW files hold undeveloped sensor data that a browser cannot open, so the editor either processes them on our servers — saved as JPG unless you pick another format, and deleted automatically afterward — or says it skipped them. A skipped file can be converted first — CR2 to JPG, NEF to JPG, ARW to JPG or DNG to JPG (TIFF if you want a lossless intermediate) — then resize the result here. Saving back to RAW is not possible: the camera format cannot be re-created from pixels.

What happens to animated GIFs and multi-page TIFFs?

The editor works on one still image. When an animated GIF, WebP or APNG opens, it says that an edit keeps only the first frame, and an edited file is saved as a still. Downloading an animated GIF or WebP without editing gives back the original file, animation intact; an APNG always comes out as a still PNG, because the editor cannot write APNG. A multi-page TIFF works the same way: an edit keeps only the first page, and the editor says so when the file opens.