Convert video formats locally without uploads

Enhance, then deliver — in one app

To convert video formats without uploading, use a local converter: pick a container and codec (MP4 with H.264 for broad playback, H.265 or AV1 for smaller files), set resolution and quality, and batch the clips on your own machine. Convert the finished master once, after enhancement, so you do not re-encode twice. Video Converter sits beside the enhancer.

Practical codec picks

• H.264/MP4 — widest player compatibility
• H.265/MP4 or MOV — smaller files for 4K delivery
• ProRes-style mezzanine only when your editor demands it (tooling varies)

Batch without babysitting

Folder batch applies the same recipe overnight. Pair with free 1s/3s/5s enhancement previews so you do not convert a look you already rejected.

Encode the look you already kept

You already spent the enhancement pass deciding which look to keep. The 1 second, 3 second, and 5 second previews are that decision, and they run on your machine. What comes next is delivery: one encode of the master you accepted, into the codec and container the other end can play. Video Converter is in the same app as the enhancer, so that encode does not start with another upload and another queue. A separate cloud converter would compress the file again after you already accepted one generation of compression. Sign-in and a paid plan are needed to export, convert, repair a file, or download a file from a link. Opening the preview does not.

Choose the codec from the destination, then the container that carries it. H.264 in an MP4 is the handoff when you do not control the player: a phone, an older television, a review link sent to someone whose software you have not seen. H.265 in MP4 or MOV is the smaller file when the destination already plays HEVC, which is the usual ask for a 4K archive or a client who requested HEVC by name. AV1 is the royalty-free encode for current browsers and devices that list it. Pick it when that target is the one you are delivering to, not because the name sits later in a menu. MKV carries the same video encodes when the file is for archive or desktop playback and you do not need the widest phone compatibility. These are routes to a player. They are not a ranking of picture quality, and the converter does not invent detail the enhancement pass left out of the master.

• A mixed or unknown audience: H.264 inside MP4.
• A 4K file you will store or send where HEVC already plays: H.265 inside MP4 or MOV.
• A current web or app target that already accepts AV1: AV1 inside MP4 or MKV.
• A timeline that still has to move between editors: keep the enhanced master, and convert a separate copy for each destination.

A ProRes-style mezzanine is a different request. Use an intermediate only when the editor receiving the file asks for one their timeline can scrub. Day-to-day outputs here are H.264, H.265, and AV1, in MP4, MKV, or MOV. If a room's house format is an intermediate this converter does not write, make that file in the editor from the local master. Do not send the enhanced master through a cloud converter merely to change the wrapper. That is another generation, and another copy of the footage leaving the machine. Tooling differs by edit bay. The stable part is the order: preview the look, keep it, then encode once for the player that will open the file.

Folder batch applies one recipe to every file whose look you already accepted: the same container, the same codec, the same resolution. That is how a delivery can run without you watching each encode. It is a poor place to discover that the look was wrong, so pair the queue with the free enhancement preview and send only the clips you kept. Audio conversion, image conversion, and GIF output live in the same Video Converter when the delivery is not a video master. They stay local, and they are not a reason to upload the picture. DVD is a separate module. It scans an ISO or a VIDEO_TS folder, you pick a title, and it writes a video file. That rip has no 1 second, 3 second, or 5 second effect preview. Do not treat it as the codec step that follows enhancement.

Resolution follows the same destination logic as the codec. Do not use the converter to enlarge a master the enhancer already finished, and do not shrink a 4K master unless the player or the platform asked for that smaller frame. The enhancement preview is where you decided the picture was worth keeping, at the size you watched. The converter wraps that picture for a player: container, codec, and a smaller frame only when the destination demands one. Batch keeps those choices identical across the folder, so one file does not leave as H.264 while its neighbor leaves as H.265. Name the recipe after the destination, a review link, a 4K archive, or a current web target, not after the camera that shot the source. All three can come from one enhanced master, as separate local encodes, while that master stays on disk. If a platform later refuses the file, change the recipe and encode again from that master. Do not run the refused file back through enhancement just to try a different wrapper.

Further reading: Drive KwaFlux from Codex, Claude, OpenClaw, DeepSeek, Hermes, and Cursor.