
A video caption can mean the description below a post or the timed words on the picture. This guide concerns timed subtitles. Decide whether viewers should be able to turn them off before choosing your workflow, because a selectable track and burned-in text behave differently.
Instagram and YouTube have native caption controls. Postbean accepts a subtitle file you supply and renders its text into a new video. That gives you visible words in the exported picture, but it does not transcribe the audio or create selectable language tracks.
Choose between native tracks and burned-in text
Use a native subtitle track when viewer control matters. A person may want to turn captions on, turn them off or select a language. Use burned-in text when the brief requires particular wording to remain visible in the picture across destinations.
You can also supply a native track alongside a captioned picture where appropriate, but check the viewing result. Two copies of the same sentence can overlap and make the video harder to follow. Do not assume the native app will detect or remove words already drawn into the frames.
Keep the original video and subtitle file outside the publishing draft as your source materials. If someone corrects a name or changes the edit later, you need both to prepare a clean revision. A screenshot of the subtitles is not an editable timing file.
Use the network’s own controls
Instagram Reels
Prepare the Reel in Instagram and review the caption controls offered before sharing. RNID’s Instagram guidance describes native autogenerated closed captions and where to enable them. Availability and controls can differ, so inspect your actual Reel rather than assuming a supplied subtitle file will attach as a native track.
YouTube Shorts
In YouTube Studio, select the video, open Subtitles, choose its language and add a timed file or use the available editing options. Follow YouTube’s subtitle instructions. YouTube also documents automatic captions for Shorts; review the words instead of treating speech recognition as a finished transcript.
Prepare a timed file for Postbean
Postbean accepts SRT or VTT, with limits of 512 KiB and 500 cues. A cue is a timed text block, not necessarily one word or one line. Keep the file aligned with the final edit, including any trimmed intro.
A simple SRT cue looks like this:
1
00:00:00,500 --> 00:00:02,500
Check the hinge before tightening it.
The first timestamp begins the cue and the second ends it. Make sure the end follows the start. Separate cues clearly and save the text in a suitable encoding such as UTF-8. If your editing tool exports a different subtitle format, export SRT or VTT rather than changing the filename extension.
Do a language pass before uploading. Check names, numbers, units and negations against the speech. Losing “not” can reverse an instruction. Split a long sentence at a natural reading point rather than forcing a full paragraph into one cue.
Add subtitles in Postbean
1. Upload the final video
Open Create post, choose Video and upload a single finished clip for this first pass. Postbean accepts MP4 or QuickTime videos up to 100 MiB. Confirm that the source has the right edit and does not already contain an outdated subtitle layer.
If you are using the same clip for Instagram and YouTube, select those accounts and review each network’s requirements. The subtitle feature does not remove caption limits or turn any video into a Short. YouTube classification still depends on the uploaded video’s actual properties.
2. Attach the subtitle file
Use Upload SRT below the video and select the SRT or VTT file. Open Edit text to inspect wording and timing. The composer preview overlays text while you work; this preview is not proof that the final rendered file has already been produced.
Check several cues, not just the first one. A track can begin correctly and drift after an edit. Test a fast sentence, a pause and the last spoken line. Watch once with sound for synchronization and once muted for readability.
3. Choose the vertical position
Select top, center or bottom according to the footage. Keep words away from a face, product label or step that viewers need to see. The native apps also place controls around the image, so inspect the result on the intended surface.
Postbean’s captioned output is a vertical 1080 × 1920 MP4. Prepare footage with that output in mind, particularly if your source is wide. Do not wait until launch to discover that a demonstration near the side of the original frame no longer reads well.
4. Save a draft to render
Save as draft to start rendering without publishing. Postbean keeps the original and creates a separate captioned output. It waits for the required render before publishing rather than quietly sending the plain clip when subtitles are not ready.
Leave enough time to inspect the rendering status and final treatment. If you change the text or position, save again and expect another render. A correction to a saved subtitle file does not update a video that is already live on a network.
Use different text for different networks
Open Native versions per network and choose the destination tab. Under its captions section, upload a different timed file or edit the inherited text. You can also choose a different position for that destination.
For example, keep English as the default and supply a Spanish file for Instagram. Postbean uses the words you provide; it does not translate them automatically. Make sure the translated text fits the same timing rather than assuming every phrase takes the same space to read.
Clearing a network’s replacement restores the default subtitles. It does not disable subtitles for that destination. If only Instagram should have text, leave the shared default unset and configure Instagram’s own file. The subtitle feature guide explains that inheritance behavior.
Check the destination limits before choosing a time
Subtitles do not expand the other text fields. In Postbean, Instagram’s caption has a 2,200-unit UTF-16 limit; YouTube’s description has 5,000 and its title has 100 characters. A new YouTube Short must also meet the square-or-vertical and up-to-three-minute eligibility rules. Keep those checks separate from the subtitle file’s 512 KiB and 500-cue limits.
For native scheduling, finish caption preparation before confirming Instagram’s schedule or YouTube Studio’s Visibility schedule. Follow the individual Instagram scheduling steps or Shorts scheduling steps and inspect the saved entry. In Postbean, wait for the captioned output before depending on the scheduled release.
Common errors
The file is rejected
Check its actual format, size and cue count. A renamed document is not a valid SRT. Inspect timestamps and ensure the file contains usable text blocks. Fix the source or export again rather than repeatedly uploading the same invalid file.
The subtitles lag behind speech
Compare the timing against the final cut. If you trimmed the opening after export, the whole track can be shifted. If only later cues drift, inspect the edit around the point where synchronization changes instead of shifting every cue blindly.
The wrong language appears
Open the destination’s subtitle version and check whether it inherits the shared default. Confirm which file you saved and wait for the latest render. A language-specific captioned video needs its own correct output; the default is not an appropriate substitute.
The schedule waits for rendering
Check render status and the supplied file. Postbean does not fall back to an uncaptioned version when that post requires subtitles. Resolve the render before relying on the slot. Do not recreate the public post while another send may still be in progress.
Review before scheduling
Play the clip through, check difficult words and inspect the first and final cues. Confirm the intended network, language, position and render readiness. Then choose the schedule and verify the saved date. After publication, inspect the native video for overlapping tracks or obscured words before repeating the setup on the next Reel or Short.
Example: a name corrected after review
If a reviewer catches a misspelled product name, correct the timed source text before producing the next render. Check every occurrence, including the last cue, then inspect the network-specific version if it uses another language. Keep the corrected subtitle file with the final video source. That small record helps you avoid reusing the old spelling when the same clip becomes another post later.
Sources
- YouTube Shorts eligibility — checked November 22, 2026
- YouTube: upload and edit subtitle tracks — checked November 22, 2026
- YouTube: automatic captions on Shorts — checked November 22, 2026
- RNID: Instagram caption controls — checked November 22, 2026