← Back to Blog

iMessage Notification Maker: Multi-Banner Sequences

·Updated ·15 min read

A single notification banner is a hook. Several of them, arriving one after another, is a story.

One alert slides into frame and the viewer wonders who texted. Three alerts in a row, each from a different sender, tell the viewer something is happening — a group chat has caught fire, a launch went live, someone is being ignored. The format carries narrative that a lone banner cannot, with no dialogue and no footage.

This guide covers the multi-banner version of the format: exactly what the iMessage notification maker controls per banner, how the sequence timing really adds up (this is where most clips go wrong), the rhythms that read as natural, and how to export the result over a lock screen, a chroma key or a transparent background.

Three banners arriving one after another — each with its own delay and display duration. Note that only one is ever on screen.

If you want the single-banner fundamentals first, start with the iMessage notification generator guide and come back here for the sequencing layer.

First, the thing older guides get wrong

Banners do not stack. They queue.

The template plays them strictly in sequence: banner one appears, holds, leaves, and only then does banner two's delay begin counting. At any instant exactly one banner is on screen. There is no overlap mode, no pile-up, no setting that keeps an earlier banner visible underneath a newer one.

That is worth stating plainly because the mental model you bring to the format decides whether your timings work. If you plan a clip as "three alerts piling up on a lock screen", you will set short delays, watch the preview, and find a tidy carousel instead. If you plan it as "three alerts in quick succession", you will set the same numbers and get exactly what you intended.

Everything below is written for the second model.

Why a sequence outperforms a single banner

A single notification is a question: who is that? A sequence is a situation. A question can be ignored; a situation asks for context, and context is what carries a viewer past the three-second mark.

Rhythm creates expectation. Once two banners have arrived at a consistent interval, the viewer's brain schedules the third. That anticipation holds attention through a gap where nothing else is happening. Break the interval on the final banner and you get a small, cheap payoff.

Multiple senders build a cast. One banner introduces one character. Three banners from "Maya", "Dev Team" and "Mum" sketch a whole life in nine words. The sender labels are doing exposition that would otherwise cost you a voiceover.

Escalation is legible without words. Shorten the gaps and the sequence reads as accelerating pressure. Lengthen them and the same three messages read as a slow, ominous drip. You are editing pacing, not content.

It survives muting. Short-form video is often watched silently. A notification sequence is fully legible with no sound, because the information is textual and the motion carries the pacing.

What the maker actually controls

Before planning a sequence it pays to be precise about the knobs, because every technique below is built on them. The template holds an ordered list of banners, and each one carries its own settings rather than inheriting a global value.

Per banner, in the editor:

ControlWhat it doesDefault
Sender NameThe bold second line. Any text, emoji included — this is your character label"New Contact"
Message PreviewThe preview line. Wraps to at most two lines, then truncates with an ellipsis—
AvatarAn optional image upload (not a URL). With a photo the banner draws it as a circle with a small Messages badge on the corner, and grows slightly to fitnone
Delay BeforeDead time before this banner appears, in seconds0.5 s
Display DurationHow long it stays fully visible. Minimum 1 s in the editor4 s
Dismiss StyleSlide Up or Fade Out — see the note belowSlide Up

Clip-level:

ControlOptions
Light ThemeDark (black screen, charcoal banner) or light
BackgroundDefault (theme colour), Chroma Key with a colour picker, Custom Image, Transparent (alpha), or Lock Screen (wallpaper, date, clock)
Sound EffectsA notification tone on each banner's arrival, baked into the export. On by default
WatermarkRemoved on a paid plan; see pricing

Two fixed parts of the animation matter for planning: the entrance takes about 0.3 seconds and the exit about 0.3 seconds, and neither is adjustable. You are shaping the dead time around them.

And one honest note on Dismiss Style: the setting is stored per banner, but the canvas renderer that draws both the preview and the export animates opacity only, so Slide Up and Fade Out currently produce the same ~0.3-second fade. Do not plan a beat around the difference — use delay and duration, which genuinely change the result.

