Recorded Video Sideways in One Player but Normal in Another? Rotation Metadata, Player Handling & Remux Diagnosis Guide

Key takeaways: A file that plays sideways in one player and upright in another is usually a rotation instruction that one player follows and the other ignores, not a damaged file. Read the Rotation value, compare the same file across players, then decide between changing the instruction and baking the rotation into the pixels so it holds in every player.
The same recording plays upright in one player and sideways in another. In the first player the picture is the right way up, the people stand on their feet, and nothing looks wrong. In the second player the whole picture is turned on its side, and the viewer has to tilt their head to make sense of it. Nothing about the file has changed between the two playbacks: it is the same file, on the same machine or on two machines, with the same picture and the same sound. The difference is in how each player reads the file.
The first instinct is often to call the file damaged, to re-record the scene, or to turn the monitor on its side. None of those steps addresses the cause, because the cause is usually an instruction written inside the file that one player follows and the other ignores. A phone camera does not turn its sensor when the phone is turned. It records the picture in the sensor's own fixed orientation and writes a note inside the file saying which way the picture should be turned before it is shown. A player that reads the note turns the picture upright; a player that does not shows the stored pixels exactly as recorded, and a portrait recording appears sideways.
This guide treats that disagreement between players as the evidence itself. Two players giving two different answers about the same file proves that the pixels are intact: if the pixels were damaged, every player would show the same damage. The diagnosis therefore asks which players follow the instruction and which do not, reads the instruction itself in the form of the Rotation value, and then chooses between two different repairs — changing the instruction, or baking the rotation into the pixels — according to which one the evidence supports. The two repairs are not interchangeable, and choosing the wrong one is the most common reason the problem comes back on a different player.
Rotation in this guide means a turn of 90 degrees, and the upside-down case means a turn of 180 degrees, and both are covered here. A recording made with the phone held upright is usually a 90-degree case. A recording made with the phone held upside down is a 180-degree case, and it needs a 180-degree repair, not a 90-degree one. The two must never be treated as the same fault, because a 90-degree repair applied to a 180-degree recording leaves the picture sideways in a different direction.
What shape is this article about?
This article covers only a narrow shape, and five conditions must all hold. First, the subject is one and the same recording file: the same file, the same recording, not two different files and not two versions of the same scene recorded at different times. The file name, the file size, and the duration must match between the two playbacks. Second, two players disagree about the direction of that one file: one plays it sideways and the other plays it upright. If both players play it sideways, the pixels themselves are sideways, and that is a different path. If both players play it upright, there is no fault at all. Third, the file opens and plays to the end, and the picture and the sound are themselves normal apart from the direction. A file that will not open or will not play is a different class of fault. Fourth, the two players must be named, with their versions and the machines they run on: VLC against a system player, a phone gallery against a computer player, or an editor against a player, for example. Without the player names, the comparison cannot be made. Fifth, the source of the file must be stated: recorded directly on a phone, recorded on a camera, recorded with screen-recording software, or produced as an editor export. The source decides whether a rotation instruction exists at all and in which layer it was written.
Several neighbouring shapes look similar and must not be confused with this one. A picture that is wrong only on a second monitor, while it is right on the main monitor, belongs to the guide on a portrait second monitor, identified in this library as article 512, which compares two screens rather than two players and hands the file and player layer to this guide. A graphics card fan that spins, rattles, or stops belongs to the fan guides, identified as articles 119, 351, and 353, which are about hardware fan rotation, not about the direction of a video picture. A picture with black bars that does not fill the screen belongs to the aspect-ratio guide, identified as article 329, where the direction is correct and only the proportions are wrong. A boot screen that renders at low resolution with stretched text belongs to the firmware-output guide, identified as article 404, which is not about a recording file at all. Each of those guides asks a different question, and a step taken from one of them will not diagnose the disagreement between two players over one file.
The shape also excludes several situations that are easy to mistake for it. If every player plays the file sideways and the stored pixels themselves are sideways — a camera mounted sideways, a dash camera, or a fixed camera that genuinely recorded sideways — the fault is in the recording layer, not the player layer, and the only repair is to bake the rotation into the pixels, because there is no instruction to change. If the thumbnail is sideways but playback is upright, the thumbnail generator and the player are two different reading paths, and the file itself is not at fault; this guide is about playback, not thumbnails. If a picture is upside down and also mirrored, so that text reads backwards, that is a mirror flip, not a rotation, and turning it 180 degrees will not correct the mirror; a horizontal flip is the repair for that shape, and it is a different operation from rotation. If a file only turns sideways after upload to a platform, the platform may have stripped the rotation instruction during its own processing, and the local file must be checked first before the upload is blamed. If an editor shows the file sideways on import, some editor import paths do not follow the rotation instruction, and the handling is the same direction as for a player — baking the rotation into the pixels is the most reliable repair — but the fault is in the import path, and it must be named as such rather than written up as a broken player.
How it works: four layers from sensor to screen
A video file's direction is decided in four layers, and each layer must be understood separately, because the fault can sit in any one of them and the repair for one layer does nothing for another.
1. The sensor does not turn; it writes down how the phone was held
The image sensor inside a phone is fixed in one orientation inside the body, and it does not turn when the phone is turned from landscape to portrait or held upside down. When a video is recorded, the sensor always reads the picture out in the same orientation. To save work, the phone does not rotate every frame before writing it to the file. Instead it stores the picture in the sensor's own orientation and writes an instruction inside the file: turn the picture by a given angle before showing it. That instruction is the rotation metadata, and the whole of this guide turns on whether a given player reads it.
A phone held upright for a portrait recording most commonly produces a Rotation value of 90 degrees: the pixels are stored as a landscape frame 1920 by 1080, and the displayed picture is a portrait frame 1080 by 1920. A phone held upside down can produce 180 degrees: the picture is upside down. A value of 270 degrees is the portrait direction the other way around. A phone held in landscape usually produces a Rotation value of 0 degrees, or no Rotation field at all, because the stored pixels are already in the correct direction.
2. Where the instruction lives: the display matrix in MP4 and MOV files
In MP4 and MOV files, the rotation instruction is not a single standalone angle number. It is written as a display matrix in the header of the video track: a set of numbers that tells the player how to transform the picture after decoding and before showing it. Many tools simplify that matrix into a single rotation angle of 0, 90, 180, or 270 degrees, and that simplified angle is what the reader sees in the diagnostic tools below.
MediaInfo shows the value in the Rotation field of the video track details, as 0, 90, 180, or 270 degrees. The ffprobe tool that ships with FFmpeg shows it as a rotate tag, for example rotate 90, together with displaymatrix side data. A phone recording measured on a Samsung S9 showed Rotation 90 with stored dimensions of 1920 by 1080, the stored landscape frame, not the displayed portrait frame. MediaInfo may show the displayed size of 1080 by 1920 for the same file, because the display size is calculated after the rotation instruction is applied. The stored size and the displayed size are two different numbers, and the Rotation value is what connects them.
3. Whether a player follows the instruction is the player's own decision
The rotation instruction is a request, not a command. Each player can choose to follow it or not, and the choice is made by the player, not by the file. Players that follow the instruction — VLC, a phone gallery, QuickTime, and modern browsers are examples — decode the picture and then turn it upright according to the display matrix before showing it, so a portrait recording looks normal. Players that do not follow the instruction — some older system players, some simple players, some televisions and projectors, and some editor import paths — draw the stored pixels exactly as they are, and a portrait recording appears sideways.
This boundary is the single most important sentence in the whole guide: the same file playing upright in one player and sideways in another proves that the pixels themselves are not at fault, and that the fault is in the player that does not follow the rotation instruction. Writing "one player plays it sideways" as "the file is broken" is a misconception, and it leads directly to the wrong repair.
Which players follow the instruction and which do not changes with versions, and the sources disagree about particular players. One source states that the Windows 8 version of Windows Media Player recognised the direction of an iPhone MOV file, while a guide dated 2026 describes Windows Media Player as a long-standing example of a player that does not follow the instruction. The two statements cannot both be treated as settled fact for every version, and this guide does not state any player's behaviour as a fixed fact. The behaviour of a named player must be established by the comparison test in the diagnostic steps, not assumed from a general claim.
4. Two repairs: change the instruction, or bake the rotation into the pixels
There are two different repairs, and they do different things. The first is remuxing, or rewriting the flag: only the rotation instruction in the file header is changed, and the pixel data is not touched. It is fast, it loses no quality, and the file size does not change. An FFmpeg example is to copy the streams and set the rotation metadata for the video stream to zero. But the repaired file still depends on the player following the instruction: a player that does not follow instructions will still play the changed file sideways. The second repair is re-encoding, or baking the rotation into the pixels: the rotation is applied to every frame, the picture is compressed again, and the result is a file whose stored pixels are already in the correct direction and which carries no rotation instruction. An FFmpeg example is to use the transpose filter for a 90-degree clockwise turn, with a different transpose value for a counter-clockwise turn, and two transpose operations for 180 degrees, while copying the audio stream without re-encoding it. This repair is slower and loses a small amount of quality through recompression, but the result is correct in every player, because it no longer depends on any player following an instruction.
One trap must be understood before either repair is attempted: the double-rotation trap. If a file already carries a rotate instruction of 90 degrees, and the transpose filter is applied for another 90 degrees, FFmpeg by default first follows the instruction and turns the picture once, and then the manual transpose turns it a second time, so the result is turned 180 degrees. The correct procedure is to check the rotate value with ffprobe first, and to switch off automatic rotation with the noautorotate option when applying the manual turn, so that the manual turn is the only turn applied. After any repair, the Rotation value must be checked again with MediaInfo or ffprobe, to confirm that it reads zero or the intended value.
| Layer | What it is | What goes wrong | How it is read |
|---|---|---|---|
| Sensor and recording | Fixed sensor orientation, instruction written at recording time | Portrait recording stored as landscape pixels | Rotation value in the file |
| Display matrix | Instruction in the video track header of MP4 and MOV files | Instruction missing, zero, or wrong | MediaInfo Rotation field, ffprobe rotate tag |
| Player handling | Each player chooses whether to follow the instruction | One player follows it, another ignores it | Same file played in two or more players |
| Repair: flag change | Remux, instruction only, pixels untouched | Still depends on the player following the instruction | Rotation value after remux, playback in the player that was sideways |
| Repair: bake into pixels | Re-encode, rotation applied to every frame | Slower, small quality loss from recompression | Rotation value cleared, playback in every player |
Rotation and mirror are not the same operation
Rotation turns the whole picture around: text stays readable, because the letters themselves are turned with the picture. A mirror flip turns the picture over horizontally: text reads backwards, because each letter is reversed. A 180-degree rotation will not correct a mirrored picture, and a horizontal flip will not correct a sideways picture. The two repairs are different operations, and the reader must decide which one the picture needs by looking at whether the text is readable but sideways, which is rotation, or readable in direction but reversed, which is mirror. This guide covers rotation; mirror is named here only so that it is not mistaken for rotation.
Diagnostic steps: five tests in order
The order below matters, because each step narrows the fault before the next step is attempted. Work on a copy of the file, never on the original, and write down every result before moving on: the player names and versions, which player was sideways and which was upright, the Rotation value, and the direction and angle of the sideways picture, clockwise or counter-clockwise, and 90 degrees or upside down.
Step 1 — Confirm the shape and write down the baseline
Confirm that it is one and the same file in both players, with the file name, file size, and duration matching. Confirm that one player plays it sideways and the other plays it upright, and note which is which. Write down the source of the file — phone recording, camera, screen recording, or editor export — and the names and versions of the two players and the machines they run on. Note the angle as well: is the picture turned 90 degrees to one side, or is it upside down at 180 degrees, and if 90 degrees, is it clockwise or counter-clockwise? The repair depends on that angle, and a repair chosen without it is a guess.
Step 2 — Compare the same file across players
This is the first decisive test. Play the same file in VLC, in the native player — the phone gallery, Windows Media Player, or QuickTime — and in an editor, one after another, and write down for each one whether the picture is sideways or upright. The pattern of answers is the diagnosis.
If some players are sideways and others are upright, the pixels are not at fault, and the fault is in the player that does not follow the instruction. The diagnosis goes to Step 3 to read the Rotation value. If every player plays the file sideways, the pixels themselves are stored sideways, or the rotation instruction itself is wrong or missing, and the diagnosis still goes to Step 3 to read the value. If every player plays the file upright, there is no fault in playback at all, and the earlier sideways view was probably in a thumbnail or preview layer rather than in playback, which is a boundary case listed below.
The comparison must be made with the same file, not with a second copy or a re-export, because a re-export may have written a different instruction or none at all. If the file was copied between machines, confirm the copy by file size and duration before comparing.
Step 3 — Read the Rotation field in MediaInfo
Open the file in MediaInfo and read the Rotation field in the video track details. The value itself is the evidence, and each value points at a different shape.
| Rotation value | What it means | What to do next |
|---|---|---|
| 90 or 270 | Standard portrait recording: pixels stored landscape, instruction says turn 90 degrees | Go to Step 4; the repair is a 90-degree turn |
| 180 | Upside-down recording: the phone was held upside down | Go to Step 4; the repair is a 180-degree turn, not a 90-degree turn |
| 0, or no Rotation field | No instruction, or instruction says no turn | If every player is sideways, the pixels themselves are sideways; only baking the rotation into the pixels will repair it |
| Value does not match the picture | The instruction itself is wrong, for example Rotation 90 with an upside-down picture | The fault is in the instruction, not the player; rewrite the instruction or bake the correct turn into the pixels |
A Rotation value of 90 or 270 with a player that plays the file sideways is the standard portrait-recording shape: the pixels are stored landscape, the instruction says to turn them, and the player that ignores the instruction shows them sideways. A Rotation value of 180 with an upside-down picture is the upside-down recording shape, and it must be repaired by 180 degrees: turning it 90 degrees would leave it sideways in a different direction. A Rotation value of 0, or no Rotation field at all, with every player showing the picture sideways, means the pixels themselves are sideways — a camera that genuinely recorded sideways, for example — and changing a flag will do nothing, because there is no flag to change or the flag already says no turn. A Rotation value that does not match the picture, for example Rotation 90 on a file that is upside down, means the instruction itself was written wrongly, and the repair must correct the instruction or bake the correct turn into the pixels.
The ffprobe reading can be used to confirm the MediaInfo reading: the rotate tag and the displaymatrix side data should agree with the Rotation field. If they disagree, write both readings down and trust the playback comparison in Step 2 as the deciding evidence, because the players are the final readers of the instruction.
Step 4 — Compare a flag change against baking the rotation into the pixels
Work on a copy, and try the flag change first, because it is fast and loses no quality. Rewrite the rotation flag by remuxing — copying the streams and setting the rotation metadata — and then play the changed file in the player that was sideways. If it now plays upright, the flag repair is complete for that player, but the reader must be told plainly that the repair still depends on the player following the instruction, and that an older player may still show it sideways. If the changed file is still sideways in that player, the flag change was not enough, and the diagnosis moves to baking the rotation into the pixels.
Baking the rotation into the pixels means re-encoding with a transpose filter: a 90-degree clockwise turn for one direction, a counter-clockwise turn for the other, and two transpose operations for 180 degrees, while the audio stream is copied without re-encoding. Before applying the transpose, check the rotate value with ffprobe and switch off automatic rotation with the noautorotate option, so that the manual turn is the only turn applied and the double-rotation trap is avoided. After the re-encode, check the Rotation value again with MediaInfo or ffprobe to confirm that it has been cleared or set to the intended value, and then play the new file in every player used in Step 2. When the picture is upright in all of them, the repair is complete, and it is the most general repair, because it no longer depends on any player following an instruction.
The choice between the two repairs is a trade-off, and it must be stated as one. The flag change is fast, lossless, and leaves the file size unchanged, but it is not universal. Baking the rotation into the pixels is slower and loses a small amount of quality through recompression, but it is universal. A file that only ever needs to play in players that follow the instruction can be repaired with a flag change. A file that must play anywhere, including on players whose behaviour is unknown, must have the rotation baked into the pixels.
Step 5 — Verify the repaired file in three places
Play the repaired file in the player that was sideways, in the player that was upright, and on a phone, and confirm that it is upright in all three before calling the repair complete. Checking in one player only is not enough: the player that follows the instruction would have shown the original file upright as well, so a single-player check proves nothing. If the file is still sideways in any one of the three places, return to Step 3 and re-read the Rotation value, because the repair either did not apply or applied the wrong angle. Only when all three playbacks are upright is the repair finished.
Boundaries: what this article does not cover
A picture that is wrong only on a second monitor, while it is right on the main monitor, is article 512. That guide compares two screens, while this guide compares two players, and its boundary section hands the file and player layer to this guide. Graphics card fan rotation is articles 119, 351, and 353, which are about hardware fans, not about the direction of a video picture. A picture with black bars that does not fill the screen is article 329, where the direction is correct and only the proportions are wrong. A boot screen that renders at low resolution with stretched text is article 404, which is about firmware output, not about a recording file.
Several further situations sit outside this guide even though they feel close to it. If every player plays the file sideways and the stored pixels themselves are sideways, the fault is in the recording layer, and the only repair is to bake the rotation into the pixels, because changing a flag cannot help. If the thumbnail is sideways but playback is upright, the thumbnail generator and the player are two different reading paths, and the file itself is not at fault. If a picture is upside down and also mirrored, so that text reads backwards, that is a mirror flip, and turning it 180 degrees will not correct it; a horizontal flip is the repair for that shape. If a file only turns sideways after upload, some platforms strip the rotation instruction during their own processing, and the local file must be checked first. If an editor shows the file sideways on import, some editor import paths do not follow the rotation instruction, and baking the rotation into the pixels is the most reliable repair, but the fault must be named as an import-path fault rather than a broken player.
The behaviour of individual players by version was not verified for every player and version, and this guide does not state any player's behaviour as a fixed fact; the comparison test is the authority. The behaviour of individual editors on import was not verified either, and this guide states only that some editor import paths may not follow the instruction. Whether individual platforms strip the rotation instruction on upload was not verified platform by platform, and this guide states only that some platforms do. How often the 180-degree case occurs in practice was not measured, and this guide does not state whether it is common or rare. Any flag change must be verified afterwards with MediaInfo or ffprobe, as Step 4 requires.
Common misconceptions: seven claims that mislead
- "Sideways means the file is damaged." Wrong. The pixels are complete, the file plays to the end, and only the direction is wrong. Damage would not make two players disagree about the same file.
- "Record it again and it will be fine." Wrong. Re-recording does not change how the phone writes the instruction. The same phone held the same way will write the same instruction again.
- "Turn the monitor on its side." Wrong. Turning the monitor only moves the problem to the viewer's neck. The file will still play sideways everywhere else, and the monitor's own rotation setting belongs to the second-monitor guide, not to a file repair.
- "Changing the flag fixes it everywhere." Wrong. Changing the flag only changes the instruction, and a player that does not follow instructions will still play the file sideways. The universal repair is to bake the rotation into the pixels.
- "Turning it 90 degrees is always right." Wrong. An upside-down recording needs a 180-degree turn, and a 90-degree turn leaves it sideways in a different direction. The Rotation value must be read before the repair is chosen.
- "If VLC plays it upright, there is nothing wrong." Wrong. VLC follows the instruction, and that proves nothing about other players. The repaired file must be checked again in the player that was sideways.
- "Rotation and mirror are the same thing." Wrong. Rotation turns the whole picture, and text stays readable. A mirror flip reverses the picture horizontally, and text reads backwards. The two need different repairs.
FAQ
The same file plays sideways in one player and upright in another. Is the file damaged?
No. If the file opens, plays to the end, and the picture and sound are normal apart from the direction, the pixels are intact. Two players disagreeing about the same file proves that the fault is in how one of them reads the rotation instruction, not in the file's data. Read the Rotation value in MediaInfo, compare the file across players, and choose the repair from that evidence.
How do I find out what angle the file needs?
Read the Rotation field in MediaInfo. A value of 90 or 270 means a portrait recording that needs a 90-degree turn. A value of 180 means an upside-down recording that needs a 180-degree turn. A value of 0, or no Rotation field at all, with every player showing the picture sideways, means the pixels themselves are sideways and the rotation must be baked into the pixels. A value that does not match the picture means the instruction itself was written wrongly.
I changed the rotation flag and the file is still sideways in one player. Why?
Because changing the flag only changes the instruction, and that player does not follow the instruction. The flag repair depends on the player reading it. Bake the rotation into the pixels instead: re-encode with a transpose filter so the stored pixels are already in the correct direction, and check the Rotation value afterwards to confirm it has been cleared. The baked file plays upright in every player.
My video is upside down, not sideways. Is the repair the same?
No. An upside-down picture is a 180-degree case, and it needs a 180-degree turn, not a 90-degree turn. Turning an upside-down recording by 90 degrees leaves it sideways in a different direction. Read the Rotation value first: if it is 180, apply two transpose operations or the equivalent 180-degree turn, and verify the result in the player that was upside down as well as in the player that was upright.
Why does the file look fine on my phone but sideways on my computer?
Because the phone gallery follows the rotation instruction and the computer player in question does not. The phone turns the picture upright according to the display matrix before showing it, while the other player draws the stored pixels as they are. The difference is in the players, not in the file, and the repair that works everywhere is to bake the rotation into the pixels.
I applied a transpose filter and the picture ended up turned the wrong way. What happened?
That is the double-rotation trap. The file already carried a rotation instruction, and the encoder first followed that instruction and turned the picture once, and then the manual transpose turned it a second time, so the result was turned twice. Check the rotate value with ffprobe first, switch off automatic rotation with the noautorotate option when applying the manual turn, and check the Rotation value again after the re-encode to confirm the result.
If the fault still cannot be divided
Write down the file name, file size, and duration, the names and versions of the two players and which one was sideways, the Rotation value read in MediaInfo, whether the picture is turned 90 degrees or upside down at 180 degrees, and the result of playing the repaired copy in each player, and bring that written record with a copy of the file, keeping the original unchanged. Bring the written record described above to Room 1209, Dali Plaza, Shek Mun for inspection. The telephone number is 2186 8010 and WhatsApp is 6558 6806. There is no Mong Kok shop, and there is no on-site service. The site's published three-tier fee is HK$400–780, HK$480–1,380, and HK$680–2,800, an overall range of HK$400–2,800, with the actual fee quoted after inspection.