How to Share a Screenshot Securely (Without Leaking What's in It)

Quick answer: to share a screenshot securely, first crop it to what the other person needs and blur anything sensitive. Then send it through a channel where only the right people can open it and the service in the middle can't read it, such as an end-to-end encrypted link or an end-to-end encrypted messenger. In Chrome, Screshot does all of it from one editor: capture, blur, then Share for a link that's encrypted on your computer before it uploads.

A screenshot is the fastest way to show a bug, a payment error or a customer's problem. It is also the easiest way to leak one. The image gets pasted into a chat, forwarded to a vendor, uploaded to a "quick share" site, and suddenly a customer's email, an API key or an internal dashboard lives in places you can't see or delete. This guide covers what "secure" actually means for a screenshot, how the common ways of sending one compare, and a four-step method you can use every time.

What "secure" means when you share a screenshot

A screenshot is shared securely when four things are true:

• It only shows what's needed. Everything else is cropped out or blurred before it leaves your screen.
• Only the right people can open it. Not "anyone who gets the link", unless that's a deliberate choice.
• The service in the middle can't read it. The app or server that carries it stores an encrypted file, not your image.
• You can take it back. You can remove someone's access, or delete it, after you've sent it.

Most everyday ways of sharing a screenshot get one or two of these right. Few get all four.

Step 1: Remove what they don't need, before you share

Security starts before you pick a channel. Whatever you send, assume it may be forwarded.

• Crop to the part that matters. A capture of the whole screen includes tab titles, notifications, bookmarks and your signed-in account. Capture or crop only the area you're talking about.
• Blur personal and secret data. Emails, names, phone numbers, card numbers, API keys, tokens and internal URLs. Cover the whole field with a strong blur or an opaque box. Light pixelation can be reversed, as we explain in how to blur sensitive info in a screenshot.
• Check the places data hides. The address bar, the tab title and the corner of the app are the usual culprits. See 6 places sensitive data hides in a screenshot.
• Send a new, flattened image. Don't share the original file with shapes drawn on top; export or copy the edited image.

If something isn't in the image, no channel can leak it.

Step 2: Choose a channel that keeps it private

Here's how the usual ways of sending a screenshot compare on the four points above.

Paste it into a chat or attach it to an email

• Good for: quick, low-risk images to people already in the conversation.
• Watch out: the file is copied to every recipient, every device and the provider's servers. Anyone in the channel, including people added later, can see and forward it, and you can't pull it back from someone's inbox.

A shared cloud drive link

• Good for: files that already live in your company's drive, shared with named colleagues.
• Watch out: links set to "anyone with the link" spread easily, and the drive provider can read the file. Check the sharing setting every time.

A "quick share" screenshot hosting link

• Good for: nothing sensitive.
• Watch out: many of these services make uploads public by default and some use short, guessable link IDs. One independent researcher showed how sequential identifiers let them collect other users' screenshots, including card details and banking credentials. If a link can be guessed, it isn't private.

An end-to-end encrypted messenger

• Good for: sending a screenshot to one person or a small group you already message, for example on Signal.
• Watch out: the image still lands as a file on every recipient's devices, it's hard to bring into a ticket or a bug report, and your team may not all use the same app.

An end-to-end encrypted share link

• Good for: screenshots with customer or internal data, sent to colleagues, vendors or customers by email, chat or ticket.
• How it works: the screenshot is encrypted on your computer before it's uploaded. The service stores only the encrypted file. The key goes only to the people you choose, so the link is useless to anyone else, including the service that hosts it.

Step 3: Share it by end-to-end encrypted link

An end-to-end encrypted link combines the convenience of a link with the privacy of an encrypted messenger. Here's what happens behind it:

1. Your browser makes a new key for this one screenshot and encrypts the image with it (AES-256).

2. Only the encrypted file is uploaded. Without the key, it's random noise, even to the service storing it.

3. The key goes only to the people you choose. Either it's wrapped for each person you invite, so only their own key can unwrap it, or it travels inside the link itself after the #. Browsers never send that part of a link to a server.

To do this in Chrome with Screshot:

• Capture. Press Ctrl+Shift+S (Cmd+Shift+S on Mac) or click the Screshot icon. Drag to keep only the area you need.
• Blur and annotate. Pick Blur and drag over every sensitive field. Add an arrow or a box if it helps.
• Click Share. Screshot encrypts the screenshot on your computer, uploads the encrypted file and copies the link. The first time, you sign in with Google and turn on encryption with a passkey and a recovery code.
• Choose who can view. Only me is the default. Invited people lets you add colleagues by email: they sign in to their Screshot account to open it. Anyone with the link needs no sign-in, because the key is part of the link.
• Send the link in your email, chat or ticket.

Add Screshot to Chrome — free

For customer data, prefer Invited people over Anyone with the link. An invited link only opens for the people you named, even if it gets forwarded. A link that carries its key is only as private as the places you paste it.

Step 4: Stay in control after you send it

Sharing securely doesn't end when you hit send.

• Remove access when the job is done. Remove an invitee, or switch the screenshot back to Only me, and the link stops working the next time it's opened.
• Delete what you no longer need. Old screenshots of customer data are a liability, not an archive.
• Don't post "anyone" links in public places. Public channels, forums and public tickets turn a private link into a public one.
• Remember what encryption can't do. Once someone has opened your screenshot, they can still take their own screenshot of it. Share with people you trust, and share only what they need.

Common mistakes when sharing screenshots

• Sending the original file with the sensitive data hidden under a shape that can be moved or removed.
• Using a link anyone can guess, or one that's public by default.
• Sending the password in the same message as a password-protected link.
• Sharing the whole screen when a small crop would do.
• Trusting "unlisted" as if it meant "private". Unlisted only means it isn't in a search index.
• Forgetting about later. Links that never expire and files that are never deleted keep the risk alive.

If your team handles customer data, these mistakes can also be a compliance problem. See screenshots, PII and GDPR in support tickets.

Checklist before you share a screenshot

• Cropped to what the other person needs
• Emails, names, numbers, keys and tokens blurred, with the whole field covered
• Tab title, address bar, notifications and account details removed
• Sending a new, flattened image, not the original
• Sent by end-to-end encrypted link or messenger, not a public upload
• Shared with named people when it contains customer data
• A reminder to remove access or delete it when you're done

FAQ

What is the most secure way to share a screenshot?

Crop and blur it first, then send it through an end-to-end encrypted channel that limits who can open it: an end-to-end encrypted link shared with invited people, or an end-to-end encrypted messenger. That way only the intended people can see it, and the service in the middle can't.

Is it safe to send a screenshot over Slack, Teams or email?

It's fine for low-risk images. For anything with customer, financial or internal data, remember that the file is copied to every recipient and stored by the provider, and you can't take it back. Blur first, or send an end-to-end encrypted link instead of the file.

What is an end-to-end encrypted link?

A link to a file that was encrypted on the sender's device before upload. The service stores only the encrypted file and never has the key. The key goes to the people you choose, either wrapped for each of them or inside the link after the #, which browsers never send to a server.

Can someone screenshot my screenshot?

Yes. No sharing method can stop a person who can see the image from capturing it again. Encryption protects the screenshot on its way and on the server; blurring protects the data you never wanted to share in the first place.

Does Screshot see the screenshots I share?

No. Screenshots are encrypted in your browser before upload, and Screshot stores only the encrypted file without the key. Capturing, blurring, copying and downloading upload nothing at all. See how the encryption works.

Do the people I share with need an account?

For Invited people, yes: they sign in to their free Screshot account to open it, so the screenshot only opens for them. For Anyone with the link, no: the key is in the link, so anyone who has the full link can open it.

Can I share a screenshot securely without installing anything?

Partly. Crop and blur with any editor that exports a flattened image, then send it through an end-to-end encrypted messenger. You lose the ability to share by link and revoke access later.

Sources

• Here's how I got your credit card number, or why sequential identifiers are a bad idea
• Signal: private messenger with end-to-end encryption
• Screshot security overview: how the encryption works

Written by

Screshot Team

Product & security team

The team that builds Screshot, the private screenshot tool for Chrome. We write about keeping customer data out of screenshots, rolling out tools across a company, and getting work done faster with your screen.