Resize an APNG by exact pixels, percentage or presets. The first frame is saved as a still PNG — the animation is not kept.
This page opens the xconvert Photo Editor on its Resize tab: type a width and height, or pick a percentage, height or platform preset, and download — the new size shows straight away, with no Apply step. It works on one decoded frame, and "Save as" has no APNG option: "Same as original" saves an edited APNG as a still PNG (the editor notes "Only the first frame is kept (animated APNG)."), and JPG, WebP, TIFF, BMP and other formats are on the list. 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.
| Group | Entries | Behaviour |
|---|---|---|
| Custom | Your own "Width" and "Height" | Pixels or percent ("Unit" px or %) |
| Percent of original | 25%, 50%, 75%, 150%, 200% | Scales both axes by the same factor |
| Long edge (fits within) | 1080, 1600, 2048, 3840 px | The longer side becomes that size; the other follows the ratio |
| By height | 240p, 360p, 480p, 720p, 1080p, 1440p, 2160p | Sets the target height; width follows the ratio |
| Facebook, Instagram, X / Twitter, LinkedIn, TikTok, YouTube, Pinterest | Platform sizes such as Instagram Portrait 1080 × 1350 or YouTube Thumbnail 1280 × 720 | Exact size, cropped to fill (centred) |
"Reset" on the Resize tab returns to the source dimensions. A platform size crops to fill from the centre; if you want to choose the framing yourself, crop to the right ratio on the Crop tab first and then set the matching size here.
What each "Save as" choice does with a frame that has a transparent background:
| Save as | Alpha channel | Encoding |
|---|---|---|
| PNG | Kept (RGBA) | Lossless |
| TIFF | Kept (RGBA) | Lossless Deflate |
| WebP | Kept | Always lossy, even at "Quality" 100 |
| AVIF | Kept | Lossy |
| GIF | 1-bit only — soft edges and shadows become hard-edged | 256-colour palette |
| BMP | Flattened onto white | Uncompressed 24-bit |
| JPG | Flattened onto white (with a note and a "Keep PNG" button) | Lossy |
TIFF is lossless too, but most viewers and web tools expect PNG; 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. Compress APNG has an Image resolution group with sizing choices like this page's Resize (a percentage, a height, a width, or both), plus an Image Compression group for a target file size. Files there are uploaded over an encrypted connection, processed on our servers, and deleted automatically afterward; 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. The editor says so when the file opens ("Animated APNG: an edit here keeps only the first frame.") Downloaded without an edit, the file is your original, animation intact; any resize saves a still PNG, because the editor cannot write APNG. 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%.
Yes — drop up to 50 APNG files at once (a mixed batch works too). The size, format and quality you set apply to every file in the batch; "Download all (.zip)" saves every resized result in one ZIP, and "Download one by one" saves them separately.
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 set the crop and switch straight to the Resize tab.
Not on this page — "Save as" takes a format, not a byte budget (the "Output" line shows an estimated size before you download). 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.