2026-11-17 · 5 min read

How to Add Captions to Instagram Stories (and Why Native Stickers Are Not Enough)

A film strip of vertical phone video scenes, the middle frame showing the captioned word STORY
This image was generated with AI.

Instagram Stories are vertical, short, and mostly watched on mute. Meta's own data has said for years that a large share of Stories play without sound, and every creator survey since has agreed. If your Story is you talking to camera, captions are the difference between watched and skipped.

The native caption sticker, and where it falls short

Instagram's built-in caption sticker is free and fast, so use it when it is enough. But it has real limits: the transcription mis-times words on fast speech, the style options fight most brand designs, the sticker only covers the segment you attach it to, and when someone reshares or downloads your Story the captions do not always travel with it.

Burned-in captions: text that is part of the video

Burning captions into the video file makes the text permanent. It survives reshares, downloads, and cross-posting the same clip to TikTok or YouTube Shorts. The style is yours: font, size, color, and position locked to your brand instead of Meta's sticker presets.

Story-specific placement

Stories are 9:16 with UI chrome at the top and bottom: your handle and timestamp above, the reply field and reaction row below. Keep captions in the lower-middle band, roughly the bottom quarter but above the reply bar. Bottom-positioned captions at a moderate size land in that band on standard 1080x1920 footage.

Caption a Story clip with the API

Upload the vertical clip somewhere addressable, then send one request. Options are nested in the request body, so the style is explicit and repeatable.

curl -X POST https://api.caption.sh/v1/videos \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "source_url": "https://cdn.example.com/stories/launch-teaser.mp4",
    "options": {
      "font": "Inter",
      "font_size": 52,
      "font_color": "#FFFFFF",
      "position": "bottom"
    }
  }'

The job moves through queued, awaiting_upload, running, and done. When it finishes, /result answers with a 302 and the download URL in the Location header. Rendered files live for 24 hours, the per-video cap is 10 minutes (far longer than any Story), and processing costs $0.10 per minute.

A workflow that scales past one Story a day

Teams running daily Stories can wire the API into their publishing flow: export the cut, caption it, download, schedule. The captions look identical on every Story you post, which is quietly one of the strongest brand signals on the format.

Back to all articles