Initializing... drag & drop files here
Supports: MXF
Both of these turn a broadcast MXF clip into a looping animation that plays inline anywhere an image can appear. The difference is what survives the trip. APNG keeps full 24-bit colour and 8-bit alpha and compresses losslessly, which is the right answer for graded footage, gradients and title elements — and the wrong answer for anything long, because lossless frames add up fast. GIF quantises to 256 colours with on/off transparency and stays smaller. If your clip is a few seconds of quality-critical material, pick APNG; if it is longer or headed somewhere with a strict size budget, pick MXF to GIF.
| Property | APNG | GIF | Animated WebP |
|---|---|---|---|
| Colour depth | 24-bit truecolour | 8-bit palette, 256 colours per frame | 24-bit truecolour |
| Transparency | 8-bit alpha, smooth edges | 1-bit, hard edges only | 8-bit alpha |
| Compression | Lossless | Lossless within the palette | Lossy or lossless |
| Relative size | Largest of the three | Smaller, at the cost of colour | Usually smallest |
| Standardisation | Part of PNG Third Edition, a W3C Recommendation published 24 June 2025 | Long-established de facto standard | Google's WebP container |
| Browser support | ~96% — Chrome 59+, Firefox 3+, Safari 8+, Edge 79+, Opera 9.5+ | Universal | ~96% |
| If unsupported | Only the first frame is displayed | n/a | Falls back to a still |
| Available from MXF here | Yes, this page | Yes | Not as an animation — our MXF to WebP page extracts a still frame |
.mxf onto the page or click "Add Files". Upload a short clip — this page has no trim control, so the entire duration of whatever you upload becomes frames.| Control | Status on this page |
|---|---|
| FRAMERATE | Renders. Eleven steps, 1 to 50 FPS, opening on 10 FPS. Sets the exact per-frame delay of 1/fps second. |
| Image resolution | Renders. Percentage, keep original (default), height-only presets with a max-resolution toggle, width, height, or exact Width x Height. |
| Trim | Not available here. The whole clip is converted — cut the source first with the video cutter, which accepts MXF. |
| Quality or colour-palette controls | Not available here. APNG output is lossless truecolour; there is no quality percentage and no palette-size setting to reduce. |
| Loop count | Not exposed. The output loops indefinitely. |
That combination is why clip length matters so much on this page. With no trim, no quality slider and no palette reduction, the only two levers on file size are framerate and resolution — so a broadcast master uploaded whole will produce an APNG measured in hundreds of megabytes. Trim first, then convert.
Because everything about this output is lossless and this page gives you no quality control to trade away. Each frame is stored as full 24-bit PNG data, so file size scales with frame count times frame area: halving the framerate roughly halves the size, and halving the resolution cuts it by about three quarters. The third lever is duration, and since there is no trim here, that one has to be applied to the source before you upload.
No — there is no trim control on the MXF to APNG page, so the full duration of the uploaded file is converted. Cut the section you want first with the video cutter, which accepts MXF directly, then bring the shortened clip here. For anything more than a few seconds of animation, a video format like MXF to MP4 is a far more sensible container anyway.
It is official now. APNG was folded into PNG Third Edition, which became a W3C Recommendation on 24 June 2025, and the animation chunks — acTL for animation control, fcTL for per-frame placement and fdAT for frame data — are specified there. It is also deliberately backwards-compatible: a decoder that knows nothing about animation ignores those chunks and shows the static image instead of failing.
It shows the first frame as a still image. That is a designed-in fallback rather than a broken render, and it applies to a small slice of traffic — support sits around 96%, covering Chrome 59+, Firefox 3+, Safari 8+, Edge 79+ and Opera 9.5+. If a first-frame fallback is unacceptable for your audience, GIF is the safer target.
If it is genuinely there, yes — frames are extracted in an RGBA pixel format and APNG stores full 8-bit alpha, so a keyed graphic or rendered title keeps soft, correctly-antialiased edges rather than GIF's hard 1-bit cutout. Most MXF material is camera acquisition, though, which is fully opaque, so in the common case there is simply no transparency to preserve.
Start at the 10 FPS the dropdown opens on and move only if the result tells you to. Motion-heavy footage tends to want 15 to 25 FPS to avoid looking stuttery; talking heads, screen content and slow pans look fine at 8 to 12. Going to 50 FPS multiplies your frame count fivefold against the default for a difference most viewers will not notice in a short loop, and the file size follows the frame count almost linearly.
No. APNG is an image format with no audio track, so the sound in your MXF is discarded — as is any timecode and metadata the wrapper was carrying. If the audio matters, extract it separately with MXF to AAC or MXF to WAV, or keep picture and sound together with MXF to MP4.
MXF is a professional broadcast and acquisition wrapper — SMPTE 377M, used by Sony XDCAM decks, Panasonic P2 cameras, video servers and digital cinema — not a consumer format, so most browser-based converters only list inputs like MP4, MOV and WebM. Here the MXF is decoded directly, which saves you the usual step of re-wrapping the clip to MP4 in an editor before you can convert it at all.
The MXF uploads over an encrypted connection, is processed on our servers, and is deleted automatically a few hours after conversion. Nothing is shared or made public, and there is no sign-up or watermark. MXF masters are large files, so upload time is usually the longest part of the job — another reason to trim before uploading rather than after.