Using a Preset
Add thepreset field to your config:
steps, output, format, or $schema. They only set visual and audio presentation.
Built-in Presets
| Preset | Theme | Sound Effects | Cursor | HUD |
|---|---|---|---|---|
polished | catppuccin | click + key (variant 1) | visible | visible |
minimal | tokyo-night | none | visible | hidden |
demo | dracula | click + key (variant 1) | visible | visible |
silent | (none) | none | hidden | hidden |
polished
The go-to preset for professional-looking recordings. Applies a warm Catppuccin color scheme with subtle click and keypress sound effects, a visible cursor, and HUD overlay.minimal
Clean recordings with a Tokyo Night theme and cursor only. No sound, no HUD — just the terminal and a cursor.demo
Similar topolished but with the Dracula theme. Good for quick demos where you want a familiar dark look with full audio-visual polish.
silent
The bare-bones preset: no cursor, no HUD, no sound. Useful when you want a clean terminal recording with no overlays, or as a baseline when you plan to customize everything yourself.Overriding Preset Defaults
Preset values are defaults — your config overrides them. For example, thepolished preset enables sound, but you can turn it off:
polished but disables sound effects.
You can also swap the theme while keeping everything else:
Presets in tuireel init
When you run tuireel init interactively (in a TTY), you’re prompted to select a preset:
.tuireel.jsonc config. In non-interactive mode (piped input), the preset prompt is skipped.