Image Resizer

How to Resize Images Online

1. Upload Your Image: Drag and drop or click "Add Files" to select an image from your device. Only the first file you pick is loaded — this editor works on one image at a time, not a batch queue. XConvert handles JPG, PNG, WebP, HEIC, TIFF, GIF, BMP, AVIF, ICO, EPS, PSD, and more.
2. Choose a Resize Method: Pick Width and Height to enter exact pixel targets (e.g., 1080×1080 for an Instagram square). Pick Percentage to scale proportionally (50% halves both dimensions). Or pick a Resolution Preset — 480p, 720p, 1080p, 1440p, 2160p — when you need a standard video-frame size. Aspect ratio is preserved by default; set width OR height and the other adjusts automatically.
3. Set Output Format (Optional): Keep the source format or convert during resize — pick JPG for smaller photos, PNG for transparency, WebP for the best size-to-quality ratio. Quality Preset (Low → Highest) controls lossy re-encoding. For PNG specifically, "Same as source" preserves transparency exactly.
4. Resize and Download: Click "Resize." Processing happens locally in your browser — no sign-up, no watermark. Save the resized image, then use + Start New to load the next one — there's no batch export.

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 10 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 10 MB on the free tier (raised in Sept 2024 from the old 8 MB cap, then standardized at 10 MB). 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. Set DPI (72/96/150/200/300/600/1200) in the resize options when output dimensions matter for print.

Social Media Image Size Cheat Sheet (2026)

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

Common Preset Targets

Format-Specific Resizers

Need to keep a specific format end-to-end? Use the dedicated tool to preserve format-specific metadata: 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; bicubic and Lanczos algorithms interpolate cleanly but can't recover detail that was never captured. 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 source and target formats both support it. PNG, WebP, AVIF, GIF, HEIC, and TIFF preserve transparency through a resize. If you resize a transparent PNG and output JPG, the transparent pixels get filled with white (JPG has no alpha channel) — pick PNG or WebP as the output if you need transparency to survive.

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?

Not on this page. The Image Resizer holds one image at a time — set width/height/percentage, resize, save, then + Start New for the next file. If the sources have different aspect ratios and you've locked the ratio, each image fits within the target as a maximum bound rather than stretching to fit. For a genuine batch — the same dimensions applied to dozens of files in one session — use Image Compressor or a format-specific compressor like Compress PNG: both run server-side, accept multiple files, and include a resize step alongside compression.

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

Pure resizing only reduces pixel count; file size is a function of pixels × encoding quality. To target a specific size in KB or MB, resize to a sensible dimension first (e.g., 1080 px wide) and then run the result through the image compressor, which exposes a target-file-size control. Many passport sites cap photos at 240 KB or 1 MB — the two-step resize-then-compress flow nails it without iteration.

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.

What DPI should I pick for print vs screen?

For screen (web, social, email), DPI is metadata only — what matters is pixel count. Set 72 or 96 DPI; nobody will see a difference. For print, DPI determines physical size: a 1200×1800 px image at 300 DPI prints as 4×6 inches; the same file at 150 DPI prints as 8×12 inches but looks softer. Photo labs and printers standardize on 300 DPI for sharp prints. Passport offices specifically require 300 DPI on photo specs.

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

JPG and HEIC outputs preserve most EXIF tags by default. PNG and WebP outputs may strip GPS and camera-specific tags depending on the encoder. If you need to keep — or deliberately remove — location data before posting publicly, check the file in any 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)?

Not in this editor. RAW files hold undeveloped sensor data and the resizer works on decoded pixels, so convert the file 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.