FLV VOB

Convert Your FLV to VOB documents conveniently

Check your files

or drag and drop your files here

Free plan: 1 Conversions/hour · Go Unlimited →

Convert files free, Pro users can convert much larger files; Sign up now

Uploading

0%

How to convert FLV to VOB

Step 1: Provide your FLV files using the button above or by toss and let go.

Step 2: Click the 'Convert' button to start the conversion.

Step 3: Fetch your converted VOB files.


FLV to VOB Conversion FAQ

How do I convert FLV to VOB without re-encoding the video stream?
+
When the FLV and VOB 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 VOB container and only the wrapper changes. A remux of a 1 GB FLV into VOB typically finishes in 5-15 seconds with zero quality loss. FLV typically holds Sorenson Spark or H.264 video with MP3 or AAC audio, wrapped in a stream format designed for RTMP delivery. A VOB holds MPEG-2 video, AC-3 or PCM audio, and DVD subpicture subtitle streams, split into 1 GB segments by the DVD spec.
Yes. FLV has no usable soft-subtitle track, so subtitles for FLV content had to be burned into the picture or shipped as a separate sidecar file. VOB carries subtitles as their own selectable stream, so after conversion you can attach an SRT track the viewer can switch on, switch off or restyle.
Yes, and it is a real upgrade over FLV. VOB treats every audio stream as a first-class track, so an original-language mix, a dub and a director commentary can live in one file with the player switching between them on demand. VOB preserves the whole DVD payload — multiple angles, multiple audio languages and subtitle tracks all survive inside it.
It does. VOB stores chapters as container metadata, so a long recording can be navigated by section instead of by scrubbing a progress bar. FLV has nowhere to put that information, so if the source shipped with a chapter list it was in a sidecar file — hand that to the converter and it gets written into the VOB.
Only if a specific piece of equipment demands the target. Both formats come from the same pre-H.264 era, so neither conversion buys efficiency, quality or future-proofing — it buys compatibility with one particular device. If the goal is to keep the footage usable long-term, convert to a current container instead of sideways. No current browser, phone or TV can play FLV — anything still in this container has to be moved out of it to remain watchable. VOB is split across files, may be CSS-encrypted, and carries navigation packets that confuse general-purpose players.
Yes — every audio track in the FLV (director commentary, alternate languages, descriptive audio) is preserved in the VOB 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. VOB is the Video Object container found in the VIDEO_TS folder of every DVD — an MPEG-2 program stream with DVD-specific navigation data added.
Soft subtitles (selectable tracks) survive when VOB 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 FLV and VOB 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 FLV to VOB drops these attachments when VOB is not MKV — the elementary streams convert, but the attached payload stays in the source. Keep FLV as a backup if you depend on attached fonts.
The default codec is chosen to match the VOB 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 VOB 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 FLV commonly survives only into MKV with HEVC; converting to a VOB container that does not carry the DV layer flattens to HDR10.
MKV and WebM record real per-frame timestamps and handle VFR natively, so FLV VFR survives into a VOB 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 FLV to 24 / 30 / 60 fps VOB for problematic targets.

FLV

FLV was the container behind Flash video on the web, now obsolete but still common in older downloads and archives.

VOB

VOB is the container on a video DVD, holding MPEG-2 video, audio, and subtitles, and it may be encrypted.


Rate this toolkit

5.0/5 - 0 votes
Or let go your files here
Made by @nadermx