How to fix footage that was recorded in the wrong orientation

Last updated 2026-09-05 · 8 min read

What is the short version?

A clip can be the right shape and still be the wrong way up. A vertical reel built from footage that was itself recorded sideways is correctly formatted and shows a product lying on its side, and the repair belongs to the source rather than to the export.

1. Go to Vizard Agent with the delivered video.
2. Say the source footage is oriented wrongly, not the frame.
3. List everything else that must stay exactly as it is.

What do you need before you start?

The original clips and a clear statement of what should be upright. "The product should be standing up and seen from above" describes the target far better than "rotate it", because rotation has two directions and only one of them is right.

• The original clips. Rotating the export loses quality.
• What upright means here. The product, the horizon, the person.
• The format you are delivering. Rotation changes the crop.
• What must not change. Voice, script, music, timing, captions.
• Which shots are affected. Sometimes only some.

What do you type into Vizard Agent?

Separate the two things: the frame shape and the picture inside it. Saying "it is sideways" about a video that is already vertical sounds contradictory until you name which one you mean, and naming it saves an entire round.

Prompt

Variants worth knowing:

• "The source, not the frame." The distinction that matters.
• "Upright and from overhead." Describes the target.
• "Do not change:" followed by a list. Protects the rest.

What does Vizard Agent actually do?

Here is the order Vizard Agent worked in on a real vertical food reel whose source clips had been shot on their side. The two tests in the middle are the whole job; the rest is putting the reel back together around them.

1. Tests both rotation directions on the source.
2. Compares the two to find which one is genuinely upright.
3. Measures where the subject sits in the rotated footage.
4. Tests two portrait crop options against that measurement.
5. Checks the wider crop on real frames.
6. Checks the tighter crop on the same frames.
7. Re-renders the reel with the upright footage.
8. Reviews the rotated render shot by shot.
9. Checks the whole reel is upright, not only the opening.
10. Verifies the orientation on the final delivered file.

Step two exists because rotation is not obvious. A tray of food seen from directly overhead looks plausible at ninety degrees in either direction, and the only way to be sure is to put both in front of somebody and look.

Step nine is a cheap check that catches an expensive mistake. A reel assembled from several clips can have one that was already upright, so rotating everything fixes most of the video and breaks one shot — and the opening frame, which is what everybody looks at, will not show you that.

Step three is the consequence people forget. Rotating a frame moves everything in it, so the crop that framed your subject nicely before now frames the edge of the table — which is why the crop is re-derived rather than reused.

What does the result look like?

The same reel, with the picture finally the right way up: the subject upright, framed deliberately in its new orientation, and everything else Vizard Agent was told not to touch — the narration, the music, the captions, the cut — exactly where it was before.

The quality holds because the rotation happened to the source rather than to the export.

When does this not work well?

Rotation is free; the crop it forces is not. Turning landscape footage upright inside a vertical frame throws away a lot of picture, and a subject that filled the old frame may not fit the new one at all.

• Landscape into vertical. A large part of the frame goes.
• Only the export available. Rotating it costs quality.
• Text inside the footage. It rotates too, and cannot.
• Mixed orientations. Each clip needs deciding separately.
• A deliberate angle. Sometimes sideways was the intention.

How do you fix a result that came back wrong?

Say which way it should have gone, or which of the two crops you prefer. Vizard Agent keeps both rotation tests and both crop options from the first pass, so choosing again is a selection you make rather than a rebuild of the whole reel.

• "It is upside down now." The other rotation applied.
• "Too tight." The wider crop used instead.
• "The subject is off centre." Re-measured and reframed.
• "Only one clip was wrong." Rotation limited to that shot.

How does Vizard Agent compare to doing it yourself?

The quick fix is rotating the finished export, which re-encodes an already-compressed file and leaves the crop wherever it happened to land. Going back to the source costs a re-render and gives you the picture the camera actually recorded.

Common questions

Can it just rotate the finished video? It can, but Vizard Agent prefers the source for quality.

How does it know which way is up? It does not guess. Vizard Agent tests both and shows you.

Will I lose picture? Some, when the orientation changes. Vizard Agent shows the crops.

Can it rotate only some clips? Yes. Name them and Vizard Agent leaves the rest alone.

Does the audio change? No. Vizard Agent keeps the mix exactly as it was.

Will the captions move? No, unless the crop demands it. Vizard Agent checks.

What about text inside the footage? It rotates with the picture, and Vizard Agent cannot correct it separately.

Can it fix a tilted horizon too? Yes, that is a smaller rotation. Say by how much, or ask Vizard Agent to measure it.

What if the metadata is wrong? Vizard Agent checks the actual pixels rather than the tag.

Can I see both crops? Yes. Vizard Agent renders both for you to pick.

Does this work on phone footage? Yes. Phones are where this happens most.

Will the reel need re-timing? No. Vizard Agent keeps the cut and the timings.

Can it check every shot is upright? Yes, and it should — Vizard Agent reviews the whole reel.

Why not trust the file's rotation flag? Because the flag records what the camera believed it was doing, while the pixels record what actually ended up in the file, and the two disagree often enough that only one of them is worth checking.