How to clip a YouTube video without downloading (2026 guide)

To clip a YouTube video without downloading, paste the public URL into a browser-based clipper that streams from YouTube's IFrame Player, mark in and out points on the timeline, and share the URL it generates. The clip plays for anyone, views count toward the original creator, and nothing is downloaded, re-encoded, or re-hosted. It takes under a minute.

That's the short answer. The longer answer is that the three workflows people used for this job before April 2026 have all degraded — one was retired, one never had end-time control, and one is heavy enough that most people abandon it after the first attempt. This post walks through each, explains what specifically broke, and shows the URL-native method that survives.

The three ways people used to do this (before April 2026)

Up until April 17, 2026, anyone wanting to share part of a YouTube video had three reasonable options. None of them were perfect, but together they covered the workflow. Here's what each did, specifically.

1. YouTube Clips. Introduced in 2020, the viewer-side Clips feature let you set both a start time and an end time on any public video (between 5 and 60 seconds), generate a custom title, and share a dedicated /clip/<id> URL that opened a stripped-down player focused on just the clipped range. Views counted toward the source video, the URL unfurled as a playable card on Discord, X, Reddit, Slack, and Substack, and no download was involved — Clips streamed from YouTube directly. For "share the moment, not the whole video," it was the canonical tool.

2. Share-at-Timestamp. YouTube's youtube.com/watch?v=...&t=43s UI, accessible from the Share dialog by ticking "Start at." It carried a start time as a query parameter and routed viewers to the full watch page, opened at the timestamp. Friction-free, no download, but only step one of the workflow — there was no end time, no curated metadata, no dedicated viewer page. It worked for "watch this from here" but not for "watch this 30-second moment."

3. Download, edit, re-upload. The pre-tooling workflow that predated both Clips and Share-at-Timestamp, and the fallback whenever the other two were too constrained. Pull the source MP4 with yt-dlp, trim with FFmpeg or CapCut, re-upload to YouTube or a third-party host, share the new link. The only method that gave full control over end-time, multi-clip sequencing, and editorial polish — also, by an order of magnitude, the heaviest, and it strips view credit and attribution from the original creator, which YouTube's Terms do not love.

For most casual sharers, options 1 and 2 covered the job. Clips for moments that needed an end time; Share-at-Timestamp for "start watching here." Option 3 was reserved for serious editorial work.

What's broken now

All three workflows have problems in 2026, in increasing order of severity.

Share-at-Timestamp still works, but never solved the core problem. The ?t= parameter only carries a start time. The YouTube share dialog does not generate an &end= parameter, and the rendered watch page ignores end-time hints even when they're manually appended. If your job is "share a precise duration," Share-at-Timestamp does not do it — it never did, and nothing changed in April. The full gap analysis is in the Share-at-Timestamp alternative breakdown.

YouTube Clips was deprecated on April 17, 2026. The deprecation note routed users to Share-at-Timestamp and said Clips usage didn't justify continued investment. Existing /clip/<id> URLs still play for now, but the creation workflow is gone — you can no longer respond to the next great podcast moment with a 30-second share. The full post-mortem on what was lost and why is in YouTube killed Clips: here's what to use instead in 2026. The short version: end-time control, multi-clip sequencing, the dedicated /clip/<id> viewer, and the unfurled-embed previews that made Clips load-bearing on Discord and X.

The download-and-reupload workflow still works mechanically but is heavier than ever. yt-dlp still pulls source files, FFmpeg still trims, CapCut Web still edits. What changed is the surrounding context: YouTube's enforcement against re-uploaded clipped content has gotten more aggressive, and the time cost — download, encode, edit, re-encode, upload, wait for processing — runs ten to fifteen minutes per clip versus the under-a-minute loop the other two methods supported. For a casual share it's wildly disproportionate; for a serious editorial pipeline it's still defensible if you've thought through the IP and attribution implications.

The result: the workflow that did the full job (Clips) is gone, the official replacement only does part of it, and the heavy fallback costs ten minutes per share and risks creator attribution.

The URL-native method that survives

The category that survives is what we'll call URL-native clipping: tools that take a YouTube URL as input, let you mark in and out points in a browser, and emit a share URL that streams the clipped range from YouTube directly. No download, no re-encode, no re-host. The viewer never has the file locally. Views count toward the source.

Segue is the one we built for this job. The workflow is four steps, and the whole loop runs in the browser:

1. Paste the YouTube URL. Open the studio at /studio. Paste any public YouTube URL into the input field. The studio loads the video in a browser-native player that streams from YouTube's IFrame Player — the same surface used by every embedded YouTube player on the web. No install, no account, nothing downloaded.

