You've got the cut locked, the audio mostly cleaned up, and now the screen feels empty. It needs a title, a lower third, maybe captions, maybe something more polished than the default white text you dragged in five minutes ago. That's usually the moment people realize DaVinci Resolve has several different ways to add text, and choosing the wrong one creates extra work fast.

If you want to add text in DaVinci Resolve without fighting the software, think less about “where is the title tool?” and more about “what job does this text need to do?” A quick label, a branded lower third, a tracked 3D title, and subtitles all belong in different parts of Resolve. Once you match the tool to the task, the process gets much simpler.

Choosing Your Text Tool in DaVinci Resolve

Resolve gives you more than one text workflow because text in editing isn't one thing. Sometimes you need a fast title card. Sometimes you need animated branding. Sometimes you need captions that update cleanly when the transcript changes. That split matters.

Text is central to how people use Resolve. As a projection cited by Boris FX's DaVinci Resolve text guide, by May 2026 DaVinci Resolve boasts over 20 million active users worldwide, with text-related features accounting for 45% of all Edit page operations. That tracks with real editing work. Titles, callouts, name straps, captions, and subtitles show up in almost every project.

Which tool fits the job

The mistake I see most often is using Text+ for everything. It can do a lot, but that doesn't mean it should do every job. If all you need is a static “Episode 12” card, basic Text is faster. If you need spoken dialogue on screen, subtitles are cleaner than stacking dozens of title clips.

What works and what doesn't

Here's the practical version.

• Use Basic Text when speed matters more than styling. It's the right choice for rough cuts, placeholders, watermarks, and simple title slates.
• Use Text+ when the text is part of your visual identity. Lower thirds, callouts, animated intros, and cleaner typography belong here.
• Use Fusion when the text has to behave like a VFX element. If it needs depth, 3D lighting, camera moves, particle treatment, or scene tracking, go to Fusion.
• Use subtitle tracks when timing matters more than design freedom. Captions need to stay editable, sync to speech, and export cleanly.

Practical rule: If the text is carrying spoken words, build it as subtitles. If the text is carrying brand or design, build it as Text+ or Fusion.

There's one more workflow choice that saves time before you even touch titles. If your footage has noisy room tone, laptop fan hum, or location audio that makes dialogue hard to parse, clean the sound first. It's much easier to create dependable captions and subtitle timing after you remove noise from video soundtracks.

The fastest decision tree

When I'm moving quickly, I use a simple filter:

1. Will viewers read this once or throughout the whole video?
   A one-off title can be a clip. Ongoing dialogue should be subtitles.

2. Does it need animation beyond basic movement?
   If yes, start in Text+ and only go to Fusion if the motion or compositing gets complex.

3. Will the wording change later?
   Subtitle tracks and simpler title setups are easier to revise than overbuilt Fusion comps.

That choice at the start saves a surprising amount of cleanup later.

Quick and Simple Text on the Edit Page

If you need text on screen in under a minute, use the Text generator on the Edit page. This is the straightforward option. No node graph, no deep inspector maze, no temptation to spend twenty minutes tuning a shadow for a temporary label.

The fastest way to get text on screen

Open the Effects Library, go to Titles, then drag Text onto a track above your video clip. Select that text clip, open the Inspector, and type what you want.

From there, handle the four settings that matter most first:

• Text content so the words are correct
• Font so it matches the tone of the project
• Size so it's readable on the target screen
• Color so it doesn't disappear into the background

That's enough for title cards, simple labels, scene identifiers, and quick watermarks.

Good uses for the basic Text generator

The basic tool works best when the text is functional, not decorative.

• Rough cut labels help you mark sections like “Cold Open” or “B-roll starts here.”
• Simple title cards are easy when you just need a centered headline over a clean background.
• Watermarks or channel identifiers can sit in a corner without needing advanced controls.
• Client review notes sometimes need temporary text markers that won't survive to final export.

