Turn research into an explainer video

Who it's for

Researchers who want their work understood beyond the people who read the paper. Science communicators, lab and institute comms teams, teachers, and anyone who has had to explain a finding to somebody who will not read forty pages.

An explainer lives or dies on the explanation, not the footage. So Rubiic spends its effort where understanding happens: the order the ideas arrive in, the one diagram that makes a mechanism click, and on-screen text that backs up what the narration says.

What to bring

• The source, as a link. A public web page, or a PDF at a public address. Rubiic reads it as text. If the source is not online, paste the passages that matter into the chat.
• The audience. “First-year biology students” and “a funder with five minutes” are different videos. Say who it is for and what they already know.
• The length and the shape. Thirty seconds for a social post or a few minutes for a lesson; landscape, square or vertical.
• What must not be lost. The caveat, the sample size, the result that is easy to overstate. Say it up front and it goes into the script.

How a build goes

It starts as a conversation. Rubiic asks what it needs to know — audience, angle, length — and tells you what it understood before it starts building.

Then it reads. It opens the pages and PDFs you link, and it can search the web for context you did not give it. Where a picture would help, it can generate an image grounded in what it found.

It writes the script, and in Review mode — the default — you approve the narration script before a voice records it. The music and the export wait for your approval the same way.

Each scene is then written as code for this script: a Remotion composition, drawn by a browser. That matters for research in particular. A chart is drawn from its numbers, labels are real text rather than painted pixels, and a diagram is corrected by asking — “the arrow should leave the receptor, not enter it” — instead of being regenerated from scratch.

Rubiic can inspect its own frames for problems such as overlapping or cut-off text. It does not check your science. Read its diagrams the way you would read a figure in a colleague's draft.

Every revision is kept as a new version, and you can compare it with the one before. When it looks right, you render the MP4 and download it, and caption files for the narration are a free export.

Before you start

See what a finished build looks like on the examples page — each one shows the brief that produced it — or read how credits work on the pricing page.