Why Is My Video Sideways After Transferring?
The clip is upright on your phone and sideways everywhere else. The rotation is a flag in the container, not in the pixels, and here is how to bake it in properly.
Your video is sideways because the rotation was never in the picture. When a phone records in portrait, the sensor writes the frames in its own landscape orientation and stores a rotation flag in the container's metadata saying "display this turned 90 degrees" — your camera app and gallery read that flag, and a TV, an older desktop player, a browser upload preview or a different operating system may ignore it entirely. Nothing corrupted on the way across. The pixels are exactly as they always were; the instruction to turn them stopped being read.
Making it upright everywhere means re-encoding the video so the frames themselves are rotated and the flag is cleared. On a phone, Convertlix for Android (8.0 or later) does that on the device: the file is opened through Android's own file picker, converted locally, and written to Downloads. Nothing is uploaded and there is no server copy — its network calls carry sign-in, licence, quota and payment traffic, never media. Sign-in is required once and there is no guest mode; after that the tools work with the network off. Free-tier videos are capped at 100 MB per file, Premium at 2 GB, and the monthly conversion allowance is server-set and shown in the app.
The video was never wrong
You are not imagining the inconsistency, and it is genuinely maddening: the same file, upright in your gallery and sideways in the thing you sent it to. Both are behaving correctly according to their own rules. One reads a piece of metadata; the other does not.
Phone camera sensors are physically mounted in one orientation, normally landscape. Turn the phone to portrait and the sensor does not turn — the app records the same landscape frames and writes a note. In an MP4 or MOV that note is a 3×3 transformation matrix in the container's tkhd box, on the video track. The common values encode 0, 90, 180 or 270 degrees.
Honouring that matrix is optional in practice. Modern Android and iOS players, VLC, Chrome, Firefox and Safari read it. What often does not: some smart-TV apps, older desktop players, hardware media players, many web upload previews, a lot of server-side video pipelines, and several editing tools that import the frames without the metadata. Rotation flags in MP4 were also widely ignored for years, so any player written to an older spec assumption may skip it.
There is a second, related trap. Photos use a completely separate mechanism — the EXIF Orientation tag — and it has exactly the same failure mode, which is why sideways photos and sideways videos feel like one problem and are two.
The part you can fix is the file: the frames can be rotated for real, and then no player needs to cooperate. The part you cannot fix is other people's players. If a TV app ignores rotation metadata, no amount of setting the flag correctly will help — which is precisely the argument for baking it in.
Why re-uploading makes it worse
The instinct when a platform shows your video sideways is to rotate it in some app and upload it again. That is often how you end up with a video that is sideways in a new way.
Here is the mechanism. Many "rotate" features do not touch the pixels at all — they flip the rotation flag from 90 to 0, or from 0 to 270. If the platform that displayed it sideways was ignoring the flag, changing the flag changes nothing there, but it now changes what every compliant player does. The result is upright on the platform and sideways in your gallery, or upside down in both.
Compounding it is worse. Rotate a flag to compensate for one player, then have a second tool bake in the rotation from the flag it now finds, and you get 180 degrees of error. Each pass through a re-encode also costs a generation of picture quality, so three rounds of "let me just try rotating it again" leave you with a softer file that is still wrong somewhere.
There is a third way to lose. Some upload pipelines strip metadata on ingest — for privacy or normalisation — so a correctly flagged file arrives flagless and defaults to the sensor's landscape frames. You cannot fix that by adjusting the flag, because the flag is being discarded.
| Approach | What changes | Where it works | What you lose |
|---|---|---|---|
| Change the rotation flag | The metadata only; the frames are untouched | Only in players that read the flag | Nothing in quality, but it fails on the players that caused the problem |
| Re-encode with rotation applied | The pixels are genuinely turned; the flag is cleared | Everywhere, including players that ignore metadata | One generation of picture quality, plus processing time |
| Rotate in the destination app | Whatever that app stores, usually its own copy | That app only | Nothing, if nothing else ever plays the file |
| Re-upload after a flag change | Often nothing useful, sometimes the orientation twice | Unpredictable | Quality per pass, and time |
| Strip all metadata | Removes the flag entirely | Nowhere — this makes it worse | The orientation instruction |
The permanent fix, stated honestly
Baking rotation in means decoding every frame, turning it, and encoding it again. That is a real re-encode: it costs one generation of quality, it costs battery and time, and a phone doing it to a long 4K clip is slow. It is not a metadata edit and no tool can make it one — rotating actual pixels requires touching actual pixels.
What you get for that cost is a file that needs no cooperation from any player, because there is nothing left to interpret. For a video going to a TV, a client, a submission portal or a platform that strips metadata, that is the outcome worth paying for.
Two related notes. Metadata is also where location and device details live, and stripping those is a separate deliberate act — Remove GPS and EXIF Data From Photos covers that for images. And if the same file also refuses to scrub when you cast it, that is a different metadata problem with a different fix: Downloaded Video Won't Seek on Your TV? The Fix.
How to fix a video that plays sideways
- Establish which way the file really is. Play it in your gallery, in VLC, and in Chrome by opening the local file. Upright in some and sideways in others means the frames are landscape with a rotation flag — the normal case. Sideways in all three means the frames themselves need turning, in the same direction, everywhere.
- Note which direction it needs to turn, once. Write it down. Most compounding errors come from guessing again on the second attempt.
- Stop rotating and re-uploading. Each flag change makes the file behave differently in compliant players without helping the one that ignores flags, and each re-encode costs quality.
- Check the size. Long-press the file. Over 100 MB is above the free per-video ceiling, so trim it first or use Premium, which takes files up to 2 GB.
- Re-encode from the original file. In Convertlix that is Video Converter, which takes MP4, MKV, MOV or AVI, writes MP4, MKV or MOV, and can trim. Work from the source, not from a copy you already rotated once, so you pay for one generation rather than three.
- Test the new file where it failed. The TV app, the upload form, the other person's computer — not just your own gallery, which was reading the flag correctly the whole time.
- For a long 4K clip, use a computer. ffmpeg's
transposefilter or HandBrake's rotation option will do it faster, and for a 2 GB file that difference is large.
When this will not work
A file whose frames were genuinely recorded upside down — some action cameras mounted inverted — is a different case, and while 180 degrees is still a rotation, some cameras write no flag at all so nothing is being ignored. Videos over 100 MB are refused on the free tier, so a 45-minute 4K recording will not convert on a free account until you trim it or move to Premium. DRM-protected downloads are encrypted and nothing here opens them. If a platform strips metadata and re-encodes on ingest, test one short clip before committing a long one, because their pipeline has the last word. And if the source is a stitched or fisheye clip from a 360 camera, its projection metadata matters more than its rotation flag, and a general converter is the wrong tool.
FAQ
Why does my video look fine on my phone but sideways on my computer?
Because your phone recorded landscape frames plus a rotation flag in the container metadata, and the two players disagree about whether to read it. Your gallery reads the flag and turns the picture for display; an older desktop player, a TV app or a web upload preview may ignore it and show the frames as stored. The file is not damaged — the instruction to rotate simply is not being honoured on the second device.
Does rotating a video reduce its quality?
Changing the rotation flag does not, because the pixels are never touched — but it also only helps in players that read the flag, which are the ones that were already showing it correctly. Actually turning the frames requires decoding and re-encoding the video, which costs one generation of quality and takes real processing time. That is the trade for a file that is upright in every player.
Why did rotating and re-uploading make it worse?
Many rotate features only change the metadata flag rather than the frames. The platform that showed your video sideways was ignoring that flag, so nothing improved there, while every compliant player now turns the picture by a new amount — giving you upright in one place and sideways or upside down in another. Baking the rotation into the pixels and clearing the flag avoids that whole class of confusion.
How do I permanently fix the orientation so every player agrees?
Re-encode the video with the rotation applied to the frames themselves, which leaves no metadata for a player to interpret or ignore. On a phone, a video converter that re-encodes will do this; on a computer, ffmpeg's transpose filter or HandBrake's rotation setting is faster and better suited to large files. Work from the original file rather than a copy you have already rotated, so you only pay one generation of quality.
Is this the same problem as sideways photos?
It is the same idea with different plumbing. Photos store orientation in the EXIF Orientation tag; videos store it as a transformation matrix in the container's track header. Both are instructions a viewer can honour or ignore, and both are fixed permanently by rewriting the actual pixels rather than the tag.
Does Convertlix upload my video?
No. The video is opened through Android's own file picker, re-encoded on the phone itself, and the result is written to Downloads, so nothing is transmitted and there is no server copy to retain. The app's network calls carry sign-in, licence, quota, configuration and payment data only, and it asks for no storage permission. Sign in once, turn on airplane mode, and the conversion still completes.
If the clip is upright in your gallery and sideways everywhere else, the flag is the problem and not the picture — Video Converter turns the frames themselves on the phone and leaves the original file untouched.