Video Player Guides

How to Load External Subtitles on Mac

A subtitle file is a second document that has to agree with your video about two things: that it belongs to this film, and what time it is. Get either one wrong and you get no text, scrambled text, or text that slowly slides out of step. Here is how each of those happens on a Mac — and how to fix it in a few minutes instead of an evening.

Download for Mac See the Mac player

Total Video Player for Mac. Apple Silicon and Intel.

Almost everyone who has ever hunted for subtitles has met the same three disappointments. The file sits in the folder and nothing appears on screen. Or the text appears, but it reads like a corrupted transmission — accented letters replaced by symbols, whole scripts reduced to boxes. Or the subtitles are perfect for the first ten minutes and then drift, so that by the end of the film the words arrive long before the mouths move. None of those are player bugs and none of them are mysterious. They are the three ways two separate documents can disagree: about identity, about character encoding, and about time. This guide takes them one at a time, with the Mac specifics that actually matter — how Finder hides extensions, why TextEdit saves the wrong format, why a file name that works on your laptop fails on a network share, and why a constant offset and a growing drift need completely different repairs.

It also covers the part most guides skip: what happens to your carefully matched subtitle file the moment you stop watching on the laptop and send the picture to a television. That is where external subtitle files most often quietly stop working, and the reason is structural rather than fixable by fiddling with settings.

Why a Subtitle File and a Video File Are Two Problems on a Mac

Video is a container full of compressed pictures and sound. Subtitles, in the external case, are a plain text document with timestamps attached to lines of dialogue. The two never speak to each other directly. The player opens the video, then goes looking for text, then holds the text against the video's clock and draws whichever line is current. Every failure mode in this article lives inside that sentence, so it is worth unpacking it into three separate questions.

The first question is identity: does the player know that this text file belongs to this video? Nothing in an SRT file says which film it is for. The bond is made entirely by naming and location — same folder, matching name — or by you pointing at the file by hand. When the bond fails, the symptom is silence: no subtitles at all, and no error message, because from the player's point of view there was never anything to load.

The second question is encoding: does the player know how to turn the bytes in that text file into characters? A text file is a sequence of numbers. Which letter each number means depends on an encoding, and the encoding is not always stored inside the file. When the player guesses differently from whoever wrote the file, every byte still gets read — it just gets read as the wrong letter. This is why garbled subtitles look like a cipher rather than like damage. The file is intact; the key is wrong.

The third question is time: does the text agree with the video about when each line should appear? An SRT cue says, in effect, "from this moment to that moment, show this line". If the video's timeline was built at a different frame rate, or was cut differently, or starts with a studio logo the subtitle author never saw, the cue times are still valid numbers pointing at the wrong moments. The text arrives — early, late, or gradually further off — and looks like carelessness when it is arithmetic.

Two more distinctions save time before we go further. An external subtitle is a separate file next to the video; an embedded or internal subtitle is a track inside the video container, and it cannot get lost because it travels with the film. And a text subtitle can be re-styled, re-timed, and re-encoded, while some tracks are pictures of words rather than words — those cannot be searched, resized, or corrected, only displayed or ignored. If the track you are fighting with is made of images, most of this article will not apply, and no amount of renaming will help.

The triage that solves most cases

No subtitles at all → it is a naming or location problem. Subtitles that look like nonsense → it is an encoding problem. Subtitles that are readable but mistimed → it is a timeline problem. Decide which of the three you have before you touch anything, because the fixes have nothing in common and the wrong one makes the file harder to rescue.

The Three Subtitle Formats You Will Meet on a Mac: SRT, ASS, VTT

Subtitle formats differ in how much they try to control, and that single axis predicts almost everything about how they behave. At one end is SRT, which controls only timing and text. At the other is ASS, which is closer to a tiny page-layout language with fonts, positions, colours, and animation. VTT sits between them, designed for the web, where the browser does the drawing.

SRT — SubRip — is the oldest and the most universally understood. Each cue is a block: an index number, a timecode line with hours, minutes, seconds and milliseconds separated by a comma, then one or more lines of text, then a blank line. That is the entire specification in practice. There is no place to say "this line should be italic and positioned at the top"; italics survive only because most renderers interpret simple markup tags if they happen to be present. In exchange for that poverty, SRT is read by essentially everything, on every platform, including televisions and set-top boxes. When a subtitle file has to work somewhere you cannot test, SRT is the safe choice.

