Create Your First Video

The core loop

1. Send a clear creative brief from the Home composer, or from the chat of an existing project.
2. Review the storyboard fluos proposes, then approve it or ask for changes.
3. Wait for the build — the preview panel appears as soon as the build starts.
4. Play the preview, quick-edit what you see, and send narrow follow-ups.
5. Export when it looks right.

Most first videos take one build and two or three follow-ups.

Write a brief that lands

The agent works best when your first message answers four things: format, duration, look, and ending. Everything else it will infer or ask about.

Create a 30-second launch teaser for an electric bike in 16:9.
Style: bold kinetic typography, warm orange highlights, fast transitions.
Ending: final 3 seconds lock on the logo and URL.

If the brief is thin, fluos may pause and ask a couple of short questions as tappable cards rather than guessing. Answer them and it continues.

Approve the storyboard

For a brand-new video, fluos does not jump straight into building. It first posts a storyboard card in the chat: a scene-by-scene plan with timing, plus an illustrated sheet of numbered scenes showing the intended look.

• Approve and build starts the build from exactly that plan.
• Request changes opens a box for your notes. fluos revises the storyboard and shows it again, and nothing is built in the meantime.

You can request changes as many times as you like. See Storyboards.

Attach what you have

Drag files onto the chat, or use Add content in the composer.

A few things worth knowing:

• SVG logos are first-class. fluos works with the vector shapes directly so individual parts of the mark can animate. Always prefer the SVG over a flattened PNG. See Brand Kit and Logos.
• Uploads default to reference, not embed. A screenshot or mood board tells the agent what to make things look like. If you want the actual file on screen, say so: "show this photo full-bleed in scene 2".
• Spreadsheets become charts. Attach a CSV and ask for an animated bar race or line chart.
• Anything you upload lands in the Library and can be reused in other projects in the same workspace.

You can also paste a URL. fluos reads the page and uses it as context — handy for "make a teaser in the style of this landing page".

Watch the build

The preview panel opens as soon as the build starts and shows a status chip:

• Building — fluos is creating the video.
• Booting — your preview is starting up.
• Live — the video is ready; you can scrub and play it.
• Updating — a follow-up is being applied. The current version keeps playing until the new one is ready.

While it works, a live shot list (the To-dos panel) ticks off each beat as it finishes. Behind the scenes fluos designs the scenes, generates any narration or music, and checks its own work before showing you the result. That is why a build takes longer than a chat reply.

You can leave or refresh the page — a running build keeps going. Only Stop cancels it.

Iterate in small steps

Follow-ups work best when each one changes a single thing.

Slow the logo reveal — it should settle by 2s and hold.

Scene 3 text is too small. Bump it and keep it inside the safe margins.

Swap the background to a deep navy gradient, keep everything else.

For visual tweaks, you can also point at the preview instead of describing where something is. See Quick edits.

Broad rewrites ("make it better", "redo it") usually cost you a good version. If you do lose one, version history has every successful build.

Export

Press Export, pick a format and quality, and start the export. MP4 keeps audio; GIF is a silent loop; other formats cover transparency and editing. Full detail in Preview and Exports.

Next steps