This is also a good tool for editors who want to avoid overbuilding early. You can place the words, keep cutting, and upgrade the graphic later if the sequence earns that attention.

Basic Text is the fastest option when the text itself matters more than the treatment.

Where this tool starts to break down

The limits show up as soon as you want personality. If you need layered shading, cleaner outlines, more nuanced positioning, or animation that feels designed instead of mechanical, basic Text runs out of road quickly.

A common trap is trying to force this tool into lower thirds for interviews or branded YouTube intros. You can make it work in a pinch, but the result usually looks thin. The typography feels flatter, and revisions become annoying because you're fighting a tool that wasn't built for that level of control.

A simple workflow habit that helps

Keep a few basic Text presets in a project template. One for centered titles, one for top-left labels, one for a watermark. That way you're not redoing the same font and size setup every time you open Resolve.

Use this tool when speed is the whole point. The second styling starts to matter, move up to Text+.

Creating Pro Graphics with Text+

Text+ is where Resolve starts feeling like a real motion graphics tool instead of just an editor with title presets. Blackmagic introduced the Text+ generator in version 12 on April 21, 2016, and that release brought over 100 customizable parameters into the workflow, according to Simon Says' DaVinci Resolve text overview. That shift is a big reason Text+ became the default choice for polished in-app graphics.

Build a lower third that actually looks finished

Drag Text+ from the Titles panel onto a track above your footage. Open the Inspector and start in the Text tab. Type the name or label, choose your font, then set size and alignment before you touch animation.

For a solid lower third, I usually shape it in this order:

1. Get the typography right first
   Pick a readable font, then adjust character spacing and line spacing. Bad spacing makes even expensive-looking graphics feel amateur.

2. Add separation from the footage
   Use shading tools like an outline, shadow, or background element so the text survives busy shots.

3. Place it with intention
   Don't just drop it in the lower left because that's where lower thirds “go.” Check if the subject, wardrobe, or frame composition fights the placement.

The three controls that matter most

Text+ has a lot of options, but most editors get the biggest gains from three areas.

Shading

Shading does the heavy lifting for legibility and polish. A subtle outline helps against bright footage. A soft drop shadow can separate text from a textured background. A gradient can make a title feel branded instead of generic.

Use restraint here. If you stack a heavy stroke, large shadow, and loud gradient all at once, the graphic starts looking like a plugin demo.

Transform

Your text starts to feel placed rather than pasted at this stage. Adjust position, size, and rotation carefully. Small moves matter. Even a slight change in vertical placement can make the frame feel more balanced.

For social content, I often keep titles a little higher than instinct suggests. Platform UI elements and caption areas can crowd the bottom of the frame.

Keyframing

You don't need complicated motion to make Text+ look professional. A short move-in and fade-in often does more than an elaborate preset.

Try this simple setup for a name strap:

• Set the first keyframe with the text slightly off position and transparent
• Move a little forward in the clip
• Bring the text to final position and full opacity
• Add a matching exit only if the cut needs it

A lower third should support the speaker, not compete with them. If you notice the animation more than the name, dial it back.

What works for real projects

A clean Text+ lower third usually includes:

• One strong font pairing instead of mixing several styles
• Moderate contrast tools like a restrained shadow or stroke
• Short animation timing so the text arrives quickly
• Consistent placement across the whole video

What doesn't work is chasing every feature in the Inspector because it's there. Text+ rewards editors who make fewer, better choices.

When to stop using Text+ and switch tools

Text+ is excellent for titles and motion graphics on the Edit page, but there's a threshold where it's smarter to switch. If the text needs true 3D depth, tracked perspective, scene lighting, or interaction with particles, you're in Fusion territory.

That doesn't mean Text+ failed. It just means the job changed.

Advanced 3D Text in the Fusion Page

