Back to blog

DaVinci Resolve Auto Subtitles: How to Get Them Without Studio

DaVinci Resolve auto subtitles need Studio, but the free version imports SRT: three free ways to make the file, one track per language, and the timecode fix.

October 3, 2026
Sablate Team

DaVinci Resolve auto subtitles are a Studio feature: Create Subtitles from Audio is greyed out or missing in the free version. Everything else about subtitles is free — importing, styling, burning in, exporting — so the working route is to transcribe with a free tool such as AutoSubs or Whisper and let Resolve do the rest.

Below: what Studio adds, three ways to get the file, the import setting that drops every subtitle an hour before your timeline starts, and the Deliver settings that decide whether subtitles reach the render at all.

Why is Create Subtitles from Audio greyed out in DaVinci Resolve?

Because it belongs to the paid version. Blackmagic's reference manual labels Create Subtitles from Audio "Studio Version Only". In Studio it sits under Timeline → AI Tools, transcribes on your own machine and writes the result to a new subtitle track. DaVinci Resolve Studio costs $295 once. It transcribes 14 languages out of the box — Chinese (Simplified Mandarin), Danish, Dutch, English, French, German, Italian, Japanese, Korean, Norwegian, Portuguese, Russian, Spanish and Swedish — and an extra download, also Studio-only, takes the list to 57. Studio also adds animated, word-highlight subtitles.

The free version is limited in creating subtitles, not in handling them. Side by side, from the same manual:

Subtitle featureFree versionStudio
Create Subtitles from Audio (automatic transcription)NoYes
Animated word-highlight subtitlesNoYes
Import .srt, .srtx, .vtt, .xml and .ttmlYesYes
One subtitle track per language, each named and styled separatelyYesYes
Reading-speed checks: characters per line, minimum duration, maximum CPSYesYes
Export .srt or .vtt, burn a track in, or write one file per trackYesYes
Advanced scripting, which some subtitle plugins rely onNo, since 21.1Yes

So the practical answer to "what can I do in the free version" is: bring Resolve a subtitle file and it does everything else. The only missing step is turning speech into that file, and the three methods below each fill it for free or for less than Studio costs.

One change from September 2026 matters for the free route. Resolve 21.1, released on 8 September, made advanced scripting a Studio feature. AutoSubs, the free plugin most guides recommend for the free version, talks to Resolve through a script bridge, and that update broke it for ten days.

Three ways to get auto subtitles into free Resolve

  1. AutoSubs — a free, open-source tool that transcribes your timeline and places styled captions on it for you.
  2. Whisper on the command line — free, one command that turns the timeline's audio into an .srt file you import.
  3. A desktop subtitle app — for the same video in several languages, or a styled burn-in that does not depend on Resolve at all.

The first puts captions straight onto your timeline. The other two hand Resolve an .srt file, which becomes a subtitle track you style and export in Resolve.

Method 1: AutoSubs, the free plugin

AutoSubs is the most complete free answer for a Resolve user. The open-source plugin runs on Windows, macOS and Linux, transcribes offline with Whisper and several newer speech models, translates, labels speakers, and sends the result to your timeline as styled captions.

The script bridge is why 21.1 broke it. Version 3.10.0, released on 18 September 2026, rewrote the integration so it works with the free edition again. From 3.10.1 on, the routine is:

  1. Install AutoSubs from its GitHub releases page and open the app first.
  2. In Resolve, choose Workspace → Scripts → AutoSubs once per session to connect.
  3. Pick a model and a language in AutoSubs, transcribe the timeline, and send the subtitles to Resolve.
  4. Read the captions through on the timeline before you export anything.

Two limits. AutoSubs does not support the Mac App Store edition of Resolve, only the one downloaded from Blackmagic's website. And because it depends on Resolve's scripting, a future Resolve update can break it again until the next AutoSubs release, as 21.1 did.

If you work in one language and want to stay inside Resolve, start here. It costs nothing, and its speaker labels are something Sablate does not do.

