Choose and preview
Select the video from your device. The preview helps you decide whether the displayed picture is already correct or still needs a clockwise, counter-clockwise or 180-degree turn.
Repair incorrect phone orientation, choose your export quality, and download a fresh MP4. Your recording never leaves your device.
Start with the automatic option. If the preview is still wrong, choose the physical rotation that matches your footage.
Choose a file, preview it, then set the correct orientation and output.
The first run loads a local processing engine of about 31 MB. Keep this tab open. Large and long videos may work better in the desktop version.
Select the video from your device. The preview helps you decide whether the displayed picture is already correct or still needs a clockwise, counter-clockwise or 180-degree turn.
Keep source dimensions for the lightest conversion, or select 480p, 720p or 1080p. Choose frame rate, target bitrate and whether to preserve the original audio.
The FFmpeg engine runs inside the page and creates an MP4. Download it, play several parts, and keep your original until the result is safely verified.
The original desktop utility was built after a recorder saved correct landscape frames with the wrong -90° display instruction. The web version keeps that practical focus.
Flatten the way the browser displays the recording into fresh frames, or apply a specific physical rotation when the pixels themselves are sideways.
Resolution presets scale the picture proportionally and add padding when necessary instead of stretching people, gameplay or text.
Set a target bitrate and see a conservative estimate before starting. Higher numbers can preserve motion, but cannot invent missing detail.
Keep source FPS or choose a standard rate from 15 through 60 FPS. Raising FPS does not create motion that was never captured.
Preserve the source audio or mute the entire output. Audio that was never recorded cannot be restored by changing video settings.
The file is read into browser memory, processed locally and offered as a local download. It is not posted to the website server.
The web tool is excellent for short and medium recordings. A desktop FFmpeg workflow remains the safer choice for multi-gigabyte files, long sessions, batch processing and hardware-accelerated exports.
| Need | Browser tool | Desktop FFmpeg |
|---|---|---|
| No installation | Best choice | Requires setup |
| File stays local | Yes | Yes |
| Short phone clips | Ideal | Also works |
| Multi-gigabyte recording | May exceed memory | Recommended |
| Batch and hardware encoding | Not available | Recommended |
Original explanations based on the same orientation, size and quality problems the desktop utility was built to solve.
Understand what “processed locally” means and when a desktop converter is the better tool.
Read guideUse the fewest transformations, keep aspect ratio, and avoid repeated lossy exports.
Read guideA practical guide to balancing detail, file size, upload speed and resolution.
Read guideNo. The selected file is processed inside your browser. WordPress receives normal page requests, but the video file itself is not submitted to this website or a cloud conversion API.
Either the frame pixels are stored sideways, or the file contains a rotation/display-matrix instruction that a player interprets incorrectly. The preview and explicit rotation options help you correct either case.
The page loads the local FFmpeg WebAssembly engine, which is about 31 MB, before processing. It is then cached by the browser where normal cache rules allow.
Not when both are mixed into the same audio track. Muting removes all sound. Specialist source separation can sometimes reduce music, but results vary and may leave artifacts.
No. If the microphone or internal audio was not captured, changing video metadata cannot reconstruct it. You would need to add a new voice-over or other replacement audio.
The browser may need memory for the source, processing workspace and finished output simultaneously. Very long or multi-gigabyte files are better handled with the desktop application or a native FFmpeg command.
No. Upscaling can create a standard 1080p frame, but it cannot reveal detail that the source did not contain. It also increases processing time and may increase file size.