Skip to content

Monospace Terminal Captions C09

0.0s

Previews are illustrative demonstrations of the technique — not your footage. Your real edit is produced later by Claude Code.

C09 · Captions · intermediate · 5–180s

Dialogue prints word by word in a monospace terminal block with a prompt and blinking cursor, older lines scrolling up and dimming.

Captions behave like a command line: each phrase prints after a prompt symbol, word by word in sync with the voice, followed by a blinking cursor. Completed lines scroll up and dim like terminal history. The deliberate, mechanical reveal suits developer, AI and technical content and makes the captions feel native to the subject rather than decoration.

Try the parameters

Distance from the platform UI edge, as % of frame height.

Best used for

  • — Developer and coding content
  • — AI and tech explainers
  • — Cybersecurity topics
  • — Product changelogs

Assets

  • ● Source video required
  • ○ Transcript with timing optional

Pairs well with

If assets are missing

Without word timing, use phrase-level SRT cues and reveal each line's words evenly across its cue. Without a transcript, transcribe locally — never type out paraphrased 'code-like' text.

Accessibility

Lowercase and monospace reduce reading speed slightly; keep lines short and hold completed lines ≥ 1s. The cursor blink is slow (≈ 1.6Hz) and small, well under photosensitivity limits.

Individual prompt

updates with the parameters above
# CES style instruction — C09 Monospace Terminal Captions

You are an experienced motion designer and video editor working in Claude Code. Apply the **C09 Monospace Terminal Captions** technique to the supplied footage as specified below.

**B. Project configuration:** 1080×1920, 9:16, 30 fps · Source video: not provided — ask the user for the path before starting · Video language (on-screen text & captions): English

**Captions** — Captions behave like a command line: each phrase prints after a prompt symbol, word by word in sync with the voice, followed by a blinking cursor. Completed lines scroll up and dim like terminal history. The deliberate, mechanical reveal suits developer, AI and technical content and makes the captions feel native to the subject rather than decoration.

### C09 Monospace Terminal Captions

- **When:** Applies to the whole video
- **Layer / track:** Captions layer (topmost text)
- **What it does:** Dialogue prints word by word in a monospace terminal block with a prompt and blinking cursor, older lines scrolling up and dimming.
- **Parameters:** Prompt symbol: ">"; Cursor: Block █; Reveal unit: Word by word; Previous lines kept: 1 lines; Text colour: #D7FF5F; Terminal title bar: on; Faint scan lines: off; Safe-zone offset: 16%
- **Steps:**
  1. Add a terminal caption layer across every spoken section of the video on the top track (1080×1920 @ 30fps).
  2. Timing source: use the supplied transcript's word-level timestamps for the English dialogue. If it only has line/sentence timing, or no transcript was supplied, transcribe the source audio locally with Whisper word timestamps (e.g. `whisper source.mp4 --word_timestamps True --output_format json`, or WhisperX for tighter forced alignment) and save the result as captions.json. Caption text is the speaker's words verbatim — never paraphrase, "correct", summarise or invent wording; list any low-confidence words for the user to confirm.
  3. Lines: one phrase per line, max 28 characters (monospace makes this exact), split at pauses ≥ 250ms; prefix every line with "> " in 50% opacity. Text keeps the speaker's words verbatim in lowercase unless the user asks otherwise (proper nouns and acronyms keep their case).
  4. Reveal word by word — each word appears whole on its start frame; a █ cursor in #D7FF5F sits after the last revealed character and blinks at 1.6Hz (on 10 frames / off 9 frames at 30fps) whenever no word is being revealed.
  5. History: when a new line starts, previous lines scroll up one line-height over 4 frames and drop to 45% opacity; keep 1 previous line visible, older lines fade out.
  6. Block: monospace (JetBrains Mono / IBM Plex Mono Medium), cap height ≈ 4.2% of frame width, text #D7FF5F, on #0A0C0A at 82% with radius 1.5% of width and a 0.15% #D7FF5F border at 25% opacity. Add a slim title bar (three 1.6%-wide dots and a 'captions' label) above the text.
  7. Placement: anchor the terminal block's bottom edge 16% of frame height (307px at 1080×1920) above the bottom of the frame, horizontally centered with ≥ 8% side margins, so it stays clear of the TikTok / Reels / Shorts interface (description text and action buttons occupy roughly the bottom 20% and the right-hand 12% of the frame). Never cover the speaker's eyes or mouth; if the face sits unusually low in a shot, lift the block above it for that shot only.
  8. Implement as a Remotion <TerminalCaptions /> component reading captions.json; derive the visible word index from useCurrentFrame() and render history lines from the same data.
- **Assets:** Source video (⚠ MISSING) · optional: Transcript with timing
- **Fallback:** Without word timing, use phrase-level SRT cues and reveal each line's words evenly across its cue. Without a transcript, transcribe locally — never type out paraphrased 'code-like' text.

**G. Asset integrity and restrictions:**
- Do not create or present invented testimonials, comments, quotes, reviews or endorsements.
- Do not fabricate numbers, metrics, charts or results. Data visualisations use only the supplied data.
- Do not create fake screenshots or UI and present them as real. Illustrative graphics must be clearly illustrative.
- Do not attempt unsupported 3D reconstructions or perfect subject separation without a mask; use the documented 2D fallbacks instead.

**I. Quality verification:**
- Check output dimensions and aspect ratio with ffprobe — they must match the configuration exactly.
- Check the output frame rate and that the duration is within ±0.5 s of the target.
- Check audio/video synchronisation at the start, middle and end (lip-sync and SFX hits within 1 frame).
- Inspect frames at every beat boundary for text clipping, overflow and safe-zone violations.
- Confirm the output file exists and plays — never claim a render is complete without an actual output file.
- Report any missing asset or unimplemented effect explicitly.

More captions styles

Choose one primary caption style per video. It usually runs across all spoken sections as a global layer.

Your recipe starts here.

Add a style to begin building.