← Back to Blog

WhatsApp Blue Tick Video: How to Animate Read Receipts

·13 min read

Most fake WhatsApp videos waste their best asset. They animate the messages, they animate the typing indicator, and then they leave the little ticks under each bubble sitting in whatever state they started in. That is a missed beat, because in a real WhatsApp conversation the ticks are the part everyone actually watches. The message is what you said. The ticks are what happened next.

This guide covers the three receipt states WhatsApp uses, how MockClip animates the transition between them as a timed chain, and how to build the two scenes that depend on that chain entirely — the anxious wait for delivery, and the far more brutal moment when the ticks go blue and nothing comes back.

One outgoing message moving through all three receipt states — single grey tick, double grey tick, double blue tick — each on its own delay.

Why the read-receipt beat carries a story

A chat bubble is a statement. A receipt is a consequence. That difference is why the ticks do so much narrative work for so little screen space.

They convert waiting into something visible. Silence is hard to film. A person staring at a phone is a cliché. But a single grey tick sitting under a message for three seconds is legible instantly, and it communicates the exact feeling — it went, and nothing has come back — without a caption, a voiceover, or a cut.

They create a countdown the viewer can read. Once the audience recognises the tick sequence, every state change is a beat they can anticipate. One tick means it is still travelling. Two ticks mean it arrived. The viewer knows what the third state is going to be, and waiting for it is what keeps them watching.

They deliver a punchline without dialogue. The turn to blue is the sharpest single frame in chat-app storytelling. It removes every excuse at once. They did not miss it. They did not lose signal. They opened the chat, they read the words, and they chose what happened next.

They are unfakeable in a screenshot. A static screenshot can show blue ticks, but it cannot show them becoming blue. The transition is the thing that only video can carry, which is exactly why it is worth animating rather than importing a still.

What the three WhatsApp check states actually mean

The template mirrors WhatsApp's own three-state model, so it is worth being precise about what each state claims.

Single grey tick — sent. The message left the sender's device and reached the WhatsApp server. It has not necessarily reached the other person. This is the state that persists when someone's phone is off, out of signal, or has run out of battery mid-conversation.

Double grey tick — delivered. The message reached the recipient's device. Their phone has it. They have not necessarily opened the chat, and they may not even have looked at the notification. This is the state that carries plausible deniability, which is what makes it useful as a middle beat.

Double blue tick — read. The recipient opened the conversation and the message was displayed on their screen. In MockClip the read state is drawn in #53BDEB, WhatsApp's receipt blue, while the sent and delivered states are drawn in #8696A0 grey. Both the light and dark themes use the same two colour values, so switching theme changes the chat background without changing the receipt colours your audience is trained to recognise.

Worth knowing for accuracy: ticks only ever appear on your own outgoing messages. They are a report on something you sent, so the template only applies receipt fields to messages whose sender is set to me. If you find yourself wanting a tick under an incoming message, the scene you actually want is the mirror image — write it from the other character's point of view instead.

How MockClip animates the receipt chain

Open the WhatsApp template and each outgoing message carries three independent receipt toggles, each paired with its own delay:

  • showSentCheck with sentCheckDelay
  • showDeliveredCheck with deliveredCheckDelay
  • showReadCheck with readCheckDelay

The important detail — and the one that trips people up — is that these delays chain. They are not three timestamps measured from the same zero point. Each one counts from the previous event:

  1. sentCheckDelay counts from the moment the message bubble appears.
  2. deliveredCheckDelay counts from the moment the sent tick appeared.
  3. readCheckDelay counts from the moment the delivered tick appeared.

So a message with sentCheckDelay: 0.4, deliveredCheckDelay: 1.2, readCheckDelay: 2.0 puts the blue ticks on screen 3.6 seconds after the bubble lands, not 2.0. Describing gaps rather than absolute times is more natural once you are used to it, because a scene is built out of pauses — but it does mean you should add the values up when you are budgeting a clip for a platform with a hard length ceiling.

You can also turn states on selectively. Enabling only the sent state gives you a message that never gets delivered. Enabling sent and delivered but not read gives you the classic "they have it and they are ignoring it" beat. Every combination is a different story, and none of them require you to edit a single frame by hand.

Step-by-step: building a read-receipt sequence

Step 1: Set the contact header

The name and status line above the conversation frame the whole scene before a single message appears. The status field takes any string, so it can carry real information: online reads as active and available, while last seen today at 23:47 reads as someone who was here recently and is not here now. Pairing a "last seen" status with a message that goes blue is a small contradiction viewers notice immediately — the chat says they left, the ticks say they came back.

Step 2: Write the outgoing message

