Skip to main content

Convert Videos Without Uploading Them

Conversion runs in your browser. Files stay on your device.

  • No upload endpoint for video. The file stays on your device
  • Verifiable in DevTools. Open the network tab during a run
  • A reasonable default for personal and work footage you would rather keep local
  • No account, no email, no per-job logging of file content
  • Same batch and compression features as the public homepage

Overview

Many online converters process files on remote servers rather than locally in the browser. The file lives on someone else's machine for the duration of the job, sits in their object storage while their retention policy ticks down, and shows up in their access logs. For casual home video that is usually fine. For internal work clips, footage you would rather not hand to a third party, or anything you would prefer to keep on your own machine, sending it to a stranger's server is something to consider.

This tool was built so the model is structurally simpler: there is no server-side upload endpoint for video at all. The site never receives the file in the first place. Conversion runs in your browser via the WebCodecs API, on your own device.

You can verify this in about 10 seconds: open your browser DevTools network tab, run a conversion, and observe that no outbound request carries the file. The page itself is just static HTML, CSS, and JavaScript.

Technical notes

What "no upload endpoint" means

There is no /api/upload, no presigned S3 URL, no multipart POST handler in the backend that accepts video bytes. The site is served as static assets; the encoder runs in the browser only.

How to verify

Open your browser DevTools, switch to the Network tab, filter to 'media' or 'XHR', and run a conversion. You will see no request body containing your video. The only network traffic is for the page assets themselves.

What is logged

Vercel Analytics records anonymized page views. There is no per-job logging, no upload log, and no retention policy for files because there is nothing to retain.

Good to know

Privacy is structural, not procedural

The bytes never reach a server, but your organization may still require approved tooling for sensitive material. This page is not legal advice. Talk to your IT or compliance team if you have a specific policy to follow.

The page itself is loaded over the network

Loading the page (HTML, CSS, JavaScript) involves your browser, your network, and the CDN, same as any website. The video bytes are what stays local.

How to convert videos without uploading them

Run a full video conversion locally in your browser, without uploading the video to a conversion server.

01

Add your videos

Drag and drop your video files into the converter, or click to pick them.

02

Choose your settings

Pick the output format, quality, optional width, and whether to remove audio.

03

Start the batch

Click Convert files. Each file is processed locally on your device.

04

Download

Download files individually, or grab the whole batch as a ZIP.

Frequently Asked Questions

Are my files uploaded anywhere?

No. There is no upload endpoint for video on this site. Files are processed in your browser via WebCodecs and stay on your device.

How do I check that nothing is uploaded?

Open your browser's DevTools network tab and filter by media or XHR while you run a conversion. You should not see a request body containing your file. The only network traffic should be for static page assets.

Is this a good fit for sensitive or work-related video?

For many privacy-conscious workflows, yes; the bytes do not leave your device. For anything covered by a specific organizational policy, treat this page as one option to evaluate, not a compliance promise.

What about the IP address mentioned in the privacy page?

Vercel may briefly process your IP for abuse prevention on page load, the same way any web host does. It is not associated with the contents of any file because no file is sent.

Which browsers does this work in?

Conversion requires WebCodecs video encoding and decoding, but each browser and device supports a different codec subset. MP4, MOV, and MKV output use H.264 video with AAC audio; Firefox and desktop Linux browsers do not natively encode AAC. Safari 16.4 added video WebCodecs, while Safari 26 added audio encoding and decoding. WebM output uses VP9 with Opus and may work where AAC output does not. For the widest support, use a recent desktop Chrome or Edge release, or Safari 26+. The converter still validates the actual source and output codec configuration when a job starts.

Sources: MDN: WebCodecs API · MDN: WebCodecs codec selection · WebKit: WebCodecs video support in Safari 16.4 · WebKit: WebCodecs audio support in Safari 26 · Mediabunny: supported formats and codecs · Reviewed 2026-10-12