Turn a document into a video

Who it's for

Teams with something written down that people need to understand: a new policy, a quarterly report, an onboarding guide, a change to how a process works. The document exists and it is right. The trouble is that it runs to twelve pages and the people it is for will skim it.

A short video does not replace the document. It walks people through the parts that matter, in an order that makes them make sense, and sends them back to the source for the detail.

What to bring

• The document. A link to it — a public web page, or a PDF at a public address — or its text pasted into the chat. Rubiic reads documents by link; the files you can attach are images and screen recordings.
• Who will watch it, and what they should do afterwards. “New starters should know who to ask for access” is a better brief than “summarise the handbook”.
• Your website. Rubiic can read your colours, fonts and logo from your pages and propose them for the video.
• Anything that must stay out. Say so before it writes, not after.

How a build goes

Rubiic reads the document and asks what it needs: the audience, the length, the one thing a viewer must remember. Then it proposes an outline and a script.

This is the step to slow down on. In Review mode, the default, nothing is recorded until you approve the narration script, so this is where you correct a figure, soften a claim or cut a section. Changing the script costs a sentence; changing a finished video costs another render.

Your brand comes next. From the pages it read, Rubiic proposes a palette, fonts and a logo for you to review, and once you confirm them every scene takes that brand as an input. A font it does not have is swapped for one it does, so look at the result the way you would look at any first draft. Save the look as a style and your next video can start from it.

Then it writes each scene as code for your script, records the narration and scores the music, asking you to approve the music and the export as it goes. You download an MP4 that is yours, and caption files for accessibility are a free export.

Before you start

See finished builds, each with the brief that produced it, on the examples page, or read how credits work on the pricing page.