Keep it short and make it demand a reply. Receipt-driven scenes fall apart when the message is chatty, because a chatty message does not need an answer and the silence stops meaning anything. A question, an ultimatum, or a single logistical line all work. so are we still doing tomorrow or not is a better read-receipt message than three sentences of context.

Step 3: Turn on the receipt chain

Enable all three states on that message and set the delays. Start with something close to 0.4, 1.0, 2.4 and adjust from there. Those values give a fast handoff from sent to delivered — which is what really happens when both phones have signal — and then a longer, more visible pause before the read state lands.

Step 4: Decide whether a reply comes

This is the fork in the road, and it defines which of the two formats you are making. Add a message from the other person and you have a normal conversation with texture. Add nothing and you have a left-on-read clip. Add a second outgoing message instead, and you have the most uncomfortable version of all.

Step 5: Preview, then export

Play the clip end to end before exporting and watch the ticks rather than the text. You are checking one thing: does the blue arrive at the moment the scene needs it. If it lands too early the tension never builds, and if it lands too late the viewer has already scrolled.

Free to use in the browser. No install, no screen recording.

Open the WhatsApp chat template

The left-on-blue-ticks format

The strongest use of the receipt chain is the one where nothing comes back. It is worth treating as its own format, because it is built differently from a normal conversation clip.

Two outgoing messages both run the full receipt chain to blue. No reply arrives. The status line reads last seen, and the silence lands harder than any answer would.

The construction is simple. One outgoing message runs the full chain to blue. Then, after a longer-than-comfortable pause, a second outgoing message — usually much shorter than the first — also runs the full chain to blue. The second message is where the scene gets its edge, because a single ? that is read and ignored says considerably more than a paragraph.

Three things make this version work:

The second message must be shorter. A long follow-up reads as explaining yourself. A one-character follow-up reads as someone who has stopped explaining. Set its delayBefore to something uncomfortable — three to five seconds — so the audience feels the gap the character waited through.

The pause before the second blue must be longer than the first. If both receipt chains run at identical speed, the scene reads as mechanical. Stretching the second readCheckDelay makes the final blue feel deliberate, like a decision rather than a notification.

Nothing follows. Resist adding a reply, a typing indicator, or a closing card. The clip should end a beat or two after the last tick turns blue. Ending on silence is the whole format.

Timing patterns that read as real

Real receipt timings are not evenly spaced, and matching their unevenness is most of what makes a clip convincing.

Sent to delivered is fast. On two phones with signal, this is a fraction of a second. Values between 0.3 and 1.2 land in the believable range. Anything longer starts implying a connectivity problem, which is a story choice rather than a default.

Delivered to read is where the drama lives. This gap is entirely under the recipient's control in the real world, so it is where you should spend your seconds. Two to four seconds reads as someone picking up their phone. Eight or more reads as someone who saw the notification, decided not to deal with it, and then dealt with it anyway.

A stalled sent tick is its own scene. Enable only showSentCheck and let the clip run. One grey tick that never becomes two is the visual language of a phone that is off, and it sets up a completely different story — worry rather than rejection.

Pair the chain with the typing indicator carefully. The other person's typingDuration and the read state interact. Typing that begins immediately after the blue ticks reads as an urgent reply. Typing that starts, and is then followed by a long silence with no message, reads as someone drafting an answer and deleting it — a beat that is unusually hard to achieve in any other format.

Where the receipt chain fits into larger content

The format is rarely a whole video by itself. It is a component, and it slots in cleanly:

  • As a cold open. Two seconds of a message going blue with no reply, then a hard cut to a talking head reacting to it.
  • Inside a storytime. Cut to the chat at the moment the story reaches "and then I saw the blue ticks", then cut back.
  • As a green-screen overlay. Composite the chat over your own footage. For the mechanics of keying a chat clip over live video, see the green-screen notification workflow.
  • As the second half of a two-app scene. Show a phone call going unanswered and then a WhatsApp message going blue. The pair says one thing: they are choosing not to respond.
  • As a product or support demo. The chain is not only for drama. A message that visibly reaches delivered and then read is a clean way to illustrate a messaging integration or a customer-support SLA without recording a real account.

Common mistakes to avoid

Every state fires at the same speed. Uniform delays are the single biggest tell. Real receipts arrive in an uneven rhythm; copy that.

The read state lands before the viewer has read the message. If your blue ticks arrive 0.8 seconds after a two-line message appears, nobody has finished reading the bubble yet, and the beat is wasted. Let the message land first.

Ticks on incoming messages. They do not exist in real WhatsApp and the template does not render them. Restructure the scene rather than trying to force it.

A status line that contradicts the scene without meaning to. online next to a message that sits unread for ten seconds is a plot hole. Use it when the contradiction is the point, not by accident.