AutoSubs not working in DaVinci Resolve? What to check first

Most AutoSubs problems since September 2026 trace back to one change: DaVinci Resolve 21.1 tightened the scripting sandbox AutoSubs used to talk to Resolve. The fixes are in AutoSubs' own release notes. Work through them in this order:

  1. Update AutoSubs. Version 3.10.0 rewrote the Resolve integration for 21.1, including the free edition, and 3.10.1 fixed a 3.10.0 bug that froze the Fusion page. If you ever ran 3.10.0, restart Resolve once after updating.
  2. Open the AutoSubs app before connecting. Since 3.10.1 the script inside Resolve can no longer launch the app. Start AutoSubs yourself, then choose Workspace → Scripts → AutoSubs once per session.
  3. Subtitles never reach the timeline? Update to 3.11.0 or later. Its release notes name a send failure when the target video track is occupied as the most common one on Resolve 21, and fix it.
  4. Resolve in another language, or a non-English Windows user name? 3.11.0 also fixes audio extraction on non-English installs of Resolve and a dropped connection when the Windows user folder name contains non-English characters.
  5. Words missing from phone calls or quiet recordings? 3.11.0 added a Speech Detection toggle that turns off silence skipping.
  6. Bought Resolve from the Mac App Store? That edition is not supported; the AutoSubs README asks you to install Resolve from Blackmagic's website instead.

If AutoSubs still doesn't work

Take the plugin out of the chain and hand Resolve a file. Every edition of Resolve imports .srt, and that route does not touch scripting at all, so no Resolve update can break it. Whisper on the command line, below, is free and makes the file in one command. A desktop app such as Sablate, method 3, adds an editor to correct the text first and handles several languages from one transcription. Either way, the import steps further down this post put the file on a subtitle track.

Method 2: Whisper on the command line

Whisper is free, runs on your own machine, and its command-line tool writes an .srt directly. OpenAI's Whisper needs Python and FFmpeg installed, which is the real cost of this route.

First export the edited timeline's audio, so the subtitles follow the final cut rather than the source clips. On the Deliver page, choose Custom Export, untick Export Video, keep Export Audio, and render a WAV file — timeline.wav here. Then:

whisper timeline.wav --model turbo --language en --output_format srt

turbo is the default model and the sensible one for transcription. Change --language to the language actually spoken, or leave it out and let Whisper detect it. The command writes timeline.srt next to the audio, ready to import.

This route has no editor. You correct the text in Resolve's subtitle inspector, which gained find and replace across a whole track in Resolve 21. If a line repeats itself, or a phrase appears over silence, that is a known Whisper failure with known settings to prevent it — see why Whisper repeats lines and invents text.

Method 3: A desktop app, for subtitles in several languages

Resolve has no subtitle translation in either version, so every language has to arrive as its own file. That is where a desktop subtitle app earns its place. In Sablate the steps are:

  1. Drop timeline.wav, or a rendered video, into Sablate and transcribe it on your own machine.
  2. Correct names and punctuation in the editor, and retime cues on the timeline where needed.
  3. Add each extra language with Add language…. A translation is a layer on the same timings, so every language lines up with the others.
  4. Export Subtitle file (.srt) once per language — or, on Pro, All languages · Subtitles, which writes one .srt per language into one folder.

What you gain is one transcription feeding every language and a handoff made of plain files. Resolve only ever sees .srt files, so this works with the Mac App Store build and does not care what the next Resolve update does to scripting. If the final delivery is a burned-in MP4 per language, Sablate can burn those itself, each language with its own font and style, and Resolve never renders a subtitle.

What you give up: speaker labels, and your Sablate styling once the subtitles are in Resolve. An .srt carries text and timing only, so each track gets styled again there. Other desktop apps that make the file offline are compared in the offline subtitle generator comparison.

