Photo orientation troubleshooting
How to fix a JPG that turns sideways after HEIC conversion
A photo can store camera pixels in one direction and an orientation instruction that tells apps how to display them. If a workflow ignores or drops that instruction, the JPG may rotate 90 or 180 degrees. Verify where the rotation first appears, flatten the correct view, and keep the HEIC original.
Locate the rotation
Find out whether the source, converter, or destination shows the wrong direction
Orientation problems are viewer-dependent. The same file can look upright in Photos, sideways in a legacy program, and upright again in a browser. Record the first point where the display changes before applying a fix.
The HEIC is upright but the downloaded JPG is sideways everywhere
The conversion or pre-export path probably did not bake the intended orientation into the pixel layout. Make a corrected rendered copy from a trusted viewer rather than rotating the original camera file.
The JPG is upright in a browser but sideways in one app
That application may ignore or misread orientation information. Test a current browser and another modern image viewer before changing a file that is already correct for most destinations.
A website rotates the JPG only after upload
The destination may strip metadata or generate a thumbnail without applying orientation first. A flattened JPG whose stored pixels are already upright is more reliable than depending on the site to honor a display instruction.
Portrait batches contain mixed rotations
Photos captured with different device positions can carry different orientation states. A single bulk rotate is unsafe: landscape images or already-correct portraits may be turned the wrong way.
Pixels versus orientation
Orientation can be an instruction rather than the physical pixel order
Cameras and phones can save sensor pixels in a consistent arrangement and include metadata telling software how to rotate or mirror the image for display. Modern apps usually honor that instruction automatically, which hides the difference from the user.
A conversion, thumbnail generator, or older viewer can decode the pixels but miss the orientation rule. This browser converter writes visible pixels to a new lossy JPG and does not preserve the HEIC EXIF metadata, so the output must be visually checked instead of assumed correct.
The robust delivery file has its pixels stored in the intended upright direction. Correct the view in a tool that renders orientation properly, export once, and avoid repeated JPEG saves that add generational loss.
Flatten the correct view
Create one upright delivery copy and verify it in the destination
- 1
Keep the HEIC camera original untouched
Duplicate the source or leave it in Photos. Use copies for rotation tests. The HEIC retains the best available original and any metadata that the browser-generated JPG will not carry forward.
- 2
Compare the source and JPG in current viewers
Open both in a current browser or trusted photo app, then test the JPG in the problem destination. If only one old viewer is wrong, update or replace that viewer rather than altering every image.
- 3
Correct the orientation before the final lossy save
Use Photos or an image editor to rotate the view to the intended direction and export a new copy that bakes the rotation into its pixels. Avoid rotating a JPG, saving it, and then converting it again.
- 4
Convert the corrected HEIC only if necessary
If the corrected rendered copy is still HEIC and is 50 MB or smaller, convert it locally in the browser. If Photos already exported a compatible JPG, use that file and skip another JPEG encoding pass.
- 5
Inspect portrait details and dimensions
Confirm that faces, text, and horizons are upright and that width and height now match the intended portrait or landscape layout. Remember that the new JPG is lossy and metadata-free, so retain the original separately.
- 6
Test the actual upload or receiving app
Upload the corrected copy and wait for the destination thumbnail. If that system still rotates a pixel-flattened image, its processing pipeline is the likely fault; provide the verified file and viewer evidence to its support team.
Have a correctly rendered HEIC?
Create one JPG copy, then check its pixel direction.
Orientation questions
HEIC and JPG orientation FAQ
Why is the same JPG upright in one app and sideways in another?
The apps may interpret orientation differently. One applies the display instruction while another shows the stored pixel order. A copy with the intended direction flattened into the pixels avoids that dependency.
Does removing EXIF cause a photo to rotate?
It can if a workflow removes the orientation field before applying it to the pixels. A careful export first renders the intended view, then writes upright pixels even when other EXIF fields are omitted.
Should I rotate the JPG multiple times until a website accepts it?
No. Diagnose the displayed direction, make one corrected copy, and verify it. Repeated JPEG saves are lossy and can soften details without fixing a destination that mishandles thumbnails.
Will this converter preserve orientation metadata?
It does not preserve the original EXIF metadata. It converts visible image data locally in the browser, so inspect the JPG orientation immediately and keep the HEIC original.
Can a large portrait fail even when orientation is the only visible issue?
Yes. Orientation and resource limits are separate. The converter accepts up to 50 MB per file, and high-resolution images can also need substantial decoded memory. Test one file at a time on a current browser.