Video Player Guides

Play iPhone Videos on Mac: HEVC, HDR, and Slow Motion Clips

The phone writes a file that opens on a Mac and plays, which makes the whole thing look solved. It is not quite solved. The clip is compressed with HEVC, it may carry a high dynamic range signal your display has to fold back down, and if you shot it in slow motion the file contains frames at four or eight times normal speed plus a timing instruction that only some players bother to read. Here is what each of those means, and how to watch every clip the way you shot it.

Download for Mac See the Mac player

Total Video Player for Mac. Apple Silicon and Intel.

A phone in a pocket now records video that would have needed a broadcast camera a decade ago, and it hides the achievement behind a thumbnail in a grid. You plug the cable in, or you drop the clip across with AirDrop, and it appears on the desktop as a small movie file with a name like IMG_4821.MOV. Double-click it and it opens. Frames move. There is sound. For a moment it seems reasonable to assume that the hard part is over, that a video is a video and the rest is just window dressing. Then three ordinary things happen. The clip you remember shooting in slow motion plays at full speed and is over in four seconds. The sunset shot that looked glorious on the phone looks either flat and grey or blown out on the laptop. The forty-minute interview you want to skim takes forty minutes to skim. None of those are bugs in macOS, and none of them require you to convert anything. They are three separate properties of what an iPhone actually writes to disk, and once you can tell them apart, each has a short answer.

The short answer, in one line: an iPhone writes HEVC inside a QuickTime wrapper with metadata attached, and the metadata is doing more work than most people realise. Codec, colour description, frame timing, rotation, and in the case of slow motion an explicit playback instruction are all carried in the file alongside the pixels. A player that reads all of it shows you what you shot. A player that reads only the compressed frames shows you something technically correct and visibly wrong. This guide walks through each piece, in the order you will meet them, and ends with a routine you can run over a whole card of footage in a few minutes.

If you only read one paragraph

Take the original file off the phone rather than a converted copy — Photos export set to Automatic can change both the codec and the brightness. Play it in something that reads frame timing, so slow motion stays slow. Expect HDR clips to look different on a laptop screen than on the phone, because the laptop is applying its own tone mapping. And when a long clip needs reviewing, run it at high speed instead of watching it twice.

What an iPhone Writes, and Why It Surprises a Mac

Start with the container, because the file extension is the first thing that misleads people. iPhone video is saved as a .MOV, which is Apple's QuickTime flavour of the family of formats that also includes MP4. On a Mac this distinction almost never matters, because macOS has spoken QuickTime natively since before most of us owned a computer. It matters the moment the file leaves the Mac — a television's USB port, an Android phone, a car head unit, an older Windows machine — where a .MOV may be refused while the identical video inside an .mp4 wrapper would be accepted. If your plan is to hand the file to a TV by stick, that is worth knowing before you spend an evening on it. If your plan is to watch it on the Mac, ignore the wrapper entirely and look at what is inside.

Inside, recent iPhones compress with HEVC, also called H.265, which is the newer and roughly twice-as-efficient successor to H.264. Apple exposes the choice in Settings under Camera, as a pair of options usually labelled High Efficiency and Most Compatible. High Efficiency gives you HEVC and smaller files. Most Compatible gives you H.264, which is bigger and plays on practically anything built in the last fifteen years. The default is High Efficiency, which means that most footage shot by most people in the last several years is HEVC, whether or not they ever chose it. HEVC is not an exotic format on a Mac — every Mac made since roughly 2017 can decode it in hardware — but it is a different decode path from H.264, and the difference shows up as heat, fan noise, and dropped frames on older machines.

Then there is resolution and rate. A modern iPhone shoots 4K at 24, 30, or 60 frames per second depending on the model and the mode, plus 1080p at 30 or 60, plus the special modes that behave nothing like ordinary recording. Cinematic mode records 1080p with a depth map so focus can be shifted afterwards. Action mode crops and stabilises hard. Time-lapse records slowly and plays back fast. The Pro models add ProRes, a lightly compressed editing format whose files are enormous, and a log recording profile that deliberately produces a flat, low-contrast image because an editor is expected to grade it later. Spatial video, on the models that offer it, writes a stereoscopic stream intended for a headset and displays as ordinary two-dimensional footage everywhere else.

