Initializing... drag & drop files here
Supports: 3GPP
Anyone converting an old .3gpp phone clip into an animated image is really choosing between two formats, and the trade is simple: APNG keeps full 24-bit color and a real 8-bit alpha channel, GIF keeps universal compatibility and usually a smaller file. Convert to APNG when color fidelity or clean transparent edges matter and the destination is a modern browser; stay on 3GPP to GIF when the loop has to embed anywhere, in anything, at the smallest size. Everything below is the detail behind that one-line answer.
| Property | APNG | GIF | Animated WebP |
|---|---|---|---|
| Standardized by | W3C, PNG Specification Third Edition (Recommendation, 24 June 2025) | CompuServe, 1987/1989 | Google, WebP container spec |
| Color per frame | 24-bit truecolor (16.7 million) | 256-color palette | 24-bit truecolor |
| Transparency | Full 8-bit alpha | 1-bit, on or off | Full 8-bit alpha |
| Frame compression | Lossless DEFLATE, inter-frame disposal | Lossless LZW on a quantized palette | Lossy or lossless |
| Typical size from video frames | Largest of the three | Middle | Smallest |
| Behaviour in a viewer that can't animate it | Shows the first frame as a normal PNG | Effectively universal | May not render at all |
| Native browser support | Chrome 59+, Firefox 3+, Safari 8+, Edge 79+, Opera 9.5+ — about 95.9% globally per caniuse | Effectively every browser ever shipped | Chrome, Edge, Firefox, Safari 16+ |
| Audio | None | None | None |
The APNG numbers are not marketing claims: the W3C's PNG Specification Third Edition became a Recommendation on 24 June 2025 and folds APNG's three chunks — acTL, fcTL, and fdAT — into the core PNG standard, with the explicit rule that a decoder which does not understand them ignores the animation and shows the static image.
.3gpp clip — a saved MMS attachment, a Nokia / Sony Ericsson / early-Samsung recording, or footage dumped off a camera card — or click "Add Files" to browse. Several clips can be queued and they all run with the same settings..png. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours. No sign-up, no watermark.This conversion deliberately exposes only Framerate and Image resolution. There is no quality slider and no colour-reduction control here, because APNG frame data is stored losslessly — the only things that move the file size are how many frames you keep and how many pixels each one holds.
| Control in Advanced Options | Choices | Effect on the APNG |
|---|---|---|
| Framerate | 1 FPS (Slideshow) up to 50 FPS (Max Speed), starting at "10 FPS (Recommended)" | Frames are stored individually, so bytes scale close to linearly with frame rate |
| Image resolution — Keep original | The default | Frames pass through at the source's own dimensions |
| Image resolution — Preset Resolutions | 4320p (8k) down to 16p | The single biggest size lever — output bytes track pixel count per frame |
| Image resolution — By Percentage | Scale every frame to a percentage of the original | Convenient when you want "half size" without knowing the source dimensions |
| Image resolution — Width / Height / Width x Height | Explicit pixels or percent, aspect ratio kept for Width or Height alone | Use when a destination has a hard pixel budget |
| Use as max resolution | A toggle alongside the preset | Treats the preset as a ceiling, so a smaller source is never upscaled |
Duration is the fifth lever and the most effective one: an APNG has no inter-frame prediction across the whole timeline the way H.264 does, so five seconds of source costs roughly five times what one second costs. Trim before converting whenever you can.
Yes — APNG carries a full 8-bit alpha channel, so semi-transparent pixels, anti-aliased outlines, soft shadows, and glows all survive, whereas GIF's 1-bit transparency makes every pixel either fully opaque or fully invisible and leaves the jagged halo you see around GIF stickers. The caveat specific to this conversion: a .3gpp camera clip has no alpha channel to begin with, so nothing is being rescued. APNG's alpha matters here only if you plan to mask or composite the loop afterwards; the immediate win over GIF is the jump from 256 colours to 16.7 million.
No. APNG cannot add detail that was never captured. 3GPP video from roughly 2002 to 2010 was commonly encoded at 176×144 (QCIF) or 320×240 (QVGA) using H.263 or MPEG-4 Part 2 at low bitrates so MMS messages stayed inside carrier limits, and that blocking is baked into the source samples. Keep Image resolution on "Keep original" or choose a small preset so you are not magnifying artifacts — enlarging blurry pixels only makes them bigger blurry pixels. What APNG does avoid is layering GIF's colour banding on top of the compression damage already present.
Because APNG stores every frame as lossless PNG data at full 24-bit colour, while GIF quantizes each frame to at most 256 colours first. Photographic video frames are noisy, and noise is the worst possible input for PNG's lossless filtering and DEFLATE stage, so the honest expectation for a video-sourced animation is that the APNG lands larger than the GIF. To pull it down, cut the duration before uploading, drop the Framerate, and lower the Image resolution — those three are the levers this page gives you, and duration is the strongest of them. If the file still has to be smaller than APNG can go, the clip wants to be a GIF or an MP4 instead, accepting a 256-colour palette or a lossy codec in exchange.
In browsers, effectively yes: caniuse puts native APNG rendering at about 95.9% globally, with Chrome 59+, Firefox 3+, Safari 8+, Edge 79+, and Opera 9.5+ all animating it. Outside browsers it is less certain — some chat platforms and email clients treat an APNG as an ordinary still image even though the underlying browser engine could animate it. The failure mode is gentle rather than broken: the PNG Third Edition specification requires a decoder that does not recognise the APNG chunks to display the static image, so the worst case is your first frame showing as a normal PNG.
No. APNG is an image format with no audio track whatsoever, so the 3GPP soundtrack — usually AMR-NB speech at 8 kHz, or AAC-LC on later handsets — is discarded during conversion. If the audio is the part you actually need, extract it separately with 3GPP to MP3. If you need picture and sound together in one shareable file, 3GPP to MP4 is the right target and will also be dramatically smaller than any animated-image format.
An animated PNG is a PNG file — the animation lives in ancillary chunks inside an otherwise ordinary PNG stream — so .png is the correct and most compatible extension, and the PNG Third Edition specification registers image/apng as the media type alongside image/png. Some tools also use a .apng extension, and renaming the file will not break it, but .png is what browsers, image editors, and upload forms expect. Nothing about the file changes either way.
.3gpp the same thing as .3gp?Yes. Both are filename spellings for the 3GPP file format defined in 3GPP TS 26.244, a container built on MPEG-4 Part 12 (the ISO base media file format) for GSM-based handsets — identical structure, identical codec set, identical content. This page accepts .3gpp; if your file carries the shorter extension use 3GP to APNG and follow the same steps. The related .3g2 extension is genuinely different — it is 3GPP2, the CDMA2000 variant, with a partly different codec list.
Files are uploaded over an encrypted connection, converted on our servers, and deleted automatically after a few hours; there is no sign-up, no watermark, and clips are never shared or made public. On size: because APNG writes whole frames rather than motion-compensated differences, the output scales with frames × pixels — doubling the Framerate or the frame area roughly doubles the file, which is why a heavily compressed few-hundred-kilobyte .3gpp can expand into a multi-megabyte APNG. Trim the clip first, then adjust Framerate and Image resolution, and check the result before uploading it anywhere with a size cap.