Questions, bug reports, and feature requests are welcome. We read every message.

Requirements

ClipReady requires an Apple Silicon Mac (M1 or later) and macOS 15 or later. Intel Macs are not supported—this is a deliberate design decision, not a missing feature, and there is no Intel build planned. Please check your Mac before buying.

Contact

Email: support@tentstudios.com

Please include:

The macOS version you’re running
The source container and codecs, if you know them
What you expected, and what happened instead
The text from the plan pane, and any note shown under Notes

Please don’t send us video files. We can almost always diagnose a problem from the plan text and the reason lines shown next to each track. If we do need a sample, we’ll ask, and a short clip is enough.

What ClipReady works on

ClipReady prepares media you already have. It opens a video file on your disk and writes a new MOV or MP4 alongside it. There is no store, no library, no browsing or search, and nothing is fetched—it has no network access at all.

It does not rip or decrypt discs, and it does not remove copy protection. Getting a file off a disc is a separate job for separate software. Your original files are never modified.

Disc rips are what it is built around—Blu-ray and DVD files in MKV, with the timing and surround work those need. Other media is the same job when the picture is MPEG-2, H.264, HEVC, or ProRes: an MXF clip, an AVCHD file, a transport stream, or a MOV that needs a clean remux. ProRes still goes through the plan—timing, timecode, audio—so you get a clean MOV, not a skip. Drop one file. It is not a general “any video file” converter.

The most common questions

Can I drop camera files, or only disc rips?

Both. Disc rips are the flagship, but MXF, AVCHD, transport-stream, and ProRes files get the same plan when the picture is MPEG-2, H.264, HEVC, or ProRes. Drop one file, not a whole card. Spanned clips and “whatever Apple can play” are a different product.

Why is my file listed as Incompatible?

Two video formats have no honest path into Apple’s media stack: VC-1 and AV1. ClipReady refuses them rather than re-encoding behind your back, because re-encoding is the one thing it promises never to do. The row tells you which stream is the problem and why.

Bitmap subtitles (PGS on Blu-ray, VobSub on DVD) stay in the original file. They are pictures, not text, and MOV and MP4 have no place to put them.

Final Cut said my file was 23.81 fps. Is that what this fixes?

Yes—that’s the flagship repair. MKV stores timestamps in milliseconds, which cannot represent 23.976 fps exactly, so frames land 41 and 42 milliseconds apart and Final Cut reads the average as 23.81. ClipReady snaps every timestamp back onto the exact frame grid. The picture is untouched; only the timing is corrected.

Will this reduce my quality?

No. The video bitstream is copied across as-is, so the picture in the output is the picture that was in the source. Audio is a different matter: formats Apple’s stack cannot read (such as DTS-HD Master Audio and TrueHD) must be converted, and ClipReady defaults to lossless 24-bit PCM so nothing is lost there either. Each track says which of those two happened before you press the button.

MOV or MP4?

Choose MOV for editing—it’s what Final Cut and Compressor prefer. Choose MP4 for playback and sharing. If your source is MPEG-2 or ProRes, ClipReady offers MOV only.

Why is my prepared file the same size as the original?

Because it contains the same video. Preparation is a repackaging job, not a compression job, so it finishes at roughly the speed your disk can copy the file. If the file got larger, it’s because lossless audio was expanded to PCM—pick Compact audio if you’d rather trade that for size.

Why does the app run `ffmpeg`?

ClipReady bundles the ffmpeg and ffprobe tools and drives them with precisely-built arguments. They run inside the app’s sandbox with no network access. Attribution and license details are in Settings → General → Acknowledgments.

It looks right in QuickTime or Final Cut, but Premiere or Resolve looks different

If QuickTime Player, Preview, or Final Cut Pro look right, the file is tagged the way Apple’s stack expects. ClipReady copies the color the source already declared (and labels untagged DVDs so they aren’t treated as Rec.709). The picture is not re-encoded.

When another editor still looks washed out, too contrasty, or treats an HDR clip as Rec.709, that’s that app’s color management—not a second tag ClipReady should write.

Premiere. Check the clip’s color space against the plan: Rec.709 for HD, Rec.2020 / PQ (ST 2084) for HDR10. If it’s wrong, Modify → Color. If the space is already right and the viewer still disagrees with QuickTime, look in Lumetri’s display / viewer settings rather than re-preparing the file.

DaVinci Resolve. A color-managed project (DaVinci YRGB Color Managed, or ACES) is what reads the file’s color tag. The default DaVinci YRGB mode leaves clips at Rec.709 until you set them. For HDR10, Input Color Space should be Rec.2020 and Input Gamma ST2084. On a Mac, Resolve’s own display-profile preferences are how its viewer lines up with QuickTime.

Refunds

Mac App Store purchases are refunded by Apple, through reportaproblem.apple.com. Purchases made directly are handled by us—email the address above.

A sample MKV, if you need one

A Mac does not come with an MKV on it, which makes ClipReady awkward to try before you have a file to try it on. There is a small one here:

clipready-sample.mkv—11 MB, 10 seconds, 1080p H.264 with an AC-3 5.1 track, a DTS 5.1 track, a subtitle track, and chapters.

Drag it onto the window and the plan appears: the video reads Video untouched, the AC-3 track reads Preserve, the DTS track reads Convert with the reason printed beside it, and the subtitle is carried. It prepares in a few seconds.

Credits for the footage in our screenshots and the sample file

The demo library in ClipReady’s screenshots, and the sample file above, are built from the Blender Foundation’s open movies, used under CC BY 3.0:

The sample file is a ten-second excerpt of Big Buck Bunny. The credit is written into the file’s own copyright and artist tags and spoken by its first subtitle, so it travels with any copy that leaves this page.