Fusion is where Resolve stops behaving like a timeline editor and starts behaving like a compositing system. If you've only used layers before, the node graph can look severe at first. It's not. It's just explicit. Every connection tells you what the graphic depends on.

A practical 3D text build

Say you want a cinematic opening title with actual depth, light wrap, and camera perspective. On the Edit page, that effect will always feel faked. In Fusion, you can build it properly.

The rough logic looks like this:

• Add or open a text element in Fusion
• Create the text as a 3D object
• Feed it into a Merge3D
• Add lights and a camera
• Send that scene into a renderer
• Composite the result back over the footage if needed

That sounds technical, but the workflow is clean once you understand that each node handles one task.

Why Fusion feels different

Fusion gives you control that title tools can't. You can extrude letters, change how they catch light, move a virtual camera through the scene, and treat text like geometry instead of a flat overlay.

According to the referenced YouTube workflow cited in the verified data, Fusion's Text+ node supports advanced OpenType features like kerning and ligatures at 60fps, and scripting JSON imports via Reactor tools can automate multi-language titling, reducing setup time by up to 70% in high-end workflows. That matters more than it sounds. Good typography and repeatable imports are what keep complex title systems maintainable.

One effect worth learning

If I were teaching a junior editor one Fusion text effect first, it would be extruded 3D title with controlled lighting. Not because every client needs it, but because it teaches the core ideas fast.

You learn:

• Scene structure through Merge3D
• Material thinking through extrusion and surface look
• Depth control through camera placement
• Render consequences through shadows, reflections, and quality settings

Once that clicks, tracked text, stylized reveals, and particle-driven treatments make a lot more sense.

Here's a useful visual walkthrough for that kind of setup:

Trade-offs nobody tells beginners

Fusion is powerful, but it punishes messy thinking. A simple title that takes seconds on the Edit page can become an unnecessary tangle if you open Fusion too early.

Keep these trade-offs in mind:

• Best use case is text that must interact with a 3D world or advanced compositing
• Worst use case is simple labels and ordinary lower thirds
• Biggest risk is overcomplicating a project that needed speed, not spectacle

If the audience only notices that the title is clean and believable, the Fusion work succeeded.

For branded promos, trailers, and hero moments, Fusion is worth the extra setup. For everyday on-screen text, it usually isn't.

The Smart Way to Add Subtitles with SRT Files

Manual captioning is one of the fastest ways to burn editing time on work that shouldn't be manual anymore. Typing each line, trimming each out-point, nudging each phrase into sync. That's the slow path, and a lot of DaVinci Resolve tutorials still push people toward it by focusing only on text clips.

The bigger gap is transcript-based workflow. As noted in the verified data from the referenced YouTube tutorial, existing DaVinci Resolve text tutorials focus on manual text placement but provide zero guidance on integrating transcription data, even though using an SRT file import can eliminate the time-prohibitive task of manually typing captions.

The workflow that saves the most time

The cleanest process is simple:

1. Create a transcript outside Resolve
2. Export it as an SRT file
3. Import that SRT into Resolve
4. Let Resolve build a subtitle track
5. Style the captions globally instead of clip by clip

This changes the job completely. You're no longer “adding text” one caption at a time. You're managing a timed language asset.

Why SRT beats manual text clips

SRT files carry timing. That's the breakthrough. Instead of dragging title clips onto the timeline and trying to align words by eye, Resolve reads the timecode and places subtitle events where they belong.

That's especially useful for podcasts, interviews, webinars, courses, and YouTube talking-head content where spoken language drives the edit. If your source transcript includes speaker changes or clean timestamps, the subtitle pass becomes review work instead of data entry.

If you need a clearer sense of common transcript export structures before you import anything, this guide to video transcription format options is worth reviewing.

How to import subtitles into Resolve

Inside Resolve, bring the SRT into the project and place it on a subtitle track. Resolve will generate subtitle segments based on the file timing. Once that track exists, you can adjust subtitle settings for the whole set instead of opening dozens or hundreds of individual title clips.