The practical consequence is that "iPhone video" is not one thing. Two clips sitting next to each other in the same folder can differ in codec, colour description, frame rate, and whether a playback instruction is attached. The table below is the map. Read it once and the rest of this guide becomes a set of variations on four themes: decode, colour, timing, and transfer.

What you shot What is actually in the file What to expect on a Mac
Standard 4K clip, High Efficiency setting HEVC, ten bits per channel, usually tagged as high dynamic range on recent models Hardware decode on any recent Mac; brightness depends on how the display and the player handle the colour tags
Clip recorded with Most Compatible selected H.264, eight bits, standard dynamic range Plays anywhere, looks the same everywhere; larger files, no colour surprises
Slow motion at 120 or 240 frames per second All frames stored at capture rate, plus a timing instruction that stretches them across a normal-speed timeline Slow in players that read the instruction, real-time in players that ignore it
Cinematic mode 1080p plus a depth track and focus decisions stored as metadata Plays as the rendered result; the rack-focus choices are already baked into what a desktop player shows
Action mode Cropped, heavily stabilised footage at a reduced resolution Nothing special to decode; the crop is permanent and cannot be undone in playback
ProRes on a Pro model Lightly compressed intra-frame video, very high bitrate Decodes on modern hardware but the data rate, not the codec, is the limit — plan storage accordingly
Log recording on a Pro model Flat, low-contrast image with a colour tag describing the transfer curve Looks washed out by design; that is the file, not a playback fault
Time-lapse Frames captured far apart, assembled into a short clip at normal playback rate Plays like any other clip; nothing to adjust
Spatial video Two views in one stream, intended for a headset Displays as ordinary footage on a Mac, with the second view unused

One quick diagnostic is worth memorising, because it settles most arguments in ten seconds. Select the file in Finder and press Command-I. The Information panel shows dimensions, duration, and often the codec. Even better, open the clip in QuickTime Player and press Command-I for the Movie Inspector, which reports format, frame rate, and data rate in plain language. If the inspector says HEVC and the dimensions say 3840 by 2160, you know exactly what you are dealing with and you know the Mac will decode it in hardware. If it says H.264, the file is the compatible kind and any oddity you see is coming from somewhere else.

Getting iPhone Video Onto a Mac Without Losing Quality

The single most common reason a clip looks wrong on a Mac is that the file on the Mac is not the file that was shot. Apple gives you several routes from phone to desktop, and they do not all preserve the original. AirDrop sends the original, which is the good news. Image Capture imports the original, which is also good news. The Photos app is where things get subtle, because Photos is built around the idea of managing a library rather than handing you files, and its export dialog offers choices whose labels do not fully explain what they do.

When you drag a video out of Photos, or use File then Export, you are usually offered a quality setting. The option called Automatic is the one that catches people. Its job is to produce a file that will play widely, and producing a widely playable file sometimes means converting HEVC to H.264 and re-mapping a high dynamic range clip down to standard range. That is genuinely helpful if the destination is an old television or a work laptop from another era. It is unhelpful if the destination is your own Mac and you wanted to see the footage as recorded. The option called Current uses whatever version Photos currently holds, which may be a converted copy if the library was set to optimise storage. The option called Original hands you the untouched capture. When the point of the exercise is reviewing what you shot, choose Original.

The iCloud wrinkle deserves its own sentence. If the Mac's Photos library is set to optimise storage, the full-resolution original may not be on the Mac at all — the library holds a smaller version and fetches the rest on demand. Exporting from that state can produce something that is not the capture, or a download that stalls halfway when the network is slow. If you are about to review footage seriously, either download the originals first or use a route that bypasses the library entirely.

Route from phone to Mac Keeps the original file? When it is the right choice
AirDrop Yes, transfers the capture as written A handful of clips you want immediately, with no library involved
Image Capture Yes, imports what the phone holds A whole card's worth of footage, straight into a folder you control
Photos, export set to Original Yes Clips already in the library that you want to hand to another app
Photos, export set to Automatic No, may convert codec and brightness Deliberately making a compatible copy for an older device
iCloud Photos with optimised storage Depends, may be a reduced local copy Convenience over fidelity; download originals before serious review
Finder and the Files app over USB Yes Pulling individual files out of an app's folder without any import step
Messaging apps and email No, recompresses and often downsizes Sending a preview to a person; never for keeping footage

