Key takeaways
- Phones store sensor-native pixels (landscape) plus an EXIF orientation tag; the sideways photo is the file with a note that some viewer failed to read.
- The permanent fix is baking: rotate the pixels to the way the photo should look, which makes orientation correct everywhere including the apps that never read tags.
- Baking orientation into a lossy JPEG means one re-encode — do it at quality 95+ or from the HEIC/original, and the loss is invisible.
- Batch the whole library: mixed orientations are a per-file accident of how the shutter was grabbed; one pass with the rotate tool's auto-orientation normalises everything.
- Auto-rotate on upload sites uses the same tag — which is why the same photo is right in the preview and wrong in the published post when the site reads the tag for preview but strips it on save.
What Is Actually Happening
Camera sensors are landscape. When you hold the phone vertically, the sensor still records a sideways rectangle — and rather than spending milliseconds rotating every pixel before the screen even shows the photo, the phone writes the raw pixels plus a tag: Orientation = 6 (right), 8 (left), 3 (upside down). Correct apps check the tag and rotate at render time, and the system gallery is not the only one — Chrome, Outlook and the Windows Photos app all honour it.
The failure cases: a website's uploader that resizes the raw pixels (the tag survives, the resize ignores it — and the server bakes the wrong orientation in), a document or PDF pipeline that treats the JPEG pixels as truth, a custom app with its own viewer that never learned about the tag. Which is exactly the point of this guide: the tag is a promise; baking rotation is a fact. The permanent fix for anything destined for other people's pipelines is pixels that need no instructions — the EXIF data guide covers the orientation tag in full.
The One-Click Bake
Open the rotate tool, load the photo, and the tool's own read of the orientation shows it the way it should look — apply the rotation and download. What just happened: the pixels moved into the upright position and the now-pointless orientation tag resets to normal. Every viewer, competent or not, agrees.
The lossy-JPEG note: a quality-preserving rotation exists (the exact-90° JPEG-transform trick that moves blocks rather than decoding) but the honest universal fix is decode-rotate-re-encode. At quality 95+ from the original it is invisible; the real mistake is doing the rotation on a file that has already been through three re-encodes. Rotate once from the master.
Batch: Normalising a Mixed Library
Orientation chaos is a library-wide phenomenon: a family album copied from two phones and a compact camera has files from four rotations, and the tag-respecting viewers hide the mess while the tag-ignoring ones (that new CMS, the photo-frame app, the print kiosk) surface it. The fix is the batch: up to 20 files per pass, apply the read-orientation-and-bake step, and the whole set becomes viewer-independent.
The same batch handles the deliberate case: a folder where everything shot sideways because the camera was mounted that way — a 90° rotation across the set, one setting, done.
The Weird Edge Cases
Rotated screenshots: nonexistent on phones (they render at the target orientation), common on rotated-monitor desktop captures where the OS rotates the buffer and gets it wrong — same fix, and the metadata check (pixel dimensions vs what you see) tells you which file is lying.
Windows File Explorer has a rotate button that rotates the preview and writes the tag on some Windows builds and rotates pixels on others — a design accident that makes files inconsistent across versions; use the tool with the explicit behaviour instead of the shell's guess.
iPhone's edit-and-rotate: the phone applies rotation to the display pipeline, and a copied original can arrive on the PC with the tag still not baked — the silent source of the 'it looks right on my phone, wrong on my PC' report, and one more argument for baking on the way out of the phone's orbit.
Panoramas: shot in one direction, and the 'wrong' orientation may be exactly the long axis the stitcher chose; the fix is the same rotate, the diagnosis is that 'sideways' for a panorama is a different question than for a portrait.
Preventing the Next Round
Once the library is normalised, keeping it that way takes one habit: anything leaving the phone toward an unknown pipeline goes through a converter or the share sheet, both of which bake orientation on the way out. The gallery keeps the originals; the world gets the upright versions.
And the meta-note: this whole class of bug exists because a 1996 camera-file field (EXIF orientation) solved a speed problem and created an agreement problem. It still solves it — the tag costs nothing and every modern viewer on your own devices reads it correctly; the moment files leave your controlled environment, pixels-only is the format that survives contact with strangers.
Frequently asked questions
The questions people ask most about why photos are sideways (and how to fix rotation permanently), answered directly.