Why Does My Vertical Product Video Appear Upright in One Editor but Sideways After Export?

Separate stored pixels from displayed orientation

Begin with the camera-original video, not a screenshot of an editor preview. Record the file's encoded width and height, the expected displayed orientation and any rotation or display-matrix metadata.

Video containers and encoded streams can represent orientation separately from pixel geometry. A file with encoded dimensions of 1920 × 1080 may be intended to display as a vertical image when a rotation instruction is applied. The numerical example is illustrative; actual orientation signaling depends on the file and codec.

FFmpeg's documentation describes display-orientation metadata and rotation handling, including display-matrix information. That establishes why stored dimensions alone may not describe how a compatible player presents the image.

Open the same source in two appropriate players or editing applications and record their actual display behavior. If one shows the product upright and the other sideways, inspect their handling of the orientation instruction before altering the source pixels.

Do not assume the application showing the image upright has physically rotated the encoded frames. It may only be applying metadata during display.

Identify where orientation changes during export

Compare the original source, editing timeline, newly exported file and final destination playback. Record encoded dimensions and orientation metadata separately at each stage.

If the source is landscape-shaped with a display rotation and the export preserves the same encoded geometry but drops the rotation instruction, the output may appear sideways in a player that displays the stored frames directly.

If the export physically rotates the pixels into a portrait-shaped frame but also retains an inappropriate rotation instruction, a receiving player may rotate the image again. Conversely, a properly normalized portrait file can use portrait pixel dimensions without requiring a nonzero display rotation.

These are diagnostic possibilities, not automatic conclusions from a filename or resolution label.

Check whether the editor's sequence dimensions, scaling and export configuration are appropriate for the intended vertical placement. Changing a container's width and height fields alone does not necessarily rotate image content correctly.

Hypothetical vertical bottle clip

Hypothetical illustration—not an executed FFmpeg or editor test: fictional bottle clip V8 is intended for a 1080 × 1920 vertical advertisement. Its original file is stipulated to contain 1920 × 1080 encoded frames with a display-rotation instruction that presents the bottle upright.

Player A honors that instruction and shows an upright bottle. Editor B imports the source into a vertical sequence. The editor exports a new file whose orientation handling is not yet verified.

In diagnostic branch one, the exported file retains landscape pixel geometry but lacks the necessary display rotation. A receiving player may show the bottle sideways.

In branch two, the editor physically rotates the image into portrait geometry and removes the now-unneeded rotation instruction. This is a plausible normalized representation for the intended vertical destination, subject to actual export verification.

In branch three, the pixels are rotated but an additional nonzero display instruction remains. The editor must inspect the resulting presentation rather than assume that two orientation operations cancel safely.

The worksheet distinguishes these hypothetical representations without asserting an actual file result.

Approve the final representation in the receiving environment

Choose one documented delivery approach supported by the receiving platform: correctly oriented encoded pixels, or a supported encoded orientation plus metadata arrangement. Do not rely on an editor preview alone.

Inspect the actual exported file in a fresh player and in the destination publishing environment. Verify that the bottle is upright, the label is readable, the product proportions are unchanged and no unexpected crop or letterboxing hides important information.

Compare a recognizable asymmetric landmark such as a printed label or handle. A symmetric bottle silhouette may appear plausible even when the orientation is wrong.

Preserve the camera-original file and give the normalized delivery version a new filename. Record encoded dimensions, rotation metadata, intended display dimensions, export route and destination result.

Do not apply an arbitrary additional 90-degree rotation until the stored-pixel and metadata states are understood. Repeated transformations can produce unnecessary resampling or incorrect double rotation.

This procedure concerns file orientation and external editing. It does not establish that a generated or filmed product's construction is accurate; that remains a separate source-reference check.

Record your own observations

The filled rows are illustrative examples. Use the blank row for your own files and observations.

Download the editable CSV worksheet

What the references establish

• FFmpeg — ffprobe Documentation: Primary technical documentation for inspecting stream information and orientation-related metadata.
• FFmpeg — Filters Documentation: Documents image transformations, including transpose-related operations used when an actual pixel rotation is required.
• FFmpeg — ffmpeg Documentation: Documents stream processing and output behavior; implementation details must be checked for the installed build and selected codec/container.