If you want the mechanical version of the routine, this is it. Connect the phone, unlock it, and tap Trust when the Mac asks whether to allow access. Open Image Capture from the Applications folder. Select the clips, choose a destination folder on the Mac rather than inside a photo library, and click Import. The files land with their original names and their original contents. From there you can play them directly from the folder, which is also the fastest way to work, because a player reading from a plain folder is not competing with a library that wants to index, generate thumbnails, and sync in the background.

Why Slow-Motion Clips Play at Normal Speed on a Mac

This one confuses people more than any other, because the file is not broken and the Mac is not failing. A slow-motion clip is not stored as slow motion. It is stored as a burst of real-time frames taken very quickly, 120 or 240 of them per second, and then a separate instruction in the file says: present these frames across a timeline that runs at normal speed. Spread 240 frames across one second of a normal-speed timeline and each frame occupies four times as long on screen, which is exactly what slow motion is. The frames were never slowed. The clock was.

QuickTime Player and the Photos app both honour that instruction, which is why the same clip looks correct in those two places and wrong somewhere else. A player that ignores the instruction and simply plays the raw frames at capture rate will show you a four-second clip that is over in one second, with motion that looks almost comically fast. Nothing was lost. The frames are all there. The player is choosing to read the sample timing and ignore the presentation timing.

There is a fast way to confirm which situation you are in. Compare the duration the file reports in Finder with the duration you remember. A clip you filmed for about four seconds that claims to be one second long is a slow-motion file being played at capture rate. A clip that claims to be four seconds and plays in four seconds at normal speed is a clip whose slow-motion section was never applied, or a clip that was shot at normal rate in the first place. That single comparison separates a player problem from a memory problem.

When you need the slow section preserved and the player in front of you will not do it, the reliable path is to let the software that understands the instruction write a new file. Open the clip in QuickTime Player, use the trim controls to keep only the portion you want, and save. Or open it in Photos, trim, and export with the setting that renders the effect. Both produce a file whose frames are already spread across a normal timeline, so every player afterwards shows the same thing. It costs a re-encode of that one clip, which is a fair trade for a file that behaves predictably everywhere.

Two smaller facts about slow motion are worth filing away. The first is size: 240 frames per second at 1080p for eight seconds is a lot of frames, and slow-motion clips are disproportionately large for their playing time. The second is light. High frame rates mean short exposures, so slow-motion footage is usually noisier than ordinary footage from the same scene, and that noise becomes much more visible when the frames are stretched out. Neither is a playback issue, but both explain why a slow-motion clip sometimes looks worse than the rest of the shoot.

HEVC, HDR, and 10-Bit on a Mac: What Is Really in the File

Recent iPhones record high dynamic range video by default, and the setting is easy to forget because the toggle lives a couple of screens deep in Camera settings. What that means concretely is that the file carries a colour description telling the player the highlights extend brighter than a standard display can show, along with the transfer curve used to encode them. The video is still HEVC, usually ten bits per channel in the Main10 profile, so the extra range has somewhere to live. On the phone this is handled seamlessly because the phone knows its own screen. On a Mac, the same file meets a display of unknown capability and a player of unknown sophistication, and the result depends on both.

The macOS side is better than its reputation. Modern Macs decode HEVC Main10 in dedicated silicon — the media engine on Apple Silicon, and the hardware decoder built into Intel chips from roughly the seventh generation onward. That hardware path is why a 4K clip that would pin a processor at full load on an older machine plays cool and quiet on a current one. When hardware decode is unavailable, macOS falls back to software, and software decoding of ten-bit 4K is exactly as expensive as it sounds. That fallback is the usual explanation for a Mac that runs hot and drops frames on iPhone footage while a newer machine in the same room does not.

Colour is where expectations need calibrating. A high dynamic range clip contains brightness values outside what a standard screen can display, so something has to decide what to do with them. macOS tone maps: it compresses the extremes so the picture fits the panel, keeping midtones intact and rolling off the brightest highlights. On a laptop with an extended-range display the result can look strikingly close to the phone. On an external monitor that is standard range, the same clip looks flatter, with skies that lose gradation and highlights that go white a little earlier than memory suggests. The file did not change. The window it is being shown through did.

This is also where a flat, grey, low-contrast image can appear, and the cause is usually not HDR at all. If the clip was shot with a log profile on a Pro model, it is supposed to look like that: log recording deliberately compresses contrast and saturation so an editor has room to grade. A player that ignores the colour tag will show it raw and grey. A player that reads the tag and applies the viewing transform will show something closer to what the camera saw. Either way, the flatness is in the file, not in the display.

