UlazAI - KI-Bild- & Video-Tools
High-impression Grok query
Grok Imagine video FPS and JSON prompts: what xAI documents now
If you are searching for Grok Imagine video FPS or a JSON prompt field for frame rate, the useful answer is not a vague checklist. As of March 31, 2026, xAI's public video generation docs document model, duration, aspect ratio, resolution, image/video inputs, and reference images for `grok-imagine-video`, but they do not document a user-set fps field. Treat FPS as something to verify in exported output or sample metadata, not as a current public JSON knob.
Quick answer
As of March 31, 2026, xAI's public video generation docs for grok-imagine-video document duration, aspect_ratio, resolution, image and video inputs, and reference_images. They do not document a public user-set fps field. If your real question is frame rate, verify it from the exported MP4 or live sample metadata instead of assuming there is a JSON knob for it.
Need the broader market comparison first? Open the AI video models guide.
Official current model
grok-imagine-video
That is the model name shown in xAI's public video generation docs, so use it as the reference point instead of older Grok video speculation.
Documented request controls
duration, aspect ratio, resolution
The public docs show duration, aspect ratio, resolution, and media inputs. That is the documented JSON surface to work from today.
Practical FPS answer
Verify the output file
If you need frame rate certainty, inspect the finished MP4 metadata or a real sample export. Do not invent an fps control that the public docs do not expose.
Grok Imagine FPS and JSON checklist: what to verify before you build or buy
This is the minimum checklist if you are researching Grok Imagine video FPS, JSON prompts, or frame-rate assumptions before you build, benchmark, or buy.
| Check | Why it matters | How to verify |
|---|---|---|
| Is FPS a documented request field? | If it is not in the public contract, you should not promise it in product copy or build assumptions around it. | Check the current xAI video generation docs and request examples first. Verify whether fps appears alongside model, duration, aspect_ratio, resolution, image, video, or reference_images. |
| Which JSON fields are documented now? | The real implementation surface matters more than SEO shorthand like 'fps' or 'json prompt'. | Review the documented request examples for grok-imagine-video and note the live fields before you build prompts, tooling, or landing-page claims. |
| What output properties can you verify from a sample? | Frame rate questions usually mean you need the real exported file characteristics, not just the request schema. | Generate a sample clip, download the MP4, and inspect the media metadata to confirm duration, resolution, and frame rate for the exact workflow you plan to use. |
| What duration and quality settings are shown publicly? | Duration and resolution affect delivery format, cost, and whether the workflow fits your actual use case. | Use the public docs and playground examples as the baseline, then cross-check in the live product UI before you budget or publish specifics. |
| What is the next commercial step? | A page like this should route to pricing, docs, or the public Grok guide instead of trapping people in generic research copy. | If you want the buying route, go to packages. If you want the product route, go to the Grok guide. If you are integrating, go to the video API docs. |
What the public docs show
5s, 10s, and 12s examples
The public generation examples we checked center around 5, 10, and 12 second requests, with 720p examples shown in the docs.
Extra control path
Image, video, and reference inputs
The public docs also show image-to-video, video edits, video extensions, and reference-image workflows. That matters more than vague SEO phrases about JSON prompts.
Best production habit
Benchmark one sample path
Run one clean sample, inspect the finished file, and then decide whether Grok, Veo, or another model is the better route for your job and budget.
FAQ
Does xAI publicly document an FPS field for Grok Imagine video generation?
Not in the current public video generation docs we checked on March 31, 2026. The documented request examples center on model, duration, aspect ratio, resolution, and media inputs instead of a user-set fps field.
What JSON fields are documented for grok-imagine-video right now?
The public docs currently show fields such as model, prompt, duration, aspect_ratio, resolution, image, video, and reference_images depending on the workflow. Use the live docs as the source of truth before you build against them.
How should I verify Grok Imagine frame rate in practice?
Generate a sample clip in the exact workflow you plan to use, download the finished MP4, and inspect the output metadata. That is more reliable than assuming a frame rate from SEO summaries or third-party blog posts.
What should I click next if I want to test, buy, or integrate?
Use the Grok guide for the product route, the packages page for live checkout economics, and the video API docs if your real job is integration.
Official references
Turn the query into a clean next step
Use the Grok guide for the product route, packages for live spend, and the video API docs if you are integrating rather than browsing.