ASS — Advanced SubStation Alpha, with its older sibling SSA — is a script format. The file opens with sections that declare the script's resolution, the styles it will use (font, size, primary and outline colour, bold, italic, shadow, alignment, margins), and then a list of dialogue events that reference those styles by name and can add inline overrides for position, rotation, fade, and karaoke timing. This is the format fansub groups use because it can put a sign's translation next to the sign, colour a speaker's lines to match their shirt, and time individual syllables. A player that understands the header renders all of that; a player that does not still shows the text, usually as plain lines in its own default style, which is a graceful enough fallback that many people never realise the file was richer than what they saw.

The catch with ASS is fonts. A style can name a typeface, and if that typeface is not installed on your Mac, the renderer substitutes something else. Complex scripts can then break: glyphs land in the wrong place, spacing collapses, or a font with no coverage for the language turns whole lines into empty boxes. It is worth knowing this before you conclude that the file is corrupt. The other catch is resolution: an ASS script is authored against an assumed frame size, so on a very different display size, positioned signs can drift towards the edges or overlap the picture in ways the author never saw.

VTT — WebVTT — is the web's subtitle format, and it looks like SRT wearing a web developer's clothes. The file begins with a mandatory header line reading WEBVTT, then cues whose timecodes use a dot before the milliseconds instead of a comma, and hours are optional. The interesting part is what comes after the timestamp: cue settings such as line position, alignment, and region, written as space-separated key and value pairs. VTT also supports voice spans that name the speaker, and class names that a stylesheet can style. Because it was designed to be parsed by browsers, it is strict about its grammar in a way SRT never was — a stray blank line or a missing header can make a whole file fail to load rather than load imperfectly.

Beyond those three, a handful of others turn up often enough to recognise. MicroDVD files use the .sub extension and time their cues by frame number rather than by clock time, which means they only make sense if you also know the frame rate they were authored against — a genuinely confusing format to receive by accident. SAMI files use the .smi extension and wrap their cues in HTML-like tags. TTML is XML and appears mostly in streaming and broadcast workflows. And plenty of subtitle files arrive with a .txt extension because a website or a messaging app renamed them in transit; the contents are still SRT and the fix is a rename, not a conversion.

Format What it can carry, and where it usually comes from What to expect on a Mac
SRT (.srt) Timing and text, plus simple italics and bold in practice. The usual arrival route is a subtitle archive, a disc rip, or a broadcast caption file exported to text. Loads everywhere. There is no styling to lose, which is exactly why it is the most reliable thing to convert to.
ASS / SSA (.ass, .ssa) Styles, fonts, positions, fades, karaoke timing, and per-line overrides. Comes from fansub releases and from anything where on-screen signs need translating. Renders fully in a player that supports the format. In a simpler player the text still appears, but flat and centred.
WebVTT (.vtt) Cue settings, speaker names, class hooks, and regions. Arrives from web video, streaming platforms, and captioning tools. Reads cleanly in players that support it. The grammar is strict: one malformed line and the whole file may refuse to load.
MicroDVD (.sub) Cue text keyed to frame numbers rather than to time. Turns up from older rips and European subtitle sites. Needs the matching frame rate to mean anything. If the cues land nowhere near the dialogue, this is why.
SAMI (.smi) Text wrapped in HTML-like tags. Legacy Windows sources and some Asian broadcast material use it. Support varies between players. Converting to SRT is usually faster than arguing with it.
TTML / DFXP (.ttml, .xml) Structured text with layout and styling expressed in XML, from streaming deliveries and broadcast masters. Not what a desktop player expects. Treat it as a source to convert rather than a file to drop in.

One rule of thumb from that table. If a subtitle file misbehaves and you cannot see why within a couple of minutes, convert it to SRT and try again. The conversion throws away styling, which you may miss, but it also throws away every grammar quirk, encoding declaration, and resolution assumption that could be causing the trouble. Getting a readable, correctly timed file first and worrying about typography second is the order that wastes least time. When you do want the typography back, our guide to changing subtitle font and style on a Mac covers the rendering side.

Encoding: Why Subtitle Text Turns to Garbage on a Mac

