DaVinci Resolve Club
Home   Troubleshooting   DaVinci Resolve Text Not Showing: Viewer and Export Fixes
Troubleshooting

DaVinci Resolve Text Not Showing: Viewer and Export Fixes

By Jason Miller Updated Oct 1, 2026 6 min read

Quick answer

Separate title, subtitle and Fusion failures, then follow the missing text from the timeline to the Viewer and final render.

DaVinci Resolve Text+ clip over a theater stage with an empty text box and opacity set to 0.00

If text is not showing in DaVinci Resolve, pin down where it goes missing before you touch any settings. Is it gone from the Viewer? Visible in the Viewer but absent from the exported file? Only the subtitles? Or broken only inside a Text+ or Fusion composition? Each symptom follows a different output path, so start with the section below that matches what you see.

SymptomCheck firstWhy it matters
Title missing in the ViewerPlayhead position, clip enable, track enable and track orderThe title must be active at the current frame and able to reach the Viewer.
Title visible in the Viewer but missing from exportTimeline, render range and Fusion-effect bypass stateThe Deliver job may not be rendering the same frames or effect path you previewed.
Subtitles visible while editing but absent from the fileDeliver > Video > Subtitle SettingsA subtitle track is not automatically burned into every export.
Text+ visible in a Fusion viewer but absent on Edit or DeliverMerge path and MediaOutA node can preview correctly without being connected to the composition’s final output.

Basic Text, Text+, a Fusion Title and a Subtitle Track are four different tools, and they fail in different places. If you still need to build the title, the separate guide to add text in DaVinci Resolve covers that. This page assumes the title or subtitle already exists.

Text Missing in the Viewer

I'd start with the timeline, because it splits placement problems from styling problems fastest. Park the playhead inside the title clip, select that clip, and confirm the title sits on a video track above the footage it should cover. A title on V1 can be hidden by an opaque clip on V2. Moving it higher is a quick diagnosis, not a reason to rearrange unrelated tracks for good.

Track stack with a title on V2 above footage on V1 and the playhead through the title, next to four checks: playhead inside the title, clip and track enabled, title above opaque footage, Inspector showing the title
Run these four checks first. If a plain Text title shows up at the same timecode, the problem is inside the original title.

Confirm the clip and track are enabled

A disabled clip appears dimmed. Select the title, open its contextual menu and make sure Enable Clip is checked. The default enable/disable toggle is D, so it's easy to switch a selected title off while you're reaching for nearby shortcuts. The whole track has its own enable button in the track header too. The Resolve 21.1 Reference Manual is explicit: disabled clips don't play back and aren't rendered, and clips on a disabled track aren't rendered on the Deliver page until that track is enabled again.

Make sure you are editing the title you selected

Select the title clip, then open the Inspector. For a basic Text title, the Rich Text field should hold the expected copy. For Text+, open the Title controls and check the Styled Text field. If the Inspector shows controls for the footage underneath, the title isn't the active selection.

Next, take styling out of the equation. Pick a readable font, bump up the size, choose a color that contrasts with the frame, and return position or transform controls toward their defaults. A title can be present yet effectively invisible because it's off canvas, too small, transparent or the same color as the background. If the project came from another workstation, also look for a missing font warning and choose an installed substitute before you judge line breaks or position.

Use a plain Text title as a control

Add a temporary basic Text title on a new enabled track at the same timecode. If that one appears, the Viewer and track stack are fine, and the fault lives inside the original title's styling, template or Fusion structure. If the plain title fails too, stay with the Edit-page checks instead of rebuilding the original effect.

Text Visible in the Viewer but Missing From Export

Once the Viewer looks correct, stop fiddling with font and position. Now the question is whether the Deliver job renders the same timeline, range and effect path.

  1. Open the timeline you actually want to deliver. Timelines with similar names make this an easy slip. Compare the visible title and its timecode before you open Deliver.
  2. Check the render range. If Render is set to In/Out Range, confirm the title falls between the active marks. Use Entire Timeline when that's the deliverable you want.
  3. Review bypass controls. A basic Text title and a Fusion-based title don't travel through exactly the same effect path. If the Bypass Color Grades and Fusion Effects button (Shift-D) is switched on, restore the normal state before you create the final job.
  4. Replace an old render-queue job after changing settings. Build the job from the current timeline and read its summary, rather than assuming an earlier queued job picked up every later change.

