Rive for broadcast

Rive is the right tool for broadcast graphics. It just isn't the whole pipeline.

Rive gives you vector animation, state machines and data binding — the three things that make a graphic feel like television rather than a looping GIF. What it does not give you is a way to put that file on air and change it while a show is running.

This page covers where the line sits, and what goes on each side of it.

Start free Read the docs

What Rive does well

Vector, at any resolution

A .riv file is geometry, not pixels. The same animation is sharp at 720p and at 4K, and it weighs kilobytes rather than megabytes — which matters when an overlay has to load on a machine in a venue.

State machines, not just timelines

Graphics respond to events. A lower third that can be brought in, held, and taken out — and interrupted halfway through — is a state machine, and Rive is built around them.

Data binding built in

View models expose properties an outside system can set. This is the feature that turns an animation into an instrument: bind a score once, change it forever after without touching Rive.

Where a .riv file stops being enough

An exported Rive file is an animation. An overlay is an animation plus a URL, plus somebody able to change it while it is on screen. Here is the split.

Capability	Rive	A .riv file alone
Vector animation at any resolution
State machines and interactive triggers
Data binding via view models
A URL an encoder can load as a browser source
Somebody changing a score mid-show, from a phone
Separate preview and live states
The same graphic on three streams at once

The bottom four rows are what a broadcast platform is for. Quadraviz hosts the .riv file, connects its bindable properties to your data, gives you a browser-source URL, and puts a control panel in front of it — so an operator changes a score and the graphic changes on air, without anyone reopening Rive.

Getting a Rive animation on air

Build the artboard in Rive

Structure your layers so each element you want to change later is addressable on its own. A scoreboard built as one flat group animates as one flat group.

Preparing a file for upload

Make it broadcast-safe

Animations need to be interruptible and loopable. A show does not wait for your entrance transition, and a lower third that breaks when triggered twice will embarrass you live.

Building view models

Bind the data once

Expose team names, scores and colours as bindable properties. Do this once and every subsequent change is a value on a dashboard rather than a re-export.

Connecting data to an animation

Put it on air

Upload the .riv file, connect it to your data, and add the resulting URL to OBS or vMix as a browser source. Your encoder composites; the page does the work.

Running a show