Remux or full transcode?
If the streams are already compatible with the target container, the stream-copy and media packaging hub rewraps them without quality loss. Stay here only when codec compatibility forces re-encoding.
Elysia Tools
Navigation
Workflow Playbook
Convert footage between MP4, AVI, FLV, MKV, MOV, and WebM containers, keep CRF and bitrate decisions under control during the re-encode, and batch a whole library under one recorded configuration.
Hubs
A container conversion rewrites the video stream. Remuxing only moves existing streams into a new wrapper, which is faster and lossless, and it belongs in the stream-copy and media packaging hub. You are in the right place when the destination cannot accept the codec at all, for example an editor that refuses HEVC inside AVI, a web pipeline that wants VP9 in WebM, or an archive standard written around Matroska. Accept that a real transcode is happening, and treat its quality settings as first-class decisions.
Old projects arrive as AVI, rescued recordings as FLV, downloads as MKV, and camera output as MOV. Converting each into MP4 first gives the pipeline one common baseline that every downstream tool accepts. Work from the highest-quality source available, because every re-encode spends quality that later steps cannot recover.
The target container is a requirement, not a preference. MOV keeps Apple editing suites happy, MKV preserves many audio and subtitle tracks for archival masters, WebM delivers VP9 to web players, and AVI or FLV serve legacy chains that refuse anything newer. When nothing forces a special container, stay with MP4. Note the requirement next to the output so the choice survives the project.
Re-encoding with defaults hides the decisions that matter. A CRF step fixes quality per frame and lets size float, while a bitrate target fixes size and lets quality float. Pick the mode that matches your constraint, test one clip with dark scenes and fast motion, and write down the passing settings. Then bring oversized results back inside budget with compression or destination-aware optimization rather than re-rolling the conversion blind.
Converting a series file by file invites drift, because each episode ends up encoded under slightly different settings. Set the target format and quality configuration once, run the library through the batch converter, and enforce a shared size ceiling with batch compression. Verify the first output in the real destination player before letting the full batch run, and keep the recorded settings with the delivered files so the run can be reproduced.
Workflow playbook
Normalize AVI relics, rescued FLV recordings, MKV downloads, and camera MOV footage into widely playable MP4 so the rest of the pipeline works from one common base.
Produce the exact container the destination demands, whether MOV for editing suites, MKV for archival masters, WebM for VP9 web delivery, or AVI and FLV for legacy chains.
Pick the CRF step or the bitrate mode consciously, because these two knobs decide whether the converted file keeps fine grain and motion detail or quietly degrades every scene.
Bring oversized conversions back inside a storage or streaming budget with compression and destination-aware optimization while checking dark and fast-motion scenes for artifacts.
If the streams are already compatible with the target container, the stream-copy and media packaging hub rewraps them without quality loss. Stay here only when codec compatibility forces re-encoding.
MP4 for universal playback, MOV for Apple editing suites, MKV for archival multi-track masters, WebM for web-native VP9 delivery, AVI or FLV only for legacy chains that still demand them.
Choose a CRF value when quality per frame matters most, a bitrate target when a bandwidth or storage ceiling is fixed, and an optimization profile when the delivery channel itself defines the settings.
Convert or compress entire folders with a single recorded format and quality setting, so episodic content ships consistent instead of file-by-file improvised.