Behind the snip
The file is made on your machine
Paste a link, cut the moment, keep the file. The interesting part is where the conversion happens: after the stream reaches your browser, it does not go back out.
The path a clip takes
- You paste a YouTube URL. Snip Vid looks up the title, duration, and thumbnail so you can confirm you grabbed the right video.
- A small API on this site fetches the stream from YouTube and pipes it to your browser. That hop exists because YouTube will not hand the file to a webpage directly.
- If you picked a range or GIF, ffmpeg.wasm — a copy of ffmpeg running in WebAssembly — trims and converts the bytes in the tab. A full-range MP4 can skip that step and save as-is.
- You download a local file. The finished MP4 or GIF is never uploaded to Snip Vid.
The technical bit
Video lookup and the stream itself go through YouTube.js on the server. Conversion uses ffmpeg.wasm in the browser. That split is why we can say the clip is processed locally without pretending the original stream never touches our Worker. For what is logged, see privacy.
GIF conversion loves short ranges. Longer loops get chunky; a few seconds is usually the sweet spot.