That global control is the reason subtitle tracks age better than hand-built caption timelines. If the client wants a different font or background style, you update the subtitle styling instead of rebuilding the sequence.

What to check after import

Don't assume the file is perfect just because it synced automatically.

• Scan line breaks because awkward sentence wraps make captions harder to read
• Watch speaker changes if the transcript came from a multi-speaker source
• Check punctuation style so the captions match the tone of the final video
• Review timing around fast edits because jump cuts can make a valid subtitle feel late

Subtitle workflow is strongest when text creation happens before editing polish, not during it.

The real advantage for creators

This method separates two jobs that often get mixed together. Transcript generation happens in one stage. Caption styling and final video finishing happen in another. That separation keeps the edit cleaner and makes revisions less painful.

For teams publishing regularly, this is the difference between captions being “something we should do” and captions becoming part of the normal post process.

Essential Tips for Readability and Polish

Many text tutorials focus only on style. They demonstrate shadows, gradients, and animations, then finish there. That misses the part that viewers feel. Good text isn't just attractive. It's readable, timed well, and consistent.

The accessibility gap is real. As summarized in the verified data from the referenced YouTube source, most text styling tutorials prioritize aesthetics over function, failing to address accessibility compliance, while creators still need guidance on WCAG 2.1 AA contrast ratios and optimal font sizes for different viewing contexts. That doesn't mean every editor needs to become a compliance specialist. It does mean text choices should survive real screens and real audiences.

Start with readability, not decoration

If viewers have to squint, rewind, or pause to read your text, the design failed. That's true even if the title looks stylish in the viewer window.

A few habits improve legibility immediately:

• Keep contrast high between text and background. White over bright footage without support almost always fails.
• Use support layers carefully. A subtle shadow, solid bar, or darkened patch behind text often solves the problem faster than changing the font.
• Choose fonts for clarity first. Thin display faces break down quickly on mobile screens and compressed exports.
• Respect safe placement. Lower edges of the frame get crowded by player controls, subtitles, and social app overlays.

If you want a deeper typography reference for caption-heavy projects, this roundup on the best font for subtitles is useful.

Motion should feel intentional

Animation is where polished text often falls apart. Editors add movement, but the movement has no rhythm. The text slams in, stops abruptly, then flies out for no reason.

Use easing on keyframes whenever possible. Linear motion tends to look robotic. Even a small ease-in or ease-out makes text feel more natural because objects in nature don't start and stop at constant speed.

A better approach to text animation

• Entrance first, exit second
  Many titles only need a clean entrance. If the cut removes the text naturally, skip the fancy outro.

• Match motion to content type
  A corporate webinar lower third shouldn't animate like a gaming montage intro.

• Limit simultaneous effects
  Position, scale, blur, rotation, and opacity all moving together usually feels excessive.

Clean text feels effortless because the editor removed distractions before export.

Build repeatable style recipes

Consistency is what makes text look professional across an entire project. One polished lower third doesn't help if the next three use different sizing, alignment, and motion language.

Try building a few repeatable patterns:

Save these as presets or duplicate from previous projects. The goal isn't sameness for its own sake. It's reducing unnecessary decision-making so every new video doesn't start from zero.

The finishing pass most editors skip

Before exporting, watch the full piece once with your attention on text only. Not the pacing, not the cuts, not the color. Just the text.

Check for:

• Inconsistent capitalization
• Placement drift between similar graphics
• Overlong caption lines
• Titles that overlap faces or important frame detail
• Animation that draws attention at the wrong moment

That pass catches more quality problems than people expect. It's also where a good video starts feeling finished instead of merely assembled.

If captions, transcripts, or subtitle exports are slowing down your workflow, meowtxt makes that part easier. You can turn audio or video into editable transcripts, generate SRT files for DaVinci Resolve subtitle tracks, and keep the text side of post-production moving without the usual manual grind.