Video Trimmer in the browser is not a generate

/free-tools/video-trimmer never spends a credit. Do not pay a model to do an in-browser file job. In and out points go on the player. The tab records that range with MediaRecorder. You already have the take. Nothing about shortening it requires Seedance, Kling, or a credit quote.

Generation on Versely always costs credits. There is no 0-credit model row. What it costs is twelve different meters — per second, per thousand characters, per megapixel, per export. A local capture of playback is none of those meters. The file never leaves the machine.

Playback in, new file out

Dropping a clip on a video model and asking it to "keep the good part" is a generate. The model will invent motion, or bill you as if it did, and you still will not have a mark on the source.

This tool does something smaller:

• You set start and end on the element.
• captureStream feeds MediaRecorder whatever is playing.
• You download whatever codec the browser writes — usually WebM.

Browsers cannot rewrite MP4 atoms. The cut is a re-encode of playback, near your marks, not a lossless keyframe trim of the bitstream. That is the honest output. Use it for dead air on a camera-roll take, a screen recording you are about to caption, a download you refuse to upload. Do not use it as a colour-accurate master.

If you needed frame-accurate studio trim on a hosted URL, that is a different page.

This is not cut_video

Trim a video is the in-app job: cut_video, one [start, end) in seconds, a new object in storage, billed as an editor operation. Ask estimate_cost on a long source if you want the figure first. The editor previews and final export scenario is that family: you pay for exports, not for inventing a scene.

The free trimmer is the opposite family: no account, no upload, no quote. Credits roll over on an active plan and never apply here, because no model ran.

Do not spend cut_video to learn whether the joke is in the first twelve seconds. Scrub it locally. Do not spend a video model to do either trim.

Feature-detect, then stop

The page needs captureStream and MediaRecorder. Safari has historically shipped neither in a usable form. The UI says so instead of failing after the file picker. That is not a Kling ticket.

Because nothing is uploaded, it still works with the network off — until the browser itself cannot capture. Generating a "shorter version" from a prompt will not rescue an unavailable trimmer. You will lose the take you already shot.

The rest of free tools follow the same rule: Canvas, File API, or arithmetic on the visitor's device. Utilities that never touch a model can be actually free; Versely has no free generate tier.

Cut locally. Pay on purpose later.

Does this file need a model?

No → trim here. Zero credits. If the keep has speech, burn captions on that shorter file. Captioning is billed. The in/out was not.

Yes → you are generating, locking a still, or scoring. Open cost and pick a real row.

A shorter hallucination is not a trim.

FAQ

Do paid plans still pay credits to use this?

No. It never calls a model, so it never quotes credits. Subscriptions buy generation and studio tools. This tab records playback on the device.

Why WebM, and why isn't it lossless?

MediaRecorder writes a new file. It does not edit MP4 atoms. Picture is re-compressed; marks are approximate. Hosted, billed trims live on trim a video.

Why does the page refuse my browser?

No usable capture pipeline — historically Safari. Switch browser, or use the in-app trim. Do not generate a replacement clip.

Trim here before captions?

When the source is already the take, yes. Captions transcribe speech; models meter renders. Both are wasted on minutes you were going to drop.