yescord

Trim a video or voice recording

Keep one part, or cut pieces out of the middle. Save MP4, GIF or WAV. The file never leaves this tab.

or drop one anywhere on this page. Video: MP4, WebM, MOV. Sound: WEBA, M4A, OGG, OPUS, MP3, WAV, FLAC. Whatever this browser can decode (checking…).

What happens to your file

Opening a file gives this tab a private blob: address for it, the same way a local video player opens it. The browser decodes the picture and sound in memory, and the new MP4, GIF or sound file is built in memory too. Download saves it like any other download. This page has no upload code and no server to upload to; it does not use browser storage either, so closing the tab forgets everything. The only network request after the page loads is an anonymous, cookie-free page-view count (GoatCounter), which never sees your video.

How to use it

  • Open a video or a sound file with the button, or drop it anywhere on the page. From the recorder, the “Trim or make a GIF” button under a finished video (“Trim” under a voice recording) opens this page with that recording already loaded. A sound file shows its waveform where a video would show its picture.
  • Choose the part to keep. Drag the two handles, type exact times into Start and End (1:05.3, 65.3 and 0:01:05.3 all mean the same), or pause where you want a cut and press “Set start here” or “Set end here”. “Play the cut” plays just that part.
  • Or remove parts from the middle. Switch “The two handles mark” to “a part to remove from the middle”. Mark a part with the handles and press “Remove this part”; it is blocked out on the timeline and listed with a “Put back” button. Mark and remove as many parts as you like. “Result” shows how long the joined file will be, and playing the file skips the removed parts, to within about a quarter of a second.
  • Save. Video: Save MP4 or Save GIF. Sound: Save WAV, and Save M4A or Save Opus where this browser can encode them. Under a video, “Save sound only” offers the same three for just its sound. A progress bar shows how far it has got, and Cancel stops it. The finished file is listed below the trimmer with its size, a player and a Download button.

MP4: a fresh encode, not a copy

The kept part is re-encoded as H.264 video, which every phone, editor and player opens. Sound becomes AAC where the browser has an AAC encoder (Chrome and Edge on Windows and macOS have one) and Opus inside the MP4 where it does not, for example Chrome on Linux. Opus-in-MP4 plays in browsers, VLC, Windows and Android, but QuickTime may play it silent. The line above the Save MP4 button tells you which one this browser will write before you press it.

Because it re-encodes, the result is a little softer than the source. The target bitrate is 0.09 bit per pixel per frame at 30 fps: about 2.5 Mbit/s (19 MB per minute) for 1280×720 and 5.6 Mbit/s for 1920×1080. Anything larger than 1080p is scaled down to fit it. The picture is captured while the clip plays in the tab, so a 40-second cut takes about 40 seconds. If the device is busy, a frame can occasionally be skipped; the one before it simply stays on screen a thirtieth of a second longer, so timing and sound stay in sync. Keep the tab in front: browsers pause video in background tabs. To get the sound, the page decodes the whole file's audio track in memory. That is quick for normal recordings, but a file of several gigabytes can make a phone tab run out of memory.

Removing parts from the middle uses the same encode. The page plays or seeks through each kept piece in turn and never draws a frame from a removed part; each piece's first frame is stamped where the previous piece ended, so the MP4 runs on without a gap or a frozen picture. The sound is cut at the same instants and each join gets a 4 ms fade so it does not click. Saving takes about as long as what is left, plus a moment per join.

Some browsers cannot encode H.264 from a web page. Where the video can still be recorded as it plays (Chrome-based browsers, Firefox), the page records the cut instead. It writes MP4 where the browser can, otherwise WebM, and says which one before you save. WebM plays in every browser and VLC, but not in QuickTime. With parts removed, this route pauses the recorder while the video jumps over each removed part; a join can come out up to about a tenth of a second long or short.

Voice recordings and other sound files

