Skip the download step
You don't need the file on your machine first. Paste the link and the video loads straight into the editor - useful when the source is a 2 GB recording you'd rather not keep a copy of.
Paste a link - a YouTube video or a direct video URL - and clip it without downloading anything first. Mark your in and out points, then export the clip or copy a share link. Nothing you load is ever uploaded.
Clipping from a URL means the video has to reach your browser without ever passing through our servers - because there aren't any. So when you paste a link, Clippingnet tries three approaches in order, stopping at the first one that works.
First it attempts a full fetch: download the bytes into memory so clipping behaves exactly like a local file. If the file is over 60 MB or the server refuses, it falls back to streaming with CORS approval - playback and export both still work.
If the server refuses cross-origin access entirely, the last resort is plain playback. You can still scrub, mark points, and preview, but the browser blocks pixel recording, so export is unavailable. The tool tells you which tier you landed on.
You don't need the file on your machine first. Paste the link and the video loads straight into the editor - useful when the source is a 2 GB recording you'd rather not keep a copy of.
Paste a YouTube watch, Shorts, or live VOD link and you get timestamped share links plus an auto-stopping embed instead of a file - the only clipping YouTube permits from a browser.
Whatever the source, the same controls apply: drag the orange handles, tap I and O while playing, or type timecodes to the millisecond.
When the source server allows it, the selected segment downloads as a WebM with full audio - named with its timestamps so repeated clips never collide.
A status chip above the timeline tells you which load tier the URL landed on, so you find out whether export will work before you spend time marking points.
Copy a link, grab an embed, or post to WhatsApp, X, Telegram, LinkedIn, Reddit and more - pointing at the original source rather than a re-uploaded copy.
Drop any YouTube link or a direct video URL into the box at the top and press Clip from URL. A direct URL is one that ends in a video file - .mp4, .webm, .mov - not a page that happens to contain a video.
Once the video loads, a chip above the timeline shows how it was loaded and whether export is available. If it says preview only, the source server blocks recording - you can still mark points and get a share link, but not a file.
Drag the orange handles to fence off your moment, or play the video and tap I for the in point and O for the out point. Nudge to the exact frame with the arrow keys, then hit Preview clip to check it.
Export clip downloads your selection as a WebM. For YouTube sources the same button produces share and embed links that start and stop at your points. Either way, the Share row posts it anywhere in one tap.
Not every link is clippable, and the reason is usually the same one: what the hosting server allows. Here's an honest breakdown.
| URL type | Example | Loads | Export file | What you get |
|---|---|---|---|---|
| Direct video file | …/clip.mp4 | ✓ | ✓ | Full editor with WebM export, when the server allows cross-origin reads |
| Direct file, CORS blocked | …/private.mp4 | ✓ | ✗ | Playback, scrubbing, and preview - but the browser blocks recording |
| YouTube watch link | youtube.com/watch?v=… | ✓ | ✗ | Timestamped share link, auto-stopping embed, and iframe code |
| YouTube Shorts / live VOD | youtube.com/shorts/… | ✓ | ✗ | Same as a watch link - the player handles all three formats |
| YouTube /clip/ link | youtube.com/clip/… | ✗ | ✗ | Hides the video ID - open it and copy the normal watch link instead |
| Page containing a video | example.com/article | ✗ | ✗ | Not a video file - right-click the player and copy the video address |
| HLS / DASH stream | …/playlist.m3u8 | ~ | ✗ | Only where the browser supports it natively, mostly Safari |
| Login-protected URL | …/private?token=… | ✗ | ✗ | Your session cookies aren't sent - download the file and load it locally |
The general rule: if you can paste the URL into a fresh browser tab and the video plays on its own, it will load here. If the link opens a webpage instead of a video, you need the underlying file address - right-click the player and choose "Copy video address."
It's almost always CORS - Cross-Origin Resource Sharing. A server decides whether other websites may read its files. If a video server doesn't send an Access-Control-Allow-Origin header, your browser will happily play the video but refuses to let this page read its pixels.
That's a browser security rule, not something a tool can work around. It exists so a malicious page can't silently read content you're authorised to see and ship it elsewhere - the same rule that protects you here.
# blocked: no CORS header at all GET /video.mp4 content-type: video/mp4 → export unavailable (tainted canvas) # allowed: server permits cross-origin reads GET /video.mp4 content-type: video/mp4 access-control-allow-origin: * accept-ranges: bytes → export ready
No hidden costs. No trials that expire. No features behind a paywall. URL clipping is totally free - here's the entire pricing table.
Why free? Because there's nothing to charge for: Clippingnet has no servers, no storage, and no processing bills - your own browser does all the work.
The URL goes to your browser, never to us. Most online clippers accept a URL, fetch the video onto their server, cut it there, and hand back a download link - which means a copy of that video now lives on someone else's disk. Clippingnet has no server in the loop: your browser fetches the URL directly, clips locally, and writes the output straight to your downloads folder.
Practical guides on working with video URLs, CORS, and streaming formats.
Right-click, DevTools Network tab, and view-source - three reliable ways to get from a webpage to the actual video file address.
Why a video that plays perfectly can still refuse to be recorded - and what the browser is actually protecting you from.
The exact nginx, Apache, and S3 configuration that makes your videos clippable from other sites - plus range request support.
What each delivery format means for clipping, which browsers handle them natively, and why an .m3u8 is not a video file.
Speed, privacy, and format limits - an honest look at what each approach gives up to get the other.
Timestamped links, fragment URLs, and auto-stopping embeds - when a link beats a file, and how to build one for any platform.
Everything people ask about clipping video straight from a link.
A URL that points at the video file itself, usually ending in .mp4, .webm, .mov, or similar. Paste it into a fresh browser tab: if the video plays on its own with no page around it, it's direct. If a webpage loads instead, that's a page URL, not a video URL.
Right-click the video player and look for "Copy video address" or "Copy video URL." If the site blocks right-click, open your browser's developer tools, go to the Network tab, filter by Media, and reload - the video file request will appear there.
No - that's the point of URL clipping. The browser fetches the video directly from its source. Downloading first is only necessary when the source server blocks cross-origin access and you need a file export.
No. There are no servers. Your browser fetches the URL directly from the source, holds the video in memory, clips it locally, and writes the output to your downloads folder. The link never passes through us.
The source server didn't grant cross-origin permission (CORS). The video plays fine, but the browser won't let this page record its pixels - a security rule no tool can override. You can still mark points and copy a share link; for a file, download the video and load it locally.
Yes. Paste any YouTube watch, Shorts, embed, or live VOD link. Because YouTube doesn't permit browser-side downloads, you get a timestamped share link, an auto-stopping embed URL, and iframe code rather than a downloaded file.
Those URLs don't contain the underlying video ID - YouTube resolves them server-side. Open the clip on YouTube, click the video title to reach the normal watch page, and paste that link here instead.
Only if you have the direct file URL, which those platforms generally don't expose. Their page URLs load a player, not a video file. For platform content, download it through whatever means the platform officially offers and clip the file locally.
Only where the browser supports HLS natively, which in practice means Safari. Chrome and Firefox need a JavaScript player library to handle .m3u8 playlists. Even where playback works, export usually won't because of how segmented streams are delivered.
Your session cookies aren't sent with the request, so a login-protected URL will fail to load. Download the file while signed in, then drop it on the zone above - local files work regardless of where they came from.
Files under 60 MB are fetched fully into memory for the smoothest experience. Anything larger is streamed instead, which still supports clipping and export as long as the server allows cross-origin access.
The video is being downloaded to your browser at whatever speed the source server provides. A slow origin server or a large file means a slower load - there's no caching layer in between, because there's no server in between.
WebM with full audio, at 8 Mbps. That's the only format browsers can encode natively without a server. Converting to MP4 takes one command: ffmpeg -i clip.webm -c:a aac clip.mp4.
The browser records your selection in real time while it plays. A 30-second clip takes roughly 30 seconds. Server-based clippers are faster, but only because the video has been uploaded to them first.
Yes. After exporting one clip, move the handles to the next moment and export again. The video stays loaded, so you're not re-fetching it each time.
Yes - the "Save full video" button downloads the complete original file in its native format. If the fetch is blocked, it opens the URL in a new tab so you can save it manually.
For YouTube links, yes - a ?t=90 parameter pre-sets the in point to that timestamp so you start from the right place. Direct video URLs with #t= fragments are handled by the browser's own playback.
Yes. Paste the link, use touch to drag the handles or the Set in/out buttons while playing, then export or copy the link. Long exports are easier on desktop since the screen needs to stay awake.
Loading a publicly accessible URL in your own browser is ordinary web use. What matters is what you do with the clip: publishing someone else's content needs permission, a license, or a legal exception. For personal reference, it's uncontroversial.
Slightly, since the export re-encodes at 8 Mbps. On typical footage the difference is hard to see. The source is never modified - you're always working from a copy in your browser's memory.
Yes, if the token is still valid and the server allows cross-origin access. Paste the whole URL including everything after the ?. Expiring links may stop working mid-session, in which case you'll need a fresh one.
Redirects are followed automatically as long as the final destination also permits cross-origin access. A redirect that lands on a login page or an HTML error page will fail to load as a video.
If your browser can play the file, you can load it, mark in/out points, and export. The result is a WebM containing your audio segment. For serious audio editing, a dedicated audio tool gives you waveform precision.
Send an Access-Control-Allow-Origin header on the video response, plus Accept-Ranges: bytes for smooth seeking. One line of nginx or S3 bucket configuration is usually all it takes.
Yes. Sharing doesn't re-host anything - the link points back at the source URL you loaded, or at YouTube with your timestamps attached. The original stays where it is.