Caption safe zones: Reels Shorts TikTok

Each short-form player draws a different chrome map on the same 9:16 file. Place captions for the chrome of the platform you are shipping to, not for a generic safe-area percentage.

A 1080×1920 export is not a finished layout. Instagram Reels, YouTube Shorts, and TikTok each composite their own interface on top of those pixels: a right-hand action column, a bottom identity row, a post-caption field, sometimes a shop tab or a subscribe control. Speech captions that sit on the true bottom of the frame are under that furniture. The safe area is the leftover rectangle, and it is not the same leftover on each app.

This page is three maps and one placement decision per map. It is not a table of pixel margins. Third-party overlays disagree with each other by hundreds of pixels, and they go stale the week a platform ships a denser caption field. The objects on the chrome do not move as fast as the measurements. Design to the objects. Check the live player.

TikTok's chrome map

TikTok's in-feed player is a right rail plus a growing bottom stack.

The right rail is the engagement column: profile avatar, like, comment, save, share, and the spinning sound disc. That column is dead for type. A caption that hugs the right edge sits under thumbs. Do not put a price, a username, or a karaoke punch in that strip.

The bottom stack is the identity of the post: @handle, then the post caption (the text you typed in the composer, not the burned-in speech), then the sound attribution. TikTok's own auction in-feed ad help is explicit that usable area depends on caption length: a longer composer caption occupies more of the frame. Organic posts inherit the same geometry even if the ad template is the document that names it. A two-line composer caption and a five-line one are two different bottom stacks on the same video.

Shop tabs, LIVE badges, and search sit on top of that map for some accounts. Treat them as extra chrome, not as a reason to invent a new percentage. The persistent decision is: the true bottom is gone, and the composer caption can steal more of it after you export.

TikTok currently takes uploads up to 10 minutes. That length does not change the chrome. A 9:16 talking-head still has the same rail and the same stack at second 8 and at minute 8. What changes is how long a bad placement stays on screen.

Reels' chrome map

Reels is a cousin, not a copy. Meta documents placement per surface in the Ads Guide rather than as one "Instagram" rectangle. Reels, Stories, and Feed each draw different overlays. A Stories-safe title card is not a Reels-safe caption.

On Reels the right rail is like, comment, reshare, and more. The bottom-left is username, then the Reel caption, then audio. Instagram has shipped a full-screen view that hides that overlay for the viewer; it does not hide it for the default feed, which is the view that decides whether the line was readable. Design for the default overlay, not for the person who taps "view full screen."

Reels can run to 20 minutes. The chrome is still a feed chrome. A 20-minute Reel is not a YouTube watch page. The username and the audio row still sit on the picture. If you treat a long Reel as "basically a video" and drop captions on the lower third the way a 16:9 explainer would, the first thing the feed covers is the line.

Reels also remixes into Stories and the profile grid. The grid crop is a 4:5-ish centre punch of a 9:16 file. Captions that only live at the extreme top or extreme bottom can vanish in that crop even when they survived the Reels player. If the clip will also sit on the profile, keep the essential line away from both extremes.

Shorts' chrome map

Shorts is the odd one of the three, and that is the reason a TikTok placement fails on YouTube.

The right rail is like, comment, share, remix — and, after YouTube's June 2026 Shorts pass, a heart in place of the old dislike control, with 2× playback in the same player (YouTube's own design-principles write-up, discussed 13 August 2026). The rail is thinner than TikTok's spinning-disc column. Right-edge type is still a bad idea. It is a smaller bad idea.

The bottom-left is the collision. Shorts draws the video title, the channel name, and a Subscribe control on the picture. That bundle is thicker than TikTok's @handle. A Classic caption parked on the true lower third sits under "Subscribe." Viewers who came from Search also get a title they already read in the shelf; your burned-in line repeating that title in the same band is two blocks of type fighting.

The top of a Short can carry search and, on some surfaces, a condensed title. Headline-family captions that default to the top of the frame (Headline in Caption Studio) need a check against that, not a free pass because "top is safer than bottom." Top is safer than TikTok's composer field. It is not empty.

Shorts currently cap at 3 minutes. The chrome does not get nicer at 2:50. If the closer is a spoken CTA captioned on the bottom, the Subscribe row will eat it.

One placement decision per platform

Do not average the three maps into a "universal" box and call the job done. A universal box is a compromise that is slightly wrong everywhere. Cross-posting is allowed; the caption position is a per-export choice.

TikTok — mid-lower, never true-bottom, hook at the top. Speech captions sit in the band above the composer field. Assume the composer caption might grow; do not design to a five-word post. Put the authored hook at the top of the frame so it cannot collide with the stack. Leave the right rail empty. If the mouth sits in the lower third, raise the caption or reframe the face — do not hope the stroke will save a line on someone's chin.

Reels — above the audio row, and use Meta's preview. Speech captions belong above username + caption + audio, not in it. The authored hook can live top-centre if the face is mid-frame. Check the actual Reel preview in the app before you batch a week. Reels is the surface that will also punch into the grid; if that destination matters, keep the claim out of the top 10% as well as the bottom stack.

Shorts — above Subscribe, and do not duplicate the title. Raise the speech block one cue-height relative to a TikTok layout. If the Short's title already states the claim, do not burn the same sentence as a Headline caption in the same vertical neighbourhood. Use the extra room Shorts gives you on the right only for picture, never for type.

Burned-in captions are pixels. A later "we'll move them for YouTube" is a second render. The AI caption generator is the transcribe-and-burn path; Caption Studio's position field is top, middle, or bottom per family, not a free-form pixel. Pick the family whose default already matches the decision: Classic / Paper / Ink at bottom for TikTok mid-lower once you have left margin above the stack; Classic Top or Paper Top when the mouth owns the bottom; Headline only when Shorts is not already printing a title there. Add captions to a video is the agent job: 165 language codes, 21 basic looks at 1× credits, 9 dynamic looks at 2×. Preview the first seconds on this 9:16, then watch the export inside each destination app.

A file posted to all three without a placement pass will be correct on at most one of them. Decide the primary, place for that chrome, and recaption the other two if the line is the product. If the line is only a transcript of speech, a slightly raised Classic block will survive all three better than a perfectly kerned karaoke punch sitting on TikTok's sound disc.

Place the next cut in Versely.

FAQ

Can I use one caption position for all three apps?

Only if you accept a compromise. A raised Classic block will usually clear TikTok's composer field, Reels' audio row, and Shorts' Subscribe control. A true-bottom karaoke line will not. If the caption is the hook, recaption per platform.

Do pixel templates from 2025 still work?

Treat them as snapshots. TikTok's own ad docs already say caption length changes the usable frame. Reels and Shorts have both densified their bottom stacks. Verify in the current player.

Should the hook line sit in the same band as the speech captions?

No. Put the authored hook at the top (or centre, off the face) and the transcript in the mid-lower band. Two layers in one strip is how both disappear under chrome.