What a Grok export carries, and what xAI leaves undocumented
Grok Imagine is the image and video side of Grok on grok.com and the phone apps, and xAI keeps the consumer-facing answers in a FAQ at https://docs.x.ai/grok/faq. On marking, the FAQ is brief. Generated images and videos include a Grok watermark to indicate that the content was created with AI, and there is no setting to remove it. The same answer adds that removing, altering, or obscuring the watermark or other provenance signals is prohibited under the Acceptable Use Policy. So the visible mark is documented, removal is a policy question rather than a toggle, and the phrase other provenance signals is left hanging without a definition.
The rest of the picture is missing. xAI publishes no field map for a Grok file, mentions no C2PA or Content Credentials record in the pages we could read, and describes no detector and no metadata switch. That one phrase, other provenance signals, is the only hint of a layer beyond the visible mark, and no document says what the layer is. Missing documentation is not a denial: a file can carry records the vendor has never described, and this page treats them as possible rather than promised.
The API side is documented at the request level and silent at the file level. Images are requested from https://docs.x.ai/developers/model-capabilities/images/generation with a model such as grok-imagine-image-2.0, delivered as temporary URLs by default, or as base64 when the response format asks for it. The sample response in the REST reference reports mime_type image/jpeg. None of those pages says which metadata segments the returned file holds, so for any single file the file itself is the only reliable evidence.
Any image can still carry the ordinary records that pipelines write. A JPEG keeps marker segments before the image data, and those segments can hold EXIF, XMP, IPTC and an APP marker for a signed manifest. A PNG keeps text chunks and an eXIf chunk. A file that passed through an editor carries the editor software string on top of whatever the generator left. The strip below targets the recognized AI-generator records in that set, and the page says which classes it knows instead of promising a clean slate.
What the strip can change, and where it stops
Metadata and pixels live in different layers. The record sits in segments and chunks that describe the file. The picture sits in the coded data that draws it. A metadata pass rewrites the record and leaves the picture alone, which is why it cannot take off a mark drawn into the frame. That split decides everything here: a Grok watermark is visible because it is painted into the pixels, and a visible mark is not metadata.
Inside the record, the pass targets fields that identify a generator. Those are a C2PA manifest store and its JUMBF wrapper when one is present, an IPTC Digital Source Type value that names synthetic media, XMP creator tool and prompt fields, and an EXIF software tag that names a generation tool. This is the family of records that declares AI origin in machine-readable form. A title, a caption, a camera model and a capture time are not in that family.
Standard display metadata stays by default. The color profile is kept so colors do not shift, orientation is kept, and genuine camera EXIF, GPS coordinates and timestamps are left where they are. That is deliberate. A file that quietly loses its color profile renders wrong on the next screen, and a privacy erase is a separate job with a different promise. The Remove Metadata page runs that second pass on the same image.
Format behavior follows the container. On JPEG, the cleaner reads the marker segments and drops the metadata ones while the coded scan stays as it was. A PNG above 8 bits per channel keeps its existing image data. An 8 bit PNG is written again by the encoder, which reproduces the same samples. WebP is decoded and encoded again, so its bytes differ even when the picture looks the same. None of those paths redraws the frame, and none of them reaches a mark painted into it.
How to keep records out of a Grok share
Start from the file Grok handed you
An API image arrives as a temporary URL, so download it while the link is live instead of saving a copy out of a chat window. The original carries whatever the service wrote. A screenshot replaces the pixels and drops most of the record, and a repost may have been re-encoded by another platform first. Begin with the download you control.
Decide the disclosure before you strip
The visible mark is the part xAI made deliberate, and its FAQ ties interference to the Acceptable Use Policy. Clearing file records is an editing choice on your own output; disguising AI origin is a different act, and some jurisdictions require disclosure whatever the file says. If you publish generated work, say so in the post itself.
Strip the copy you will actually send
Every converter, editor or sync tool that touches the file after the strip can add a fresh software string. Run the pass after your final edit and upload the cleaned result directly. If you resize or crop later, inspect that export again, because it is a new file with a record of its own.
Read the result before it travels
Open the cleaned file in an image metadata viewer and look for the fields that were there before. The manifest should be gone, and the generator strings should be gone. The watermark will still be in the picture, because that layer was never in scope. Confirm both outcomes so you know what you are sharing.
How it works
How to strip the metadata from a Grok image
Step 1: Upload the Grok export
Drop the Grok image into the panel below, or pick it with the file browser. The upload travels from your browser to processing storage and is not published. Until a job runs, the copy on your disk stays untouched, which leaves you a reference to compare against.
Tip
Use the download from Grok or its API rather than a copy saved out of a chat thread. The original is the file that still holds the record.
Step 2: Run the metadata strip
The panel runs one image metadata operation with removal enabled, so no setting needs a decision. The job clears the generator records it recognizes: a C2PA manifest store, an IPTC source type for synthetic media, XMP creator and prompt fields, and an EXIF software string that names a generator. The picture data is not redrawn, and the visible mark is not touched.
Tip
A credit is charged when a job runs, not when the panel opens.
Step 3: Download and inspect the copy
Once the job finishes, download the cleaned image and look at it once. The frame should match what you uploaded, colors should land as before, and the watermark should be exactly where it was. A visitor without a session signs in first, and the panel comes back after that.
Tip
Upload this copy, not the original. An editor you run afterwards can write a new record into the result.
Limitations and what stays in the file
Where to go next
The AI Metadata Remover page is the general entry point for generator records on images from services other than Grok, and it covers the IPTC and XMP fields a hosted service can add. The Flux Metadata Remover page goes deeper on a hosted generator whose exports carry a signed credential and a workflow record, which is useful if you work with more than one service. The Remove Metadata page handles the layer this page keeps: location, device and capture time fields.
The facts above come from official documents. The Grok FAQ states the watermark policy and points at the Acceptable Use Policy at https://docs.x.ai/grok/faq. The image generation documentation describes the request format, the temporary URLs and the base64 option at https://docs.x.ai/developers/model-capabilities/images/generation. The C2PA standard and the manifest model behind a signed credential are published at https://c2pa.org/. Any claim about a mechanism xAI has not described is left out of this page on purpose.
Sign in to run. Free credits included.
FAQ
Frequently asked questions
What xAI documents about Grok images, what it leaves unstated, and what a metadata strip can change before you share.
Explore more tools
AI Metadata Remover
The general entry point for generator records, for images that came from a service other than Grok.
Remove Metadata
The privacy pass for location, device and capture time fields, the layer this page keeps by default.
Flux Metadata Remover
A closer look at a hosted generator whose exports carry a signed credential and a workflow record.
C2PA Remover
The credential layer in an image file, separate from what xAI documents about its mark.
Image Metadata Viewer
Read the generator entries in a Grok export before deciding what to remove.
All tools
Every remover and detector on one page, grouped by what each one cleans or checks.
Share a Grok image with a clean file
One metadata pass clears the recognized generator records while the visible watermark stays where xAI put it. The strip costs 5 credits and leaves PNG and JPEG pixels intact.