Resize PNG images by pixels, percentage, or preset dimensions. Preserves transparency. Free, no quality loss.
PNG is a lossless raster format defined by W3C, with full 8-bit alpha transparency. Re-encoding a resized PNG does not introduce JPEG-style compression artifacts, so the only quality change comes from the resampling step itself. That makes PNG the right format to resize when you need a smaller pixel grid but cannot tolerate compression noise around hard edges (UI assets, screenshots, logos, line art). Common reasons to resize:
| Use case | Width x Height | Notes |
|---|---|---|
| Browser favicon (legacy ICO bundle) | 16, 32, 48 | Pack into a single.ico via PNG to ICO |
| Apple Touch Icon | 180 x 180 | iOS rounds corners automatically — keep logo padded |
| Android home-screen icon | 192 x 192 | Also ship 512 x 512 for the maskable icon |
| Open Graph / Facebook share | 1200 x 630 | Meta's recommended, 1.91:1 aspect ratio |
| Twitter/X large summary card | 1200 x 675 | 16:9 aspect ratio |
| LinkedIn share image | 1200 x 627 | Effectively the same slot as OG |
| Instagram square post | 1080 x 1080 | 1:1 |
| YouTube thumbnail | 1280 x 720 | 16:9, must be under 2 MB |
| Full-HD wallpaper / hero | 1920 x 1080 | Downscale 4K captures here |
| 4K asset | 3840 x 2160 | Source size for hero crops |
| If you want to... | Use | Why |
|---|---|---|
| Change the pixel grid (1920x1080 → 800x450) | Resize PNG (this page) | Scales every pixel; preserves the whole image |
| Cut off the edges to change framing | Crop PNG | Removes pixels rather than rescaling them |
| Shrink the byte size at the same dimensions | Compress PNG | Re-encodes with stronger zlib + optional palette quantization |
| Keep dimensions, drop to a smaller format | PNG to WebP or PNG to JPG | WebP lossless averages ~26% smaller than PNG (Google) |
| Resize a different image type | JPG resize or the universal image resizer | Same controls, different source format |
PNG itself is lossless, so re-encoding adds no artifacts — but resampling does. Downscaling produces clean results because the algorithm averages neighboring pixels into one output pixel. Upscaling has to invent pixels that were never captured, so even a good interpolator (bicubic, Lanczos) softens edges. For photographic content, start with the largest source you have and scale down once.
Yes. PNG supports 8-bit alpha (256 levels of partial transparency), and the resize step keeps the alpha channel intact. Anti-aliased edges on logos, drop shadows, and feathered cutouts come through correctly. If you export to JPG instead, transparency is flattened against an opaque background — pick WebP if you need transparency in a smaller file.
Toggle the aspect-ratio lock and enter either the width or the height — the other dimension fills in automatically using the source ratio. To deliberately stretch (rare, usually a mistake on photos), unlock the ratio and enter both dimensions manually.
Modern sites ship at least three PNGs: 32x32 for desktop browser tabs, 180x180 for the Apple Touch Icon, and 192x192 plus 512x512 for Android and PWA manifests. A 16x16 PNG is still useful for legacy IE/older Edge support. After resizing, bundle the small sizes into a single.ico with PNG to ICO.
Meta's documentation recommends 1200 x 630 pixels at a 1.91:1 ratio, with an 8 MB file-size ceiling. The same dimensions work for LinkedIn (technically 1200x627). Twitter/X's "summary large image" card wants 1200 x 675 (16:9). PNG is accepted, but if file weight matters consider exporting to JPG since OG images rarely need transparency.
Resizing only changes the pixel grid. Pixel count drives most of the file size, but PNG also stores a full alpha channel and uses lossless DEFLATE compression — for photos, the resulting file can still be heavy. If the file is too big after resize, run it through Compress PNG (palette quantization can cut size 5-10x) or convert to PNG to WebP.
Not on this page — the editor holds one image at a time; resize it, save, then + Start New for the next file. For a real batch — the same width, height, or percentage applied to a whole set of files in one session — use Compress PNG, which runs server-side and includes a resize step alongside compression. If the source files have different aspect ratios and you keep the lock on there, each file scales to fit within the entered bounds — they won't be stretched to a single shape.
You can, but expect softness. Standard interpolation (bicubic, Lanczos) fills new pixels by averaging existing ones, so detail that wasn't in the source can't reappear. For logos and line art the result is usually acceptable; for photos, a dedicated AI upscaler will do better than any classical resizer.
Processing happens locally in your browser. There's no public link, no account requirement, and no third-party sharing.