Three more things the template does not have, so you can stop looking for them: an editable timestamp (every banner reads "now"), an app-icon picker (it is always a Messages alert; a sender photo takes the leading slot and keeps the Messages badge), and any kind of simultaneous stack.

The sequence arithmetic

This is the single most useful thing to internalise, because it explains why clips come out longer than planned.

Total length is:

0.5 s lead-in
+ for each banner:  delay + 0.3 s in + display duration + 0.3 s out
+ 1.0 s tail

Worked through, with three banners at the defaults (0.5 s delay, 4 s hold):

  • Lead-in: 0.5 s
  • Banner 1: 0.5 + 0.3 + 4.0 + 0.3 = 5.1 s
  • Banner 2: 5.1 s
  • Banner 3: 5.1 s
  • Tail: 1.0 s
  • Total: 16.8 s

That is a long clip for three lines of text. Now the same three banners tuned for a burst — 0.3 s delay, 1 s hold:

  • Lead-in: 0.5 s
  • Three banners at 0.3 + 0.3 + 1.0 + 0.3 = 1.9 s each → 5.7 s
  • Tail: 1.0 s
  • Total: 7.2 s

Two consequences follow:

The perceived gap between banners is bigger than the delay. Because the previous banner has to finish leaving before the next one starts arriving, the real gap is roughly delay + 0.6 s. A 0.3-second delay reads as nearly a second of air.

The hold is the dominant term. Cutting display duration shortens the clip far more effectively than cutting delays, and the editor's floor is 1 second (the MCP tool allows 0.5). If a sequence feels sluggish, the hold is almost always why.

Building a three-banner sequence

The structure that works most reliably:

Banner one — establish the world. Mundane on purpose. A friend, a normal message. Its job is a baseline for the escalation to escalate from. Give it a slightly longer delay — around 0.6 s — so the viewer registers a still frame before motion starts.

Banner two — introduce tension. A different sender, a message that implies something is in motion. This is where the viewer realises they are watching a sequence rather than a single alert. Shorten the delay a little.

Banner three — the turn. The message that recontextualises the first two or raises the stakes. Extend its display duration so the final line is what is on screen when your main content cuts in.

Three senders, three registers, no narration. The demo above follows exactly that shape: a friend's message about a group chat, a work notification, then a personal one.

Runs in the browser. No install.

Open the iMessage notification maker

Timing patterns that read as natural

Most multi-banner clips fail in the same way: identical values on every banner, so the sequence reads as a slideshow.

The accelerating burst. Descending delays — 0.6, 0.5, 0.4 — with a short hold on the first two. Each message arrives fractionally sooner than the last. The compression is small enough that nobody consciously notices and large enough that the sequence feels like it is speeding up. This is the default choice for "phone blowing up" content; remember to pull the holds down to 1–1.5 s or the acceleration is swamped by dead air.

The deliberate drip. Invert it: 0.5, 0.8, 1.2, with longer holds. Each banner feels more reluctant than the last. Suits ominous or sad framing where the final message is bad news.

The held final beat. Whatever the arrival pattern, give the last banner a longer display duration than the others. The clip then ends on a readable frame rather than an empty screen — and that final frame is often what a viewer is looking at while deciding whether to keep watching.

Respect reading time. A hold under about two seconds is too short for a preview of more than a handful of words. The classic version of this mistake is a third banner nobody read because it dismissed while they were still parsing the second. If you want short holds, cut the copy to match.

Writing preview copy that survives truncation

The preview is a truncated medium — at most two wrapped lines, then an ellipsis. Write to the wrap rather than to a character count: paste the line in, press Play, and look at where it cuts.

Front-load the payload. The first three or four words carry the meaning. "did you see the group chat" works because the subject arrives immediately.

Lowercase reads as real. People do not text in carefully capitalised sentences. Dropped capitals and missing terminal punctuation read as authentic; formal sentence case reads as advertising.

Let the sender label do the work. "Mum" plus "call me when you land" is a complete scene. Two fields did the job of a paragraph.