A sound file (the recorder's .weba or .m4a voice recordings, or OGG, OPUS, MP3, WAV and FLAC files) opens in a waveform view. The browser's own decoder turns the whole file into samples at 48 kHz; the waveform is drawn from those samples, one bar per two screen pixels showing the loudest moment in that slice, and the parts that will not be saved are drawn faint. The handles, the time fields and remove mode work exactly as they do for video.

  • WAV works in every browser: 16-bit PCM at 48 kHz, which every audio editor, phone and transcription tool opens. It is big: 5.8 MB a minute in mono, 11.5 MB in stereo. A 3-minute voice memo is about 17 MB.
  • M4A (AAC at 96 kbit/s, about 0.7 MB a minute) is offered where the browser has an AAC encoder for web pages, such as Chrome and Edge on Windows and macOS; the line above the save buttons says whether this one does. It opens everywhere.
  • Opus is offered instead where there is an Opus encoder but no AAC one, for example Chrome on Linux: an Ogg .opus file at 64 kbit/s, about 0.5 MB a minute. It plays in Chrome, Edge, Firefox, Android and VLC; Safari and other Apple software may not open it.

Decoding needs memory: the page holds the decoded sound as 32-bit samples, about 11.5 MB per minute per channel, so an hour of stereo takes about 1.4 GB. That is fine on a laptop and too much for many phones. The same holds for the sound of a video, which is decoded whole even when only a short part is kept. A file with a different sample rate (say 44.1 kHz) is converted to 48 kHz, and a surround file is saved as its first two channels. When the browser cannot decode a file, the page reads the first bytes to name the codec and says which browsers can: for example, Apple Lossless (ALAC) opens only in Safari, and old AMR phone memos in almost no browser.

Just the sound of a video

Under a loaded video, “Save sound only” saves the sound of the part you kept, with any removed parts left out and the same 4 ms fade at each join, as clip-sound.wav, clip-sound.m4a or clip-sound.opus for a video called clip.mp4. The picture is not touched: the page decodes the video's sound track with the same decoder it uses for sound files, the first time you press a sound button, and keeps it for the next save of that file. That is useful for a talk or meeting recording you only need to listen to or transcribe: ten minutes of 1280×720 video saved here as MP4 is about 190 MB, and its sound alone as M4A about 7 MB (as WAV, about 115 MB in stereo).

The formats and sizes are the ones listed above for sound files. Where the browser has no AAC encoder for web pages (Firefox, and Chrome on Linux), there is no M4A button and the line above the buttons says so; WAV and Opus are still offered. A video with no sound track at all (many screen recordings made without a microphone) is not saved as a silent file: the page says the video has no sound track. If the video has sound in a codec this browser cannot decode, it says that instead and names the codec when it can tell.

GIF: why 30 seconds, and what to expect

A GIF stores every frame as its own 256-colour picture. It has no sound, and it cannot reuse one frame to describe the next the way video does. A 480×270 frame is 129,600 pixels; 30 seconds at 15 fps is 450 of them. How well they compress depends almost entirely on the picture. Measured with this page's encoder at 480×270, in bytes per pixel per frame: a slowly scrolling code editor 0.02, a moving test pattern 0.1, a zooming fractal 0.3, and grainy camera-like footage 0.98. The estimate under the GIF options uses 0.35 and shows the range. At 0.35, that 30-second GIF is about 21 MB; grainy footage would be nearer 58 MB. The same 30 seconds as a 480×270 MP4 at this page's bitrate is about 2 MB, sound included. The GIF grows in memory while it is encoded, so the page stops at 30 seconds rather than let a long GIF exhaust a phone. While it encodes, the progress line projects the final size from the frames done so far.

  • Width is 320, 480 or 640 pixels, never wider than the source, and the height keeps the proportions. 480 is sharp enough to read on-screen text in most screen recordings.
  • 10 fps is fine for screen recordings and gives smaller files. 15 fps looks smoother for people and motion. GIF timing is stored in hundredths of a second, so 15 fps alternates 70 ms and 60 ms frames to keep the total length exact.
  • Each frame gets its own 256-colour palette, so colours stay faithful frame by frame, but smooth gradients show banding. The GIF loops forever.

What it cannot do yet

  • One file at a time. It cannot join two separate files into one, put a voice recording under a video, or add music.
  • No cropping, rotating, text or speed changes. The GIF width is the only size control. For a still image that needs cropping, arrows, a label or private details blacked out, pause on the frame, take a screenshot and use Screenshot.
  • No volume, noise-removal or fade controls for sound here. The only change it makes is the automatic 4 ms fade at each join. For noise and volume, the “Clean up this recording” button under a saved sound file opens it in Clean audio. No speech-to-text here either: for a written transcript of a saved sound file, use Transcribe.
  • No lossless cut. Every MP4 and GIF save re-encodes, even when only a second is trimmed off. A WAV holds the decoded sound exactly, but it is not the original file, and it is much bigger.
  • No frame-by-frame stepping. The handles move in 0.1-second steps; for a more exact cut, type the time, which is used to the millisecond.
  • It opens only what this browser can decode. HEVC (H.265) video from iPhones plays only where the system has an HEVC decoder, so it may not open in Firefox or on Linux, and no browser plays ProRes. Sound in Apple Lossless opens only in Safari, and AMR in almost no browser.

What works where

Needed forChrome / EdgeFirefoxSafari (Mac)iOS SafariAndroid ChromeThis browser
MP4 picture (VideoEncoder)*9413016.416.494…
MP4 sound, M4A and Opus files (AudioEncoder)*94130262694…
Capturing each frame as it plays (requestVideoFrameCallback)8313215.415.483…
Fallback: recording the playing video (captureStream)62149 (as mozCaptureStream, partly, from 15)NoNo62…

Version numbers are the first release with the feature, from MDN browser-compat-data for VideoEncoder, AudioEncoder, requestVideoFrameCallback and captureStream, checked 2026-09-23. They are not test results. *MDN tracks the encoder API, not which codecs it offers. H.264 and AAC depend on the operating system and the build. The “This browser” column asks the browser you are using now, for the exact settings this page uses. Without an encoder or captureStream (for example Safari before 16.4), the MP4 button is switched off and says why. Without requestVideoFrameCallback, the page seeks through the cut frame by frame instead, which is slower. The GIF needs only canvas and Web Workers, which all of these browsers have had for over a decade. The waveform and WAV need only Web Audio's decodeAudioData, which every current browser has; whether a given codec decodes is the browser's own business (see the sound section above).

What has actually been tested

One browser: headless Chrome 150 on Linux, driven by the automated test in this site's repository on 2026-09-23. It opened a 3-second WebM, typed 1.0 and 2.0 as the start and end, and saved a 320-pixel, 10 fps GIF (10 frames) and an MP4 through WebCodecs: H.264 picture lasting 1.00 s and Opus sound lasting 1.02 s, Opus because Chrome on Linux has no AAC encoder. It saved the same MP4 again with requestVideoFrameCallback switched off (the seeking route), and once with WebCodecs switched off: the page announced the recording fallback in advance and produced an MP4 of about 1.06 s. It also checked that a webcam recording made on the front page opens here through the hand-off.

Sound and middle cuts, same browser and test, 2026-09-23. A 3-second 440 Hz tone saved as .weba (Opus in WebM, like the recorder's voice files) opened as a waveform; trimmed to 0.5–2.5 s it saved as a mono 48 kHz WAV of exactly 2.000 s and as an Ogg Opus file that decodes back to 2.000 s. A voice recording made on the front page opened here as a waveform through its “Trim” button. The same tone as .m4a (AAC) opened too, and with the decoder made to fail on purpose, the page named “AAC in MP4” and the browsers that decode it. The M4A output was not tested: Chrome on Linux has no AAC encoder. With 1.0–2.0 s removed from the 3-second test video, the MP4 through WebCodecs had a 2.00 s picture track (and 2.02 s of Opus sound), and the recording fallback made a file that plays for 2.1 s. In the sound and middle-cut runs, the tab made no network request at all from the moment the file was chosen until the result was saved. Firefox, Safari and phones have not been tested; their columns above come from MDN only.

The sound of a video, same browser, 2026-09-30. A 3-second MP4 (H.264 with a 440 Hz AAC tone) trimmed to 0.5–2.5 s saved as a stereo 48 kHz WAV of 2.000 s whose strongest frequency is 440 Hz, and as an Ogg Opus file that decodes back to 2.000 s at 440 Hz; with 1.0–2.0 s removed instead, the WAV lasted 2.000 s. This Chrome has no AAC encoder, so the page showed no M4A button and said why. The M4A route was checked with a stand-in encoder that hands the page ready-made AAC frames of the same tone: the page's clip-sound.m4a was a valid MP4 sound file (ftyp box, one mp4a track) that decodes to 2.005 s at 440 Hz. That tests this page's part of the job, not a real browser's AAC encoder. A 3-second MP4 with no sound track made no file and said it has no sound track. No network request was made from choosing the video to fetching the saved files.

Made with AI tools. · Privacy