How to show a text message exchange on screen long enough to read it

Last updated 2026-09-15 · 8 min read

What is the short version?

A screen-recorded or recreated chat is a piece of writing pretending to be an event. If it animates at the speed somebody types, nobody finishes reading it, and the whole point of putting it in the video is lost.

1. Go to Vizard Agent with the clips and the exchange.
2. Say the whole chat must be readable, reply included.
3. Ask for the reply to appear separately.

What do you need before you start?

The exchange and a view on how long it can run. Vizard Agent paces reveals to reading time, so the number of messages sets the section's length — and a long chat in a thirty-second video is the two constraints fighting each other.

• The messages. Written out, in order.
• Where it sits. Usually early, after the setup shot.
• Whether names are shown. They usually should not be.
• How long the video can run. Reading takes seconds.
• What the reply is worth. It is often the whole joke.

What do you type into Vizard Agent?

Say it has to be read, not just seen. A chat overlay looks finished long before it is legible, and asking for "a text message animation" gets you an animation rather than something a viewer gets to the end of.

Prompt

Variants worth knowing:

• "Including the response." The part that gets cut.
• "Let the reply land on its own." Separate reveals.
• "Different tones." Sent and received are not the same sound.

What does Vizard Agent actually do?

Here is the sequence Vizard Agent worked through on a real short built around a message exchange. The chat went in early and then took three separate passes to settle, and every one of them was about time rather than about how it looked.

1. Builds the animated chat overlay and renders a first cut.
2. Moves the sequence to where it belongs in the story.
3. Generates short, distinct sending and receiving tones.
4. Checks the reveals against the tones for sync.
5. Extends the chat so the exchange can be finished.
6. Separates the reply from the last message.
7. Anonymises the chat area before delivery.
8. Verifies on the uploaded copy that the whole chat is readable.
9. Confirms nothing identifying survived the anonymising.

Step three is a detail worth insisting on. Two identical tones tell a viewer nothing, whereas a distinguishable send and receive lets them follow who is talking without reading the alignment of the bubbles.

Step five is the one that costs you seconds and is worth them. Extending the chat so the exchange can actually finish means the section grows, and the temptation is to speed the reveals up instead — which gets you back to a chat nobody reads.

Step six is where the beat comes from. A reply that appears with the message it answers reads as a screenshot; one that arrives a moment later reads as an exchange, and that small gap is what makes a punchline in a chat land at all.

Step eight matters because chat overlays are always checked in the edit and rarely on the phone. Text that is comfortable on a monitor can be too small in a vertical video, and the only honest check is the delivered file at its real size.

What does the result look like?

An exchange a viewer actually finishes reading, with the reply landing as its own separate moment. The section runs longer than you expected it to, because reading is a good deal slower than typing and the video has to make room for that.

Vizard Agent also tells you how long each message holds, so you can trade seconds between them if the runtime is fixed.

When does this not work well?

Chat sections are expensive in screen time, and Vizard Agent will say when the arithmetic does not work. A long exchange simply does not fit a short video, and squeezing it to fit produces something that is present on screen and unreadable, which is worse than leaving it out altogether.

• Long exchanges in short videos. The arithmetic fails.
• Fast-cut formats. Reading needs stillness.
• Small vertical formats. Bubbles get tiny.
• Real conversations. Anonymising is not optional.
• Screenshots as-is. They rarely read at video size.

How do you fix a result that came back wrong?

Say which particular message you could not finish reading. Because Vizard Agent times each reveal separately rather than as one animation, holding a single message longer is a local change that does not push everything after it down the timeline.

• "I could not finish the third one." That one holds longer.
• "The reply gives it away too early." More gap before it.
• "It is too long now." Fewer messages, not faster ones.
• "A name is still visible." The anonymising missed it.

How does Vizard Agent compare to doing it yourself?

By hand a chat animation is built to look like typing, because that is what a chat looks like. It is then judged in the timeline at full size by somebody who already knows what it says, which is the one person who cannot tell whether it is readable.

Common questions

How long should a message hold? Long enough to read it twice. Vizard Agent sizes it to the words.

Can it use my real screenshots? Yes, though Vizard Agent will usually rebuild them to be legible.

Will it hide the names? Yes. Ask Vizard Agent to anonymise the whole chat area.

Does the reply need its own beat? Almost always, and Vizard Agent gives it one. That is where the moment is.

What about typing indicators? They add time. Vizard Agent will say what they cost you.

Can it add the tones? Yes. Vizard Agent generates short, distinct ones for sent and received.

Will it fit thirty seconds? Depends on the message count. Vizard Agent will tell you before building.

Can the chat scroll? Vizard Agent can, though scrolling and reading compete. A hold is safer.

What if it is a real exchange? Then anonymise it, and Vizard Agent checks the delivered copy.

Does it match a particular app's look? Vizard Agent can approximate one. Tell it which style you want.

Can it read the messages aloud? Yes, though Vizard Agent treats that as a different effect from showing them.

Will the music duck under it? Ask and Vizard Agent will drop the bed for the tones.

How do I shorten it? Cut messages rather than hold times. Vizard Agent will suggest which.

Why did mine feel unreadable? Because it was paced to how fast someone types, not how fast someone reads.