You notice it in a quiet scene first. Someone closes a car door, and the thud arrives after the door has already settled. Or a comedian delivers a line, the audience laughs, and the laugh sounds like it belongs to the previous joke. Audio that sits slightly late is oddly harder to tolerate than audio that is simply missing, because your brain keeps trying to reconcile it and never manages. The instinct is to blame the file, or the app, or the speakers. Sometimes that is right. More often the file is fine, the app is fine, and the two streams inside a perfectly ordinary video have quietly stopped agreeing about time. That disagreement can happen in three completely separate places on a Mac: in the output path the sound travels through, in the clocks the player uses to keep the streams aligned, or in the timestamps baked into the file itself. Each one leaves a distinct fingerprint, and each one is fixed by touching a different thing. This guide sorts them in the order that costs you the least time, with checks you can run in under a minute each.
Why Audio and Video Drift Apart on a Mac
A video file is not one thing. It is a container holding at least two independent streams, one of pictures and one of sound, plus a table of timestamps telling a player when each piece is supposed to appear. Nothing inside that file physically binds a frame to the syllable spoken over it. The binding is an agreement, and every player has to keep re-making that agreement, thousands of times a minute, for as long as the file runs. When the agreement holds, you never think about it. When it slips, you get lips that move a fraction early or a fraction late, and no error message anywhere.
The reason the agreement is fragile is that the two streams are consumed at completely different rates by completely different machinery. Audio is a stream of samples flowing into a hardware buffer at a fixed rate, and that buffer cannot be starved without producing an audible click or a gap. Video is a sequence of images that has to be decoded, scaled, and presented on a display refresh boundary, and it is entirely acceptable for a frame to be dropped or repeated when the machine is busy. Sound is rigid. Pictures are flexible. That asymmetry is the root of nearly every sync problem you will ever troubleshoot, because it means the system will almost always protect the audio and let the video bend.
On a Mac the problem has a second layer that Windows and televisions do not: the number of ways sound can leave the machine. Built-in speakers, a USB interface, an HDMI cable into a receiver, a display with its own speakers, Bluetooth headphones, a HomePod, an AirPlay receiver across the room. Every one of those paths has a different internal buffer, a different amount of processing, and a different idea of how long it takes a sample to become sound in the air. A player can only compensate for latency it has been told about. When an output device under-reports its delay, the picture arrives on time and the sound arrives late, and the file gets blamed for something the route did.
So the first useful move is to stop thinking of this as "the video is out of sync" and start asking which of three families you are in. Fixed offset means the lag is the same at the opening credits and at the final scene. Progressive drift means it starts near zero and grows, so a two-hour film is unwatchable by the halfway mark. Timestamp damage means the offset is specific to one file, or to files produced by one camera or one editor, and follows them around every player on every machine. The three have almost nothing in common. Once you know which one you have, the fix is usually a couple of minutes.
The Three Clocks a Mac Video Player Reconciles
To fix sync you have to know what is being synchronised, and the honest answer is three clocks, not two. The audio clock is the sample counter inside your output device. It advances at the rate the hardware is actually consuming samples, which is not exactly the nominal rate printed on the box: real crystals run a few parts per million fast or slow, and that tiny error is enough to accumulate into a visible offset over a long film. The video clock is not a clock at all in the hardware sense; it is the presentation timestamps in the file, mapped onto the display's refresh boundaries. The system clock is the wall clock the player uses to schedule work, and it is the one that matters when a decode takes longer than expected.
Every player has to choose a master. The most common arrangement is audio as master: the audio device's counter drives playback, and video is fitted to it by duplicating or dropping frames when the two disagree. This is why a machine that is struggling shows stutter rather than echo. A second arrangement is video as master, where the picture leads and the audio is gently resampled to keep up, which is smoother for the picture and can introduce a faint pitch shift if the correction is large. A third is external clock, used when the audio and video are locked to a device such as a receiver or a capture interface. When the master changes mid-playback, or when two components disagree about who is master, you get exactly the symptom this page is about.
Buffers are where the practical damage happens. An audio buffer is small, typically a few tens of milliseconds, because large buffers make the interface feel unresponsive. A video pipeline buffer is much larger, often a few hundred milliseconds, because decoding, scaling, and colour conversion all take time and the player would rather run ahead than risk a gap. That asymmetry is deliberate, and it is also one of the ways sync goes wrong: if the video pipeline fills up and then drains, the picture can jump forward relative to sound that never paused. A player that handles this well adjusts its video scheduling continuously. A player that handles it badly produces a visible lurch every few minutes.
Then there is the delay that nobody tells you about. Bluetooth headphones introduce a transmission delay that depends on the codec and the hardware, and the operating system compensates for the figure the headphones report. When a device under-reports, the compensation is short and the sound comes out late. Televisions do the same through their own processing: motion smoothing, noise reduction, and upscaling all add frames of delay to the picture, and a set that is slow to display needs its audio delayed to match. Many televisions expose a lip-sync or audio-delay control for exactly this reason, and it is the correct place to fix a lag that only exists when you watch through the television. Casting adds a third buffer, because the sender, the network, and the receiver each hold a piece of the timeline.
One more distinction earns its own paragraph, because it fools people constantly. Video running late and audio running late look similar and are opposites. If the sound is behind the lips, either the audio path added latency or the video path got ahead. If the sound is ahead of the lips — you hear the impact before you see it — the video path is late, which almost always means decode load, display scaling, or a refresh-rate mismatch. Treating those two as one problem is why so many people spend an evening adjusting the wrong end of the chain.
Read Your Symptom: A Diagnosis Table for Mac Audio Sync
Before changing a setting, spend thirty seconds deciding what you are actually seeing. The table below maps the way the fault behaves to the mechanism behind it and to the fastest test that confirms it. Read the "fastest test" column as a single action, not a procedure — each one is designed to move you from "something is wrong" to "this layer is wrong" in well under a minute.
| What you notice | What is actually happening | Usual culprit | Fastest test |
|---|---|---|---|
| Same lag from the first second, never changes | A fixed delay was added somewhere in the output path | Bluetooth route, television processing, USB interface buffer, split audio and video devices | Switch output to the Mac's built-in speakers and replay the same moment |
| Starts in sync, slides further out the longer it plays | Two clocks are running at slightly different rates | Sample-rate conversion, a device with an inaccurate clock, casting to a receiver with its own timebase | Seek back ten seconds; if it snaps into sync and drifts again, it is drift |
| Sound is early, picture is late | The video pipeline is behind, not the audio | Heavy decode load, scaled display mode, high refresh rate, background export | Quit other work and drop the display to its default resolution |
| Out of sync at the start, then settles after a couple of seconds | Buffers are filling at different speeds during start-up | Receiver handshake, network jitter on a cast, a cold audio device waking up | Pause for three seconds, then resume; if it converges, it is buffering |
| Fine for minutes, then a lurch or a jump | The player corrected a growing error in one visible step | Clock drift being corrected in bursts rather than continuously | Note the interval between lurches; regular spacing means drift correction |
| One file only, every player, every machine | The timestamps inside the container are wrong | Variable-frame-rate camera footage, an editor's edit list, a bad remux | Open a different file in the same player; if only this one misbehaves, it is the file |
| Only when casting or mirroring to a TV | The receiver is displaying late and not delaying audio to match | Television picture processing, a wireless link with jitter, mirroring instead of casting a file | Play the same file locally first, then cast; if only the cast is off, it is the receiver |
Two rows in that table catch most people, and they are the two that look most alike. A constant offset that never changes is a latency problem, and latency lives in the hardware path — no player can undo a delay it was never told about, though a good one can be told. A growing offset is a rate problem, and rate problems live in clocks. The third row, where the picture lags behind the sound, is the one people misdiagnose as an audio problem for hours, because the sound "feels" wrong. It is not the sound. The sound is perfectly on time and the picture is behind it.
There is also a fifth family that deserves a mention even though it is rarer: an offset that appears only after a specific action, such as pausing for a long time, dragging the window to another display, or switching output mid-playback. That pattern points at state rather than latency or rate — a buffer that was rebuilt without re-stamping, or a device that renegotiated its format while the player kept its old timeline. The fix there is boring and reliable: stop playback, switch the output, and start the file again from the beginning rather than resuming, so both streams are rebuilt against the same device state.
Fixes on the Mac Side: Output, Bluetooth, and Sample Rate
Start with the output path, because it is both the most common cause of a fixed offset and the easiest to test. Open System Settings, go to Sound, and look at what the output device actually is. On a laptop with an external monitor, the answer is often not what you expect: the display may have registered itself as an audio device and taken over the output, so the sound is coming from the monitor's speakers with the monitor's processing, while the picture comes from the same cable with a different amount of delay. Switching the output back to the built-in speakers and replaying the same ten seconds tells you immediately whether the fault is in the route or in the file.
If the offset disappears with the built-in speakers, work outward. A USB audio interface usually reports its latency honestly, but its buffer size is configurable and a large buffer adds a constant delay. An HDMI path into a television or receiver is the worst offender, because the far end adds processing that the Mac cannot see: motion interpolation alone can add several frames. A split path — picture over one cable to a display, sound over a different cable or a Bluetooth link to something else — is guaranteed to be out of sync by exactly the difference between the two delays, and that is a design fault, not a bug. Keep audio and video on the same physical route and most fixed offsets vanish.
Bluetooth deserves its own paragraph because it is the single most common source of "my Mac's audio is late" complaints, and because it cannot be fixed by fiddling with the player. Wireless audio is buffered for retransmission, so the sound you hear left the Mac noticeably earlier than the frame you see. macOS compensates using the latency figure the headphones declare, and that figure is sometimes optimistic. The test is physical: plug in a wired pair of headphones or switch to the built-in speakers and replay the moment. If the sync returns, nothing is wrong with the file, the player, or the Mac. The honest options are a wired connection, a pair that reports its latency accurately, or accepting the offset for casual listening and using wires for anything where lips matter.
Sample rate is the subtlest item in this section, and worth understanding because it explains drift rather than offset. If a file was recorded at the older CD rate and the output device is locked to a different rate, macOS resamples in the background. Resampling is generally transparent, but it introduces both a small constant delay and a small rate difference, and the rate difference is what accumulates. Over a two-hour film, a few parts per million becomes a visible offset by the closing act. Devices that expose a sample-rate control — audio interfaces, some DACs, the Audio MIDI Setup utility — should be set to match the material you are playing. In Audio MIDI Setup you can also combine several devices into one aggregate device and enable drift correction, which forces the members to follow a single clock instead of each drifting on its own.
Display settings belong here too, even though they are not audio. If the picture is the thing running late, the cause is usually that the video pipeline cannot keep up: a scaled resolution the window server has to render, a refresh rate the panel cannot hold, or a decode that fell back to software. Switching the display to its default resolution and a standard refresh rate, closing other heavy apps, and letting the hardware decoder do the work will bring the picture forward without touching a single audio setting. On Apple Silicon, H.264 and H.265 playback is handled by the media engine, which is both faster and far more consistent than a software path — consistency matters here as much as speed, because a decoder that occasionally spikes is exactly what produces intermittent desync.
When the File Itself Is Wrong: Timestamps and Mac Playback
If the offset follows one file around — wrong in every player, on every Mac, at every moment — stop troubleshooting the machine. The container is lying about time, and no player can invent the truth. The most common source is variable-frame-rate footage. Phones, action cameras, and screen recorders often write frames at irregular intervals and then describe them with timestamps that do not match the cadence a player expects. A player that honours the timestamps shows the correct timing; a player that assumes a constant rate shows drift. When the two disagree, you get a file that looks fine in one app and hopeless in another, which is a strong hint that the timestamps are unusual rather than wrong.
The second source is the edit list. When a clip is trimmed, the editor may not rewrite the audio; it may instead record an instruction that says "start the audio this many samples late," and rely on the player to honour it. Players that ignore edit lists play the untrimmed audio against the trimmed picture, which produces a constant offset equal to the trim. This is why a file can be perfectly in sync in the editor that made it and out of sync everywhere else. The same mechanism produces the classic "audio is a fraction of a second late after I cut the intro" complaint, and the fix is on the export side: export with the edit list applied rather than referenced.
The third source is encoder delay. Modern audio encoders need a few milliseconds of run-up, and they record that run-up as a fixed priming delay so the decoder can discard it. If the delay is recorded correctly, everything is fine; if the muxing tool dropped that metadata, every copy of the file will be late by the same small amount — usually just enough to be annoying and not enough to be obvious. Remuxing the file with a tool that preserves the delay metadata fixes it, and re-encoding the audio fixes it too, at the cost of a generation of quality.
There is a fourth case that is not damage at all: pull-down and frame-rate conversion. Material shot at one rate and presented at another is often retimed, and the audio is retimed with it. If the retiming is done correctly the result is in sync; if a tool converted the video and left the audio alone, the offset grows steadily and looks exactly like clock drift. The tell is that the drift is large and predictable rather than tiny and slow, and that it appears in every player on every machine. That is a conversion problem, and the answer is to convert again with a tool that handles both streams.
What a player can honestly do about all four is limited by design: it renders the timeline the container declares, and it does so accurately. That is not a limitation to work around, it is the contract. The right response to a file with damaged timestamps is to repair the file — remux it, re-export it, or convert it with a tool that rewrites the timing — and then play the repaired version. Spending the evening adjusting a player to compensate for one broken file means every other file you own will now be wrong.
How to Fix Out-of-Sync Audio on Mac, Step by Step
Work down this list and stop at the first step that changes the symptom. The order runs from the cheapest test to the most invasive, and each step eliminates one family of causes so that later steps are informed rather than hopeful. If you only have a minute, do steps one to four; they resolve the majority of cases.
- Measure the offset instead of estimating it. Pause on a frame where something visible makes a sound — a hand hitting a table, a door closing, a clapperboard — and note whether the sound is early or late by roughly how much. "About a quarter second late" and "about a quarter second early" send you to opposite ends of the chain, and guessing wrong costs more time than measuring.
- Switch the output to the Mac's built-in speakers. Replay the same moment. If the sync is now correct, the fault is entirely in the output path — Bluetooth, HDMI, a monitor with speakers, or a split audio route — and you can skip everything below except step seven. If it is still wrong, the fault is in the file or in the player's scheduling.
- Play a different file in the same player. A file you know is well authored, from a different source. If that one is in sync, you have a file problem, not a Mac problem, and the answer is to repair or re-export the container rather than to change settings.
- Seek back ten seconds and watch what happens. If the offset resets to near zero and then grows again, you are looking at clock drift: two rates disagreeing. If it returns to exactly the same offset, you are looking at a fixed latency. This single observation separates the two biggest families in the table above.
- Take the load off the video pipeline. Quit exports, browser tabs playing video, and anything else using the hardware decoder. Set the display to its default resolution and a standard refresh rate. Then replay. If the picture catches up, the problem was decode or display latency all along, and hardware decoding of H.264 and H.265 on Apple Silicon is the durable fix.
- Rebuild the audio route deliberately. Choose one output device, set its sample rate to match the material, and if you are using an aggregate device, enable drift correction so its members follow a single clock. Then start the file from the beginning rather than resuming, so both streams are stamped against the new device state instead of the old one.
- Replace the wireless link when lips matter. Bluetooth audio is buffered by design, and its latency compensation depends on what the headphones report. A wired pair or the built-in speakers is the only reliable test and, for interviews, lectures, and anything with close-up faces, the only reliable arrangement.
- Test locally before you blame the cast. If the file is perfect on the Mac and late on the television, the Mac is finished with its job. Look at the television's own lip-sync or audio-delay control, its picture-processing modes, and whether you are mirroring a desktop instead of casting a file. Mirroring adds an encoder to the chain and has no timestamps to negotiate with; casting a file does not.
Casting Without Desync: AirPlay, Chromecast, and DLNA From a Mac
Casting is where sync problems get interesting, because the picture and the sound stop travelling together. When a Mac plays a file locally, both streams come out of the same machine and the player can align them against one clock. When you cast, the player becomes a sender: it either pushes a stream to a receiver or hands the receiver a reference and lets it pull. From that moment there are two or three buffering stages in the path, and the receiver is responsible for re-joining sound and picture at the far end. Most of the time it does this well. When it does not, the offset usually comes from the receiver's own picture processing rather than from the network.
The three transports behave differently enough to be worth separating. AirPlay sends audio and video as separate streams with their own timing information, and the receiver reassembles them; this is robust, and it is also why an AirPlay session can show a perfectly good picture with late sound when the television is applying heavy motion smoothing. Chromecast usually asks the receiver to fetch the media itself, so the sender's job ends early and the receiver's buffering dominates — which means network jitter shows up as start-up delay rather than as a permanent offset. DLNA push behaves similarly, with the added wrinkle that the renderer may decide to transcode, and a renderer that transcodes is a renderer that can get the timing wrong in ways you cannot see from the Mac.
| Transport | Where sound and picture are re-joined | Typical sync behaviour | Where to look when it slips |
|---|---|---|---|
| Playback on the Mac | Inside the player, against the audio device's clock | Most stable; offsets come from the output route | Output device, sample rate, decode load |
| AirPlay to a TV or Apple TV | On the receiver, from separately timed streams | Reliable control path; picture processing can add delay | Television lip-sync setting, picture modes |
| Chromecast | On the receiver, which buffers and plays independently | Start-up delay is normal; permanent offset is not | Receiver buffering, link quality, format support |
| DLNA to a renderer | On the renderer, sometimes after transcoding | Varies most between devices | Renderer transcode settings, receiver audio delay |
| Screen mirroring | Nowhere — the receiver shows what it is given | Adds encoder latency, no timestamp negotiation | Use a cast instead of a mirror for files |
The practical rule that falls out of that table is simple: cast the file, do not mirror the desktop. A mirrored display is a live encode of whatever the Mac is drawing, with no timing metadata for the receiver to reconcile, so any latency in the encoder or the receiver lands directly on the lips. A cast file is a stream with timestamps, and the receiver has something to work with. If a film is out of sync when mirrored and correct when cast, nothing was ever broken — the wrong transport was being used for the job.
This is the arrangement Total Video Player for Mac is built around. The app opens the file — MP4, MKV, MOV, AVI, M4V, MPEG, WMV, FLV, WebM, MTS, M2TS, or TS, with the audio inside it including MP3, AAC, AC3, FLAC, WAV, WMA, OGG, and M4A — and decodes it on the Mac, 4K UHD included, with H.264 and H.265 handled by the Apple Silicon media engine. The picture is then sent over AirPlay, Chromecast, or DLNA. Because the Mac does the decoding, the receiver never has to guess at a format, and because the streams leave the app already timed against one clock, there is only one place for a timestamp argument to happen. Files can stay on the network too: SMB, NFS, SFTP, FTP, and WebDAV playback means a film does not have to be copied locally first, and the built-in DLNA Media Server covers receivers that would rather browse a folder than accept a push. If you want the transport comparison in more depth, the casting guide covers it, and the AirPlay troubleshooting page handles the case where the picture never appears at all.
Everything else that makes a player worth living with is present as well: dual subtitle tracks for watching with a translation, subtitle styling so captions stay readable from the sofa, playback speed up to 10x for lectures and interviews, A-B loop for a passage worth hearing twice, playlists for a whole series, rotate and mirror for footage that arrived sideways, and a screenshot control for a frame you want to keep. The paid Pro edition sets out the higher tier, and the product page has the full feature list. If your problem is silence rather than delay, the no-sound guide is the closer match; if the picture itself stutters while the sound runs on, the 4K stutter guide takes that apart.
Frequently Asked Questions About Audio Sync on Mac
Why is the audio delayed on my Mac when I use Bluetooth headphones?
Because wireless audio is buffered for retransmission, so the sound you hear left the Mac later than the frame you see. macOS compensates using the latency figure the headphones declare, and that figure is sometimes optimistic. The test is physical: switch to the built-in speakers or a wired pair and replay the same moment. If the sync returns, the file and the player are fine and the wireless link is the whole story.
Why does audio start in sync on my Mac and then drift?
Two clocks are running at slightly different rates. The audio device consumes samples at its own crystal's pace, which is never exactly nominal, and over a long film a few parts per million becomes a visible offset. Seeking back ten seconds re-aligns the streams and the drift starts again from zero, which is the signature of a rate problem rather than a fixed delay. Matching sample rates and enabling drift correction on aggregated devices reduces it.
Why is only one video file out of sync on my Mac?
Because that container's timestamps disagree with its own content. Variable-frame-rate footage from phones and action cameras, an editor's edit list that a player ignores, a lost encoder priming delay, or a conversion that retimed the video and left the audio alone all produce this. When the fault follows one file to every player and every machine, the machine is not the problem and the file needs remuxing or re-exporting.
Why do I hear the sound before I see the picture on my Mac?
That is a late video pipeline, not an early audio one. The audio clock is keeping perfect time while the picture is stuck behind decode work, display scaling, or a refresh rate the panel cannot hold. Quit background encodes, set the display to its default resolution and a standard refresh rate, and let hardware decoding handle H.264 and H.265. The picture catches up; the audio never moved.
Is there a lip-sync setting in macOS I can just adjust?
Not a global one. macOS exposes sample rate and drift correction in the Audio MIDI Setup utility, and it relies on each output device to report its own latency, but it does not offer a system-wide audio delay slider. A delay that only appears through a television is normally corrected on the television, which is where the extra processing is being added. A delay that appears only on one file is corrected in the file.
Does casting video from a Mac make audio sync worse?
It can, though usually because of the receiver rather than the network. Casting adds buffering at the sender, on the link, and on the receiver, and the receiver is the stage that re-joins sound and picture. A permanent offset on a cast is typically the television applying picture processing without delaying its audio to match. Network jitter more often shows up as start-up delay or stutter than as a steady lag.
Should I mirror my Mac to the TV or cast the file?
Cast the file. Mirroring sends a live encode of your desktop with no timing metadata for the receiver to reconcile, so encoder latency lands directly on the lips. A cast file carries timestamps, and the receiver has something to align against. Mirroring is the right tool for showing a desktop, a slide deck, or an app; it is the wrong tool for watching a film.
Can a video player correct a file with broken timestamps?
Only by guessing, which is worse than not guessing. A player renders the timeline the container declares, and it does so accurately; when that timeline is wrong, a compensating offset that fixes this file will break every other file you own. The durable answer is to repair the container — remux it, re-export it from the editor, or convert it with a tool that rewrites the timing — and then play the repaired version.
Keep Picture and Sound Together on Mac
The reassuring part of this problem is how quickly it becomes obvious once you stop treating it as one fault. A lag that never changes is latency, and latency lives in the route — Bluetooth, HDMI, a monitor, a split audio path. A lag that grows is a rate disagreement, and rate disagreements respond to matched sample rates and drift correction. A lag that follows one file is a damaged timeline, and the file is what needs repairing. And a lag that only exists through the television is the television's own processing, which has its own control for exactly this. Four tests, each under a minute, and you know which of those you have.
What is worth avoiding is the habit of compensating at the wrong layer. Adjusting a player so one broken file looks right means every healthy file is now wrong. Buying a different pair of headphones to fix a drift that was never wireless to begin with wastes an afternoon. Assuming the Mac cannot decode the file, when the real complaint is that the television is displaying it late, sends people shopping for hardware they do not need. The measurement comes first, and the measurement is almost always just "is the sound early or late, and does the answer change as the film runs".
When the answer is that the file is fine and the Mac plays it correctly, the remaining work is about keeping it that way: decode on the machine that has the hardware for it, keep the output route honest, and cast the file rather than the desktop when the screen is across the room. That is not a workaround for a sync problem. It is the arrangement that avoids most of them.
Play It on the Mac and Keep Sound in Step
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.