Avoid resolving the message. A preview that answers its own question kills the reason to keep watching. "the build is green, shipping now" implies an entire afternoon without describing it.

Vary the register across senders. Three friends with similar names produce a flat cast. A person, an organisation and a family member imply a whole life.

Backgrounds: where the clip can be used

The background field decides what the sequence can be dropped into.

  • Default (Theme Color). Black in dark theme, light grey in light. Fine when the banners are the whole video.
  • Lock Screen. A gradient wallpaper preset or an uploaded photo, with an editable date and clock above the banners. The highest-fidelity "this is what arrived on my phone" look, and the only way to show a clock time.
  • Chroma Key. A flat colour behind the banners, green by default and chosen with a picker. Export MP4 and key it out. Pick a colour that does not appear in your banner content or avatars. The green-screen iPhone notification workflow covers the keying step editor by editor.
  • Custom Image. Upload any still and the banners render over it.
  • Transparent (Alpha Channel). Nothing drawn but the banners — no screen fill, no status bar, no home indicator. Only MOV (ProRes 4444) and WebM (VP9) carry it; MP4 and GIF fall back to the theme colour. Professional export is a paid-plan feature. See transparent notification video export.

When compositing, keep the banners in the upper third, where iOS puts them and where viewers expect them, leaving the lower two-thirds for captions.

The same sequence rendered against a flat chroma background, ready to key out and composite over footage.

Frame, text size and export

Turn the iPhone bezel off and you get the aspect-ratio picker — 9:16, iPhone, 3:2 and 1:1 — plus status-bar and home-indicator toggles. With the bezel on, a 1:1 crop frames the top of the phone, which suits feed posts.

One control is worth knowing about for this format specifically: text size zooms the whole phone UI, banners included, up to 1.5×. A single banner on a 9:16 frame is small; at 1.3× it fills enough of the frame to be read on a phone held at arm's length. It applies to chat and notification templates.

Export formats are MP4, GIF, MOV (ProRes 4444) and WebM (VP9), at 720p or Full HD and 15, 24, 30 or 60 fps. 720p30 is the default and right for a short banner clip. Full HD takes up to four times as long to encode, and the render happens in your own tab.

A note on sound: the tone fires once per banner arrival, so a four-banner sequence has four hits — which is part of what makes a burst feel like a burst. If you are putting a trending audio over the clip in the platform editor, switch Sound Effects off first so the two do not collide.

For ads and client work

Real-app templates recreate designs that belong to their owners, and MockClip's licence grants no rights in them on any plan — the terms point you at a brand-free template for advertising and client deliverables. For this format that is the Lock Screen Notifications template: the same banner engine, the same per-banner timing, with its own app name, monogram and accent colour instead of Messages'. Watermark-free export of the brand-free templates is a Studio feature. See brand-free app mockups for ads and the Lock Screen Notifications template.

Building the sequence from a prompt

If you have MockClip connected to an AI client, create_imessage_notification takes the whole sequence in one call: one to ten banners with per-banner sender, message, delay, duration, dismiss style and an avatar URL, plus the theme, background, lock-screen fields and sound settings. Ask for "four banners on a lock screen, 0.3-second delays, one-second holds, then export as a transparent WebM" and the reply is a link that opens the finished clip. How to connect MockClip to Claude and ChatGPT covers the setup.

Where the format fits

  • Cold-open hooks. A few seconds of alerts before the main content. The most common use, and the reason the format exists.
  • Storytime setups. The sequence establishes the situation, then you cut to camera. The banners replace the "so basically what happened was" preamble.
  • Product and launch content. Alerts from teammates as a feature ships — build-in-public content without screen-recording a real inbox. Keep the messages honest about what shipped.
  • Reaction videos. Composite over a reaction shot so the alerts and the face share the frame.
  • Comedy and prank formats. Escalating messages as a punchline structure. The iMessage prank text guide covers the conversation-side version.
  • Missed-connection framing. Pair the sequence with a phone call notification so messages and a call arrive in the same clip.

