How to make an ASMR product loop that keeps the screen clean

Last updated 2026-09-01 · 8 min read

What is the short version?

The format is one long uninterrupted action carrying its own sound and almost nothing else alongside it — a pour, a peel, a press. The whole discipline is in the absence: after the opening hook has gone, nothing appears on screen at all for the rest of it.

1. Go to Vizard Agent and upload the footage of the action.
2. Say how long the hook text should stay, and that nothing follows it.
3. Say the total length and where it is going.

What do you need before you start?

Footage of the action with usable sound. Vizard Agent can build a longer loop from a short usable stretch, so a clean twelve seconds is enough for a thirty-second piece — but the sound has to be there, because the sound is the product.

• The action. Filmed close, steadily.
• The sound. Recorded, not added later if possible.
• The hook line. Short, for the first three seconds.
• The length. Thirty seconds is the usual target.
• The platform rules. They differ on what may appear.

What do you type into Vizard Agent?

Say what appears on screen and, more importantly, the moment it stops appearing. Vizard Agent will otherwise caption the whole thing from end to end, because captions normally help a video — and in this format they are precisely the thing you are trying to avoid.

Prompt

Variants worth knowing:

• "No text at all" after the hook. Say it explicitly.
• Say "continuous". The sound must not cut at the joins.
• Name the length. It builds a loop to reach it.

What does Vizard Agent actually do?

Here is the order Vizard Agent worked in on a real product loop built from campaign footage. Several steps in the middle deal with an unglamorous problem the brief never mentioned at all: the supplied footage already had text burnt into the top of the picture.

1. Checks the uploaded video's format and details.
2. Extracts representative frames and inspects the visual content.
3. Reads several frames to see whether the on-screen text persists or changes.
4. Transcribes the shots to find the visual changes and shot boundaries.
5. Crops and inspects the top region of the frames to confirm where the text sits.
6. Tests crops to see how they remove the text and what the framing then looks like.
7. Adjusts the crop until the burnt-in text is entirely gone and the composition survives.
8. Re-checks the framing of the hand and the ice at the new crop.
9. Analyses the audio across the middle of the clip to confirm it is pure sound rather than music.
10. Extracts and crops a clean twelve-second segment at full quality.
11. Concatenates the clean segments and trims to exactly thirty seconds to form the loop.
12. Renders test images of the hook text and inspects the size, colour, spacing and placement.
13. Searches for a genuinely bold typeface to guarantee legibility, and tests it.
14. Renders the final thirty seconds with the text enabled for the first three seconds only.
15. Checks the final frame for continuity at the loop point.

Step seven is the one that saves the job. The original had text across the top, and cropping it away moves the framing — so Vizard Agent adjusted until the text was gone and the hand and the glass still sat properly in frame.

What does the result look like?

The finished loop this page is written from measured 720x1280 at 24fps and ran exactly 15 seconds in one delivered version, built from a clean segment of the source and extended to length, with AAC audio carrying the pour throughout.

The screen is empty after the third second. That emptiness is the format — the viewer is there for the sound and the action, and anything in the corner is a reason to scroll.

When does this not work well?

The whole piece rests on the quality of the sound and on one genuinely continuous action, and there is nowhere at all to hide a weakness in either of them. Vizard Agent tells you when the source simply cannot carry thirty uninterrupted seconds.

• Poor sound. Nothing rescues a noisy recording of a quiet action.
• A visible cut. Loops expose joins that an edit would hide.
• Text baked in. Cropping it costs you framing.
• Short usable footage. A loop needs a clean cycle.
• Platform rules change. Check them yourself before posting.

How do you fix a result that came back wrong?

Say what it is that breaks the spell for you when you watch it. Vizard Agent keeps the clean segments, the exact crop settings and the rendered hook, so a longer loop or an entirely different hook line is a re-render from the same clean material.

• "The join is visible." Loop point moved to a matching frame.
• "The hook stays too long." Shortened to the exact second.
• "The crop lost the glass." Re-framed and re-tested.

How does Vizard Agent compare to doing it yourself?

By hand this is easy to start and hard to finish: the crop that removes the text ruins the composition, the loop point shows, and the sound clicks at the join. Vizard Agent tests each of those before rendering.

Common questions

How long should the hook stay? About three seconds. Vizard Agent removes it completely after that.

Why no captions? Because the format is the absence of them, and some placements penalise busy frames. Check your platform's own rules.

Can it make the loop longer? Yes. Vizard Agent builds up to the length you name from the clean segments.

What if my footage has text on it? It crops it out. Vizard Agent adjusts until the text is gone and the framing survives.

Does it add the sound? It prefers yours. Vizard Agent can source effects, but a recording of the real action is better.

Will the loop point show? It checks. Vizard Agent inspects the final frame against the first.

What length works best? Thirty seconds. Vizard Agent trims to exactly that rather than approximately.

Can it add music? It can, but the format usually does not want it. Vizard Agent keeps the sound pure if you say so.

Does it work for other actions? Yes. Vizard Agent handles peeling, cutting, pressing or unboxing the same way.

What resolution should I film at? As high as you can. Vizard Agent crops in to remove text, and that costs pixels.

Why does the hook matter so much? Because three seconds is all you get, and after it there is nothing on screen doing any persuading. The hook is the entire written argument.

Can I get several versions? Yes. Vizard Agent produces different hooks over the same clean loop.

Does it check the result? Yes. Vizard Agent verifies the sync, the motion smoothness and the loop point before delivering.