Is It Safe to Convert or Compress Video Files Online?
Published 2 August 2026 · 6 min read
Say you just finished a client call on Zoom, recorded it for your own notes, and the file is 800MB — way over what Slack or email will accept. Somewhere in that hour of screen-share are account numbers, a pricing sheet, maybe a roadmap slide nobody outside the company has seen yet. You just need it smaller, or in a different format so your editor can open it. So you search "compress video online," pick the first result, and drag in the recording.
With a PDF, you could at least skim the first page before deciding whether to trust a site with it. A video file doesn't give you that option — you're not going to watch an hour of footage before uploading it, you're just going to trust that the tool handles it reasonably. That's a bigger leap of faith than most people realize they're taking.
Why video is a bigger ask than a PDF or a photo
A typical PDF is a few hundred kilobytes to a few megabytes. A phone photo might be 4-8MB. A few minutes of screen-recorded video, even compressed, is routinely 50-500MB, and a proper camera recording can run into gigabytes. Re-encoding video is also genuinely CPU-intensive — it's not a quick text operation, it's frame-by-frame recompression, which is exactly why so many video tools push the work onto a server with more processing power than your laptop, rather than running it in your browser tab.
That combination — a large file, a slow upload, and real processing time on the far end — means your video sits on someone else's infrastructure for noticeably longer than a PDF merge would. More time uploaded somewhere is more time for something to go wrong, whether that's a misconfigured server, a breach, or just a retention policy that's looser than advertised.
What "process it on a server" actually looks like
Same basic shape as any other online file tool: your video leaves your device, reaches a data center, gets decoded and re-encoded there by server-side software (commonly the same open-source engine, FFmpeg, that FormatDog uses locally — the difference is where it runs), and the result streams back down to you. A privacy policy somewhere usually promises deletion after some window. For an 800MB recording of a client call, that's a lot of confidential screen content sitting on a server you don't control, for however long that window actually is.
How FormatDog's video tools avoid this entirely
Every video and audio tool on FormatDog — Compress Video, Video Format Converter, Trim Video, Extract Audio from Video, and the rest — runs on a real, self-hosted build of FFmpeg compiled to WebAssembly, downloaded once (about 30MB) and executed entirely inside your browser tab. Your video is read using your browser's own File API and never leaves your device. The actual re-encoding happens on your own CPU, in local memory, the same way it would if you'd installed FFmpeg yourself on your laptop — just without needing to install anything.
That does mean the one-time 30MB engine download and the processing time both depend on your own device rather than a data center's hardware. For most compress/trim/convert jobs on a typical laptop, that's a perfectly reasonable trade for a recording never leaving your machine.
You don't have to take that on faith
Same check works here as with any file tool: open your browser's developer tools (F12, or
right-click and choose "Inspect"), click the Network tab, then select a
video and run whichever tool you're testing. Outside of the one-time engine download
(visible as a request for ffmpeg-core.wasm, which happens once and is then
cached), you won't see your actual video file appear as outgoing traffic. If a site is
uploading your video for processing, that request shows up in the same tab, usually as a
large POST request the moment you hit convert.
The honest caveat
Server-side video processing isn't inherently reckless, and most established tools do delete files on the schedule they claim. But video files carry an unusual combination of being both large and, for a screen recording or a personal clip, often quite sensitive — and unlike a document, you generally can't skim one before deciding whether to trust it to a stranger's server. Skipping the upload step removes that decision entirely, for free, with no real downside.