The free plan covers videos up to 10 minutes, three jobs a month and one offline translation layer, and its .srt files end with a short "Made with Sablate" line. Pro is a single $29 payment with no length limit, no credit line and no limit on languages; the pricing page lists the rest. The multilingual workflow explains why the transcript gets corrected before any translation.

How to import an SRT into DaVinci Resolve

Most guides skip over this step, and it is where subtitles vanish. Resolve starts new timelines at 01:00:00:00 by default, while an .srt counts from zero. Insert the file by timecode into a timeline that starts at one hour, and every subtitle lands an hour before the first frame: present in the project, invisible on the timeline.

The reliable order, screen by screen:

  1. Open the Edit page, where the Media Pool and the timeline sit side by side.
  2. In the Media Pool, right-click the timeline, choose Timelines → Starting Timecode and set it to 00:00:00:00.
  3. Right-click an empty area of the Media Pool, choose Import Subtitle and pick the .srt.
  4. Right-click the imported subtitle clip and choose Insert Selected Subtitles to Timeline Using Timecode.
  5. Double-click the new subtitle track's name and rename it after its language. Resolve uses track names when it exports or encodes subtitles.
  6. Repeat for each language. Every file gets its own subtitle track, and only one subtitle track shows at a time.
  7. Click any subtitle on a track and open the Inspector, then its Track tab, to style that whole track, as described below.
  8. Render from the Deliver page, where subtitle output has its own switch, covered at the end of this post.

If the timeline has to keep its start timecode — broadcast deliveries often require 01:00:00:00 — drag the subtitle clip onto the timeline instead. Resolve puts the first subtitle where you drop it and keeps the rest relative to it, so drop it on the frame where the first line is spoken.

Resolve does not list .ass among its import formats, so bring .srt even if your subtitle tool can write styled .ass — what each format carries explains what that costs. Then style each track from the Track tab of the Inspector: font, size, colour, position, stroke, drop shadow and background apply to every subtitle on that track. The same tab holds the track's subtitle settings. Untick Use Project Settings to give a track its own Max CPS, Max Line Length and Min Duration — with several languages that matters, because a comfortable reading speed in English is too fast in Korean or Japanese. The per-language CPS limits give you numbers to start from.

Moving CapCut auto captions into DaVinci Resolve

If the captions already exist in CapCut, there is no need to transcribe again. CapCut can write them out as a subtitle file, and Resolve imports that like any other SRT:

  1. In CapCut desktop, export with Caption Export selected instead of Video Export, and choose SRT as the format.
  2. In Resolve, import that .srt and insert it by timecode, exactly as in the steps above.

Two limits, both from CapCut's own help page: only automatically recognised captions can be exported, not text you typed in yourself, and if Resolve or another tool will not read the file, re-save it as UTF-8 without a byte-order mark. What carries over is text and timing. CapCut's caption styles and animations stay behind, so the track gets styled again in Resolve's Inspector.

Which method should you use?

Resolve StudioAutoSubsWhisper CLISablate
Price$295 one-timeFree, open sourceFree, open sourceFree tier; Pro $29 one-time
Needs Resolve StudioYesNoNoNo
Puts subtitles on the timeline for youYesYesNo, you import an SRTNo, you import an SRT
Spoken languages14, or 57 with an extra downloadDepends on the modelAbout 100100
Translates subtitlesNoYesInto English onlyYes, as layers
Depends on Resolve's scriptingNoYesNoNo
PlatformsWindows, Mac, LinuxWindows, Mac, LinuxWindows, Mac, LinuxWindows and Mac

"I edit in one language and want to stay in Resolve." AutoSubs. It is free, and the subtitles land on the timeline already styled.

"I already own Studio." Use Create Subtitles from Audio if your language is on its list. Nothing else here is worth installing for one language.

"I need this video in four languages." Sablate: one transcription, four .srt files, four subtitle tracks, each styled for its own language.

"I bought Resolve from the Mac App Store." Whisper or Sablate. AutoSubs does not support that edition.

"I'm comfortable in a terminal and need one file now." Whisper. One command, and nothing to install beyond Python and FFmpeg.