An honest note on what this player claims

Total Video Player for Mac decodes HEVC — including the ten-bit Main10 stream that iPhone high dynamic range clips use — through macOS hardware decoding, and presents the picture the way macOS presents it to your display. It does not claim high dynamic range output of its own, and it makes no claim about wide colour gamut delivery to a television. If a clip looks different here than on the phone, the difference is the tone mapping performed by the operating system for the screen in front of you, which is the same mapping QuickTime Player applies. We would rather say that plainly than sell you a brightness claim the file cannot support.

For a much deeper treatment of ten-bit versus eight-bit, and of what a player can and cannot do about colour, the companion guide on playing 10-bit video on a Mac goes through it properly. The point to carry away here is narrower: an iPhone HDR file is an ordinary HEVC file with extra tags, and a Mac with hardware decode handles it without drama. If you are seeing something dramatic, the cause is almost always the export route described in the previous section — a converted copy really does look different, and it is the copy that is wrong, not the player.

Playing 4K iPhone Video Smoothly on a Mac

Bitrate is the number that determines whether playback feels effortless. iPhone 4K footage typically runs somewhere between fifty and a hundred megabits per second, which is a few hundred megabytes per minute and enough that a single minute of footage can be larger than an entire standard-definition film. Modern Macs move that much data without noticing, especially from internal storage. The problems appear at the edges: a clip read from a memory card through a slow reader, a library stored on a network share, an external drive connected through a hub that is also carrying a display, or a machine busy indexing a large import in the background. In each case the decoder is fine and the data path is not.

Frame timing is the second thing iPhone files do differently. Phone recording is variable frame rate in practice: the encoder emits frames as they arrive rather than on a perfect grid, so the intervals between timestamps are not identical. Most of the time this is invisible, because players schedule frames against the audio clock and smooth out the jitter. It becomes visible when a player assumes a fixed interval and drifts, which shows up as sound gradually separating from picture over a long clip. That is a different fault from the one where sound is late by the same amount from the first second, and the companion guide on fixing audio that drifts out of sync on a Mac separates the two properly. For iPhone footage specifically, the fix is usually to play in a player that respects the timestamps in the file rather than one that infers a rate.

Rotation is the third. A phone knows which way up it was held, and the file records that as orientation metadata rather than by physically rotating the stored pixels. A player that reads the metadata shows a portrait clip upright. A player that ignores it shows the same clip lying on its side, and the viewer concludes that the file is damaged. It is not. If you have a mixed batch — some clips shot upright, some sideways — the practical answer is either a player that honours the flag, or a rotate control you can apply at playback without touching the file. Total Video Player for Mac includes rotate and mirror controls for exactly this, and the guide on rotating a video while it plays on a Mac covers the workflow.

Finally, thermals. A MacBook Air with no fan will sustain 4K HEVC decode indefinitely because the work is done in dedicated silicon, but it will not sustain software decode of the same file for long before it slows down. If playback starts smooth and degrades after ten minutes, that pattern points at thermal throttling rather than at the file. If playback stutters from the first frame and only on one particular clip, the pattern points at the data path or at a file that was written by something other than the phone. Learning to read those two patterns saves a great deal of pointless conversion.

Reviewing iPhone Footage on a Mac: Speed, Loops, Stills, and Playlists

Once the files play correctly, the next problem is time. A day of shooting produces far more minutes than anyone wants to watch at normal speed, and the ordinary desktop players make this worse than it needs to be, because they treat every clip as something to be viewed from beginning to end. Reviewing is a different activity. You are looking for the two seconds where the focus landed, the frame where nobody blinked, the moment the light changed. That calls for different tools than playback.

Speed is the first. Running a clip at several times normal speed turns a twelve-minute take into a couple of minutes of scanning, and dropping back to normal when something catches your eye is a single keystroke in a player that supports it. Total Video Player for Mac goes up to ten times normal speed, which is fast enough to skim a long interview and still slow enough to see a cut. The guide on video speed control on a Mac covers the practical range and when each setting helps.

Loops are the second. When you find the moment, you usually want to see it again, and again, without hunting for the position each time. Setting an A and a B point around a two-second window and letting the player repeat it turns a fiddly scrub into a clean comparison — useful for judging whether a handheld shot is steady, whether a subject's eyes are open, or whether the autofocus hunted. The guide on looping a section of a video on a Mac explains the mechanics.

