Formats Fetchora can actually handle.
Container names are not promises. A platform may expose one rendition, a manifest, or nothing at all. These tables describe what the resolver and local toolkit can recognize or produce.
Video containers
FormatPathNotes
MP4Native / extractorH.264 + AAC is broadly compatible; extractor may return other codecs.
WebMNative / extractorCommon VP8/VP9 + Opus. Supported by modern browsers, not every editor.
MOVNativeDelivered as-is; browser conversion may require re-encoding.
MKVExtractor / muxUsed for local muxing when sources are not MP4-compatible.
HLS (m3u8)Detect / manifestNot treated as a finished video. Renditions require an extractor or player.
DASH (mpd)Detect / manifestSegmented streams with separate tracks are not silently converted to files.
Audio, images, and animation
FormatPathNotes
MP3 / M4AExtractor / localAudio-only when returned; local extraction uses LAME or AAC.
WAV / OGG / OpusExtractor / localCodec support is checked per job; failures are surfaced.
JPEG / PNG / WebP / AVIFNativeServed as attachments. SVG is deliberately not accepted.
GIFNativePreserved as animation; not silently converted to a static image.
HLS / DASH manifestsDetect onlyCan be saved as manifests, but that is not a playable complete file.
Browser conversion outputs
The local toolkit can produce MP4 (H.264/AAC), WebM (VP9/Opus), MP3, M4A, WAV, OGG, and muxed MKV/MP4 when the selected streams are compatible. These operations are constrained by the pinned FFmpeg.wasm build and available device memory. A conversion that cannot complete returns a real error, not a truncated file.
Quality information
Resolution, codec, frame rate, bitrate, duration, and size are displayed only when returned by the source, extraction engine, or the local FFmpeg report. Unknown values are omitted. Fetchora does not estimate a resolution from a filename.