2. Mark the in point. Drag the playhead on the timeline to the start of the moment. Click Set in. The studio anchors the clip's start to that timecode. The timeline is precise enough for frame-level work, and there's a timecode field if you want to type an exact value.

3. Mark the out point. Scrub forward to the end of the moment. Click Set out. The clip is now defined as a precise range with both endpoints — the capability Share-at-Timestamp does not provide and the reason every URL-native clipper exists.

4. (Optional) Add more clips. Set additional in/out points on the same video to chain multiple moments into one share. Drag to reorder. On the Pro tier, paste a second URL from the same YouTube channel and the studio adds its clips into the same mix, with smooth transitions between sources. This is the multi-video sequencing workflow neither Clips nor Share-at-Timestamp ever offered.

5. Share one link. Click Share. The studio generates a /m/<slug> URL that contains the entire mix. Paste it into Discord, X, Slack, Substack, an email, or any platform that handles links. Recipients click and the curated clip plays in a clean viewer that streams from YouTube directly.

The whole loop runs in the browser. Nothing is downloaded to your machine; nothing is uploaded to ours. The source MP4 stays on YouTube's servers, the clipped range plays through the IFrame Player, and the share URL is just a description of what to play and when. The free tier supports up to three clips per mix on a single video and five of fourteen transition presets, no account required. Pro Annual ($29/year) unlocks unlimited clips, cross-video mixing on the same channel, all fourteen transitions, no watermark, and clean short URLs. Pro Lifetime ($49 one-time, capped at the first 500 buyers or 90 days) is the launch-window SKU. Full breakdown on the pricing page.

How the methods compare

The first row is the headline question — set an end time? — because that's the capability whose presence or absence determines whether the tool actually does the job. The remaining rows show the secondary capabilities most users care about: download burden, multi-clip sequencing, single-URL sharing, and cost.

Two cells worth flagging: the "Cost" column for the download workflow ("time + IP cost high") is the load-bearing one — the dollar cost is zero, but the per-clip time cost is ten to fifteen minutes versus under a minute for the URL-native methods, and the IP exposure depends entirely on what you do with the resulting MP4. And the "Multi-clip" column is the one Clips users have been trying to fake for years by posting three /clip/ URLs in a row; the URL-native method is the first option that does it natively in a single share.

Edge cases

A few situations don't fit the happy path and are worth being explicit about.

The video has embedding disabled. Some music labels, sports rights-holders, and a small minority of individual creators turn off the embed permission on their videos. When that's the case, the source cannot be clipped through any IFrame-based tool — including Segue, including the old YouTube Clips feature when it was alive, including any other URL-native clipper. The IFrame Player respects the embed permission. If you encounter a video where Segue refuses to load, it's almost always this. The only workflow that still functions on embedding-disabled videos is download-and-reupload, which trades the embedding-disabled problem for an attribution and IP problem.

You only need a timestamp link, no end time. If "watch this video starting here" is genuinely the entire job — for example, jumping someone into a long lecture at a specific moment with the expectation they'll watch the rest — Share-at-Timestamp is still the right tool. Hit Share on the YouTube watch page, tick "Start at," copy. It's free, native, and unfurls correctly. The URL-native methods exist for the duration-bounded job; if duration doesn't matter, the simpler tool wins.

You need a sequence across multiple unrelated videos. Segue's cross-video mixing is constrained to a single YouTube channel. That's a deliberate choice — same-channel curation (a podcast best-of, a season highlight reel) sits cleanly inside fair-use territory; cross-creator aggregation does not, and tools that allow it tend to attract cease-and-desists. If you genuinely need to sequence clips from unrelated channels, the only workflow that survives is download-edit-reupload, and you should think hard about the attribution implications before shipping it. The head-to-head with YouTube Clips covers the same-channel rationale in more detail.

You're a paid clipper. If clipping is your job — Whop or similar — the post-Clips workflow is its own conversation. URL-native tools fit well structurally, but contract terms, attribution requirements, and earnings mechanics are a separate problem. The paid-clipper write-up covers it.

The video gets deleted. Because Segue streams from YouTube, a deleted source means a clip that stops playing. The trade-off is the same any embedded YouTube player makes: view attribution and zero hosting cost in exchange for being downstream of the creator's deletion decisions. If long-term availability matters more than attribution, the manual download workflow is a better fit.

Make your first mix free

If you used to clip podcasts, sports moments, or music to share with your audience, the URL-native workflow is the closest thing to your old loop back. Open the studio, paste a URL, mark in and out, share one link. The free tier handles up to three clips per single-video mix with no account required; Pro unlocks unlimited clips and cross-video mixing on the same channel.

Make your first mix free →