Dot Matrix

Big numbers lit on a dot board that re-lights column by column, with hard cream-to-black cuts.

16:9Medium pace7.5sprecisetechnicalconfident

Stat-reel style for status pages, milestones and metrics. A 41×7 board of round dots spells each number in a 5×7 bitmap font; between stats a hot-pink scan line sweeps across and every dot re-lights in column order while the background cuts between cream and black. Mono HUD corners and a frame timecode keep it technical.

Use this style

With Frame Jam installed, press Use this style in the local gallery, or just ask your agent:

Make a video with the Frame Jam style "dot-matrix" and open it for review.

Palette

background#f1ede4
backgroundDark#0b0b0b
dot#161616
accent#ff2e88
dotOffrgba(22,22,22,0.08)
dotOffDarkrgba(255,255,255,0.07)

Type

Display
Dot grid (5×7 bitmap built from divs)34px dots on a 44px pitch, 7 characters wide
Body
JetBrains Mono 500, 700Uppercase captions 30px and HUD labels 18px, tracking 0.12–0.14em, in accent pink

Motion

Pop
back.out(3)
Relight
power2.out
Shift
power3.inOut
Scan
none
Average shot
2.4s

One number per beat of ~2.4s. The relight itself takes ~0.6s; let each number sit for at least 1.5s before the next sweep.

Transitions and text

  • hard background cut (cream ↔ black) on the scan line
  • column-ordered relight, 14.5ms per column
  • board slides half a character to keep odd-length numbers centred
  • lit dots pop in with a seeded pseudo-random stagger (never Math.random)
  • whole board breathes +12% from the centre once per stat
  • caption swaps and rises 16px after each relight
  • frame timecode in the HUD

Style guide your agent follows

  1. Build numbers from a fixed grid of round dots and a 5×7 bitmap font; never swap in a text font for the hero number.
  2. Unlit dots stay visible at 8% and scale 0.55, so the board reads as hardware. Lit dots are ink on cream or hot pink #ff2e88 on black.
  3. Change numbers by re-colouring dots column by column behind a pink scan line, and cut the background on the same frame.
  4. Use seeded staggers (index math) instead of random so parallel render workers agree.
  5. Every number needs an uppercase mono caption saying exactly what it counts ("Incidents caught before users noticed").
  6. Frame with thin pink corner ticks, a section label top-left, product name top-right and a timecode bottom-left.