Text-story guide
A convincing text-message story is a tiny screenplay between two people. Start with the final reversal, work backwards through the evidence, preview the bubble rhythm, then add narration, captions, music, and deliberate reading time in an editable video project.
Maintained by the FrameCompose product team · Last reviewed 23 August 2026
Choose two fictional speakers and one clear source of tension.
Write the final reveal before filling in the earlier messages.
Preview every bubble for clarity and realistic reading speed.
Keep narration, captions, music, and scene timing editable.
Write the last important message first. It should reveal evidence, expose a false assumption, or force one speaker to make a decision. A final bubble that merely repeats the premise will feel like the story stopped rather than ended.
Then write one sentence describing what the viewer believes before the reveal and what they understand afterwards. That contrast is the spine of the conversation.
Keep the conversation between exactly two people so the viewer can immediately understand which side owns each bubble. One speaker usually wants an answer while the other delays, denies, redirects, or reveals information.
Use different vocabulary and message lengths for each person. Names, emojis, and slang can help, but the story should still be understandable without relying on colour alone.
A practical six-beat structure is: normal opening, suspicious detail, denial, specific evidence, reversal, and final consequence. Delete greetings or reactions that do not change the situation.
Keep most messages to one or two short lines. Long explanations slow the visual rhythm and make the viewer read ahead instead of waiting for the next bubble.
Paste the conversation into the free text story maker as “Name: message” lines. Check that the correct speaker appears on each side, the names remain consistent, and the reveal still works when the messages are seen one at a time.
Read the thread aloud. If a sentence sounds unnatural or requires rereading, simplify it before creating narration and scenes.
Let short reactions move quickly, but hold evidence and the final reveal long enough to read comfortably on a phone. Narration should support the message instead of speaking far ahead of the visible bubble.
Preview the complete video once with sound and once muted. Correct names, timing, captions, and music, then confirm that the scenario is clearly fictional or authorised before publishing.
A few quick answers before you jump in.
Use the fewest messages needed to establish the situation and deliver the reversal. Six to twelve concise bubbles is a useful starting range, but clarity matters more than a fixed count.
Not necessarily. Narration can improve accessibility and pacing, but a readable silent version can work when the message timing, captions, music, and sound design carry the scene.
Yes. The FrameCompose text story maker previews a two-person iMessage-style thread in the browser without an account. The conversation can then be handed into the editable video workflow.
Only when you have the right and permission to publish it. For entertainment examples, use fictional names and details and never make invented messages look like evidence against a real person.
Explore the rest of the workflow, from first idea to final export.
Write or load a conversation and preview the message bubbles instantly.
Read pageSee the two-speaker scene, narration, caption, and editing structure.
Read pageStart from a complete fictional reveal and its live generation settings.
Read page