CloudConvert and similar services convert your video by uploading it to their servers. NearVid trims and converts video directly in your browser: lossless trimming and WebM/GIF output via a self-built, GPL-free ffmpeg.wasm engine, plus MP4 export using your browser's own built-in codecs where supported — your video is never uploaded anywhere.
→ 0 files sent to a server · video processing runs on your device
A service like CloudConvert is built as a server pipeline: your video uploads first, waits in a conversion queue, gets processed, then downloads back — which is why cloud converters meter file sizes and conversion minutes. NearVid removes that pipeline entirely: a real FFmpeg build compiled to WebAssembly runs inside your browser tab, so processing starts the moment you pick a file — no upload time, no queue, no daily limits, just your own device's speed and memory. That covers lossless trimming, WebM conversion, GIF creation, and audio extraction in every supported browser, plus MP4 export through your browser's own built-in H.264 encoder where it's available.
An honest comparison cuts both ways. A server fleet can run codecs a browser tool can't ship: a cloud converter supports many more output formats, and it produces MP4 on any browser, because the encoding happens on machines it controls. NearVid's GPL-free FFmpeg build deliberately contains no H.264 encoder, so its MP4 export exists only where the browser itself provides one through WebCodecs (Chrome and most Chromium-based browsers), and only for sources that path can read (MP4, MOV, WebM, MKV, MPEG-TS). If you need an exotic output format that must work on every device, a cloud converter is genuinely the better tool.
What you get in exchange is structural, not a policy promise: your video cannot be uploaded here, because there is no server to receive it and the page's Content-Security-Policy blocks sending it anywhere. That removes everything the pipeline brings with it — the upload wait, the conversion queue, per-day minutes, file-size tiers, and the question of when the copy of your file gets deleted. The only ceiling is your own hardware: files up to 500 MB (50 MB on low-memory phones), processed at whatever speed your device can manage. For everyday jobs — trimming a recording, converting a clip to WebM or GIF, pulling out the audio — the work starts the instant you choose the file.
No. NearVid processes video entirely on-device — a strict Content-Security-Policy technically blocks any request that could send your video out. CloudConvert and similar tools need an upload because the conversion happens on their servers; NearVid's conversion happens in your browser instead.
Yes, in most Chrome- and Edge-based browsers — NearVid detects support and uses your browser's own built-in H.264 encoder via the WebCodecs API, so even MP4 output never leaves your device. When MP4 isn't available, NearVid still offers lossless trimming, WebM conversion and GIF creation, which work in every supported browser.
When the job needs what only servers can offer: uncommon target formats, codecs like H.265, batch conversion of many large files, or an API for automated pipelines. NearVid deliberately covers the everyday cases — trim, WebM, GIF, audio and frame extraction, and MP4 where the browser supports it — with the guarantee that your video never leaves your device.