wikis / HyperFrames / wiki / concepts / rendering-pipeline.md view as markdown

Rendering Pipeline

Definition

The rendering pipeline converts HTML compositions into video outputs such as MP4, MOV, or WebM using browser capture and encoding.

How It Works

A render command loads the composition in headless Chrome, advances through frames, captures pixels, handles audio/media, and encodes the final artifact. The engine layer handles seekable page capture; the producer layer handles the complete render pipeline.

Key Parameters

• Output format/path.
• Canvas size and FPS.
• Chrome/engine availability.
• FFmpeg/encoding environment.
• Local versus Docker or deployment runtime.

When To Use

Use local rendering for development and final exports. Use deployment/Lambda patterns when rendering needs automation from a backend or service.

Risks & Pitfalls

Validate before rendering. Rendering can expose missing assets, console errors, poor contrast, layout overflow, non-seekable animations, and environment issues.

Related Concepts

• hyperframes packages
• deterministic rendering
• deployment and performance

Sources

• raw/docs/guides__rendering.md
• raw/docs/packages__producer.md
• raw/docs/packages__engine.md
• raw/docs/packages__cli.md