Typography · 8 August 2026
Burned-in subtitles vs native captions
When to burn titles into the file, when to leave words to TikTok or Reels, and how to keep both layers readable on a 1080×1920 canvas.
By the FramePad editorial desk · 12 min read · Updated 2026-08-28
They are not interchangeable
Burned-in type is pixels. Native captions are a UI layer. Accessibility, search, and muted autoplay all want the native field. Brand and the one-second hook want pixels you control. Using one layer for both jobs is how a caption covers a subtitle that was covering a lower-third.
A working split: burned-in type is three to six words, high contrast, in the title-safe centre or the title band below the status bar. The native field is the sentence, the names, the words a deaf viewer needs. If you only have time for one, use the native field and put the hook in the picture — a face, a product, a gesture.
Line length at 1080 wide
At 42 pixels on a 1080-wide master, a comfortable line is about 18–22 characters before it wants to wrap. A 28-character burn-in will wrap onto a second line that collides with TikTok’s username if you parked it at y = 74%. Measure. The overlap estimator on each tool page exists for this. If a six-word hook wraps into the caption well, shorten the hook.
Open captions that transcribe every word as burn-in will always collide. They are a landscape habit. On 9:16 they become a wall. Transcribe in the native field. Burn the title.
Contrast and the overlay
White type on a white shirt disappears before the caption well has a chance to cover it. Outline or a dark plate is not a taste. It is insurance. Do not put the plate in the rail. A full-width plate at the bottom is a caption well you drew yourself; TikTok will draw another on top.
Yellow burn-in on a yellow product is the same failure in a different hue. Check the still, not only the playhead.
Auto-captions will not save a bad burn-in
Platform auto-captions are useful and often wrong. They also occupy the well. If your burn-in already sits there, the auto-caption double-books the pixels. Turn auto-captions off only if you have provided a better native caption. Do not turn them off to “clean the picture” if the picture’s type is unreadable without them.
The article on captions covering text is the geometry. This page is the editorial rule: two jobs, two layers.
Language, search, and the file
Burned-in English on a file you will also post with a Spanish native caption is how you exclude one of the two audiences. Either burn nothing and caption natively per language, or version the burn-in. Search indexes the native field and the spoken audio more reliably than pixels. Pixels are for the person who will not unmute.
Export the clean file without the overlay. Proof with the overlay. Never ship the proof. Never burn “subscribe” into a file that will also run as a paid Story ad — Meta will read it as text overlap near the CTA.
Open the matching tool
Keep reading
TikTok vs Reels vs Shorts: where the overlays actually differ
A measured comparison of TikTok, Instagram Reels, and YouTube Shorts UI overlays on a 1080×1920 canvas — caption wells, action rails, and where on-screen type survives.
How to crop 16:9 to 9:16 without cutting faces
A practical method for converting landscape video to 9:16 vertical: pan per shot, avoid centre-crop accidents, and know when blur padding is the better master.
Instagram Story vs Reel safe zones
Stories and Reels are both 1080×1920, but the progress bars, reply field, caption well, and tab bar do not match. Here is what to keep clear on each.
Meta ad placements and the 9:16 safe zone
Where Meta draws sponsored labels, profile rows, and CTA buttons on 9:16 placements — and how to proof a creative before you spend.