Remove metadata from screenshots before Slack or Discord
Screenshots are the default language of team chat and community servers. A bug gets reported with a screenshot. A support ticket gets a screenshot of the error. A Discord server shares a screenshot of a crash, a settings panel, a DM gone wrong. It's fast and it feels low-risk — there's no attachment to download, no form to fill out, just drag the image into the channel. But the file still carries whatever was captured inside it, and channels are rarely as private as they feel.
What's hiding in the file itself
A screenshot is still an image file, and image files can carry metadata — the same kind of hidden data that rides along in a photo. Depending on the tool and device used to capture it, that can include the capture software, the OS and device model, a timestamp, and editing history if the image was cropped or annotated before it was shared. None of that shows up in the preview Slack or Discord renders — it's inside the file, and it travels with it if someone downloads the original.
Why a "private" channel isn't the same as private
A screenshot dropped into a team channel or a support ticket often sits there indefinitely, gets forwarded, exported in a compliance request, or pulled into a public bug tracker when someone escalates the issue. A Discord screenshot can get reposted outside the server entirely. Treat anything you post to chat the way you'd treat an email attachment: once it's sent, you've lost control of where it ends up next.
What's usually the bigger risk
The metadata inside the file is rarely the main concern here — what's visible in the frame usually is. A support screenshot can show a full file path with your username, an internal hostname, an API key printed in a log panel, another open tab, or a notification banner with someone else's name in it. None of that is metadata scrub can find or strip; it's pixels on the screen, and the only fix is looking at the frame before you hit send and cropping or blurring anything that shouldn't be public.
What to check before you post
For the file itself, scrub reads a screenshot locally and shows you any EXIF, XMP or appended data hiding inside it, then strips it losslessly if you want a clean copy — nothing is uploaded anywhere to do this. It won't catch what's visible in the image; that part is on you, every time. The habit that actually holds up: glance at the full frame for anything you wouldn't want screenshotted back at you later, then run the file through scrub before it goes into the channel or the ticket. It's the same check worth running before posting a code screenshot anywhere else.
The short version
Chat feels casual, but a screenshot you post there can outlive the conversation. Check the frame for anything visible you didn't mean to share, and clean the file's hidden metadata locally before it goes in. Get scrub free and check a screenshot in seconds.