Rotate videos 90 or 180 degrees or flip the frame, processed entirely in your browser, files never uploaded.
Your video is rotated locally with FFmpeg running in your browser. Nothing is uploaded; the file never leaves your device. First use downloads the ~31 MB engine once. Files up to 200 MB.
A 90° rotation swaps width and height. The rotation is baked into the pixels, so the output displays the same way in every player.
Loading engine…
Sideways videos happen constantly: you hit record before the phone's orientation sensor settled, the camera was mounted upside down, or an exported file ignores the rotation flag other players respect. The fix is the same every time: rotate 90° clockwise or counter-clockwise, spin 180° for upside-down footage, or mirror the frame with a horizontal or vertical flip (handy for un-mirroring webcam recordings or matching which way a subject faces across cuts).
This tool bakes the transformation into the pixels: every frame is re-encoded with FFmpeg's transpose and flip filters, so the result displays identically in every player, editor, and platform; there is no metadata flag involved that a given app might ignore. A 90° rotation swaps width and height, and 180° is applied as two chained 90° rotations. The audio track is copied without re-encoding, so sound quality is untouched.
One container caveat: the output keeps your source's file extension, and rotation re-encodes to H.264, a codec the WebM container refuses. If you start from a .webm file, run it through the Video Converter to MP4 first. For related fixes, the Video Muter strips audio and the Video Trimmer shortens the clip.
Yes, rotating the output 90° in the opposite direction restores the original orientation, and both flips are their own inverse. But every pass re-encodes and slightly degrades quality, so it is always better to go back to your original file and rotate that once, rather than rotating a rotation.
Rotation re-encodes the video to H.264, and the WebM container only accepts VP8, VP9, or AV1 video, so FFmpeg refuses to write the output. Convert the file to MP4 first with the Video Converter, then rotate the MP4; it keeps the same extension and codec without trouble.
Probably not. Phones typically store orientation as a metadata flag rather than rotated pixels, and most (but not all) apps honor it. If a clip appears sideways somewhere specific, this tool fixes it permanently by baking the rotation into the frames, so every player shows it the same way.
One re-encode at CRF 23 is visually negligible for typical footage, and a 90° rotation only swaps width and height; no pixels are added or removed. File size may shift slightly in either direction; rotating the same clip repeatedly compounds quality loss, so always start from the original.
Every single frame is decoded, transformed, and re-encoded inside your browser via WebAssembly, which is considerably slower than a native desktop encoder. Files up to 200 MB are accepted, but long, high-resolution clips can exhaust browser memory on machines with little RAM; trim first if you only need part of the footage.