Common mistakes

Planning for an overlap that does not exist. Covered at the top, and the root cause of most disappointing previews.

Uniform timing. Identical delays and holds across every banner produce a sequence with no shape.

Default holds on a burst. Four seconds each is right for one banner and far too long for four. Burst sequences live at 1–1.5 seconds.

Too many banners. Beyond about five, individual previews stop being read and the sequence becomes texture. If the story needs more than five messages, the full conversation template is the better format — see how to make a fake iMessage conversation video.

Previews written as sentences. Long, grammatical, fully punctuated lines look like notifications from a brand, not from a person.

Forgetting the final frame. If the last banner dismisses with time left, you end on empty background. Extend its hold.

Keying against a colour you used. A green accent in an avatar will punch a hole in your composite. Change the chroma colour with the picker.

Quick start

  1. Open the iMessage notification template
  2. Add three banners and give each a distinct sender
  3. Write each preview at three to eight words, lowercase, front-loaded
  4. Set descending delays — roughly 0.6, 0.5, 0.4
  5. Set holds of 1–1.5 s for a burst, 2.5–4 s for a drip
  6. Give the final banner a longer hold so the clip ends on a readable frame
  7. Pick the background: Lock Screen for realism, Chroma Key or Transparent for compositing
  8. Set the frame, nudge text size up if a banner looks small, then export

Once the copy is written the build takes a couple of minutes. Export and watermark options vary by plan — see pricing.

Related templates and guides

Frequently Asked Questions

Can two iMessage notifications be on screen at the same time?

No. The template plays banners strictly in sequence: each banner finishes leaving before the next one's delay even starts, so exactly one banner is on screen at any moment. For the feeling of a phone being flooded, use short delays and short display durations so the banners follow each other quickly. A true overlapping stack is not something the renderer draws today.

How many notifications can I chain in one clip?

In the editor there is no fixed cap — Add Notification keeps appending banners, and you reorder them by dragging. The MCP tool that builds a clip from a prompt accepts between one and ten in a single call. On screen, three to five is where the format reads best: enough to establish a rhythm, few enough that each preview line can still be read.

What is the difference between Slide Up and Fade Out dismissal?

In the current renderer, nothing visible. Both options store a different dismissStyle on the banner, but the canvas renderer that draws the preview and the export animates opacity only, so either setting produces the same roughly 0.3-second fade out. Treat the control as a stored preference rather than a creative lever, and shape the pacing with delay and display duration instead.

How long will a three-banner clip actually be?

Longer than most people expect, because the banners never overlap. The clip is a half-second lead-in, then for each banner its delay plus about 0.3 seconds in, its display duration and about 0.3 seconds out, then a one-second tail. Three banners at a 0.5-second delay and a 2.5-second hold come to about ten seconds. For a fast burst, drop the hold to the one-second minimum.

Can I export the sequence on a green screen or with transparency?

Both. Chroma Key draws the banners over a flat colour — green by default, and the colour is a picker — which you key out in your editor after exporting MP4. Transparent draws nothing but the banners and needs MOV or WebM to survive, because MP4 and GIF carry no alpha channel; professional export is a paid-plan feature, so check the pricing page.

Can I change the time shown on the banner?

No. Each banner reads MESSAGES on the left and now on the right, and neither is editable — that is what a notification that just arrived shows. If a specific clock time matters, use the Lock Screen background, which draws an editable date and clock above the banners.

Do I need an iPhone to make this?

No. The banners are drawn by a canvas renderer in the browser and exported as a video file, so there is no screen recording, no status-bar clutter and no capture artefacts. The clip is clean at full resolution on any machine.

Is it legal to make fake iMessage notification videos?

Making clearly fictional notification clips for entertainment or illustration is legal in most jurisdictions. Do not use the format to impersonate a real, identifiable person, to defraud anyone, or to harass. Label the clip as dramatised when the context could genuinely mislead a viewer, and use a brand-free template for ads and client work.

Related Articles