Convert to animated GIF and APNG

GIF and APNG are both raster containers that can hold animation, but they make opposite compromises. GIF is the universal one: it opens in practically every browser, chat app, and image viewer made in the last few decades. It pays for that reach with a 256-color palette and 1-bit transparency, which means a pixel is either fully opaque or fully see-through with nothing in between. Photographs and smooth gradients band into visible steps, and soft edges turn jagged because there is no partial transparency to feather them.

APNG keeps the full color range and a full alpha channel, so gradients stay smooth and anti-aliased edges stay soft. It typically produces a cleaner and often smaller result than an equivalent GIF. The trade is support: APNG is the newer of the two and is not understood by every tool that opens a GIF without complaint, so it rewards a destination you know can display it.

Neither format is one you reach for by habit. Each earns its place on a particular job, and the choice comes down to how much color and edge quality the content needs versus how widely the file has to open.

Before you commit to either output, open convert.novusstreamsolutions.com/conversions and confirm that your pair — your specific source format into GIF, or into APNG — is an active route. The image matrix runs to hundreds of pairs, and this directory is the always-current authority on which ones are live. A format appearing in the output list does not guarantee that every source reaches it, so the directory is where you check rather than guess.

Treat what any given route actually produces as something to verify, not assume. GIF and APNG are listed as animation-capable outputs, but let the directory, not this guide, be the source of truth for what a specific conversion will do with your file. If the pair you want is not listed at /conversions, it is not active, and renaming a file will not change that. Confirming the route up front saves you from queueing a job the current release cannot deliver.

Open convert.novusstreamsolutions.com/convert and add the image, either by dragging it in or using the file chooser. The active image inputs are HEIC, HEIF, AVIF, JPG, PNG, WebP, SVG, BMP, and TIFF/TIF. Every file is identified by its signature rather than its filename, so a mislabeled image is caught here instead of producing a broken result later.

The outputs offered on a row are exactly the active routes for that signature. In practice this means GIF or APNG appears as an option only when the route is genuinely live for that source — the same truth the /conversions directory publishes, expressed inside the interface. If the animation output you expected does not appear on the row, the route is not active for that input.

HEIC and HEIF sources are common starting points and decode through a lazy-loaded local WebAssembly worker, so those photos are never uploaded. Whatever the source, the file stays on your device while the app determines which outputs it can validly produce.

Let the destination decide. If the file has to open anywhere — embedded in an old page, opened by an unknown viewer, or dropped into a channel that only understands GIF — then GIF is the safe target despite the color and transparency cost. If it is going somewhere you control and full color or smooth alpha matters, APNG is the cleaner and usually smaller result. The decision is reach versus fidelity, and the content tells you which one is scarce.

Transparency behaves differently between the two, so settle it on purpose. Both formats store transparency, unlike JPG or BMP, which flatten a transparent source onto a white background rather than dropping the channel. But transparency in a GIF is 1-bit: a pixel is either fully opaque or fully clear, so anti-aliased edges that were smooth in the source harden into a jagged fringe. APNG carries the full alpha channel through intact, so soft and feathered edges survive. When the source has delicate edges against transparency, APNG preserves them and GIF will not.

Run the conversion and let the row finish. Everything happens in browser memory, and the download button appears only after the output matches its expected signature, container, or decodability. A file can therefore fail after processing, which is the validation gate doing its job — it is safer to withhold a result than to offer a download that merely has the right extension.

A validated GIF or APNG that reaches your downloads folder is structurally a real file in that container, but structural validity is not the same as visual judgment. Open it at full size and check the things these formats stress: color banding in a GIF, edge quality where transparency meets the subject, and, if the route produced motion, that it plays as expected. Results live behind temporary object URLs, so removing the job or closing the page revokes them — save what you need before you close the tab.

Keep the practical constraints in view. Image routes accept sources up to 100 MB and 80 megapixels, and daily download allowances are tracked by input format on your local calendar day. A PNG or JPG source falls under the 25-per-day bucket for other active formats, a HEIC or HEIF source under 15, and an AVIF source under 20. The remaining count sits beside the download control, so the app is free to use but not unlimited.

Know what the adjacent surfaces do and do not cover. The compression surface at /compress is a deliberately separate tool that re-encodes JPG, PNG, and WebP with an adjustable quality control and reports the measured size before download — it does not shrink GIF or APNG, so do not expect it to. For anything about which pairs exist, return to /conversions, which remains the authority on every active route rather than a promise that a given animation conversion is available.