Drop a video and NearVid trims it losslessly, converts it to MP4 or WebM, turns it into a GIF, or pulls out the audio — right in your browser. Nothing is ever uploaded to a server.
→ 0 files sent to a server · video processing runs on your device
Most video tools upload your file to a server to process it — which means someone else's computer briefly has your video. NearVid runs entirely on-device: trimming, WebM conversion, GIF creation, and audio extraction use a real FFmpeg build compiled to WebAssembly, and always work, on any browser. Where your browser supports it, MP4 output is also available — it uses your browser's own built-in H.264/AAC encoder via WebCodecs, not anything NearVid bundles, so it only appears as an option on Chrome and other Chromium-based browsers with hardware or software H.264 encoding support.
NearVid isn't a thin front-end to a conversion server — the converter itself runs in the page. Trimming uses FFmpeg's stream copy: the compressed video and audio packets are copied into a new file without ever being decoded, which is why even a long recording trims in seconds and the result is bit-for-bit the same quality as the source. WebM and GIF conversion are true re-encodes done by the same WebAssembly engine. MP4 export takes a separate path — the WebCodecs API — which calls the H.264/AAC encoder your browser itself ships; NearVid bundles no proprietary codecs, so that option exists only on browsers that provide one.
Doing everything on-device also draws honest limits. Your device's memory is the ceiling: the whole file is processed in RAM, so NearVid accepts files up to 500 MB (50 MB on low-memory phones). GIF clips are capped at 10 seconds, because the format balloons quickly. A stream-copied trim can only start on a keyframe, so a cut point may shift by a fraction of a second. And NearVid is deliberately not a full editor — there is no timeline, no subtitles, no merging of clips, and no “compress to a target size” mode. For a fast, private cut or conversion, those trade-offs are the point.
Every operation is free, with no account, no watermark and no daily limit. Because your device does the processing, NearVid has almost no server costs to recover; the site is paid for by ads on this page (shown only with your consent) and clearly labelled affiliate links. The processing screen itself carries no ads at all.
Anything the bundled FFmpeg can demux — MP4, MOV, WebM, MKV, AVI and most other common containers. Lossless trim, WebM and GIF conversion, and audio extraction work for all of them. MP4 export is narrower: it needs a source its WebCodecs path can read (MP4, MOV, WebM, MKV or MPEG-TS) and a browser with H.264 encoding support.
Yes — and you don't have to take our word for it. The page's Content-Security-Policy technically prevents it from sending your file anywhere, and you can keep your browser's developer-tools network panel open while processing: once the engine has loaded, no request carrying your video ever appears, because none is ever made.