Resize any image to exact dimensions, compress for web, batch resize for social media — all free, no signup, no watermark. Works on phone and desktop.
Last Tuesday I needed to resize 47 product photos for a friend's Etsy shop. Each one had to be exactly 2000x2000 pixels, under 1MB, and ready to upload before her evening launch. She was panicking. I told her to give me ten minutes.
I opened a browser tab, dropped all 47 images in, set the dimensions, hit resize. Done. No software to install. No account to create. No watermark stamped across her lovingly photographed ceramics. Ten minutes, and she had 47 perfectly sized images sitting in her downloads folder.
This is what image resizing looks like in 2026, and it's wild how many people still don't know these tools exist.
I've been resizing images for the web since the days when you needed a $700 copy of Photoshop to change an image from 3000 pixels to 1200 pixels. The fact that you can now do this — including batch resizing, format conversion, and intelligent compression — completely free, in a browser, on your phone, is genuinely one of the best things about the modern internet.
This guide covers everything. Not just "how to make an image smaller" — that's a two-sentence answer. I'm talking about the exact dimensions every social media platform requires in 2026, why some resized images look terrible and how to prevent it, what DPI actually means (and when it doesn't matter at all), how to handle batch resizing without losing your mind, and the privacy implications most people never think about.
Let's get into it.
Here's a question: when was the last time you uploaded a photo exactly as your phone captured it?
Modern smartphones shoot at absurd resolutions. An iPhone 16 Pro captures 48-megapixel images — that's 8064x6048 pixels, roughly 12-15MB per photo. A Samsung Galaxy S26 Ultra shoots at 200 megapixels. These are fantastic for printing wall-sized canvases. They're terrible for literally everything else.
If you're running a blog, online store, or portfolio, your images are probably the single heaviest thing on your pages. The HTTP Archive's 2026 data shows images account for roughly 42% of the average web page's total weight. An unresized phone photo on your homepage could be 15MB. Your entire page should ideally be under 2MB.
Every extra megabyte costs you:
Most email providers cap attachments at 25MB. A handful of unresized phone photos will hit that limit instantly. Even if the email goes through, your recipient's inbox takes forever to load, and their IT department silently hates you.
Every social platform has specific dimension requirements. Upload the wrong size and your image gets cropped awkwardly, compressed aggressively, or displayed with weird black bars. I'll give you the exact dimensions for every major platform later in this guide.
Your phone's 256GB of storage fills up a lot faster when every photo is 15MB instead of the 200KB it actually needs to be for 99% of use cases.
This one's counterintuitive — sometimes you need to resize up for printing, or at least understand the relationship between pixels and physical size. More on this in the DPI section.
If you just need to resize one image right now and don't care about the theory, here's the fastest path:
That's it. The whole process takes about 15 seconds.
But if you want to understand why certain settings matter and how to get the best possible results, keep reading. The difference between someone who just resizes images and someone who does it well is significant — especially if you're doing it for a business, a brand, or a portfolio.
Before we get into specific use cases, let's clear up some terminology that confuses almost everyone.
A pixel is a single dot of color. When someone says an image is "1920x1080," they mean it's 1920 pixels wide and 1080 pixels tall. That's 2,073,600 total pixels — roughly 2 megapixels.
For anything displayed on a screen — websites, social media, emails, presentations — pixels are the only unit that matters. Period.
Here's where people get confused. DPI (dots per inch) and PPI (pixels per inch) tell you how many pixels fit into one physical inch when you print the image. A 300 DPI image at 3000x2000 pixels will print at 10x6.67 inches.
For screens, DPI is irrelevant. A 1920x1080 image at 72 DPI and a 1920x1080 image at 300 DPI look identical on your monitor. The screen doesn't care about DPI — it just displays the pixels. This is one of the most common misconceptions in image editing.
When does DPI matter? Only for print:
The relationship between width and height. A 1920x1080 image has a 16:9 aspect ratio. A 1080x1080 image is 1:1 (square). An 1080x1350 image is 4:5.
When you resize an image, you generally want to maintain the original aspect ratio. If you don't, the image gets stretched or squished, and everything looks distorted. Most online resizers lock the aspect ratio by default — change the width, and the height adjusts automatically.
There are times you want to change the aspect ratio — cropping a landscape photo to a square for Instagram, for example. But that's cropping, not stretching. Cropping removes parts of the image. Stretching distorts it. Never stretch.
This is the section you'll probably bookmark. These are the exact, current dimensions for every major social media platform as of March 2026. I update these whenever platforms make changes, because they do — regularly.
| Content Type | Dimensions (px) | Aspect Ratio | Notes |
|---|---|---|---|
| Square Post | 1080 x 1080 | 1:1 | Classic Instagram format |
| Portrait Post | 1080 x 1350 | 4:5 | Takes up more feed space — higher engagement |
| Landscape Post | 1080 x 566 | 1.91:1 | Gets cropped in grid view |
| Story / Reel | 1080 x 1920 | 9:16 | Full-screen vertical |
| Profile Photo | 320 x 320 | 1:1 | Displays at 110x110, upload at 320 |
| Carousel | 1080 x 1080 or 1080 x 1350 | 1:1 or 4:5 | All slides must match |
Pro tip: The 4:5 portrait format (1080x1350) is the sweet spot for Instagram feed posts. It takes up more vertical real estate in the feed, which means more screen time and typically higher engagement. Square posts are fine, but portrait outperforms them consistently.
| Content Type | Dimensions (px) | Aspect Ratio | Notes |
|---|---|---|---|
| Feed Post | 1200 x 630 | 1.91:1 | Optimal for link previews too |
| Square Post | 1080 x 1080 | 1:1 | Works well in feed |
| Cover Photo | 1640 x 924 | 16:9 | Mobile crops differently — keep key elements centered |
| Profile Photo | 170 x 170 | 1:1 | Displays as circle, upload at 170+ |
| Event Cover | 1200 x 628 | 1.91:1 | Similar to feed post |
| Story | 1080 x 1920 | 9:16 | Same as Instagram |
| Group Cover | 1640 x 924 | 16:9 | Same as page cover |
Pro tip: Facebook's cover photo is notoriously tricky because it displays differently on desktop and mobile. Keep all important elements (text, faces, logos) in the center 820x312 safe zone.
| Content Type | Dimensions (px) | Aspect Ratio | Notes |
|---|---|---|---|
| Single Image Tweet | 1600 x 900 | 16:9 | Displays in full without cropping |
| Two Images | 700 x 800 each | 7:8 | Side by side |
| Profile Photo | 400 x 400 | 1:1 | Displays as circle |
| Header/Banner | 1500 x 500 | 3:1 | Gets cropped on mobile |
| Card Image | 1200 x 628 | 1.91:1 | For link previews |
Pro tip: X finally stopped its aggressive auto-cropping in 2024, but 16:9 is still the safest bet for images that display as intended across all devices.
| Content Type | Dimensions (px) | Aspect Ratio | Notes |
|---|---|---|---|
| Feed Post | 1200 x 627 | 1.91:1 | Standard professional format |
| Square Post | 1080 x 1080 | 1:1 | Increasingly popular |
| Portrait Post | 1080 x 1350 | 4:5 | Maximum feed presence |
| Cover Photo | 1584 x 396 | 4:1 | Very wide — text must be large |
| Profile Photo | 400 x 400 | 1:1 | Displays at various sizes |
| Company Page Cover | 1128 x 191 | ~6:1 | Extremely wide |
| Article Cover | 1200 x 644 | 1.86:1 | For LinkedIn articles |
Pro tip: LinkedIn's algorithm favors native image posts over link posts. If you're sharing a blog post, consider uploading a compelling image with the link in the comments rather than using a link preview.
| Content Type | Dimensions (px) | Aspect Ratio | Notes |
|---|---|---|---|
| Video Thumbnail | 1280 x 720 | 16:9 | Minimum 640px wide |
| Channel Banner | 2560 x 1440 | 16:9 | Safe area: 1546x423 center |
| Channel Profile | 800 x 800 | 1:1 | Displays as circle at 98x98 |
| Community Post | 1200 x 675 | 16:9 | Same as standard video |
Pro tip: YouTube thumbnails are arguably the most important images on the internet for content creators. Use high contrast, readable text (if any), and a close-up face when possible. The recommended file size is under 2MB, but I'd aim for under 500KB for the fastest load times in search results.
| Content Type | Dimensions (px) | Aspect Ratio | Notes |
|---|---|---|---|
| Profile Photo | 200 x 200 | 1:1 | Upload higher, it auto-scales |
| Photo Post | 1080 x 1920 | 9:16 | Full-screen vertical |
| Carousel Photo | 1080 x 1920 | 9:16 | Up to 35 slides |
| Content Type | Dimensions (px) | Aspect Ratio | Notes |
|---|---|---|---|
| Standard Pin | 1000 x 1500 | 2:3 | The golden ratio for Pinterest |
| Square Pin | 1000 x 1000 | 1:1 | Less engaging than vertical |
| Long Pin | 1000 x 2100 | 1:2.1 | Maximum length — great for infographics |
| Profile Photo | 165 x 165 | 1:1 | Small — keep it simple |
| Board Cover | 600 x 600 | 1:1 | Square crop |
Pro tip: Pinterest is the one platform where vertical images dramatically outperform everything else. A 2:3 ratio consistently gets more saves and clicks than square or landscape. If you're resizing images specifically for Pinterest, go tall.
Since "resize image for Instagram" is one of the most common searches, let me walk through this specifically.
All images in a carousel must have the same aspect ratio. If you have a mix of portrait and landscape photos, pick one ratio (I recommend 4:5) and crop them all to match. On akousa.net's image resizer, you can process multiple images at once with the same target dimensions — saves a ton of time when you're building carousels.
This is the question I get asked more than any other: "How do I resize a photo without losing quality?"
The honest answer: it depends on the direction.
Making an image smaller almost always looks great. You're removing pixels, not inventing them. A 4000x3000 photo resized to 1200x900 will look sharp and clean, often better than the original because you've eliminated noise and subtle imperfections that were visible at full size.
The key settings for high-quality downsizing:
This is where things get tricky. You can't create detail that doesn't exist. If you have a 400x300 image and try to resize it to 4000x3000, you're asking the software to invent 90% of the pixels. The result is always blurry to some degree.
That said, 2026 AI upscalers are remarkably good. They don't just interpolate pixels — they actually generate plausible detail based on the image content. Faces, text, textures — modern upscalers handle all of these surprisingly well.
Practical limits for upsizing:
Whenever possible, start with the highest resolution original you have. Resize down to your target dimensions. It's always easier to go down than up.
Sometimes you don't want to change the pixel dimensions at all — you just want a smaller file. This comes up constantly with email attachments, CMS upload limits, and website performance.
Here's the thing: an image's file size and its pixel dimensions are two separate things. A 1920x1080 image can be 500KB or 15MB depending on the format, quality setting, and content.
Convert to WebP: WebP produces files 25-35% smaller than equivalent JPEG at the same visual quality. It's supported by all modern browsers. If you're serving images on the web, there's no reason not to use WebP in 2026.
Reduce JPEG quality to 82-85%: The jump from 100% to 85% quality reduces file size by 60-70% with virtually no visible difference. Most people can't tell the difference between 85% and 100% in a side-by-side comparison.
Strip metadata: Photos from cameras and phones include EXIF data — camera model, GPS coordinates, timestamps, color profiles. This can add 50-200KB to every image. Stripping it reduces file size with zero impact on appearance. (Bonus: it removes potentially sensitive location data.)
Use PNG only when necessary: PNG is lossless, which means perfect quality but huge files. Use it for screenshots, logos, and images with text or transparency. For photographs, JPEG or WebP is almost always the better choice.
Use a dedicated compression tool: Tools like the image compressor on akousa.net let you visually compare the original and compressed versions side by side, so you can find the perfect balance between quality and file size.
Choosing the right format before resizing can save you more file size than the resize itself. Here's a no-nonsense breakdown:
Best for: Photographs, complex images with gradients and many colors Compression: Lossy (removes some data to reduce size) Transparency: No File size: Small to medium When to use it: Any time you're working with a photograph and don't need transparency. JPEG handles continuous-tone images (skin, sky, landscapes) beautifully. When NOT to use it: Screenshots, text, logos, or anything with sharp edges and flat colors. JPEG creates visible artifacts around sharp edges.
Best for: Screenshots, logos, text, images requiring transparency Compression: Lossless (no quality loss) Transparency: Yes (alpha channel) File size: Large When to use it: When you need transparency, when the image has text or sharp edges, or when you absolutely need pixel-perfect reproduction. When NOT to use it: Photographs. A PNG photograph can easily be 5-10x larger than a JPEG of the same image with no visible quality improvement.
Best for: Everything on the web Compression: Both lossy and lossless modes Transparency: Yes File size: 25-35% smaller than JPEG at same quality When to use it: Whenever your target is web display. WebP is supported by all modern browsers (Chrome, Firefox, Safari, Edge). It's smaller than JPEG and supports transparency. It's the best general-purpose web format in 2026. When NOT to use it: When you need maximum compatibility with very old software, or for print workflows.
Best for: Next-generation web images Compression: Lossy and lossless Transparency: Yes File size: 30-50% smaller than JPEG When to use it: If you want the absolute smallest file sizes and your audience uses modern browsers. Support is excellent in 2026 — Chrome, Firefox, and Safari all handle AVIF. When NOT to use it: When encoding speed matters (AVIF is slow to encode) or when you need universal compatibility.
Many online image tools, including the format converter on akousa.net, let you convert between all these formats while resizing — so you can do both in one step.
If you've ever needed to resize more than three images, you know the pain of doing it one at a time. Open, resize, save, open, resize, save. It's mind-numbing.
A good bulk image resizer handles this automatically. Here's how to approach it:
Set one target size and stick to it. Decide on your dimensions before you start. For product photos, 2000x2000 is the e-commerce standard. For blog images, 1200px wide is usually perfect.
Use "resize by width" mode if your images have mixed aspect ratios. Set the width (e.g., 1200px) and let the height adjust proportionally. This maintains each image's original composition while standardizing the width.
Choose your output format upfront. If all images are going to the web, convert everything to WebP during the resize. One step, two optimizations.
Watch for orientation issues. Phone photos sometimes have embedded rotation data (EXIF orientation). A good resizer respects this and rotates the image correctly. A bad one ignores it, and your portrait photos come out sideways.
Test with a small batch first. If you're about to process 200 images, try 5 first. Check the output quality, dimensions, and file size. Adjust settings if needed, then run the full batch.
Here's my real workflow when I have a pile of images to process:
Compare this to opening each image in Photoshop individually. For 50 images at 30 seconds each, that's 25 minutes of tedious, repetitive work. The batch approach is not just faster — it's more consistent.
More than half the people reading this are on a phone right now. Good news: you don't need a desktop to resize images.
This is the best approach for phone-based resizing. Modern mobile browsers (Chrome, Safari) handle image processing tools just as well as desktop browsers. You don't need to install yet another app.
Simply open an image resizing tool in your phone's browser, upload from your camera roll, set dimensions, and download. The process is identical to desktop.
This is something most people never think about, but it matters — especially if you're resizing sensitive images (medical records, legal documents, personal photos, proprietary business content).
Most online image tools upload your images to a server, process them there, and send the result back. This means:
Some tools — and this is the approach I strongly prefer — process images entirely in your browser. Your image never leaves your device. The resizing, compression, and conversion all happen locally using your computer's or phone's own processing power.
The advantages are significant:
The image tools on akousa.net process everything client-side. I mention this not as a sales pitch but because it's a genuine technical advantage that matters for privacy-conscious users. Your images never leave your browser.
Watch your network activity. If you open your browser's developer tools (F12 → Network tab) and see no large file uploads when you "upload" an image, it's client-side. If you see a multi-megabyte POST request, the image is being sent to a server.
Simpler test: turn on airplane mode after the tool loads. If it still works, it's client-side.
I've seen every mistake in the book. Here are the ones that come up most often:
Someone has a 200x200 pixel profile photo and wants to use it as a billboard background. No amount of resizing will make that work. You cannot create detail that doesn't exist. Start with the highest resolution original you can find.
When you need to change an image's aspect ratio, crop — don't stretch. A stretched image is immediately, obviously wrong. A cropped image just shows a different portion of the scene, which almost always looks natural.
Every time you open, edit, and re-save a JPEG, it goes through another round of lossy compression. After 5-10 rounds of this, the quality degradation becomes very visible. It's called "generation loss," and it's why you should always:
I see this constantly. Someone takes a photo, saves it as PNG "for better quality," and ends up with a 25MB file that takes forever to load. PNG is lossless, yes — but for photographs, the visual difference between a lossless PNG and an 85% JPEG is imperceptible, while the file size difference is enormous (5-10x).
Modern screens have pixel densities of 2x or 3x. If you're displaying an image at 600px wide on a Retina display, the screen actually uses 1200 or 1800 pixels. If your image is only 600px wide, it'll look blurry on high-density screens.
The fix: Resize to 2x your display size. If the image will display at 600px wide on the page, resize it to 1200px wide. The CSS keeps it at 600px visually, but the extra pixels make it sharp on Retina screens. For most web use cases, 2x is enough — 3x offers diminishing returns for the extra file size.
Social media cover photos display differently on mobile and desktop. Facebook cover photos, LinkedIn banners, and YouTube channel art all get cropped on mobile. Always check how your image looks on both before publishing.
Email is surprisingly hostile to large images. Here's what actually works:
Email clients (Gmail, Outlook, Apple Mail) have a maximum rendering width. Outlook renders at 600px. Gmail is slightly wider, but 600px guarantees your image looks right everywhere. Sending a 2000px wide image to an email that renders at 600px is just wasting bandwidth.
This ensures fast load times, universal compatibility, and happy recipients who don't have to wait 10 seconds for your newsletter to render.
Remember what I said about DPI not mattering for screens? For print, it's a completely different story.
For high-quality printing, you need 300 DPI at the physical print size. Here's the formula:
Required pixels = Print size (inches) x DPI
Examples:
Take your image's pixel dimensions and divide by 300. That gives you the maximum print size at high quality.
Modern phone cameras capture more than enough resolution for large prints. That 48MP iPhone shot can print at nearly 27 inches wide at full quality.
For large prints viewed from a distance — posters, banners, trade show displays — 150 DPI is perfectly acceptable. Your audience isn't pressing their nose against a 3-foot poster; they're viewing it from several feet away, where 150 DPI is indistinguishable from 300 DPI.
Favicons need multiple sizes: 16x16 (browser tab), 32x32 (Retina tab), 180x180 (Apple touch icon), 192x192 (Android Chrome), and 512x512 (PWA splash). Start with a 512x512 source and resize down. Simpler icons resize better than complex logos.
When someone shares your link on social media, the preview image pulls from your Open Graph tags. The universal safe size is 1200 x 630 pixels (1.91:1 ratio). This works across Facebook, X, LinkedIn, and most messaging apps.
Product images for Google Shopping must be:
If you regularly work with images — for a blog, an online store, social media, or client work — having a repeatable workflow saves enormous amounts of time.
Organize originals: Keep full-resolution originals in a dedicated folder. Never modify originals directly.
Decide on standard sizes: Create a reference sheet for the dimensions you use most. For example:
Batch process: When you have new images, process them in batches. Resize everything to all needed sizes in one session rather than doing it piecemeal throughout the week.
Name consistently: Use a naming convention that includes the size: product-photo-1200x675.webp, headshot-1080x1080.jpg. When you're looking for the right version later, you'll thank yourself.
Compress after resizing: Resize first, then compress. Compressing before resizing can introduce artifacts that get amplified when the image is scaled.
If multiple people handle images for your brand, create a shared reference document with exact dimensions for every use case, standardize on one or two tools, and set quality guidelines (e.g., "JPEG 85%, WebP for web, always strip metadata"). Review outputs periodically — quality drifts when multiple people are involved.
Yes. Browser-based tools work on mobile. Open the tool in Chrome or Safari, upload from your camera roll, set dimensions, download. No app required.
Resizing down (making smaller) has minimal quality impact. Resizing up (making larger) always reduces quality to some degree, though AI upscaling has gotten very good at minimizing this.
JPEG at 85% quality. All social platforms accept JPEG, it's universally compatible, and at 85% quality the file is small without visible compression. Some platforms also accept WebP and PNG, but JPEG is the safest universal choice.
Most resizing tools don't let you specify an exact file size. Instead: resize to reasonable dimensions, compress at 80-85% quality, and check the result. If it's still too large, lower the quality to 75% or reduce the dimensions further. For photos that need to be under a specific limit, the image compressor on akousa.net shows you the output file size in real time as you adjust the quality slider.
For web display, yes. WebP produces 25-35% smaller files at equivalent visual quality, supports transparency, and is supported by all modern browsers. For email and print, JPEG remains more universally compatible.
It depends on the tool. Some preserve EXIF data, some strip it. For web use, I recommend stripping it — smaller file size and no leaked GPS coordinates. For archival purposes, keep it.
Tools that process images client-side (in your browser) are completely safe — your images never leave your device. Server-based tools require you to trust the provider. When in doubt, use a client-side tool or turn on airplane mode after the page loads to verify.
Avoid tools that offer a "free trial" of a paid product — those are the ones that add watermarks. Genuinely free tools like the image resizer on akousa.net don't watermark because resizing is their core free feature, not a teaser for a subscription.
Image resizing is one of those tasks that sounds simple but has surprising depth. The difference between someone who just makes images smaller and someone who does it well shows up in page load times, social media engagement, print quality, and professional polish.
Here's what I want you to take away from this guide:
The tools exist, they're free, they work on your phone, and they don't require a Computer Science degree. There's no excuse for uploading a 15MB unresized phone photo to your website in 2026.
Go resize something. Your website visitors, email recipients, and social media followers will thank you — even if they never know why everything suddenly looks and loads better.
Akousa