Render a short range that includes the failing title before committing to a long export. That's an editorial recommendation, not a performance benchmark: a small diagnostic file tells you whether the current delivery path carries the title without waiting on unrelated frames. The full DaVinci Resolve export guide covers the rest of the delivery setup.

Subtitles Need Their Own Export Decision

A subtitle track can look correct in the timeline and still be missing from the video file, because subtitle output is a separate choice. On the Deliver page, open Render Settings > Video > Subtitle Settings and enable Export Subtitle.

Export Subtitle switched on branches into three outputs: Burn into video, As a separate file with IMSC1, DFXP, SRT or WebVTT, and As embedded captions in QuickTime or MXF with Text or CEA-608
Burn into video when the words must always be visible. A separate file only shows up when the player loads it.

Then pick the output that matches the deliverable:

  • Burn into video renders the selected subtitle track into the image. Use it when the words must always be visible in the exported video.
  • As a separate file writes a timed subtitle file; Export As offers IMSC1, DFXP, SRT and WebVTT. The video itself won't show those words unless a player loads that file.
  • As embedded captions stores caption data inside a compatible media format. The manual names QuickTime and MXF renders, with Text or CEA-608 as the caption codec, and the available options still depend on the chosen clip format.

Then select the intended subtitle track. With several language or caption tracks in the project, picking the wrong one can give you an empty or unexpected result. The site's subtitle and caption workflow explains track creation, timing and separate-file delivery in more detail.

Text+ or Fusion Text Does Not Reach the Output

Text+ is Fusion-based. Inside a Fusion composition, seeing Text1 in a node viewer only proves that the node renders its own image, not that it reaches the final composition. Follow the connection from the text node into a Merge node and from that Merge into MediaOut.

Fusion wiring for a text overlay: MediaIn1 into the Merge1 background, Text1 into the foreground and Merge1 into MediaOut1, with two broken versions where Text1 goes straight to MediaOut1 or Merge1 never connects
Text1 joins the footage in Merge1, and only what reaches MediaOut1 makes it to the Edit page and the export.

For a text overlay, the usual wiring looks like this:

  • MediaIn supplies the underlying picture to the Merge background input.
  • Text supplies the foreground input.
  • The Merge output connects to MediaOut.

If Text connects straight to MediaOut, you may see text over transparency but lose the footage. If the Merge isn't connected to MediaOut, the branch can look correct in a node viewer while the Edit page and the export receive a different path. If the graph is new to you, the Fusion beginner guide walks through the flow from source nodes to the final output.

Check animation at the failing frame

A Text+ title can also be wired correctly and still be invisible at one timecode. Go to the frame where it fails and check Styled Text, opacity or blend, Write On values and any transform animation. A start or end value that hides every character is a different problem from a broken MediaOut connection. Diagnose that one frame first, then confirm the title stays visible for its whole intended duration.

Clear Cache Only After the Output Path Is Correct

Cache work helps when the structure is correct and Resolve is still showing an older result. It can't enable a disabled clip, add a subtitle track to Deliver or reconnect a Fusion branch. Once those checks pass, delete the render cache for the affected clip or turn caching off for a moment, reopen the project if needed, and run a new short diagnostic render.

If the problem hits several unrelated projects, or the interface behaves inconsistently, write down the Resolve build, operating system, Free or Studio edition, title type and exact failing timecode. Then compare the behavior with current material on the official Blackmagic Design support page. The broader Resolve troubleshooting hub routes crashes, render failures and media problems that aren't limited to text.

Final Missing-Text Checklist

  • Playhead is inside the title or subtitle duration.
  • Title clip and its video track are enabled.
  • Title sits above any opaque footage it should overlay.
  • The selected clip exposes the expected text controls in Inspector.
  • Text color, size, opacity and position make it visible.
  • Deliver is using the intended timeline and render range.
  • Subtitle output is enabled and set to burn in, separate file or embedded captions as required.
  • Fusion text reaches a Merge and the final result reaches MediaOut.
  • A fresh short render confirms the repaired path before the full export.
Updated October 1, 2026 Check version and edition requirements before following a workflow.
Jason Miller
Jason Miller I run DaVinci Resolve Club as an independent publication: hands-on edits, color grading breakdowns, Fairlight sessions, Fusion tests, and honest notes on where Resolve gets in the way.
Explore the troubleshooting hub: match the symptom, then test the smallest fix