Grok Imagine on X is the surface; the catalog row is the job
Grok Imagine Video on Versely is 6 / 10 / 15 / 20 / 30s, 720p, 7 credits, native audio. The X composer is how xAI ships Imagine to a feed. It is not captions, not Seedance, not a 4K Veo take.
Grok Imagine Video on Versely is 6 / 10 / 15 / 20 / 30s, 720p, 7 credits, native audio. The X composer is how xAI ships Imagine to a feed. It is not captions, not Seedance, not a 4K Veo take.
That sentence is a product boundary, not a dunk on grok.com. The composer inside X (and the Grok app that shares it) is a surface for xAI's Imagine family. It is a good surface for a clip that should look like Imagine and live in that feed. It is not a studio. Treating it as one is how a 10-second Imagine post turns into Imagine plus three other apps.
Grok Imagine Video is already in the Versely catalog with those durations, 720p, native audio, 7 credits. The model does not change because you launched it from a post box. The surrounding work does.
What the X composer is
The composer is xAI's launcher with a posting button. You type a shot, you get an Imagine clip, you can drop it on a timeline people already associate with Grok. If the entire job is “I want an Imagine-looking short and I already live on X,” that box is a reasonable place to press generate.
That is the whole compliment. A surface is allowed to be good at one family. The mistake is inferring the rest of a pipeline from a composer.
The X box does not become a studio because the post went live from it. A studio, in production terms, is the place you can:
- pick the model the job needs, not the model the vendor ships in that text field
- caption, crop, dub, and deliver without exporting through a side door
- keep a brand kit and a credit pool that survive a bad week on one family
- fail over when Imagine is the wrong row
The composer is not those things. It is Imagine with X's furniture around it. Grok Imagine when the destination is X is the routing rule for where the file lives. This page is the rule for where you press generate. Destination can still be X. The launcher does not have to be.
What the catalog row actually sells
On Versely, Imagine is rows, not a feed.
- Grok Imagine Video — text-to-video, 6 / 10 / 15 / 20 / 30 seconds, 720p, native audio, 7 credits. This is the generate. This is the job.
- Grok Imagine Extend — continue an existing Grok Imagine clip at a timestamp, 2–10s, 8 credits, audio false. In-family continuation. Not a chat model “going on.” Not a 4K upscale.
Those are pixel jobs. They do not caption or schedule. They do not become Seedance 2.5 (4–30s, 720p, 47 credits, native audio, a single-pass hold) because you asked the composer for “more cinematic.” They do not become Veo 3.1 (4 / 6 / 8s, 4K, 40 credits, native audio) because you typed “4K.” 720p is the published ceiling. A 4K Veo take is a different slug.
Chat is a third object. Grok Imagine is the generate family; Grok 4.6 is the chat brain. Pin x-ai/grok-4.6 as the planner if you want that brain. Name Imagine Video as the renderer if you want those pixels. Saying “use Grok” in the X box collapses both knobs.
Extend will not grow a soundtrack the Video row already baked in: audio is false on Extend. Continue picture. Score on the original take, or accept a silent continuation.
What you still have to do after generate
An Imagine take is a 6-to-30-second file at 720p with native audio. Shipping it usually requires work the composer is not for:
- Captions. Word-timed, burned or platform-native. That is an editor, not a prompt synonym for “add subtitles.”
- A second model. Pack-shot identity hold, 4K plate, presenter file, multilingual explainer — none of those are “try a different Grok preset.” They are different catalog rows.
- Publishing that is not X. Aspect sets, a hook pack, a YouTube crop. The composer is not an account on those apps.
- A shared bill. When Imagine misses, the next credit should land on Seedance or Veo or Kling without a new login.
If your week is “generate in the X box, download, finish in four other tabs,” you are in a launcher plus a pile of launchers. The AI video generator is “run the model.” The rest of the app is why you do not live in the composer.
Keep Imagine, leave the composer
You do not need to stop using Imagine. You need to stop treating the X box as the building.
Bring the job that is actually Imagine's — loosely styled shorts, a 10- or 30-second menu at 7 credits, native audio, in-family extend — and run it next to the models the composer cannot see. When the next shot is a 4K Veo plate, a 30-second Seedance hold, or a silent Kling motion pass, change the row, not the vendor relationship with xAI.
Same pattern as every other single-vendor surface: Flow is how Gemini users run Veo; the Kling app is how you run Kling; the X composer is how xAI ships Imagine to a feed. Correct as a launcher, expensive as a home. The switcher is a Grok Imagine alternative. The side-by-side is Versely vs Grok Imagine. This page is only the composer.
Do not migrate off Imagine because X feels small. Migrate off the composer because the slate was never only Imagine. If the slate is only Imagine posts for an X account, stay.
List the last ten clips you shipped. If eight were Imagine-shaped X shorts, the composer is a tolerable house — you will still caption somewhere else. If four needed a different family — 4K, a product identity hold, a talking presenter — those four were forced through Imagine or a second app. Run Imagine where it wins. One bill is the point of not living in a vendor surface. Grok chat next to Imagine inside X is still xAI's roster. A studio is a roster you can leave.
FAQ
Is the X composer a competitor to Versely?
It is a competitor for the hour you spend generating an Imagine clip into a post. It is not a competitor for the week you spend captioning, routing other models, and publishing off X. If Imagine Video is the only row you need, the comparison is launcher versus launcher. If it is not, the comparison is surface versus studio.
Do I lose Grok Imagine Video if I stop generating inside X?
No. Imagine is the model. The composer is one place that runs it. Grok Imagine Video is in the catalog with the same job: 6 / 10 / 15 / 20 / 30s, 720p, native audio, 7 credits. You keep the model. You change the door. Extend stays the in-family continue: Grok Imagine Extend, audio off.
Can the X composer replace captions, Seedance, or Veo 4K?
No. Captions are an editor. Seedance 2.5 is a different 30-second contract at 47 credits. Veo 3.1 is a 4K, 4 / 6 / 8s plate at 40 credits. Typing those jobs into Imagine's box does not purchase them. Plan the row, then the post.
Why not stay in X and open other apps for the rest?
You can, and many people do, until the second app has its own subscription, its own login, and no shared history with the Imagine takes. That pile is what a shared bill is for. The X composer plus three other products is the expensive way to assemble a studio out of launchers.