Why aren't my subtitles in the exported video?

Because subtitle output is its own switch on the Deliver page, and burn-in takes one track at a time. At the bottom of the Video panel in the Render Settings, the Subtitle Settings group holds an Export Subtitle checkbox and a Format menu with three choices:

  • Export Subtitle — the master switch. Unticked, the render carries no subtitles at all.
  • Burn into video — burns the currently selected subtitle track into the picture. One render gives you one language; four burned-in languages take four renders, selecting each track in turn.
  • As a separate file — writes one file per ticked track, as SRT, WebVTT, IMSC1 or DFXP. This is the option for YouTube and Vimeo uploads.
  • As embedded captions — writes the selected track inside the video file, but only as CEA-608 captions in MXF OP1A or QuickTime files, not in MP4.

If the burned-in language is the wrong one, check which subtitle track is selected on the timeline before you render again.

Resolve's free version does everything with subtitles except write them. Hand it an .srt and it takes care of the tracks, the styling, the reading-speed checks and the delivery. For one language inside Resolve, AutoSubs is free and good. For the same video in several languages, download Sablate for Windows or Mac, transcribe the timeline once, and import one file per language.

Frequently asked questions

Can the free version of DaVinci Resolve create subtitles automatically?

No. Create Subtitles from Audio is a Studio feature, which is why it is greyed out or missing in the free version. The free version still imports, styles, burns in and exports subtitles, so let a free tool do the transcription: AutoSubs puts captions on your timeline, and Whisper writes an SRT file you import as a subtitle track.

How much does DaVinci Resolve Studio cost?

$295, paid once, with no subscription. For subtitles, Studio adds automatic transcription in 14 languages, or 57 with an extra download, plus animated word-highlight subtitles. If subtitles are the only reason you would upgrade, a free plugin or a separate subtitle app costs less and leaves the free version doing the styling and the export.

How do I import an SRT file into DaVinci Resolve?

Right-click in the Media Pool, choose Import Subtitle and pick the file. Set the timeline's starting timecode to match the SRT, usually 00:00:00:00, then right-click the subtitle clip and choose Insert Selected Subtitles to Timeline Using Timecode. Each file lands on its own subtitle track, which you style from the Track tab of the Inspector.

Why do my imported subtitles disappear or land an hour early?

Because Resolve starts new timelines at 01:00:00:00 and SRT files count from zero. Inserting by timecode then places every subtitle an hour before the timeline begins. Set the timeline's starting timecode to 00:00:00:00 before inserting, or drag the subtitle clip onto the timeline by hand and drop it where the first line is spoken.

Can DaVinci Resolve translate subtitles?

No. Neither the free version nor Studio translates subtitles. Translate the SRT before importing it, then put each language on its own subtitle track. Resolve lets you name every track, style it separately, give it its own reading-speed limit, and export each one as a separate subtitle file when you render.

Why are my subtitles not showing in the exported video?

Subtitle output is switched off, or the wrong track is selected. On the Deliver page, find Subtitle Settings at the bottom of the Video panel, tick Export Subtitle and choose Burn into video, which burns in only the currently selected subtitle track. For subtitle files instead, choose As a separate file and tick each track.

Why is AutoSubs not working in DaVinci Resolve?

Usually because Resolve 21.1 tightened the scripting sandbox AutoSubs relied on. Update AutoSubs to 3.10.1 or later, open the AutoSubs app before running Workspace, Scripts, AutoSubs in Resolve, and update to 3.11.0 if subtitles never reach the timeline. The Mac App Store edition of Resolve is not supported; if it still fails, import an SRT made with another tool.

Can I move CapCut auto captions into DaVinci Resolve?

Yes, as an SRT file. In CapCut desktop, export with Caption Export selected instead of Video Export and choose SRT; CapCut's help notes that only automatically recognised captions can be exported. Then import the file into Resolve's Media Pool and insert it by timecode. Text and timing carry over, but CapCut's caption styling does not.