Stills are the third. A phone clip is often the only record of a moment, and pulling a single frame out of it gives you a photograph without opening an editor. Total Video Player for Mac can capture a frame as an image while the video plays, which is enough for a thumbnail, a reference, or a frame to compare against the next take. Combine that with the loop and you can step through a short window frame by frame and keep the one that works.

Playlists are the fourth, and the most underrated. A shoot is not one file, it is thirty files with names that tell you nothing. Building a playlist in shooting order, or in the order you want to show someone, converts a folder into a sequence, and the player can then move from clip to clip without you going back to Finder between each one. Total Video Player for Mac supports playlists for this reason. If the footage lives on a network drive rather than on the Mac, the same player opens it over SMB, NFS, SFTP, FTP, or WebDAV, so a shoot copied to a NAS behaves like a local folder. The guide on playing video from a NAS on a Mac covers the connection side.

Casting iPhone Video From a Mac to a TV

Sooner or later someone says "put it on the big screen", and there are two very different ways to do that from a phone-centric workflow. The first is to mirror the phone itself: AirPlay from the iPhone to an Apple TV or an AirPlay-capable television, which sends whatever is on the phone's screen. The second is to move the file to the Mac and cast the file from there. They look similar and behave nothing alike.

Mirroring is convenient and lossy. The phone encodes its entire display, letterboxes a landscape clip inside a portrait screen unless you rotate the phone, keeps the screen awake, and burns battery throughout. Quality is capped by what the mirroring encoder decides to send, and the television receives a picture of a phone rather than a video stream. It is fine for showing a clip to two people on a sofa. It is the wrong tool for watching a film you shot.

Casting the file from the Mac inverts the arrangement. The Mac reads the original, decodes it in hardware, and streams the finished picture over AirPlay, Chromecast, or DLNA. The television is a display and nothing more, so it does not need to understand HEVC or the QuickTime wrapper, and it does not need to be the same brand as anything else in the room. Rotation is applied before the stream leaves the Mac, which means portrait clips arrive upright. Subtitles, if you have loaded any, travel with the picture because the Mac is drawing them. The one thing that does not travel is the high dynamic range signal: the stream is standard range in practice, so a clip that looks punchy on the laptop will look flatter on the television. That is a property of casting, not of the file.

Both routes are covered in more depth in the guides on casting video from a Mac to a TV and on what to do when AirPlay shows a black screen. For iPhone footage the rule of thumb is simple: if you care about how it looks, cast the file from the Mac. If you care about showing something in fifteen seconds to the person next to you, mirror the phone.

An iPhone-to-Mac Playback Checklist

Everything above collapses into a short routine. Run it once over a batch of footage and the surprises stop.

  1. Take the originals, not a converted copy. Use AirDrop or Image Capture, or export from Photos with the setting that preserves the original. Skip messaging apps and skip Automatic export unless the destination genuinely needs a compatible file.
  2. Import into a plain folder. A folder you can point a player at beats a library that wants to index and sync. Name the folder after the shoot while you still remember what it was.
  3. Check one file's codec before you judge the rest. QuickTime Player's Movie Inspector, or Command-I in Finder, tells you whether you are looking at HEVC or H.264 and what the frame rate actually is.
  4. Test a slow-motion clip early. Compare the duration reported by the file with the duration you remember shooting. If it is a quarter or an eighth of what you expect, the timing instruction is being ignored and that clip needs to be rendered out.
  5. Set expectations for colour. A high dynamic range clip will look different on a standard-range monitor than on the phone. Judge the footage on the Mac against the Mac, and do not "fix" it by converting the file.
  6. Scan at speed, then slow down. Run long takes at several times normal speed, and drop to normal only where something is worth a proper look. Set an A-B loop around anything you need to compare.
  7. Pull stills as you go. Capture the frames worth keeping during the review rather than planning a second pass you will never do.
  8. Build a playlist before you cast. Order the clips the way you want them shown, then send the file stream to the television from the Mac instead of mirroring the phone.

None of those steps involve converting anything, which is the point. The format the phone writes is a format a Mac decodes natively, and the extra metadata is what makes the difference between footage that behaves and footage that seems broken. The only conversions worth doing are the ones where you deliberately want a different result: a compatible copy for an older television, a rendered slow-motion clip for a player that will not read the instruction, a trimmed section for sending to someone. Those are choices. Everything else is just a matter of using a player that reads the whole file.

