Why does an uploaded product photo look rotated in another tool?

Observe the mismatch before changing the file

Open the same source in the local viewer and the actual workbench preview. Note whether the image is rotated, mirrored or cropped. These are different problems. A missing top edge may be a display crop rather than orientation, while left-right reversal changes handed construction.

For an illustrative pump bottle, a sideways upload makes the cap and label difficult to review. Keep the untouched original and record the observed preview instead of overwriting the only source immediately.

MDN documents a browser display rule that can use EXIF orientation data. The encoded pixel arrangement and its displayed direction are therefore separate things to inspect. A viewer that shows a photo upright does not alone prove that all receiving tools will interpret its orientation the same way.

Create an orientation comparison

Normalization should be done in an appropriate image editor and checked afterward. Do not repeatedly rotate files based on assumptions about metadata until the pixels become wrong.

Upload the reviewed source

Prepare a new clearly identified export if needed, then replace the reference using the normal workbench upload. Check its visible orientation before confirming any chargeable operation. Retain the exact product details and label; a rotation fix should not introduce a new crop or lower-quality compression unnoticed.

CartVisual’s upload preview is the receiving surface you can inspect. This guide does not claim automatic orientation correction in every path or explain a confirmed current bug. Record an actual defect report if the preview contradicts the normalized source.

Verify the new result against the right file

Compare the generated candidate with the corrected reference, not a differently displayed original. Inspect handed controls and text as well as vertical orientation. A correct display does not establish product fidelity by itself.

Use mirror review for handedness and defect reporting for a reproducible mismatch. Keep original, corrected export and observed preview identities in the private review record.

Fictional source A has sideways encoded pixels and an orientation instruction that a local viewer follows. A receiving preview shows the sideways pixel arrangement. Keep A untouched. Create derivative B with deliberately upright pixels in an appropriate editor, then reopen B and inspect the actual upload preview before any chargeable step.

Deleting an orientation flag alone can expose sideways encoded pixels rather than fix them. Use a controlled export and verify it. Preserve other needed metadata, including applicable AI-origin information, rather than treating orientation correction as a reason to strip all properties. No image was uploaded or normalized for this fixture, and it does not establish a current platform defect.