DaVinci Resolve leaves subtitles out of the render unless the Deliver page is told to output them. In Render Settings, open the Video panel, scroll to Subtitle Settings at the bottom, tick Export Subtitle and set Format to Burn into video. Blackmagic's manual describes that format in one line: "Renders all video with the currently selected subtitle track burned into the video."
That wording is from the DaVinci Resolve 21 Reference Manual (July 2026), pages 1287 and 1288, read on 11 November 2026. The same pages explain the two other formats, which are the usual reason subtitles are "exported" and still not on screen. This post covers what goes wrong at export. For adding, importing and styling subtitles, read how to add subtitles in DaVinci Resolve.
The fix: Subtitle Settings on the Deliver page
- Open the Deliver page with your timeline loaded.
- In Render Settings, open the Video panel and scroll to the bottom. The manual says the Subtitle Settings group appears there once the timeline has at least one subtitle track.
- Tick Export Subtitle. The manual describes this checkbox as the switch that enables or disables subtitle output.
- Set Format to Burn into video.
- Click Add to Render Queue, then start the render.
If you picked a preset and cannot find the group, switch to Custom Export. The manual says presets lock some settings and may hide others, and that Custom unlocks every setting in Render Settings.
The three formats, and which one puts text on screen
| Format | What Resolve outputs | Text visible in the video |
|---|---|---|
| Burn into video | The video with one subtitle track drawn into the picture | Yes, for every viewer, and it cannot be turned off |
| As a separate file | One file per ticked track, as IMSC1, DFXP, SRT or WebVTT | No. The video is clean; the file has to be uploaded or loaded next to it |
| As embedded captions | One track as a metadata layer inside the file; the manual names CEA-608 in MXF OP1A and QuickTime | Only in players that read that layer, with captions switched on |
So a render with "As a separate file" worked as designed even though the video shows nothing. The manual names MXF OP1A and QuickTime for embedded captions and does not name MP4, which is the format Resolve's own YouTube preset renders. Our guide to burned-in vs closed captions covers when each makes sense.
Other causes the manual documents
The wrong subtitle track is burned in. Burn into video uses a single track, the "currently selected" one. The manual does not define that phrase further, but page 1268 says only one subtitle track can be visible at a time and that enabling one disables the others. With two languages on the timeline, enable the track you want on the Edit page, confirm it in the viewer, then render and check the first seconds of the file.
The subtitle track is disabled. Subtitle tracks have the same enable control as other tracks. Hiding the subtitle tracks area with the Timeline View Options button is a different thing: the manual says hiding does not turn subtitle display off, while disabling the displayed track does. If the viewer shows no subtitles on the Edit page, fix that before you render.
Separate file chosen, no track ticked. With "As a separate file", a row of checkboxes under "Include the following subtitle tracks in the export" decides which tracks are written. Track names are used when exporting, so name each track with its language first.
The job was queued before you changed the setting. A job in the Render Queue is a saved render setup. To change one, the manual says to click its pencil button, change the settings, then click Update Job, or Add New Job to keep the old one.
You used Quick Export. File > Quick Export runs a preset. You can add your own from the Deliver page (Custom Export, Save as New Preset, Add to quick export). The manual does not say whether a preset keeps the Subtitle Settings, so render a ten-second range to check before a long export.
The captions are titles, not a subtitle track. Text placed as title clips on a video track is part of the picture and ignores Subtitle Settings. The manual says clips on disabled tracks are not rendered to the video output, and its own example of a textless version is disabling the track that holds the titles. Check that the title track is enabled on the Deliver page.
The style in the render is not the style you set. Since Resolve 20, a Fusion title template dragged onto the subtitle track header overrides the track and per-caption styling from the Inspector.
Subtitles not showing on YouTube
A burned-in render shows its text on YouTube like any other part of the picture. If the text is missing there, the file was rendered without burn-in, so play the file on your computer first.
If you chose a separate file, YouTube only shows it after you upload that file to the video; how to add subtitles to a YouTube video has the steps. Resolve's YouTube preset does not do it for you: the manual lists what the preset sets (MP4, H.264, AAC audio) and what its direct upload sends (title, description, chapters from markers, thumbnail, visibility, category), and subtitles are in neither list.
If an uploaded SRT appears at the wrong time, open it in a text editor and read the first timestamp. New Resolve timelines start at 01:00:00:00 by default, so a first line stamped at about one hour points at the timeline's start timecode. The manual does not say how the subtitle export treats that timecode, so treat this as a check, not a documented cause. What is an SRT file shows how to read the timestamps.
Resolve 20 and 21: what changed
Blackmagic's New Features Guide for Resolve 20 (April 2025) adds AI Animated Subtitles and extra transcription languages, both marked Studio Version Only, plus Fusion templates on subtitle tracks. The guide for Resolve 21 (April 2026) adds find and replace, fade handles on subtitle clips, and word timing for typed or imported captions: if a word-highlight animation is out of step after you correct the text, select the clip and press Update Word Timings in the Inspector's Caption tab, or right-click the track header and choose Synchronize Word Timings.
Neither guide lists a change to the Deliver page's subtitle output. We did not read the Resolve 19 or 20 reference manuals, so if your panel looks different, look for the same three format names.
When burning in outside Resolve is quicker
If the cut is already exported without captions and all you need is burned-in text, you can caption the exported file instead of re-rendering the timeline. CapsAI does that in a browser: upload an MP4 or MOV of up to 10 minutes, pick the spoken language, correct the words and timing, and export one MP4 with the captions drawn into the picture. You can try it on a video of up to 3 minutes without signing up, and you sign in when you export. Exporting needs a one-time pack, from $4 (₹49 in India).
Where it loses to Resolve: it writes new captions from the audio, so the subtitle track you already corrected in Resolve does not carry over, and it cannot read an SRT. It transcribes 11 languages, English, Hinglish and nine Indian languages, so Spanish or French dialogue is out. It gives no SRT, VTT or embedded caption track, and the result is a second encode of your file. If you need a caption file or a broadcast deliverable, stay in Resolve. Burn subtitles to video has the details, and DaVinci Resolve subtitles alternative compares free Resolve, Studio and the browser route.
What we did not test
Everything above comes from Blackmagic's manual and its two new-features guides. We did not reproduce these renders in Resolve. Blackmagic's user forum has threads on missing subtitles, but it would not load for us on 11 November 2026, so nothing here comes from forum posts.
What to do next
Tick Export Subtitle, choose Burn into video, and render ten seconds to confirm. If the wrong language appears, enable the right subtitle track first. If you wanted a caption file, choose As a separate file, tick the track, and upload the file to the platform yourself.