Frequently Asked Questions About iPhone Video on Mac

Why does my iPhone slow-motion video play at normal speed on my Mac?

Because the file stores frames at 120 or 240 per second plus a separate instruction telling the player to spread them across a normal-speed timeline, and the player you are using is ignoring that instruction. QuickTime Player and Photos both honour it, so the clip looks correct there. A player that reads only the raw frame timing shows the same clip at capture rate, which is why four seconds of footage is suddenly over in one. To make the effect permanent, trim and export the clip from QuickTime Player or Photos so the frames are written across a normal timeline.

What format is iPhone video in when it lands on a Mac?

A QuickTime movie file with a .MOV extension, containing either HEVC (H.265) or H.264 depending on the camera setting you chose. High Efficiency produces HEVC with smaller files and is the default on recent models; Most Compatible produces H.264 with larger files and wider device support. On a Mac the distinction is mostly about decode cost rather than compatibility, because macOS decodes both natively. The wrapper matters only when the file leaves the Mac for a television, an Android phone, or an older Windows machine.

Will an iPhone high dynamic range clip look right on a Mac?

It will look correct in the sense that macOS reads the colour tags and tone maps the picture for whatever display is attached, which is what QuickTime Player does and what Total Video Player for Mac does. It may not look identical to the phone, because the phone knows its own screen and a laptop or external monitor has different capabilities. Highlights will roll off earlier on a standard-range panel. That difference is the operating system mapping the file, not a fault in the clip or the player.

Does AirDrop reduce iPhone video quality when sending to a Mac?

No. AirDrop transfers the file as recorded, so what arrives on the Mac is the capture itself, codec and metadata intact. The place quality gets lost is on the other routes: messaging apps recompress and often downsize, and exporting from Photos with the Automatic setting can convert the codec and remap the brightness. If you want the original, AirDrop or Image Capture will give it to you, and exporting from Photos with the original setting will as well.

Why does my iPhone video appear sideways or rotated on my Mac?

Because the phone records which way up it was held as orientation metadata rather than by rotating the stored pixels, and the player you are using is not reading that metadata. The picture is intact; it is simply being drawn in the wrong orientation. Use a player that honours the flag, or apply a rotation at playback — Total Video Player for Mac has rotate and mirror controls for exactly this case, and neither changes the file.

Can a Mac play iPhone 4K footage at 60 frames per second without converting it?

Yes on any Mac with hardware HEVC decoding, which covers Apple Silicon machines and Intel models from roughly the seventh generation onward. The clips open and play as they are, because 4K HEVC is a format macOS decodes in dedicated silicon rather than in software. If playback stutters on a machine that should handle it, look at the data path before the codec: a slow card reader, a network share, a hub, or a background import will all cause the same symptom without anything being wrong with the file.

How do I get a still frame from an iPhone video on a Mac?

Pause on the frame you want and capture it as an image from inside the player. Total Video Player for Mac includes a screenshot control that saves the current frame, which is faster than opening an editor and exporting a still, and it is good enough for a reference, a thumbnail, or a comparison between takes. If you are choosing between several similar moments, set an A-B loop around the window and step through it rather than scrubbing back and forth.

Is it better to cast iPhone video from the phone or from the Mac?

From the Mac, if you care about the result. Mirroring the phone sends an encoded picture of the screen, letterboxes landscape clips inside a portrait frame, keeps the display awake, and burns battery. Casting the file from the Mac means the Mac decodes the original and streams the finished picture over AirPlay, Chromecast, or DLNA, so the television needs no knowledge of HEVC, rotation is already applied, and subtitles travel with the image. Mirror the phone only when you want to show something in the next fifteen seconds.

Play iPhone Video on a Mac Without Converting It

Total Video Player for Mac opens MP4, MKV, MOV, AVI, M4V, MPEG, WMV, FLV, WebM, MTS, M2TS, and TS, decodes 4K UHD in hardware on Apple Silicon, plays from SMB, NFS, SFTP, FTP, and WebDAV, runs a DLNA Media Server, and casts over AirPlay, Chromecast, and DLNA — with dual subtitles, subtitle styling, playlists, 10x speed, A-B loop, rotate and mirror, and screenshot capture. Audio support covers MP3, AAC, AC3, FLAC, WAV, WMA, OGG, and M4A.