What Microsoft writes into a Bing Image Creator image
Bing Image Creator is Microsoft's free image generation surface. Its feature page at https://www.microsoft.com/en-us/bing/features/bing-image-creator lists the models behind it, MAI-Image-1, GPT-4o and DALL-E 3, and the places it opens from, bing.com/create and the Bing search bar. That page is about prompts, models and daily limits. It says nothing about what travels inside the file after the download.
The provenance layer is documented elsewhere. The Microsoft Designer FAQ states that all images generated using AI features in Designer have metadata attached to the files to identify the source, and it names the mechanism: content credentials, provenance based on the C2PA standard. The same FAQ says images made with Designer editing features carry content credentials as well. The page is at https://support.microsoft.com/en-us/designer/frequently-asked-questions-about-microsoft-designer.
Bing's own announcement post goes further for this surface. It says Microsoft has implemented content credentials, provenance based on the C2PA standard, to help users identify AI-generated images. In the same post it describes a second mark: a watermark in the bottom left corner of each image created with Image Creator. The post is at https://blogs.bing.com/search/2024/12/Bringing-more-magic-to-Bing-Image-Creator/. Those two statements describe two different layers, and the distinction runs through this whole page.
A Microsoft newsroom feature on provenance lists the products that use its Content Credentials tooling: Designer, Copilot, Paint and select models in Azure OpenAI Service. The article is at https://news.microsoft.com/source/features/ai/fighting-deepfakes-with-more-transparency-about-ai/. That is why one strip fits all of them. The app named on the credential can change, and the metadata layer stays the same across the family.
C2PA itself is an open technical standard from the Coalition for Content Provenance and Authenticity. Its specification at https://spec.c2pa.org/specifications/specifications/2.5/index.html defines a signed record that certifies the source and history of media content. A Content Credential can name the tool that made the file, the time it was signed and the entity that signed it, and it binds those claims to the image data with a hash. The record lives in the metadata, not in the pixels.
Bing Image Creator, Designer and Copilot: one record, three doors
The three surfaces feel different to use and produce the same kind of file. Bing Image Creator is the generation page, with prompts typed at bing.com/create or into the Bing search bar and Copilot Search. Designer is the design app, where you generate an image and then lay out a card, a poster or a social post around it. Copilot is the assistant surface, where an image request can sit in the same conversation as a question about something else.
What they share is the provenance layer. Microsoft's provenance program covers all three, and the Designer FAQ is explicit that AI-generated images and edited images both get content credentials. A picture generated in one app and cropped in another can carry a record of both steps, if the export keeps it. A picture copied out of a chat answer carries whichever record survived that route. The surface changes; the metadata design does not.
That is why one strip covers all three. The panel at the top of this page does not need to know which door the file came through. It reads the metadata block and removes the parts that declare an AI source, and the same pass works on a Designer export and a Copilot image. What changes between the apps is how the file was saved, and whether a screenshot or a re-encode already dropped the record before you got it.
How it works
How to remove the metadata from a Bing Image Creator image
Step 1: Save the original download
Download the image from Bing Image Creator, Designer or Copilot and keep that file untouched. The metadata record is attached at generation and survives a plain save, so the original download is the copy worth cleaning. If the only version you have is a screenshot, the metadata is usually gone already, because a screenshot is a new file built from pixels. That is a different problem, and the strip below will have less to remove.
Tip
Keep a private copy of the original before you clean it. The signed history cannot be rebuilt once it is gone.
Step 2: Run the metadata strip
Drop a PNG, JPEG or WebP into the panel and start the job. One pass removes the C2PA manifest store and its JUMBF wrapper, the XMP packet that points at the manifest, IPTC source-type fields, and the AI generator strings the strip recognizes in XMP and EXIF. Standard display fields such as orientation and the color profile stay, so the image renders the way it did before. The file keeps its dimensions and framing, and PNG and WebP keep their original quality. The job runs server-side and costs 5 credits on the lite tier.
Tip
The strip is metadata only. A visible watermark or a logo baked into the frame is outside this pass.
Step 3: Download the clean file and check it
Download the result and open it in a metadata viewer before you share it. The viewer should show no C2PA manifest and no AI source field. If the file still declares a generator, run the strip once more after the last edit, because some editors write a fresh record on export. Then upload the cleaned copy, not the original. The visible watermark, if the source image had one, is still in the frame, and this page has not removed it.
Tip
Cleaning is a file step. Where the image is posted and what you say about it are separate decisions.
What the visible Bing watermark actually is
Microsoft's announcement post describes a watermark in the bottom left corner of every image created with Image Creator. That is a visible mark drawn into the frame. It is not the C2PA record, it is not hidden in the file's metadata, and the two do not travel together. A metadata strip can remove the credential while the corner mark stays exactly where the generator put it.
This page therefore makes one claim about the file layer and none about the visible mark. The C2PA manifest, the IPTC source type and the generator fields come out in one pass. The bottom-left watermark does not, because removing pixels is a different operation with different risks. Until a real-sample test confirms what a visible-mark pass does to this specific watermark, this page will not promise to remove it, and you should not read the metadata strip as a logo remover.
The same care applies to screenshots. Cropping or re-photographing an image removes most signed metadata and keeps the visible mark, which is the opposite of what many people expect. If the goal is a file with no AI declaration, the metadata strip is the direct route. If the goal is a clean frame with no corner mark, check the sample first and treat the result as a pixel edit, not a metadata edit.
What the strip removes, and what it leaves
C2PA Content Credentials
The signed manifest store and the JUMBF box that carries it. This is the record Microsoft documents. It can name the generating tool, the signing entity and the time of signing, and it binds those claims to the image with a hash. The specification is at https://spec.c2pa.org/specifications/specifications/2.5/index.html. The strip removes the store and the XMP pointer that leads to it.
IPTC DigitalSourceType
The older controlled vocabulary for where media came from, including trainedAlgorithmicMedia for model output and compositeSynthetic for mixed material. Microsoft's own pages describe C2PA rather than IPTC, so this page does not attribute the field to Microsoft. It sits in the same metadata block, and the same pass clears it.
XMP and EXIF generator fields
Plain text records that can name the software, the model or the export path, and sometimes the prompt itself. They are not signed, and any metadata viewer can read them. The strip targets the records that carry a recognized AI-generator marker; removing one leaves no such marker behind, which matters on platforms that read names rather than signatures.
The visible watermark stays
Microsoft's post describes a bottom-left watermark on Image Creator output. That mark is part of the pixels. This page does not remove it, and it does not claim to until a real-sample test confirms the result. Use the metadata strip for the signed record and treat the visible mark as a separate job.
Limitations and honest expectations
FAQ
Frequently asked questions
Short answers about the Bing Image Creator metadata remover, from the C2PA record to the visible watermark it does not touch.
Explore more tools
Remove AI Label
The cross-platform page that explains which apps read metadata at upload and how the strip fits before you post.
Metadata Remover
The privacy pass for the same file: EXIF, GPS, device details and edit history cleared before a share.
Adobe Firefly Metadata Remover
The Adobe side of the same job: what Firefly signs into Content Credentials and how the file is cleaned.
Image Metadata Viewer
Read the C2PA and IPTC fields inside a Bing export before deciding what to strip.
C2PA Remover
The signed provenance record on its own: what Content Credentials state and what removal leaves behind.
All tools
Every remover and detector on one page, grouped by what each one cleans or checks.
Clean the file before you share it
One strip removes the C2PA manifest, the IPTC source type and the generator fields. The image comes back at its original dimensions, and the visible watermark stays where the generator put it.