Forgetting the ticks are small. On a phone screen, viewed at arm's length, the difference between grey and blue is a few pixels of colour. If the receipt change is your punchline, hold on it — give the clip an extra second after the transition rather than cutting on the frame it happens.

Overloading the clip. A receipt-driven scene needs one or two messages, not twelve. The template accepts up to twenty messages, but a left-on-read clip that uses all twenty has buried its own ending.

Exporting and posting

Export produces a vertical MP4 sized for short-form feeds, which is what TikTok, Reels, and YouTube Shorts all expect. Because the frames are rendered rather than screen-recorded, there is no capture artefacting and no risk of a real notification sliding into shot mid-take.

A few practical notes for the platforms:

  • Hold the last frame. Feeds loop. A clip that cuts one frame after the blue ticks appear will loop before the beat registers. A short tail gives the transition room.
  • Add sound deliberately. The receipt change is silent in real WhatsApp, so the temptation is to leave it silent here. A quiet sting or a beat drop placed exactly on the colour change is one of the cheapest ways to make the moment land.
  • Caption for sound-off viewing. Most of the feed watches muted. If the story depends on the ticks, a caption that points at them — "watch the ticks" — measurably helps the first-time viewer know where to look.

For watermark and export-resolution details on each plan, see the pricing page.

Quick start

  1. Open the WhatsApp template
  2. Set the contact name and a status line that frames the scene
  3. Write one short outgoing message that demands an answer
  4. Enable the sent, delivered, and read states on it
  5. Set the delays to roughly 0.4, 1.0, 2.4 and adjust after previewing
  6. Decide whether a reply comes — or deliberately let it not come
  7. Preview, watching the ticks rather than the text, then export the MP4

Related MockClip templates and guides

Frequently Asked Questions

What do the WhatsApp ticks actually mean?

One grey tick means the message left your phone and reached the WhatsApp server. Two grey ticks mean it was delivered to the recipient's device. Two blue ticks mean the recipient opened the chat and the message was displayed. MockClip's WhatsApp template renders all three states as separate, individually timed steps so you can animate the transition rather than showing a single frozen state.

Can I animate the change from grey ticks to blue ticks?

Yes. That transition is the entire point of the template's receipt fields. Each of the three states has its own toggle and its own delay value, so the ticks change on screen while the clip is playing instead of being baked in as a static image.

How are the receipt delays measured?

They chain rather than stacking from a single zero point. The sent delay counts from the moment the message bubble appears, the delivered delay counts from when the sent tick appeared, and the read delay counts from when the delivered tick appeared. That means you describe the gaps between states, not absolute timestamps.

Do read receipts work on messages from the other person?

No, and that matches real WhatsApp. Ticks only ever render on your own outgoing messages, because they report the status of something you sent. In the template the receipt fields are only applied to messages whose sender is set to me.

What colour are the blue ticks?

MockClip renders the read state in #53BDEB, the WhatsApp receipt blue, and renders the sent and delivered states in #8696A0 grey. Both the light and dark themes use the same two values, so a clip keeps the same receipt colours whichever theme you export.

Can I make a left-on-read video where the blue ticks appear but no reply comes?

Yes. Turn on all three receipt states for your outgoing message, then simply do not add a following message from the other person. The ticks turn blue, the chat sits there, and the silence does the work. Adding a second outgoing message a few seconds later sharpens it further.

Do I need a real WhatsApp account or a screen recorder?

No. The template draws the WhatsApp interface in the browser and exports it directly to MP4. Nothing is captured from a real device, so there is no status-bar clutter, no notification interruptions, and no compression from a screen-recording pass.

Is it legal to make fake WhatsApp chat videos?

Making clearly fictional chat clips for entertainment, education, or illustration is legal in most places. Do not use the format to impersonate a real, identifiable person, to defraud anyone, or to harass. Where a viewer could genuinely be misled, label the clip as dramatised.

Related Articles

How to Make a Fake WhatsApp Chat Video (2026 Guide)

Complete 2026 guide to creating realistic fake WhatsApp chat videos for TikTok, Reels, and Shorts — typing dots, blue ticks, MP4 export, no install required.

WhatsApp Chat Animation Generator: Create Viral Videos

Free WhatsApp chat animation generator for creating realistic message videos. Animate conversations with typing indicators, read receipts, and timestamps.

WhatsApp Chat Video for YouTube Shorts: Full Guide

Create fake WhatsApp conversation videos for YouTube Shorts and TikTok. Free browser tool with typing indicators, read receipts, and MP4 export.

WhatsApp Prank Video Maker: Create Fake Chat Videos

Create realistic fake WhatsApp prank conversation videos with typing dots, blue ticks, and reactions. Free browser-based tool for TikTok, Reels, and Shorts.