DivX MKV

Fetola Ea Hau DivX ho MKV lifaele ka mokhoa o bonolo

Khetha lifaele tsa hau

kapa tobetsa le ho tobetsa ho kenya faele mona

Free plan: 2 Liphetoho/hora · Ha ho letho →

Fetolela lifaele tse fihlang ho 1 GB mahala, basebelisi ba Pro ba ka fetolela lifaele tse fihlang ho 100 GB; Ingolise hona joale

Ho kenya

0%

Mokhoa oa ho fetolela DivX ho MKV

Mohato oa 1: Kenya ea hau DivX difaele o sebedisa konopo e ka hodimo kapa ka ho hula le ho dihela.

Mohato oa 2: Tobetsa konopo ea 'Convert' ho qala phetoho.

Mohato oa 3: Khoasolla sesebelisoa sa hau se fetotsoeng MKV lifaele


DivX ho MKV Lipotso Tse Botsoang Khafetsa Mabapi le Phetoho

How do I convert DivX to MKV without re-encoding the video stream?
+
When the DivX and MKV containers can both carry the same codec (H.264, H.265, VP9, AV1), the converter falls back to a remux: the elementary streams are copied byte-for-byte into the MKV container and only the wrapper changes. A remux of a 1 GB DivX into MKV typically finishes in 5-15 seconds with zero quality loss.
Yes — every audio track in the DivX (director commentary, alternate languages, descriptive audio) is preserved in the MKV 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.
Soft subtitles (selectable tracks) survive when MKV 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 DivX and MKV 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, so converting AVI to MKV produces an unchaptered file unless you add markers manually.
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 DivX to MKV drops these attachments when MKV is not MKV — the elementary streams convert, but the attached payload stays in the source. Keep DivX as a backup if you depend on attached fonts.
The default codec is chosen to match the MKV 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.
HDR static metadata (HDR10 mastering display values, max content light level) carries through to MKV 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 DivX commonly survives only into MKV with HEVC; converting to a MKV container that does not carry the DV layer flattens to HDR10.
MKV and WebM record real per-frame timestamps and handle VFR natively, so DivX VFR survives into a MKV 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 DivX to 24 / 30 / 60 fps MKV 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 DivX (Blu-ray rip) to a low-bitrate MKV (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 DivX into MKV are limited by disk I/O, not CPU — a 30 GB DivX typically remuxes to MKV in under a minute regardless of resolution. Re-encodes scale with pixel count.
Yes — uploaded DivX 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.
Not in the same job — keep conversion focused on container / codec. Use /trim/ to clip the DivX first, then queue the DivX -> MKV step. For joining several clips into one MKV, 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 MKV file at the end.

DivX

DivX ke theknoloji ea compression ea video e lumellang khatello ea video ea boleng bo holimo ka boholo ba lifaele tse nyane. Hangata e sebelisoa bakeng sa kabo ea video ea inthaneteng.

MKV

MKV (Matroska) e ka boloka divideo tse sa feleng, modumo le dipina tse nang le di-subtitle faeleng e le nngwe, e loketseng difilimi.


Lekanya sesebelisoa sena

5.0/5 - 2 likhetho
Kapa lahlela lifaele tsa hau mona