Upload an APNG and resize it by percentage, preset resolution, or custom width and height, then download the resized APNG.
This page opens the xconvert Photo Editor on its Resize tab: type a width and height, or pick a percentage or screen-height preset, hit Apply, and save. It works on one decoded frame, and the Save dropdown offers JPG, PNG, WebP, TIFF and BMP — APNG is not among them. So an animated .apng scales down to a resized still image here, while a static .apng (which is what a single-image APNG conversion actually produces — a plain PNG with no animation chunks) resizes exactly as you would expect and can round-trip losslessly through PNG.
If the file is genuinely animated and every frame needs to shrink, skip to the section on Compress APNG below — that route does resize an animated APNG with the loop intact, and it is the one worth bookmarking.
.apng or .png. The open dialog is not extension-filtered, so .apng files appear normally. Only the first file you pick is loaded, even if you multi-select.| Group | Entries | Behaviour |
|---|---|---|
| (top of list) | Original | Returns to the source dimensions |
| Percentages | 25%, 50%, 75%, 100%, 150%, 200% | Scales both axes by the same factor |
| Screen Size (Height) | 170p, 200p, 315p, 320p, 396p, 400p, 500p, 566p, 627p, 628p, 851p, 900p, 1080p, 1200p, 1350p, 1500p, 1584p, 1600p, 1920p | Sets the target height; width follows the locked ratio |
The Screen Size numbers are not arbitrary — they are pulled from the platform image specs the Crop tab also offers, so both axes of a given spec show up in the list (315p is a Facebook cover's height and 851p its width; 396p is a LinkedIn banner's height and 1584p its width; 1920p is a full-height story). If you are producing a specific social asset, crop to the right ratio first and then set the matching height here.
Measured by pushing a 200x120 RGBA test frame with a transparent background through this page's own encoders:
| Save as | Alpha channel | Encoding | Bytes for the test frame |
|---|---|---|---|
| PNG | Preserved (RGBA, colour type 6) | Lossless DEFLATE | 2,252 |
| TIFF | Preserved (RGBA) | Uncompressed | 96,258 |
| BMP | Written to a 32-bit bitfield header; not every viewer honours BMP alpha | Uncompressed | 96,122 |
| WebP | Discarded — a bare lossy VP8 bitstream with no ALPH chunk |
Lossy | 2,320 |
| JPG | Discarded — transparent areas save as solid black | Lossy | 6,574 |
Note how far apart the lossless options sit: identical pixels are 2,252 bytes as PNG and 96,258 bytes as TIFF, because the TIFF this page writes applies no compression at all. Unless something downstream specifically demands TIFF, PNG is the lossless choice.
Compress APNG is the route that keeps the loop. It runs server-side and treats an animated source properly: every frame is re-extracted across the real duration, rescaled, and reassembled into a new APNG with apngasm, then squeezed with apngopt. The Image resolution group there gives you the same shapes you have on this page — Resolution Percentage, Keep original, a preset height list, Width alone, Height alone, or an explicit Width x Height — plus an Image Compression group for a target file size. Processing happens locally in your browser; no sign-up, no watermark.
Because APNG stores full-colour frames losslessly, dimensions are the biggest lever you have on its size: halving both width and height removes about 75% of the pixels in every frame at once, so it compounds across the whole animation. If that is still not enough, APNG to GIF trades colour depth for size, and APNG to MP4 trades the alpha channel for real temporal compression.
No. We verified this with a purpose-built 3-frame APNG (200x120, one distinctly placed coloured circle per frame): once the image was drawn into the editor's canvas and saved back out as PNG, only frame 1's circle was present, and the saved file's chunk list was just IHDR, IDAT, IEND — no acTL, which is the chunk that makes a PNG animated. Compress APNG is the resize route that keeps the loop.
For UI spinners, emotes and icon-scale artwork, 64x64 to 128x128 is usually the floor before antialiased detail starts collapsing. Because pixel count scales with the square of the dimensions, dropping 512x512 to 128x128 removes about 94% of the pixels — a much bigger saving than any quality setting will get you on a lossless format.
No. Upscaling interpolates between pixels that already exist; it cannot invent the ones that were never captured. Whole-number multipliers (200%, 300%) hold up better than odd ratios because each source pixel maps onto a clean block of output pixels instead of being blended across a fractional boundary. If the artwork is a flat-colour icon, redrawing it at the target size from a vector source will always beat upscaling.
Downscaling resamples: several source pixels are averaged into one output pixel, which is exactly what makes the file smaller and is unavoidable at any scale factor other than 100%. The PNG container itself adds no loss on top of that. If the source is line art or pixel art, resizing to an exact integer fraction (50%, 25%) keeps edges crisper than an arbitrary value like 63%.
Not on this page — the editor holds a single image and hands the result straight back to you. Compress APNG is the batch-capable route: add several files in one session and the Image resolution setting applies to all of them.
Crop first, then resize. Cropping discards pixels at full source resolution, so the resize afterwards only has to resample the region you are keeping. Doing it the other way spends detail on pixels you are about to throw away. Both tabs act on the same working image, so you can Apply the crop and switch straight to the Resize tab.
Not on this page — the Save menu takes a format, not a byte budget. Compress APNG has an Image Compression group with "Target file size (%)" and "Specific file size" inputs, which is the right tool when a platform enforces a hard KB cap.
APNG plays natively in Chrome 59+, Edge 79+, Firefox 3+, Safari 8+ (desktop and iOS), Opera 46+ and Samsung Internet 7.2+ — around 96% of global browsers per caniuse. Viewers without support, such as Internet Explorer or Opera Mini, fall back to rendering the first frame as a static PNG rather than failing.
It is a ratified part of the PNG standard now. The W3C published PNG Third Edition as a Recommendation on 24 June 2025; that document defines the acTL, fcTL and fdAT animation chunks in the spec proper and registers image/apng as an Internet Media Type alongside image/png. Practically, that means APNG's 24-bit colour and 8-bit alpha are the standards-backed alternative to GIF's 256-colour palette.