Promptpan

All · Motion graphics · Product intro

063Fill the Fields — a 15-second product demo short that shows your service in use

Enter your service name and three input fields: the fields fill in, values change, the result assembles and a 15-second vertical product demo MP4 comes out.

What you get

  • A vertical MP4 (15 seconds, 60fps, no sound)
  • An HTML file with a settings panel to change the text, fields and colors
  • A render script that makes a new MP4 with one command
Example — made from the field examples with Claude Opus 5.5 (no background music)

Made with Claude
  • Claude Opus 5.5 Made with this AI

Fill in the fields

  1. 1Fill in the fields
  2. 2Copy the prompt
  3. 3Paste it into an AI that can run code (Claude Opus 5.5 · GPT-6 Astra · Gemini Argon)
  4. 4It builds the HTML, renders it itself and leaves an MP4
  5. 5To change it, edit the settings panel at the top of the HTML and run one render command No new request
Ideas
Ideas
Ideas
Ideas
Ideas
Ideas
Output format

Choose a mode, then set the size.

Full prompt 4,112 characters
Make a 15-second vertical 2D product demo as one self-contained HTML file and render it to MP4. The idea: one living app screen. A person fills three fields, every value they enter instantly changes the result, and the finished result comes out. It must look like a dense, premium editing tool in motion, not a slideshow. Stay flat 2D on a canvas: no 3D, no WebGL, no light simulation, so it renders fast on an ordinary PC. Do the whole job now without asking questions.

[Inputs]
Name: "【Name】"
Problem line: "【Problem line】"
Three field labels: "【Three field labels】"
Three field values: "【Three field values】"
Result: "【Result】"
Closing line: "【Closing line】"
Palette: "【Palette】" — the meaning of color is fixed: red = problem, orange = in progress, green = done:
  Dark = background #0B1016, panels #151C24, text #F2F4F7
  Light = background #F2F1EC, panels #FFFFFF, text #17171A
Aspect ratio: Output size 1080x1920 pixels, 9:16 portrait story. Keep all text inside the central 80% of the height. (default 9:16).

[One world]
The whole film is one screen that never changes place. Top: a two-line caption with a small status pill such as "Fields 0/3 · 8% done". Middle: the input panel with the fields, sliders, swatches and a live prompt preview. Under it: a slowly scrolling timeline of small tags that always keeps moving. Bottom: the result preview with a round progress gauge and live numbers.

[Story]
0 to 3 s: empty dashed fields, a big question mark in the result, red tags, the progress low, the problem line in the caption.
3 to 7 s: the camera snaps in on the panel. A cursor fills the three fields one by one, letter by letter; each field gets a green check and a small "+16" chip, and the gauge climbs.
7 to 10 s: the cursor flips options and swatches; the result recolors instantly, in sync. The camera snaps in on the result; measuring marks and green tags appear around it.
10 to 13 s: the camera snaps to the copy button, it is pressed, and lines of text get checks one by one. Back to the result: the outline fills with color piece by piece until 100%.
13 to 15 s: focus pulls back; the name, the closing line and three small summary chips appear. Hold, with the timeline still moving.

[Motion rules]
The world always flows; no pause over 0.5 s. Small events follow each other about every 0.3 s: a tag, a number, a check. The camera has only two states, full view and close-up; it moves in about 0.2 s with blur and then stays still. No slow push-ins, and never zoom back with a visible cut. Reading text never moves: only the current word changes color. A flash or burst appears once, only at a meaningful moment. Scene changes are depth changes in the same space: the old layer blurs away while the new focus sharpens. No HUD decoration without meaning. Text in Archivo Black and Inter from Google Fonts. Keep a 6% safe margin. No sound.

[Build]
One HTML file, one canvas. The script starts with a `const CONFIG` holding every input plus fps 60 and a seed. All drawing comes from a pure `seek(t)`, with no timers and no CSS animation. A settings panel above the preview (hidden with ?render=1) with English labels for the inputs, play/pause, a scrubber and a "Copy settings" button that copies CONFIG as code.
Write render.mjs: open ?render=1 in headless Chromium (Playwright), wait for fonts, step every frame through seek(frame / 60), screenshot the canvas at 1080 px on the short side and pipe into ffmpeg (libx264, yuv420p, crf 18) to make motion.mp4. Close the browser at the end. Accept an optional JSON file that overrides CONFIG.

[Check before finishing]
Look at stills every 0.5 s. Check that text is readable at phone size, nothing overlaps or clips, and motion never stops. Fix and re-render if anything fails. Finish with the file paths and the single command to re-render after editing settings.

[Final output format]
Output size 1080x1920 pixels, 9:16 portrait story. Keep all text inside the central 80% of the height.
This selected output format takes priority over any fixed canvas size or aspect ratio elsewhere in this template. Adapt the composition, text zones and margins to the selected canvas without stretching or cropping essential content. Device safe areas apply only when a device is selected. Never print these format instructions on the image.

Browse more cards

How to use it · FAQ

Show your service instead of explaining it

Empty fields fill in, the result changes as values change, and one copy finishes the output, all on a single unbroken screen. Use it to explain an app, web service or automation tool in a 15-second short.

Paste it into an AI that runs code

Paste it into an AI that writes and runs code, not an image AI. The AI builds the HTML, renders it and leaves an MP4. There is no sound, so add your voice or music afterwards. Check each service's pricing and terms on its own site.

How to fill it in

Write three labels and three values separated by commas. Shorter values look bigger on screen. A problem line phrased as a question brings the first screen to life.

Edit without asking again

Change the text and colors in the settings panel at the top of the HTML, press "Copy settings" and run the one render command for a new video.

What your PC needs

Your PC may slow down briefly while the video is being made. That is not a fault, and it returns to normal when finished. We recommend 16GB of memory or more. Keep one browser window open and pause other work while it renders.