Is it safe to share screenshots?

Usually yes. A screenshot is safer than a photo from your camera, because it carries no GPS and none of the camera EXIF that pins a photo to a place and a device. The real risk is not hidden in the file, it is sitting in the frame: a notification you did not notice, another window behind the one you meant to show, a name, an email header, the clock in the corner. And if you tried to hide something with a blur, a blur can be reversed. Crop tight, cover secrets with a solid fill, export a fresh file, and check it before you send. Do that and a screenshot is one of the safest things you can share.

The short answer, and the catch

A screenshot is a picture of your screen, so it is exactly as safe as whatever was on your screen when you pressed the shortcut. That sounds obvious, but it is the whole problem. People check the thing they meant to capture and miss everything around it. The file itself is fairly clean. What leaks is the context: the stuff in-frame you stopped seeing, and any secret you thought you had hidden but only covered up. The rest of this page is those two failure modes and how to close them.

What can leak from a screenshot

There are five common ways a screenshot says more than you meant it to. Here is each risk, how it leaks, and the fix.

What is in the frame that you did not notice

This is the risk that actually bites people, and it has nothing to do with hacking. It is that a screenshot is a snapshot of a busy screen. A Slack or Messages notification slides in for a second and lands in the shot. The browser tab strip shows a site you were on. A window you forgot was open sits behind the one you meant to share. The menu bar shows the time, your name, the network. In a group chat, other people's replies are captured alongside the one you wanted. None of this is hidden in the file. It is right there in plain sight, and the sender skated past it because they were looking at one thing. The habit that fixes it is boring and works: turn on Do Not Disturb before you capture, crop to the smallest useful region, then look at every edge of the image as if a stranger will.

Hiding a secret is not the same as removing it

The second failure mode is when you did spot something sensitive and tried to cover it. A blur or a mosaic looks like it did the job, and it did not. Pixelation maps each block to the average of the pixels beneath it, a fixed rule, so tools like Depix and Bishop Fox's Unredacter reconstruct the original text by rendering guesses in the same font and matching them back. It works best on exactly the short, structured strings people pixelate, like account numbers and codes. So the honest answer to whether you can reverse a blurred or pixelated image is often yes. If the thing you are covering is a secret, do not blur it. The full method is in how to redact a screenshot on a Mac: cover with a solid, fully opaque fill, flatten it into a fresh file, and check the result. The same trap applies whether you are hiding text in a photo or a face: a soft blur obscures, it does not remove. It applies just as much to a specific secret, whether that is an API key in a screenshot or the numbers on a bank statement.

A cover can leak a second way too. If the black box sits on its own layer, or the marker was applied below full opacity, the data underneath is still there. Someone can select and copy the text out, delete the layer, or just push brightness and contrast until the ghost of the words appears. Covering is only real once the image is flattened, meaning the cover has been painted permanently into the pixels and there is no separate object to peel back.

The file can keep what you cropped out

Here is the one that surprises people, because it is invisible. In 2023 a bug nicknamed aCropalypse (CVE-2023-21036) showed that when you crop a screenshot and save over the original, some editors do not shrink the file to match the smaller image. They write the new image and leave the old bytes sitting past the end of it, so the cropped-out part can be reconstructed, up to roughly the original picture, out of a file that looked clean. It hit Google's Pixel Markup editor and Microsoft's Windows Snipping Tool, and both were patched. It did not affect macOS Preview, so this is not a Mac warning. It is the general lesson: cropping is only safe when you export a brand-new file, never when you overwrite the original. If part of the picture is sensitive enough to crop away, treat it like a secret and start a fresh file.

What about metadata?

Less than you would fear. A screenshot is not a camera photo, so it carries no GPS coordinates and none of the EXIF that records the camera, lens and exposure. That is the data people are usually anxious about, and it simply is not in a screenshot. What a screenshot does hold is modest: the capture date and time, the screen dimensions, and a color profile. On a Mac the timestamp is also baked into the default filename, the "Screenshot 2026-07-11 at ..." pattern, which is often the most revealing part. So the precise position is: metadata is a small risk in a screenshot, not the big one, and if the exact moment you captured something matters, rename the file and strip its metadata before you send it.

How to share a screenshot safely

The whole checklist is short.

1. Turn on Do Not Disturb before you capture, so a private notification cannot slide into the shot.
2. Capture just what you need. On a Mac, use ⇧⌘4 for a region rather than the whole screen.
3. Crop tight to drop anything around the edges you do not want to send.
4. Cover any secret with a solid, fully opaque fill, not a blur or a mosaic. If you use a box, make sure it is flattened into the image.
5. Export a fresh file rather than saving over the original, so nothing cropped away survives inside it.
6. Open the file you are about to send and look at every corner one last time.

The most secure way is to keep it on your Mac

Notice what the safe method does not include: uploading the image to a website. When you paste a screenshot into a free online blur or redaction tool, the image leaves your machine and lands on a stranger's server so it can be processed there, exactly the screenshot you were trying to be careful with. The most secure way to share a screenshot is to do all the editing on your own device and only send the finished, flattened file through a channel you already trust. Nothing sensitive should touch a third party in between.

How ScrubShot fits

This is the whole reason I built ScrubShot. It captures with Fn + Space, opens the shot in an editor, and lets you crop and cover before you share, all on your Mac. The Scrub tool is the part that matters here: instead of a normal pixelate, which is the reversible kind, each mosaic block is filled from pixels sampled at random from across the whole selected region. The pattern is decoupled from whatever sat underneath, so there is nothing to solve back to. It reverses to nothing by design, and it is baked straight into the image rather than sitting on a removable layer.

The capture, scrub and share flow makes no network connections, so a screenshot with a password or a client's details in it never leaves your Mac, and it is never uploaded to a web tool to be processed. Finished images save to ~/Pictures/ScrubShot and to the clipboard, already flattened. ScrubShot runs on macOS 14 and later, on both Apple Silicon and Intel.

FAQ

Is it safe to share screenshots?

Usually yes, but a screenshot carries more than the thing you meant to send. The main risk is what is visible in the frame that you did not notice: a notification banner, another window behind it, a name, an email header, the clock. A screenshot has little of the camera metadata a photo does, so the real exposure is on screen, not hidden in the file. Crop tight, look at every corner, and send it.

How do I screenshot and send it to someone?

On a Mac, press Shift Command 4 to grab a region, or Shift Command 3 for the whole screen. The image lands on your desktop as a PNG. Before you send it, turn on Do Not Disturb so a private notification cannot pop in mid-capture, crop to just the part you need, and cover anything sensitive with a solid opaque fill rather than a blur. Then attach the file and send it the way you normally would.

What is the most secure way to share a screenshot?

Keep the image on your own device for as long as you can. Crop it tight, cover any secret with a solid fill or a scramble that cannot be reversed, and export a brand-new flattened file rather than saving over the original. Send it through a channel you already trust, like the message thread it belongs to. Uploading to a free web blur or redaction tool is the opposite: your screenshot leaves your machine and lands on someone else's server.

Do screenshots contain hidden metadata?

Far less than a photo. A screenshot has no GPS and no camera EXIF, so the location and device fingerprints people worry about are simply not there. What it does carry is modest: a capture date and time, the screen dimensions, and a color profile. On a Mac the timestamp also sits in the default filename. If the exact time matters, rename the file and strip metadata before you send it.

Does ScrubShot upload my screenshots?

No. The capture, scrub and share flow makes no network connections, so a screenshot never leaves your Mac, unlike a web blur tool that uploads it. The app talks to a server only for the trial check, license activation and update checks, and those requests carry a hashed machine identifier and your license key, never any image data.