DEV Community

Fix Quotes
Fix Quotes

Posted on

Why doesn’t Windows have “Rotate left” and “Rotate right” for videos?

There is a small Windows feature I have loved since Windows 10: right-click a photo in File Explorer, choose Rotate right or Rotate left, and move on with my day.

No Photoshop. No export dialog. No choosing a new file name. It was such a good little feature that it made me wonder why the exact same thing was missing for video.

Then came the real irritation: Snapchat videos shot on an iPhone, synced to OneDrive, and sitting in File Explorer in the wrong orientation. You can play them that way, send them that way, and eventually somebody will ask why the video is sideways.

There are two obvious fixes, and both have annoyed me.

The first is a small video rotator that only changes the orientation flag. It is almost perfect: fast, no re-encode, and no questions. Until I send the file to someone else, play it on Plex, upload it somewhere, or open it in software that ignores the flag. Then the old problem comes back.

The second is proper video-editing software. It has a Rotate button, which is great. Then I press Ctrl+S and get a long list of questions: output format, FPS, bitrate, encoder, audio, quality, naming, destination. I only wanted to turn the video 90 degrees.

That is the frustration that made me build ClipTurn. I wanted the File Explorer photo experience for video: right-click, choose a direction, and get a result I can actually use elsewhere.

So why did Microsoft not just add the same two commands for video? I think the short answer is that video is a much harder promise than a JPEG.

Why video rotation is not just a button

A JPEG can lose a little quality when it is saved again, but it is still one image. A video can contain compressed picture frames, audio streams, subtitles, timing, colour information, HDR metadata, extra tracks, and a container with its own rules.

To make a sideways video reliably upright everywhere, ClipTurn turns the stored picture itself. It does not just set an orientation instruction and hope every downstream player honours it.

ClipTurn workflow in File Explorer: choose a direction, wait for the worker, then read the verified result.

That means I have to be honest about the compromise. With normal compressed video, a physical turn requires decoding the picture, rotating it, and encoding it again. That is not mathematically lossless, and I do not want to pretend otherwise.

The goal is not “lossless at any cost.” The goal is a quality-preserving result, in the same codec when possible, without turning a simple rotation into an export wizard. When that cannot be done faithfully, ClipTurn explains why instead of silently making a worse file.

I still wanted right-click to feel simple

The fast path is intentionally boring: right-click a supported video in File Explorer, open ClipTurn – Video Rotator, choose Rotate video left or Rotate video right, and read the result card.

That is it from the user’s point of view. There is no account, no upload, no codec picker, and no list of quality sliders.

If I want more control, I can open the video in ClipTurn first, preview the direction, inspect the file, choose a backup, and then save one deliberate rotation.

The single-video flow: preview a direction first, then save one deliberate rotation.

The preview is non-destructive. I can spin the preview left, right, or back to zero as many times as I want. The original is untouched until I select Save rotation.

The part that got complicated very quickly

Making the UI simple does not mean the work behind it is simple.

I did not want ClipTurn to encode over the original while it was still working. A rotation is treated as a small file-replacement transaction instead:

  1. Check the source location, identity, attributes, and request.
  2. Record a full SHA-256 fingerprint of the source.
  3. Build the turned video as a separate candidate.
  4. Decode and verify that candidate: its geometry, physical turn, audio path, promised tracks, container details, and supported metadata.
  5. Check that the original has not changed underneath the job.
  6. Stage a same-volume replacement, keep rollback material while it is active, and write the durable result.

If another app, sync process, or person changes the source while ClipTurn is working, it does not overwrite those new bytes. It reports the conflict. It may feel overly cautious for a rotate button, but the file is more important than the button.

The codec rabbit hole

The thing I learned most clearly while building this is that a file extension tells you very little.

An MP4 might be H.264 or HEVC. It might be 8-bit or 10-bit. It might carry HDR, multiple audio tracks, subtitles, camera data, timecode, or a layout that cannot be safely reproduced by the available Windows media components.

ClipTurn has a few explicit policies rather than a mysterious “best” choice:

  • Keep codec and quality is the recommended path for normal compressed video.
  • Strict and Exact require a sample-exact pixel permutation. In this release, that is for eligible uncompressed packed-pixel AVI—not ordinary phone footage.
  • A 10-bit HEVC source never quietly turns into an 8-bit file. If there is no faithful Main10 path, ClipTurn refuses it.

The app can also inspect Windows Media Foundation capabilities for H.264, HEVC, VP8, VP9, AV1, and Windows Media paths. That is useful evidence, but it is not a promise that a particular file will work. The actual rotation still has to decode, encode, write, and verify the complete candidate.

System Capabilities shows what this PC has registered—useful evidence, but not a guarantee that every file can be processed.

Sometimes the correct answer is “I won’t touch this file”

This has been a hard product decision, but an important one.

ClipTurn refuses files when it cannot prove a safe result: cloud placeholders that are not fully available locally, network or removable storage, read-only sources, unsupported colour geometry, tracks it cannot preserve, duplicate requests for the same physical file, and codec/container combinations that would require an unannounced compromise.

If a source cannot be safely replaced but the PC can prove a separate copy is possible, ClipTurn stops and presents the exact change before creating anything. The original stays where it is until the user approves the copy.

Reviewed copies make the trade-offs explicit before a separate display-orientation or H.264 copy is created.

I would rather show a clear limitation than show a fake success message after silently dropping something important.

A folder should not hide the awkward files

I also wanted batch work to be honest.

Batch Rotate does not treat a folder as one all-or-nothing operation. Every row is its own job. One video can rotate, another can be safely refused, and another can wait for a reviewed-copy decision without hiding or stopping the rest.

Batch Rotate keeps each file’s status visible, including verified rotations and files that need review.

The selected direction and settings are snapshotted at the start. Concurrency is bounded. Stopping a batch stops new jobs from starting, rather than pretending active processing vanished.

I wanted proof for the awkward cases

After a verified result, ClipTurn writes a local receipt for that exact file version. It records the file identity, timestamps, length, SHA-256, direction, app version, and the checks it established.

The receipt is not embedded in the video or attached as a sidecar file. If the video changes later, the old receipt is stale. In Details, I can do a quick identity, size, and time check, or run a full hash recheck if I need stronger evidence.

Video Details shows the current file information and the local verification state for that exact version.

That matters to me. “I processed a file with this name last week” is not the same thing as “this exact file was verified.”

Privacy is part of the point

These are often personal videos. ClipTurn processes selected files on the PC; it does not require an account or upload videos to FixQuotes. It also ships without analytics, advertising, telemetry, or automatic crash reporting.

That does not mean the whole world disappears: Windows, Microsoft Store, a sync provider such as OneDrive, or a support channel I choose can have their own data practices. But ClipTurn itself should not need my video to leave the computer just to rotate it.

Back to the original question

I still think Windows should have native Rotate Left and Rotate Right for video.

But I also understand why that is not as simple as it looked when I first right-clicked a photo. A reliable video rotation command has to decide what it can preserve, what it cannot, when it needs a separate copy, and when it should leave the source alone.

ClipTurn is my answer to that gap: make the common case as simple as the photo command, but do not hide the complicated bits when they matter.

If you have a sideways video on Windows 11, ClipTurn is currently free in the Microsoft Store. The complete manual covers supported formats, policies, recovery behaviour, and limits in more detail.

And here is a short walkthrough:

https://youtu.be/-_kdhLjnPy0

Top comments (0)