Discord: the clip is a file; Imagine is not the share path

Generate, caption, export. Do not treat X-native as Discord-native.

A Discord community does not ingest a Grok share sheet. It ingests an MP4 (or it doesn't). The clip is a file. Captions have to be on the file, because autoplay in a channel is often silent and Discord is not X's native player. Imagine's path is a destination constraint for X. It is not a Discord upload.

Discord wants a file

Generate the take in the catalog — AI video generator is the Versely door for "run the model." Export an MP4. Attach it. That is the share path.

Grok Imagine is xAI's generator with a sharing path aimed at people whose next post lives on X. Reverse the picker when the network is X: name the timeline, then pick the family. Reverse it again when the network is Discord: name the file, then pick any family that can produce one.

If you generated inside Imagine because the clip "felt social," you still have to leave with a file to put in a channel. Native posting to X is not a Discord feature. Treating it as one is how a community manager sits on a take they cannot drop into #announcements.

The destination can still be a Discord server after a Versely generate. The launcher does not have to be grok.com, and it does not have to be X.

Caption on the file, not on the platform

Discord does not burn your hook. People scroll channels muted. If the words are not in the picture, the first second is a silent rectangle.

Add captions to a video is the transcription job: add_veed_captions listens to the clip's own audio, times the lines, and burns styled captions into an MP4. Twenty-one BASIC presets at the standard credit rate; nine DYNAMIC presets (glass, whisper, glide, fusion, terminal, handwritten, backdrop and the rest) at 2×. One hundred sixty-five language codes. It transcribes what is spoken. It does not translate, and it does not typeset a headline you never said — that is a text-overlay job.

Preview a style on the first seconds with preview_caption_style before you pay for a full render. Accuracy follows audio clarity. A music-bed server trailer will caption worse than a dry VO.

Caption before you export to Discord. Pasting a transcript in the message is not burned-in. A Grok-native post that looked captioned on X is not a Discord file.

Imagine is an X path

Use Imagine when the post lives on X and the look can be Imagine's look. Grok Imagine Video is a catalog row: text-to-video, native audio, 6 / 10 / 15 / 20 / 30 seconds, 720p ceiling, 7 credits listed. That mix and that sharing dialect are the point of the family.

Use a file workflow when the post lives in Discord:

1. Generate (any row the job needs — Imagine included, if the look is Imagine).
2. Caption on the MP4.
3. Export. Upload the file. Write the Discord caption as a message, not as a substitute for burned-in type.

Do not skip step 2 because X showed you words. Do not skip step 3 because Imagine has a post button. Community managers who live in X's generator and then "also drop it in Discord" are doing two destinations with one path. The Discord path is the file.

FAQ

Can I share an Imagine clip to Discord without exporting?

Not as Discord-native. Discord wants the attachment. Generate, caption, export. The X share path does not become a channel upload.

Do I need captions if the Discord post has a text message?

Yes, if the video autoplays muted. The message is beside the player, not on the frames. Burn the line with VEED captions, then write a short Discord message for context.

Is Grok Imagine banned for Discord work?

No. Run the family when you want that look. Leave with an MP4. Caption the MP4. The mistake is treating Imagine's X-native share as the Discord share.

Will add-captions-to-video invent my server CTA?

No. It transcribes speech. If nobody says the CTA, put it on with a text overlay job, or say it on the take before you caption.