Here is the mechanism in one paragraph. A text file stores characters as numbers, and there is more than one agreed mapping between numbers and characters. UTF-8 is the modern one and can represent every writing system; older single-byte encodings covered one region each, with the same number meaning a different character depending on which region's table you used. A subtitle file authored in Central Europe on a Windows machine may well be in one of those legacy encodings, with no declaration inside the file saying so. macOS, and most software on it, assumes UTF-8 by default. Read legacy bytes as UTF-8 and every character outside plain English comes out wrong — and because the wrong interpretation often produces invalid sequences, you get replacement symbols rather than plausible-looking text.

The symptom is distinctive once you know it. Accented Latin letters become pairs of odd symbols, curly quotation marks and dashes become gibberish, and non-Latin scripts collapse into runs of boxes or question marks. Nothing about the timing is wrong; the cues appear exactly when they should, reading like a transmission from a broken machine. That combination — right place, wrong characters — is diagnostic. It is an encoding problem, and it is almost always fixable without finding a different subtitle file.

The repair depends on whether you want to fix this file or all future ones. For a single file, open it in a text editor that lets you choose the encoding, then save it as UTF-8. On a Mac, TextEdit can do it, but there is a trap that catches people constantly: TextEdit's default save format is rich text, and a subtitle file saved as rich text is no longer a subtitle file. The command you need is Format → Make Plain Text before saving, and then confirm the extension is .srt rather than .rtf when the save dialog appears. If you skip that step, the player will either refuse the file or show the formatting codes as dialogue.

For stubborn files, the Terminal is faster and more certain. macOS ships the file command, which will tell you what it thinks the encoding is, and iconv, which converts between encodings. Reading the file's reported charset first, then converting from that charset to UTF-8, is a two-command job and removes all guesswork — and it works on files that TextEdit opens as a wall of symbols. If the reported charset looks like an ISO or Windows codepage rather than UTF-8, that is your answer, and you can stop looking for a different subtitle source.

Two smaller encoding issues are worth knowing about. A byte order mark at the very start of a file — an invisible signature some Windows tools write — can confuse a strict parser into treating the first cue number as part of the text, so the very first line fails to display while everything after it works. And line endings differ between platforms: Windows files end lines with a carriage return and a line feed, Unix files with a line feed alone. Most modern parsers accept both, but a file that displays as one long paragraph of dialogue is almost certainly a line-ending problem rather than a corrupt download.

How a Mac Player Decides Which Subtitle File Belongs to Which Video

Automatic subtitle matching is a naming convention, not a database lookup. The near-universal rule is: the subtitle file lives in the same folder as the video, and its name matches the video's name up to the extension. A file called holiday.mkv is matched by holiday.srt. Change either side and the bond breaks — which is why renaming a video after you have collected subtitles for it silently loses them.

Language suffixes extend the convention. A file named with a language code before the extension — the pattern the video's name, a dot, a short language code, then .srt — is understood by many players as a specific language track, and the same idea with a "forced" marker is used for the subtitles that only translate on-screen text and foreign dialogue. Treat these as conventions rather than guarantees: how a given player interprets the suffix varies, and some ignore suffixes entirely. They are worth using because they cost nothing and help the players that read them.

Case sensitivity is where Mac users get ambushed, and it is worth a paragraph because the behaviour differs between your laptop and your network. The default macOS file system is case-insensitive, so Holiday.SRT and holiday.srt are the same file and matching works whatever the capitalisation. A network share is a different machine with a different file system, and many of them are case-sensitive. Move the same pair of files to a NAS and the match can fail even though the names look identical on screen. This is one of the most common reasons subtitles that worked yesterday stop working today, and the fix is to make the base names byte-for-byte identical, capitals included.

Folders matter too. Some players look only at the video's own folder, others also scan a subfolder named for subtitles, others search one level down. Because the behaviour is not standardised, the reliable arrangement is the flat one: video and subtitle side by side, nothing in between. There is one more wrinkle worth flagging — if the video is on a read-only share or a mounted disk image, a player can still read a subtitle sitting next to it, but it may be unable to remember your offset or style changes, since that state usually lives in a settings file keyed to the video's path. If your adjustments keep vanishing, that is why.

