A video can look sideways for two very different reasons. The actual frame pixels may be portrait, or the pixels may already be landscape while a metadata instruction tells the player to rotate them again. Treating both problems the same can waste hours and reduce quality.
Pixels versus instructions
A phone sensor records a rectangular grid of pixels. The file can also carry a rotation value or display matrix. Modern players read that instruction and rotate the image during playback without changing the underlying frames. Problems begin when a recorder writes the wrong instruction, an editor ignores it, or a converter preserves a flag that no longer matches the pixels.
How to choose a fix
If the image is correct in a player that ignores metadata but wrong elsewhere, normalizing the orientation flag may be enough. If the pixels themselves are sideways, the frames must be rotated and re-encoded. Preview the file first and keep the original.
Why unnecessary re-encoding matters
Every lossy encode can soften text, introduce blocks and take significant time. A metadata-only repair is faster and usually lossless, but it only applies when the underlying frame orientation is already correct. The web fixer offers an automatic normalize option and explicit clockwise, counter-clockwise and 180-degree choices for cases that need physical rotation.