Supported Output Patterns

Page role: this page helps map user intent to the right ReelForge path (Recipes first, Timeline when needed).

Use this page as a capability map when a user request is broad, specific, or unusual.

This is not a rigid rules engine. It is a reasoning aid to match user intent to the nearest supported ReelForge pattern.

How to use this page

Identify the nearest pattern by output intent.
Start on the recommended path (Recipes or Timeline).
Validate before render.
Switch paths if the request exceeds that path's control surface.

Capability map

Pattern	Best starting path	Why this path fits	Minimum inputs (high level)	Switch paths when
Captioned talking-head clips	Recipes (`captioned_clip`)	Fast social-caption workflow with strong defaults	1 video URL, transcript words, style preset	You need custom multi-layer layout/timing beyond recipe controls
Photo slideshows	Recipes (`photo_slideshow`)	Built-in pacing from audio + image sequencing	Audio URL, 2+ image URLs, style preset	You need custom per-image overlap/stacking or advanced layer choreography
Ranked listicles	Recipes (`listicle_ranked`)	Guided countdown structure with hook/item pacing	Music URL, items array, style preset	You need non-standard list transitions or custom mixed layer behavior
Voiceover explainers	Recipes (`voiceover_explainer`)	Strong default path for narration + caption progression	Voiceover URL, background assets, transcript words, style preset	You need precise multi-track timeline authoring beyond recipe knobs
Story-led b-roll	Recipes (`storytime_broll`)	Guided narration + b-roll pattern (status: Coming soon)	Voiceover URL, background video URL, transcript words, style preset	Recipe is not yet live, or you need custom timeline behavior now
Stitched clip reels	Timeline API examples	Direct control over sequencing (`auto_stitch` or explicit timing)	Manifest with assets + timeline layers	A recipe already matches your intent with less payload complexity
Split-screen videos	Timeline API examples	Explicit layout control per layer	Manifest with 2+ visual layers, layout coordinates, timing	A recipe can express the output without custom layout math
Text-overlay videos	Timeline API examples	Fine-grained control over overlay timing/style/layout	Manifest with base media + text overlays	You only need standard recipe-level text behavior

Fallback when no pattern fits exactly

Choose the nearest supported pattern and start there.
Validate first with POST https://api.reelforger.com/v1/videos/validate.
Escalate to Timeline API if recipe/path controls are not enough.

Pattern-level boundaries

Use Recipes when

You want reliable speed and minimal request shape complexity.
A known pattern already matches the request closely.
You can express output intent as recipe_id + variables.

Use Timeline API when

The request needs explicit control over layer timing, positioning, overlap, or media behavior.
You need composition behavior that is not represented by recipe controls.
You need custom manifests as the primary authoring model.

Execution loop owner

For the canonical step-by-step decision tree and execution flow, use Start Here for Agents.