Finder, meanwhile, hides the very thing you need to check. macOS hides known extensions by default in some views, which means a file displayed as "holiday" might be holiday.srt, or might be holiday.srt.txt because a browser appended a second extension and the system is faithfully hiding only the last one. Turn on Settings → Advanced → Show all filename extensions in Finder once, and this class of confusion disappears permanently. It is a two-second change that prevents an hour of debugging.

Loading an External Subtitle by Hand on a Mac, Step by Step

The sequence below runs from the least invasive action to the most, which is the order that preserves the most information. Steps one to four solve identity problems, five solves encoding, six and seven solve timing, and eight is the fallback that works when nothing else does.

  1. Confirm the file is really a subtitle file

    Turn on filename extensions in Finder and read the end of the name. A .srt, .ass, .ssa, .vtt, or .smi file is what you want. A .zip means you are looking at the archive rather than its contents; a .txt may be fine inside but needs renaming; a .rtf is a word processor document that a player will not read. Most "the player won't load it" reports end here.

  2. Put both files in one folder

    The video and the subtitle, side by side, in a folder the player has permission to read. Not a subfolder, not the Downloads folder while the video is on the desktop. If the video is on an external drive or a network share, put the subtitle there too rather than on the internal disk — the pair has to travel together.

  3. Rename the subtitle to match the video exactly

    Take the video's full name including its extension, then replace only the video's extension with the subtitle's. Keep capitals identical if the files live on a network share. Do not rename the video to match the subtitle, because everything else that references the video — playlists, bookmarks, other subtitle files — will break instead.

  4. Open the video, then load the track from the player's subtitle menu

    Let the automatic match have its attempt first, since it costs nothing. If nothing appears, use the player's subtitle control to load a file from disk and pick the subtitle explicitly. That manual route bypasses naming entirely, which is also the fastest way to prove whether a mismatch was the problem: if the file loads by hand but never automatically, the naming is wrong and you now know exactly which part of it.

  5. If the text is scrambled, fix the encoding rather than the file

    Reopen the subtitle in a plain text editor, confirm you are in plain text mode rather than rich text, and save it as UTF-8. This preserves the timing you already have and only changes how the bytes are labelled. Replacing the subtitle file with a different one is the wrong instinct here, because a mis-guessed encoding looks like corruption but is not.

  6. If the cues are readable but early or late, apply an offset first

    Check the size of the error at the start and again an hour in. If it is the same at both points, it is a constant offset and the player's subtitle delay control will fix it in a few presses — a step of a quarter or half a second at a time gets you there quickly. If the error is small at the start and large later, stop: an offset will not help, and step seven is your problem.

  7. If the error grows over the runtime, the file was timed for a different frame rate

    This is a retiming job, not a nudging job: the subtitle's timeline has to be scaled, not shifted. Some players can do this; many can only shift. If yours can only shift, you need either a retimed copy of the subtitle or a tool that rewrites the timestamps. Recognising this early saves you from a long session of adding delay that keeps being wrong.

  8. When nothing works, convert to SRT and start from a known-good base

    Convert the file to plain SRT, save it as UTF-8, name it after the video, and load it. If that plays, the original format was the obstacle and you can stop. If it does not, the problem is upstream of the file — the folder, the permissions, or the player's support for that extension — and you have eliminated every other possibility in one move.

Constant Offset or Progressive Drift: Fixing Subtitle Timing on a Mac

Two mistimed subtitles can look identical for the first five minutes and need opposite repairs, so the single most useful diagnostic is to sample the error at two distant points. Pause at the very beginning and note whether the text arrives before or after the speech, and by roughly how much. Then jump to somewhere near the end and do the same. The pattern of those two readings tells you which of several distinct faults you have.

What you see What it means First move
Everything late or early by the same amount from start to finish A constant offset — most often a scene or a logo at the head of the video that the subtitle author's copy did not have Subtitle delay control. Adjust once, check at the end, done.
Correct at the start, increasingly wrong towards the end The subtitle was timed against a different frame rate — the classic film-to-television speed change is around four percent, which puts a hundred-minute film more than four minutes out by the credits Retime or scale the file. An offset cannot fix a growing error.
Fine for long stretches, then suddenly wrong for a scene, then fine again A different cut of the film — extra scenes, removed scenes, or reordered material Find a subtitle for your exact edition. No offset or scaling will reconcile two different edits.
Cues land a fraction early and the picture looks slightly speeded up Audio and picture are fine; the subtitle belongs to a faster or slower transfer of the same film Same as the drift case: this is a timeline scale, not a shift.
Two lines on screen at once, or a line vanishing before it is read Overlapping cues, or a reading speed faster than a person can follow Edit the cue boundaries in a text editor. Players display what they are given; they do not rewrite timing for readability.

