Trim, crop, rotate and resize video
Six changes, one pass, nothing uploaded. Three of them — rotating, removing the sound, and cutting the end — don't require re-encoding at all: the compressed picture is copied straight through, so they finish in seconds and every pixel survives. The other three do re-encode, and the tool says which is which before you press anything.
Three of these six changes are free
Editing video is usually assumed to mean re-encoding it: every frame decoded, changed, and compressed again, with time and quality spent in the process. For half of what this page does, that assumption is simply wrong. Rotating a video, removing its soundtrack, and cutting off the end can all be done without decoding a single frame — the compressed picture is copied from one file into the next exactly as it is. The result comes out in seconds no matter how long the video is, and it is not merely close to the original, it is bit-for-bit the same picture.
The reason is worth knowing, because it explains where the boundary falls. A rotation isn't stored by turning pixels; it's a number in the file's header that tells the player which way up to render. Removing audio means writing one fewer track. Cutting the end means stopping the copy early. None of those requires understanding the picture, so none of them touches it. Cropping, scaling and changing the frame rate are the opposite: each one produces frames that didn't exist in the source, which can only come from decoding and re-compressing everything.
This tool works out which side of that line your selection falls on, per change, and shows it before you commit. Pick only free changes and you get the instant path. Add one that isn't, and the whole video is re-encoded — there's no partial version of that, which is why the badge switches the moment you touch one of them.
| Change | What it costs | Why |
|---|---|---|
| Rotate 90° / 180° / 270° | Nothing | Written as an orientation flag in the MP4 header. Players read it and turn the picture as they draw it, so no frame is ever modified. |
| Remove the sound | Nothing | The audio track is simply not written. The video track is copied untouched, exactly as it would be with no changes at all. |
| Trim the end | Nothing | The copy stops at the point you chose. Everything before it is already compressed and lands in the new file unchanged. |
| Trim the start | Re-encodes | Your new starting point almost certainly isn't a keyframe, and the frames after it can't be decoded without one. The alternative would be silently giving you back a second or two you asked to remove. |
| Crop the frame | Re-encodes | A smaller frame is a different picture. Every frame has to be decoded, cut, and compressed again. |
| Change resolution or frame rate | Re-encodes | Same reason — the output frames don't exist in the source and have to be produced. |
When re-encoding does happen, the video comes out as H.264 with AAC audio, the pairing that plays everywhere. That's a deliberate choice about portability, and it has one consequence worth reading below if your source is HEVC.
Trimming: why the end is free and the start isn't
The timeline has two handles and they do not cost the same thing. Dragging the right one shortens the video by stopping the copy early — nothing is decoded, nothing is compressed, and a two-hour file is trimmed about as fast as a two-minute one. Dragging the left one re-encodes the entire remaining video, and it's worth understanding why rather than treating it as an arbitrary limitation.
Compressed video is not a series of independent pictures. A keyframe is complete on its own; the frames after it store only what changed since, sometimes for several seconds at a stretch. Cut at an arbitrary point and you land in the middle of one of those runs, holding frames that describe changes to a picture you no longer have. There are only two honest ways out: quietly extend your cut backwards to the previous keyframe — handing back up to several seconds you explicitly asked to remove — or decode from that keyframe and re-encode from your actual cut point. This tool takes the second, so the video starts where you said it starts.
In practice that means cutting a long intro off a long video takes real time, and cutting the tail off the same video doesn't. If you only need one of the two, doing just the end is dramatically cheaper. If you need both, the cost is the same as doing the start alone — a single pass handles everything you've selected.
The soundtrack follows the same rule. Trimming the end copies the audio untouched; trimming the start re-encodes it to AAC. One case has no good outcome: a Dolby track can't be re-encoded in a browser at all, so trimming the start of a file with Dolby audio means losing the sound. The panel says so before you start, and moving the start handle back to zero keeps the track.
Cropping and rotating, and the order they happen in
Drag a box on the preview to crop. Drag inside the box to move it, drag a corner to resize it, tap once to clear it. It also works from the keyboard: focus the box and the arrow keys nudge it, holding Shift resizes it instead — useful when you want a precise edge and a trackpad isn't cooperating.
Rotation is applied first, and the crop box lives in the rotated picture. This matters as soon as you use both: rotate a landscape video to portrait and the frame becomes 1080 wide by 1920 tall, so a box that was near the right edge is now near the top. Rather than making you re-draw it, the box turns with the picture and keeps hold of whatever you framed. Resolution is applied last, to whatever the crop left behind — so cropping a 1080p video to a small region and then choosing 720p gives you 720p of that region, not a 720p frame with a small region in it.
One thing the crop box cannot do is preview a file your browser can't play. MKV and ProRes are the common cases: this tool reads them perfectly well, but the browser's own video element often won't display them. When that happens you get a correctly-proportioned empty frame instead of a picture, and the crop still works — you're drawing on the right shape, just without the reference. Cropping is disabled entirely for codecs that can't be decoded at all, since a crop that can't be rendered isn't a crop.
- Rotate first if you're going to. The crop box follows the picture, so you won't lose your framing.
- Drag out the region you want to keep. The area outside it dims so you can see the result.
- Choose a resolution if you also want the output smaller. It applies to the cropped region.
Both output dimensions are rounded to even numbers, because video encoders require it. A crop of 801 pixels becomes 802 — a difference you will not see, and the only alternative would be refusing the crop.
Resolution, frame rate, and what actually makes a file smaller
Resolution and frame rate can only go down here. Choosing a resolution higher than the source would invent detail that was never recorded and charge you bytes for it; the same goes for frame rate, where the extra frames would be duplicates. Options above your source are hidden rather than offered and quietly ignored.
Lowering the resolution does reliably shrink the file, because fewer pixels genuinely need fewer bits. Lowering the frame rate is a different story, and this is where a lot of advice is wrong. Fewer frames per second does mean less data in principle — but the encoder here picks its bitrate from the output's dimensions, not from how many frames it's given, so halving the frame rate does not halve the file. What it reliably does is make motion choppier. Change frame rate when 60fps is more than you need for the destination, not as a way to save space.
If size is the goal, this is the wrong page and the compressor is the right one: it lets you set a quality level or a target size and works backwards to a bitrate. What this page does to size is mostly incidental — trimming makes the file shorter and therefore smaller, cropping and scaling reduce it, and rotating or muting barely move it.
There's one way this page can make a file bigger. If your source is HEVC — which is what recent iPhones record — and you make a change that re-encodes, the result is H.264, because that's what plays everywhere. H.264 needs more bits than HEVC for the same picture, so a cropped HEVC clip can come out larger than the original despite having fewer pixels. Rotating, muting and end-trimming avoid this entirely: they keep the HEVC exactly as it was.
What happens to the soundtrack
Removing the sound is the simplest operation on this page: the audio track isn't written, the video track is copied, and the file comes out in seconds. It's a genuine removal rather than a volume change — the track is gone, not silent, so nothing can recover it and the file is slightly smaller.
When you keep the sound, what happens to it depends on the other changes. Everything except trimming the start copies the audio bit-for-bit, surround channels and all. Trimming the start re-encodes it to AAC for the same keyframe reason the picture has, which is quick and doesn't affect the video. Multichannel audio is mixed down to stereo on that path, because browser AAC encoders refuse multichannel input outright — a downmix beats a failed export.
Dolby Digital is the exception, and the panel spells it out when it applies. AC-3 and E-AC-3 tracks can be copied but not re-encoded, since browsers ship no Dolby decoder. So they survive every change on this page except one: trimming the start, which forces a re-encode that cannot happen. Rather than failing the whole export, the tool drops the audio and tells you first — and trimming only the end keeps the track intact.
What this tool doesn't do
This is a single-pass adjustment tool, not an editor, and the edges are worth stating plainly rather than leaving you to discover them.
- It outputs MP4 only. Whatever you put in, what comes out is an MP4.
- One clip, one pass. There's no joining two videos, no cutting a section out of the middle, and no batch queue.
- There's no timeline scrubbing or playback preview of the result. The preview shows the frame at your start point so you can see what you're cropping — it isn't a player.
- No filters, no colour adjustment, no speed change, no text or watermarks.
- Subtitles, chapters and attachments are dropped, as they are anywhere this site converts video. Only picture and sound are carried over.
- There's no size limit, but there is a disk check. The result is written to local storage as it's produced, so memory doesn't grow with the file — but the space has to exist, and that's verified before anything starts.
Your original is never modified or moved. What you download is a new file, so deleting the source stays an explicit decision you make yourself.
FAQ
How do I crop a video without uploading it?
Drop the video into the tool above and drag a box on the preview. Everything runs in your browser: the file is read from your disk, decoded and re-encoded by your own device, and written back to local storage. Nothing is sent anywhere — you can open the network panel while it runs, or disconnect from the internet after this page has loaded and crop anyway. Cropping does re-encode, because a smaller frame is a different picture, so it takes time proportional to the video's length.
Why is rotating instant but cropping slow?
Because they're different kinds of operation. Rotation is stored as a flag in the file header that tells players which way up to draw the picture, so no frame is ever touched — the video is copied across as-is in seconds. Cropping produces frames that don't exist in the source, which means decoding every frame, cutting it, and compressing it again. That's real work, and it's proportional to how long the video is.
Does trimming a video lose quality?
Not if you only trim the end — that's a straight copy and the remaining picture is bit-for-bit identical to the original. Trimming the start does re-encode, because the new starting point almost never lands on a keyframe and the frames after it can't be decoded without one. That costs one generation of quality. If you only need to cut the tail off, doing just that is both faster and lossless.
Why can't I move the start handle on this file?
Because the file's video codec can't be decoded in a browser — ProRes is the usual case — and cutting the beginning requires re-encoding, which requires decoding. Rather than letting you wait through an export that would fail, the start handle is pinned at zero. Trimming the end, rotating and muting all still work on those files, and all three are instant.
Will changing the frame rate make my video smaller?
Not reliably, and it's worth being clear about that because the opposite is widely repeated. The encoder chooses its bitrate from the output's dimensions rather than from the number of frames, so halving the frame rate does not halve the file. What it definitely does is make motion choppier. Lower the frame rate when the destination doesn't need 60fps — to reduce size, lower the resolution instead, or use the compressor, which targets a size directly.
Why did my file get bigger after cropping?
Almost certainly because the source was HEVC. Recent iPhones record HEVC, and any change that re-encodes produces H.264 instead, because H.264 plays everywhere and an HEVC file doesn't. H.264 needs more bits for the same picture, and that can outweigh the pixels you removed by cropping. Rotating, muting and trimming the end sidestep this completely — they keep the original HEVC untouched.
Can I rotate a video without re-encoding it?
Yes, and that's what this tool does. MP4 stores orientation as a transformation flag rather than by turning pixels, so rotating means writing one number and copying the picture across unchanged. It finishes in seconds regardless of length, the quality is identical, and it works even on files whose codec browsers can't decode. Combine it with muting or an end trim and the whole job is still instant.
Can I make several changes at once?
Yes — that's the point of doing it here rather than one export at a time. Everything you select is applied in a single pass, so a crop plus a resolution change plus a trim costs one re-encode, not three. It also matters for quality: each separate export would be another lossy generation. Note that adding one re-encoding change to a set of free ones re-encodes the whole thing; there's no partial version of that.
Why is my crop preview blank?
Because your browser can't play that particular file, which is common with MKV and ProRes. The tool reads those files perfectly well — it uses its own reader rather than the browser's video player — but the preview element has nothing to display. You'll get a correctly-proportioned empty frame instead, and the crop box still works, so you're drawing on the right shape without a picture underneath.
Is there a file-size limit?
No. The result is written to your browser's local storage as it's produced rather than assembled in memory, so a two-hour file needs about as much memory as a two-minute one. What's checked instead is free disk space, before anything starts rather than halfway through. For the instant changes it barely matters anyway: rotating or muting a multi-gigabyte file is still a matter of seconds, because no frame is ever decoded.
Which browsers does this work in?
Chrome, Edge and other Chromium browsers, plus Safari 18 and later. Firefox doesn't provide the WebCodecs video support this relies on, and the page detects that when it loads rather than failing after you've picked a file. Mobile browsers work on recent devices, though a long crop or resize is slow going on a phone.
Is my video uploaded anywhere?
No. There's no server involved at any point — the file is read locally, processed by your own device, and written back to local storage. That's also why there's no queue, no daily quota, no account and no watermark: there's no infrastructure cost to recover. Open the network panel while it runs and you'll see nothing leave.
Related reading
AskClean Team · Updated 2026-08-21