The file may rely on an orientation tag
Many cameras store the pixels in the sensor's native orientation and add an EXIF tag that tells software how to display them. Applications that honor the tag show the expected view. Software that ignores or removes it may display the stored pixel arrangement instead, causing the same file to appear differently.
Why applications disagree
Support for EXIF orientation varies. Galleries and current browsers generally handle it, while some viewers, upload systems, email workflows, or image processors may ignore the tag or remove it during resizing and conversion. Once the tag is gone, the stored pixel orientation determines what appears on screen.
Metadata changes and pixel rotation are different
- Metadata-only rotation. Some tools change the EXIF flag without touching the actual pixel data. This is fast, but it only works reliably in software that respects the flag; anywhere that ignores it, the photo is right back to looking sideways.
- Actual pixel rotation. A proper rotate tool physically re-renders the image data in the new orientation and saves it that way. The photo now looks correct in absolutely everything, regardless of whether the viewing software reads EXIF data or not, because there's no flag to ignore: the pixels themselves are oriented correctly.
Changing only the orientation tag still depends on every later application reading that metadata. Rotating the image content and exporting it in the intended orientation removes that dependency for the new file.
Upside-down photos work the same way
The same explanation applies to a 180-degree inversion. Normalize the image content and export a corrected copy rather than relying only on a display instruction.
How to fix it permanently
Choose 90 degrees left, 90 degrees right, or 180 degrees, inspect the preview, and export a corrected copy. The new file should store the image content in the intended orientation instead of depending on the original EXIF tag.
How to recognize an orientation-tag problem
If the image is upright in one application and sideways in another, inconsistent handling of the orientation tag is likely. If every application shows the same incorrect orientation, the stored content may already be rotated that way. Exporting a normalized copy addresses both cases.
Questions about rotating photos
Why can the same file look different? Applications may interpret or discard the EXIF orientation tag differently.
Does rotation reduce quality? The geometric rotation itself does not require interpolation at 90 or 180 degrees, but exporting a JPG may re-encode it and introduce a small amount of compression loss. The result depends on the tool and output format.
Will existing uploads update automatically? No. The correction applies to the new file; replace copies already uploaded or sent where possible.
Fix a sideways photo permanently
Rotate the image content and export a normalized copy that does not depend on the original orientation tag. Orisod processes the photo locally in your browser.
Rotate an image →Save the corrected file and test it in the application where the problem appeared. That verifies the orientation is now stored as expected rather than merely displayed correctly in one viewer.