The arithmetic behind the second row is worth doing once so it stops being mysterious. When a film shot for cinema is transferred for television at a higher frame rate, the whole thing plays about four percent faster, and the sound is pitched up to match. A subtitle file authored for the original speed therefore runs ahead of the picture, and the lead grows every minute. The error is proportional, not constant — which is precisely why nudging the delay makes it better and then worse. The fix is to multiply every timestamp by the ratio between the two frame rates, and that is a job for a retiming tool or a player that offers it, not for the delay buttons.

Overlapping cues deserve a note because they produce a specific and confusing symptom. If one cue ends at the same moment the next begins, some renderers show both stacked, others replace cleanly, and a few show the first line for a single frame and then swap. The visible result is a flash of doubled text or a line that blinks. Editing the file so that each cue ends a fraction before the next begins removes the ambiguity, and it also makes the output consistent across players and across casting targets, where the renderer may differ from the one you tested on.

One more category deserves naming because people misdiagnose it as drift. If the subtitles are correct but the audio is late, that is not a subtitle problem at all — the text is where it should be and the sound has moved. Our guide to fixing audio that is out of sync on a Mac covers the clock side, and the two faults are worth separating before you start adjusting a file that was never wrong.

Embedded Tracks, External Files, and Casting From a Mac

Most video containers can carry subtitle tracks inside them, and when they do, the whole identity problem disappears. An MKV can hold several text tracks, an MP4 can hold one or two, and the player simply lists what it finds. The advantage is portability: the file carries its own words, so it plays the same on any machine, in any country, with no matching and no renaming. The disadvantage is inflexibility — you cannot swap in a better translation, restyle a track you dislike, or fix a cue that never should have been there.

So the practical rule is: use the embedded track when it is in the language you want and its timing is right, and use an external file when it is not, or when you want something the embedded track does not give you — a second language simultaneously, a version with the on-screen signs translated, or a cleaner translation than the one that shipped. Our MKV playback guide covers how tracks are listed and selected inside a container if you want the detail.

Casting is where the difference between the two becomes decisive, and it is the part almost nobody warns you about. When you cast from a Mac by streaming the picture the Mac has already decoded — which is how AirPlay and Chromecast work in this scenario — the subtitles are drawn by the player before the frames leave the machine, so whatever you see on the laptop is what appears on the television. External files work perfectly, in other words, because the television never learns they exist.

When the receiver fetches the file itself — the pattern DLNA renderers often use when you push a file to a television — the situation inverts. The television now opens the video and looks for subtitle tracks inside it. An external SRT sitting in a folder on your Mac is not part of that transfer and will not appear, no matter how neatly it is named. The repairs are to pick a subtitle track that is embedded in the container, or to cast in the mode where the Mac does the decoding. Choosing between the two is the difference between a film with subtitles and a film without, and it has nothing to do with the subtitle file's quality.

A second casting caveat is worth knowing for anyone who watches with two languages at once. When one language has to be visible alongside another, the work moves onto the player: both tracks are drawn before the frame is sent. That is one more thing the laptop is doing per frame, and on a long session over a wireless link it is worth knowing that the cost is on the sender, not the television. The mechanics of running two tracks are covered in our guide to dual subtitles on a Mac, which pairs naturally with the language-learning workflow described in the language-learning player guide.

Frequently Asked Questions About Loading Subtitles on a Mac

How do I add subtitles to a video on Mac?

Put the subtitle file in the same folder as the video and give it the same name as the video, keeping the subtitle's own extension. So a film called holiday.mkv is matched by a file called holiday.srt. Open the video in a player that reads external subtitle files and the track is usually found automatically. If it is not, use the player's subtitle menu to load the file from disk by hand — that route ignores names entirely and will confirm in one step whether the problem was the name or the file itself.

