Remove AI metadata before posting to X
X is the least consistent of the major platforms. Provenance is read on some upload routes and not others, and behaviour has changed repeatedly, so the same image can be treated differently depending on how you post it.
Cleaning before upload is the only reliable approach when the platform’s behaviour is a moving target.
Drop an image here
We read what is inside it first, then show you every field before anything is removed.
JPEG · PNG · WebP: up to 25.0 MB · 30 files at a time
How it behaves
How X (Twitter) handles AI metadata
- X strips a lot of metadata during processing, but any provenance read happens before that.
- Behaviour differs between the web composer, the mobile apps and third-party scheduling tools.
- Community Notes and user reporting often surface AI origin regardless of what the file contains, a social mechanism no tool affects.
Where it is read
Which uploads carry metadata
- Post images
- Main upload path, behaviour varies by client.
- Profile and header
- Frequently AI-generated or AI-edited.
- Scheduled posts
- Third-party tools may re-encode and change what is present.
Questions
X (Twitter) metadata FAQ
›Does X label AI-generated images?
Inconsistently. X has read provenance on some upload paths and its handling has changed over time. Because it is unpredictable, cleaning before upload is the only dependable approach.
›Does X strip metadata anyway?
It removes a good deal during processing, which is why EXIF rarely survives a post. That does not help you, because any provenance check happens on the file you upload, before stripping.
Other platforms