Badilisha AV1 kwa WebM

Yes — every audio track in the AV1 (director commentary, alternate languages, descriptive audio) is preserved in the WebM when the target container supports multi-stream audio. MKV and MOV handle unlimited audio tracks; MP4 supports many but some hardware players only see track 1; WebM is capped at one Opus / Vorbis track. Mtandao wa intaneti ni picha ya Matoska ambayo Google ilichapisha mwaka 2010 hasa ili kuipa video ya HTML5 kontena ya kifalme isiyo na risasi.

Soft subtitles (selectable tracks) survive when WebM can carry them: MKV holds SRT, ASS, SSA, PGS, VobSub natively; MP4 only holds mov_text (a stripped-down format). Converting an MKV with ASS styled subs to MP4 will typically downgrade them to mov_text or burn them in. Hardsubs (burned into the video) carry over regardless.

Chapter metadata transfers between AV1 and WebM whenever both containers support a chapter atom (MKV, MP4, MOV). WebM stores chapters in a Matroska-compatible block, so MKV <-> WebM chapters round-trip cleanly. AVI has no chapter spec at all, so an AVI source arrives with no chapters to carry across and an AVI target cannot store the ones it was handed; add markers manually afterwards if you need them.

MKV is the only mainstream container that stores arbitrary attached files (TTF fonts for ASS subs, JPG cover art, fan-translated PDF inserts). Going from AV1 to WebM drops these attachments when WebM is not MKV — the elementary streams convert, but the attached payload stays in the source. Keep AV1 as a backup if you depend on attached fonts.

The default codec is chosen to match the WebM container conservatively: MKV defaults to H.265 (HEVC) for better compression; MP4 defaults to H.264 for the widest device support; WebM defaults to VP9; AVI uses MPEG-4 ASP (DivX/Xvid lineage). Override via the advanced codec dropdown — AV1 is available for MKV / WebM where you want maximum compression and can wait through the encode. Mtandao wa intaneti unacheza kwa asili katika kila kifaa cha kisasa cha kunasa habari bila kutumia plagi, bila ada ya leseni na bila haki ya kupata haki ya kisheria, jambo ambalo linaifanya kuwa kama nafasi ya video inayopigwa na mtandao. Mtandao wa WebM ni duni mahali popote nje ya wahariri wa video wa BAKE, simu za mkononi BAKE na televisheni za hali ya juu zinaipuuza sana.

HDR static metadata (HDR10 mastering display values, max content light level) carries through to WebM when both containers and the chosen codec support it (HEVC, AV1 in MKV / MP4). Dolby Vision is more fragile — DV profile 5 / 7 / 8.1 in AV1 commonly survives only into MKV with HEVC; converting to a WebM container that does not carry the DV layer flattens to HDR10.

MKV and WebM record real per-frame timestamps and handle VFR natively, so AV1 VFR survives into a WebM of those formats with no resampling. MP4 nominally stores timestamps too but some players assume CFR; the converter exposes a "force CFR" toggle that resamples VFR AV1 to 24 / 30 / 60 fps WebM for problematic targets.

Same-codec remux produces a near-identical size (container overhead differs by 0.1-2%). A codec change can swing the size by 50% or more: H.264 to H.265 typically halves the file at the same visual quality; H.264 to AV1 halves it again on a slow preset. Going from a high-bitrate AV1 (Blu-ray rip) to a low-bitrate WebM (web upload) is the most common reason for a dramatic drop.

Yes up to 8K (7680x4320) on Premium. Free tier handles 4K (3840x2160) up to the 1 GB file cap. Pure remuxes (same-codec passthrough) of large AV1 into WebM are limited by disk I/O, not CPU — a 30 GB AV1 typically remuxes to WebM in under a minute regardless of resolution. Re-encodes scale with pixel count.

Yes — uploaded AV1 files are processed in isolated workers and deleted within minutes of completion. We never view, store, retain, or share the content. See /privacy/ for the data retention window. The conversion pipeline runs on hardware we control end-to-end; no third-party APIs receive your file. AV1 husambaza takriban asilimia 30 ya kitambaa cha kufinya kuliko H.264 kwa kiwango kilekile na hailipizi ada ya leseni, ndiyo sababu YouTube na Netflix hukisukuma.

Not in the same job — keep conversion focused on container / codec. Use /trim/ to clip the AV1 first, then queue the AV1 -> WebM step. For joining several clips into one WebM, the /merge/ tool stitches them on a per-codec basis (it remuxes when the inputs share a codec, re-encodes otherwise) and emits a single WebM file at the end.