Why do my subtitles show as strange characters on Mac?

The file's text encoding does not match what macOS assumes. Subtitle files are plain text, and a file authored on an older Windows machine may be in a regional single-byte encoding while macOS reads it as UTF-8, so every accented letter and every non-Latin character is interpreted as the wrong symbol. The timing is unaffected, which is the giveaway: correct cues, unreadable text. Reopen the file in a plain text editor, make sure it is in plain text mode rather than rich text, and save it as UTF-8. The Terminal tool iconv will convert from a known encoding to UTF-8 if the editor will not open the file cleanly.

What is the difference between SRT and ASS subtitles?

SRT carries timing and text and almost nothing else, which is why every player on every platform reads it. ASS is a script format that also declares fonts, colours, positions, fades, and per-line overrides, so it can translate an on-screen sign in place or colour each speaker's dialogue. A player that supports ASS shows everything the file describes; a player that does not usually still displays the text, plain and centred. If you need maximum compatibility, convert to SRT and accept losing the styling. If you need the styling, keep ASS and use a player that renders it.

Can I load two subtitle files at once on a Mac?

Yes, if the player is built for it — that is what dual subtitle support means, and it is the reason some people choose one player over another. Two tracks are drawn simultaneously, typically one at the bottom and one higher up or at a smaller size, and both are re-timed by the same offset control when you adjust it. The feature is most useful for language learning, where the point is to read one language while hearing another, and it depends on the player rather than on the files: any two subtitle files in supported formats will do.

Why are subtitles out of sync at the end but fine at the start?

Because the error is growing, not fixed. That pattern means the subtitle was timed against a video running at a different frame rate, and the classic case is a film transferred for television at a speed about four percent higher — over a hundred minutes that accumulates to more than four minutes of drift. Adding a delay will make the early part worse without fixing the late part, since a shift cannot correct a scale. You need a retimed copy of the subtitle or a player or tool that can scale the timestamps. Check by comparing the error at the one-minute mark with the error an hour in; equal errors mean an offset, growing errors mean a retime.

Do external subtitles work when I cast to a TV?

It depends on who decodes the video. When the Mac decodes and streams the finished picture, the subtitles are drawn before the frames leave the machine, so external files work exactly as they do on the laptop. When the television fetches the file itself — common with DLNA renderers — it opens the video and looks for subtitle tracks inside the container, and a separate subtitle file on your Mac is simply not part of what it received. In that case, choose a track embedded in the file, or switch to a casting mode where the Mac does the decoding.

Can a Mac play VTT subtitle files?

Yes, in players that support WebVTT, which is now most of the ones worth using. VTT is stricter than SRT: it requires a header line at the top of the file and it dislikes malformed cue blocks, so a file that was hand-edited or truncated can fail to load entirely rather than partially. If a VTT file refuses to appear, check that its first line is intact and that no cue is missing a blank line before the next one. When in doubt, convert it to SRT — you lose cue positioning but gain a format that loads everywhere.

Do I need to convert an ASS file to SRT on a Mac?

Only if the player will not render it or the result looks wrong. ASS files load in players that support the format and look better there than any conversion will, because the styling travels with the file. Convert when you see boxes instead of letters, when positioned text lands in odd places, or when the file has to work on a device that only understands SRT. The conversion is one-way in practice: SRT to ASS gains a wrapper but no styling, while ASS to SRT permanently discards fonts, positions, and colour.

Play Any Video on a Mac With the Subtitles You Want

Total Video Player for Mac reads external subtitle files alongside the video and keeps the pairing once you have set it. It opens MP4, MKV, MOV, AVI, M4V, MPEG, WMV, FLV, WebM, MTS, M2TS, and TS, decodes 4K UHD in hardware on Apple Silicon, plays straight from SMB, NFS, SFTP, FTP, and WebDAV shares, runs a DLNA Media Server, and casts over AirPlay, Chromecast, and DLNA. Subtitles support two tracks at once with font and style control, and the player also gives you playlists, 10x speed, A-B loop, rotate and mirror, and screenshot capture. Audio support covers MP3, AAC, AC3, FLAC, WAV, WMA, OGG, and M4A. If you want the fuller feature set, the Pro edition is the paid upgrade.