Resize any image to the exact size you need. Nothing ever uploads.

Exact pixels, a percentage, or a one-click social preset — resized entirely on your device. No accounts, no limits.

  • Zero uploads — verifiable
  • Unlimited free use
  • Batch resize
  • Social presets built in

Resize images online

Add your images

Drag & drop images here

or browse your files · you can also paste from clipboard (Ctrl+V)

JPG, PNG, WebP, GIF, BMP, AVIF — everything is resized on your device with a canvas. No file is ever sent anywhere.

    No images yet. Everything stays on this device. Downloads start instantly.
    Resize settings
    Resize by
    New dimensions (px)

    With the lock on, changing one side recalculates the other from the original photo.

    Output format

    90% is the sweet spot for photos. Lower values shrink the file but soften detail. PNG ignores this setting — it is lossless.

    Background for transparent areas (JPG has no transparency)

    Privacy you can verify, not just trust

    Most online image resizers upload your photos to their servers first — some require an account before they even show you the result, and some cap free use at a handful of images a day. This one can't: the resize runs entirely in your browser, on a canvas on your own device. Your images are never sent anywhere — the only requests to other sites are the site's own analytics, which count page views — and it uploads nothing, ever. Don't take our word for it:

    External requests during processing: 0
    1. Press F12 to open developer tools, then the Network tab.
    2. Resize any image above. Watch: apart from the site's analytics, nothing is requested — no uploads, and no image data ever leaves your device.
    3. Extra credit: disconnect your internet after this page loads — resizing still works.

    How to resize an image without losing quality

    Every photo you take is bigger than the place it ends up. A phone camera saves a 4000 × 3000 image; an Instagram post displays at 1080 × 1080; a blog hero rarely shows wider than 1200 pixels. Uploading the full-size original wastes bandwidth, slows the page, and in the case of social platforms gets silently re-compressed by the platform anyway — on its terms, not yours. Resizing first means you control the result.

    This tool resizes the image where it already is: in your browser, on a canvas, with no server involved. Drop an image in, pick exact pixels, a percentage, or a preset, and download the result. Your original file is never modified.

    Resize vs compress: two different jobs

    People use the two words interchangeably, but they fix different problems. Resizing changes the pixel dimensions: a 4000 × 3000 photo becomes 1200 × 900. Compressing changes how much data is used to store those pixels — usually by lowering the JPG quality or switching to a more efficient format. Resizing alone does not guarantee a small file: a 1200 × 900 PNG of a detailed photo can still be over 1 MB. And compressing alone does not change the dimensions, so an oversized image still wastes layout space and bandwidth. The combination is what works: resize a camera photo down to the size the page actually displays, then export it as a JPG at quality 90 (or WebP), and a 5 MB original routinely becomes a file under 200 KB. Use this resizer for the dimensions, and the quality slider for the compression.

    Aspect ratio, explained in one paragraph

    Aspect ratio is simply the shape of the image: width divided by height. A 4000 × 3000 photo is 4:3; a 1080 × 1080 Instagram square is 1:1. When you change the width without changing the height proportionally, the shape changes — and everything in the photo stretches or squashes with it. Faces get wide, circles become ovals. That is why this tool locks the aspect ratio by default: type a new width and the height follows from the original shape, or pick a preset and the image is fitted inside that preset's box, keeping its own shape. The trade-off to understand: a landscape photo fitted to a square preset does not become square — it stays landscape, sized to fit within the square. If you genuinely need a square, crop the image first (or turn the lock off and accept the stretch, which almost nobody wants). The lock exists because silent distortion is the single most common resizing mistake.

    Preset dimensions for every platform

    Each platform publishes a recommended size, and uploading close to it avoids a second, hidden resize by the platform itself. These are the presets built into the tool:

    PresetDimensions (px)Aspect ratioUsed for
    YouTube thumbnail1280 × 72016:9Video thumbnails
    Instagram square1080 × 10801:1Feed posts
    Instagram portrait1080 × 13504:5Feed posts, taller crop
    Instagram story1080 × 19209:16Stories and reel covers
    Facebook post1200 × 6301.91:1Shared link and photo posts
    Facebook cover820 × 312~2.63:1Page cover photo
    X post image1600 × 90016:9Images attached to posts
    X header1500 × 5003:1Profile header banner

    Two practical notes. First, the Facebook cover is unusually wide and short — a photo fitted with the lock on will leave large empty bands, so covers usually need a crop first. Second, uploading larger than the recommendation does not help: platforms downscale anyway, and you have only paid extra upload time for the privilege.

    Quality loss: what actually degrades, and what doesn't

    Making an image smaller almost never causes visible quality loss — the pixels that remain are the same pixels, just fewer of them. What people blame on resizing is usually the format: a JPG saved at quality 50 shows blocky artefacts around edges and gradients, while the same image at quality 90 looks identical to the original at normal viewing distance. Making an image larger is the genuinely lossy direction: no tool can invent detail that was never captured, so an upscaled photo looks softer the further you stretch it. Enlarging up to about 2× is acceptable for screen use; beyond that, the softness is obvious and no amount of sharpening fixes it. The honest rule: shrink freely, upscale sparingly, and judge the result by looking at the resized preview at 100% zoom — not by the file size.

    Honest limitations

    Upscaling can't add detail

    Enlarging a 400 px image to 2000 px spreads the same pixels thinner. The result is softer, never sharper. If you need a bigger image, start from the largest original you have.

    GIFs become still images

    An animated GIF is resized as a single still frame — the animation is not preserved. Convert or resize the frames separately if the motion matters.

    JPG has no transparency

    Exporting a transparent PNG as JPG flattens the transparent areas onto the background colour you pick (white by default). Use PNG or WebP output to keep transparency.

    Metadata is stripped

    Resizing through a canvas drops EXIF data, including camera settings and GPS location. That is good for privacy, but if you need the original metadata, keep the original file — this tool never modifies it.

    Very large images need a capable device

    Resizing happens in memory, so an image above 8000 pixels on a side, or a batch of dozens of 20-megapixel photos, can slow down or run out of memory on a low-end phone. Resize in smaller batches if a file fails.

    Five mistakes people make when resizing images

    1. Stretching instead of fitting. Turning the aspect-ratio lock off and typing both dimensions distorts the photo. Keep the lock on unless you genuinely want a stretch.
    2. Uploading the full-size original. A 12 MB phone photo on a blog post slows the page for every reader. Resize to the display width first — usually 1200 px or less.
    3. Upscaling a tiny image and expecting it to look sharp. It won't. Find the largest original, or accept the softness.
    4. Saving a logo as JPG. JPG's compression smears sharp edges and kills transparency. Logos, icons, and screenshots belong in PNG or WebP.
    5. Resizing the only copy. Keep the original. A resized image can never be faithfully enlarged back to the original quality, and platforms change their recommended sizes.

    Frequently asked questions

    Does resizing an image reduce its quality?

    Making an image smaller almost never causes visible quality loss: the pixels that remain are the same pixels, just fewer of them. The quality loss people notice usually comes from the format and the quality setting, not the resize itself — a JPG saved at quality 90 keeps its detail, while the same image saved at quality 50 will show blocky artefacts. Making an image larger is different: no tool can invent detail that was never there, so an upscaled photo looks softer the further you stretch it. As a rule of thumb, shrinking by any amount is safe, and enlarging up to about 2x is acceptable for screen use, but beyond that the softness becomes obvious.

    What is the difference between resizing and compressing an image?

    Resizing changes the pixel dimensions — a 4000 x 3000 photo becomes 1200 x 900. Compressing changes how much data is used to store those pixels, usually by lowering the JPG quality or switching format. They are often used together: resize a camera photo down to the size a web page actually displays, then compress it to a sensible quality, and the file can shrink from 5 MB to under 200 KB. Resizing alone does not guarantee a small file — a 1200 x 900 PNG of a detailed photo can still be over 1 MB — and compressing alone does not change the dimensions, so an oversized image still wastes bandwidth and layout space.

    Which image formats does the resizer keep, and which can it output?

    You can drop in JPG, PNG, WebP, GIF, BMP, or AVIF images. The output format is your choice: keep the original format, or export as JPG, PNG, or WebP. JPG is best for photos and gives the smallest files, but it has no transparency — transparent areas are flattened onto a background colour you pick. PNG is lossless and keeps transparency, so it suits logos and screenshots, but its files are larger. WebP is the modern middle ground: smaller than JPG at similar quality and it keeps transparency. GIF input is resized as a still image — animation frames are not preserved.

    Is there a maximum image size or a limit on how many images I can resize?

    There is no account, no daily limit, and no file-count cap. The only practical limits are your own device and browser: resizing happens in memory with a canvas, so a very large image — say, above 8000 pixels on a side, or a batch of dozens of 20-megapixel photos — can slow down or run out of memory on a low-end phone. If a file fails, try fewer files at once or resize in two steps. Output dimensions are capped at 8000 pixels per side, which covers every screen and social-media size.

    Will resizing change the aspect ratio or stretch my photo?

    Only if you ask it to. With the aspect-ratio lock on — the default — the tool keeps your photo's proportions: type a new width and the height follows automatically, or pick a preset and the image is fitted inside that preset's box without stretching. Turn the lock off and the image is stretched to the exact width and height you type, which distorts faces and circles. If a preset has a different shape than your photo and the lock is on, the result keeps your photo's shape and fits inside the preset's dimensions — it is not cropped, so a landscape photo fitted to a square preset comes out as a landscape image inside a square-sized box, not a square image.

    What size should I resize an image to for Instagram, YouTube, Facebook, and X?

    The common sizes are: YouTube thumbnail 1280 x 720, Instagram square post 1080 x 1080, Instagram portrait post 1080 x 1350, Instagram story or reel cover 1080 x 1920, Facebook shared post 1200 x 630, Facebook cover 820 x 312, X post image 1600 x 900, and X header 1500 x 500. All eight are built into this tool as one-click presets, so you do not need to remember them. These are the sizes the platforms recommend; uploading much larger only wastes upload time, and uploading much smaller looks blurry once the platform displays it at full size.

    Are my images uploaded anywhere when I use this resizer?

    No. The resizer runs entirely in your browser: your image is drawn onto a canvas on your own device, resized there, and downloaded from there. No image data is sent to any server — the only requests to other sites are the site's own analytics, which count page views. You can verify this by opening your browser's Network tab while resizing, or by disconnecting from the internet after the page loads: resizing still works.