Sign in
← AI PulseAug 20, 2026

Wire · news · Single-source brief

Grok Build Video Tools Require User-Supplied S3 Storage Under Zero Data Retention

Under Zero Data Retention (ZDR), users of Grok Build video tools must configure their own S3-compatible storage for generated videos, as xAI does not store this content.

By Illumora Editorial

Source · Aug 20, 2026, 3:13 PM · On Illumora · Aug 20, 2026, 3:53 PM

Media from the primary source — shown here so you can stay on Illumora.

Rewritten from one allowlisted primary — not independent enterprise reporting. Lanes →

Brief drafted by Illumora’s editorial model from the linked primary source. Ops desk reviews flagged pieces. How we write →

Read the source →xAI Docs — Video Output Storage under ZDR | SpaceXAI Docs
Save

xAI has detailed the requirements for using video tools within Grok Build when operating under Zero Data Retention (ZDR). This configuration ensures that generated videos are stored directly in user-supplied S3-compatible storage, rather than by xAI.

Until this storage is properly configured, the video tools in Grok Build will return an error. The system uses presigned upload URLs for each video generation, which directs the video content to the user's specified bucket without xAI ever storing it.

Key Points

  • Grok Build video tools require user-supplied storage under Zero Data Retention (ZDR).
  • Generated videos are stored directly in an S3-compatible bucket configured by the user.
  • Grok Build presigns an upload URL for each generation, passing it to the API.
  • xAI does not store the video content; it lands directly in the user's bucket.
  • Configuration involves setting bucket, endpoint, region, and access keys in ~/.grok/managed_config.toml.
  • The configuration supports both read-write and optional read-only credentials.
  • Changes to the configuration require restarting Grok Build to take effect.

Context

According to xAI Docs, the grok-4.6 model's video tools operate under a Zero Data Retention policy. This policy necessitates that users provide and configure their own storage solutions for any video output. The documentation specifies that the credentials used for presigning URLs never leave the user's machine and are not sent to xAI.

Why It Matters

This requirement shifts the responsibility for video data storage and retention directly to the user, aligning with Zero Data Retention principles. Builders must integrate S3-compatible storage into their infrastructure to utilize Grok Build's video capabilities, impacting system architecture and data management practices.

What To Do

  • Configure an S3-compatible bucket (e.g., AWS S3, Cloudflare R2, MinIO) for video storage.
  • Edit the ~/.grok/managed_config.toml file to include the bucket details, endpoint, region, and access keys.
  • Ensure both read_write and, optionally, read_only access keys are correctly set.
  • Restart Grok Build after making any changes to the configuration file.
  • Note that video tools are enabled if the privacy setting is off, as detailed in the /privacy section of the documentation.