Remove AI Metadata Before Posting Images to Discord

Discord does not show Meta-style AI Info badges on attachments today. Files you upload in art servers, commission channels, and DMs are often downloaded and reposted to Instagram, Behance, Pinterest, or client sites that do read C2PA and XMP at upload.

Clean the master before first upload. Discord re-encodes images for CDN delivery — starting from a metadata-free source avoids baking provenance into copies that community members save.

Enable PNG chunk removal for SD and ComfyUI exports shared in art servers. Workflow JSON in tEXt chunks identifies generator settings and can trigger labels when the file is reposted elsewhere.

Upscaled JPGs and PNGs often retain XMP software tags naming Midjourney or third-party upscale tools. Strip before posting in feedback channels so downloaders get a clean master.

OpenAI exports frequently include C2PA. A “quick share for critique” in Discord can become a client Instagram post later — clean at the source when you own the file.

No — metadata blocks are removed; pixels are unchanged. Discord’s subsequent compression is separate; still start from the highest-quality cleaned master.

Metadata hygiene applies to any raster you upload. Clean before sharing WIP or deliverable previews so buyers do not inherit C2PA when they post approved finals publicly.

This page covers files you upload manually. Bot pipelines that pull raw generator URLs may re-fetch marked files — download, clean locally, then upload the cleaned attachment.

Yes — up to 30 images per browser session. Clean every variant before a “pick your favorite” post; each download should be safe for Instagram reposts.

Tool-specific C2PA and XMP differ, but the workflow is the same: strip on the master in Discord before community members circulate it to portfolio sites.

Do not rely on Discord to remove C2PA or PNG chunks. Re-encoding may change compression but is not a proven metadata scrub — use the browser remover explicitly.

This tool targets JPG, PNG, and WebP stills. Video provenance in MP4/MOV is a separate problem — export a cover still and clean that raster when you need a clean thumbnail.

Screenshots often drop chunks but harm quality. Prefer original PNG export plus metadata removal for art you want critiqued at full resolution.

Clean files you may share. Removing metadata does not change pixels; follow contract terms on AI disclosure and public posting.

Discord is a distribution hub, not the final destination. Downstream Instagram AI Info, Etsy listing scans, and Behance gallery uploads are why server moderators recommend clean masters.

Inpaint exports from SD WebUI and ComfyUI often retain PNG workflow chunks plus partial C2PA when merged back into Photoshop. Clean the flattened WIP before posting — clients frequently repost WIP to Instagram for approval.

Only downloadable JPG/PNG/WebP attachments need this workflow. Stickers and emoji are separate assets; raster art posted for saves and reposts should still be cleaned.

Discord server banners and invite backgrounds are static JPG/PNG uploads that can inherit C2PA from AI generators. Clean before uploading to Server Settings. Custom emoji uploads are small but can still carry EXIF software strings — strip if bots flag assets.

Discord is a common handoff path for MJ and SD images — downloading and re-uploading does not remove metadata. Clean locally, then post the attachment to art channels if file-level labels matter for downstream reposts to Instagram or Reddit.

Small emoji uploads still carry metadata bytes. Strip before uploading custom emoji when server members repost emoji assets to Twitter as PNG.

Community Stage events use wide banners — export at Discord spec, strip C2PA, upload once per event series.

Onboarding screens use wide JPEGs — new moderators often upload raw MJ exports. Add strip step to moderator handbook before granting banner permissions.

Large communities run weekly event banners across multiple servers — template one cleaned master per event, resize per server spec in Express, strip again after each resize. Moderator teams should not pass raw Midjourney files in staff channels; staff-only channels still leak when screenshots repost to public X announcements.

Level 2 and 3 server banners rotate with seasons — strip each season banner before upload; animated banner GIF not supported here, export static PNG frame for strip then convert per Discord spec.

Servers above 50k members rotate banners for partnerships and esports seasons — treat each partnership banner like a product launch: strip, upload, archive credentialed source separately for sponsor reporting. Esports orgs posting match result graphics from AI assist pipelines should strip before #match-results announcements; fans cross-post to X within minutes carrying same bytes. Staff bots that auto-post welcome images need stripped assets in bot asset folder — update bot folder when banner season changes, not only human-visible banner.

Partner server kits include banner PSD and PNG — strip PNG before Season launch even if PSD archived for sponsors.

Yes — ping partners with cleared banner PNG only in #partners channel; partners repost to Twitter within the hour.