Astra 6 vs Fable 5.1: Can AI Really Do Motion Graphics?

I gave Astra 6 and Fable 5.1 the same motion-graphics brief: make a short explainer with real logos, screenshots, animation, and strong transitions.

Then I pushed both further. Find demos on X and turn them into a new video.

I preferred Astra in this test. The difference went beyond the animation: it added music, sound effects, and transitions that made the result feel more finished. You can watch all four renders in the video above.

I ran Astra 6 in Ultra mode and Fable 5.1 in Claude Code. I asked for the Remotion skill and Higgsfield MCP, plus source material from the official product websites.

I kept the initial wording the same apart from the model name. This was a hands-on comparison of my two setups, with very little creative direction.

Fable produced a quick, dynamic animation. I liked parts of the movement, but its first video ran for about 10 seconds despite the 15-second request.

Astra gave me the stronger first result. The music, sound effects, animated text, and transitions worked together. I watched it again because I wanted to see how much it had done from that short brief.

Watch the first comparison at 2:20 →

For the follow-up, I asked each model to find popular demos of its own model on X, then include those examples in a new video. I wanted to see how much of the research and editing each could handle.

Astra sourced clips and assembled a reel with text, motion graphics, music, and sound effects. Fable also assembled a demo reel, including creator handles, view counts, and full-screen footage. I liked that full-screen treatment, though the render had no music or sound effects.

Both did useful work. I still preferred Astra, especially on the first explainer. Fable's second run took about 32 minutes in the recorded session, so this was not an instant workflow.

Watch the demo reels from 6:03 →

This is a cleaned-up version of the first brief. Replace the bracketed details with your product.

Create a 15-second motion-graphics explainer for [product]. Use its official logos, screenshots, fonts, and product visuals. Show [three features] with a fast pace, readable text, movement, and clear transitions.

Use the Remotion skill and Higgsfield MCP to help with the animation, timing, and motion design. Gather the source material from [official website]. Deliver the finished video.

For a follow-up, give the agent a few approved demo clips and ask it to build a second version around those examples. If you use someone else's clips, check permission and attribution before publishing.

Before you use the video, watch it with the sound on and check the requested duration, readable text, logos, transitions, and source footage. Fable's shorter first render and missing audio in round two were easy details to miss if I only looked at a preview.

I also looked at reported token usage and estimated API costs near the end of the recording. Those were session estimates, not invoices or a reliable cost per video. Check the usage in your own account before planning a batch.

Watch the full Astra 6 vs Fable 5.1 test →

Try the brief on one product you know well and compare the first render with a revised version. That will show you where a little direction makes the biggest difference.

Marcin

Want to learn and build alongside other AI builders? Join us here.