⏰ Black Friday Deal Soon ⏰ Personal licenses will be on sale for $39 $291 starting Monday, November 23rd!
Blog · Guide

Before You Paste That Screen Shot: Redact, Encrypt and Expire What You Share

6 min read

Screen shots and screen recordings show more than the bug or the button you meant to point at: email addresses, card numbers, API keys, customer names. Here is what typically leaks, and how Dropshare helps you redact it, encrypt the file on your Mac, and share it with a link that expires or needs a password.

What leaks through screen shots

A screen shot is quick to take and even quicker to paste. That is exactly why it is easy to share more than you meant to. Look at the last few you sent and you will probably find some of these:

  • Personal data: email addresses in a sidebar or a To: field, phone numbers, customer names in a CRM, a notification banner that happened to pop up.
  • Payment details: a card number in a checkout form or a billing dashboard.
  • Secrets: API keys, access tokens, passwords in a terminal, a .env file open in your editor, a session ID in a URL.
  • Internal details: intranet URLs, IP addresses, ticket and order IDs, project names in open tabs or the bookmarks bar.

Then there is the link itself. Once it is posted in a chat, it can be forwarded, end up in someone's notes, or still work a year later. Dropshare has tools for each of these steps: what is in the image, how the file is stored, and how long the link works.


Redact before you upload

Dropshare's annotation editor has Blur and Pixelate tools. Select either one and the sidebar shows an Auto-redact section. Dropshare recognizes the text on the screen shot right on your Mac and covers every match with one click on Auto-pixelate (or Auto-blur). Built-in types you can turn on or off:

  • Credit card numbers (checked with the same checksum card numbers use, so random runs of digits are left alone)
  • Phone numbers in international format, starting with +
  • Email addresses
  • URLs
  • UUIDs
  • IPv4 addresses

For anything else, add a custom rule with a regular expression. The rule editor lets you paste a line from one of your screen shots and shows what the pattern matches before you save it. For example, to catch GitHub personal access tokens and Stripe live keys:

ghp_[A-Za-z0-9]{36}
sk_live_[A-Za-z0-9]+

Auto-redact only finds text it can read, so always look over the result before you share. Names, faces, handwriting or a partly cut-off key need a manual rectangle with the same tools. Pick a strong setting and cover the whole field, not just part of it.

When you upload, save or copy from the editor, the annotations are rendered into the image. The redacted areas are part of the pixels of the file you share, not a separate layer that someone could remove.


Redact in screen recordings

Recordings are harder: things move, and a notification can appear at any time. While you record, click Pixelate in the recording controls to put a pixelation overlay on the screen. Move and resize it over the area you want to hide, such as a sidebar with customer names or the part of a terminal that shows a token, and add more overlays if you need them. Everything under an overlay is pixelated in the recording.

The overlay covers a fixed area of the screen, so keep sensitive windows where it is, or record only the part of the screen you need. Settings > Screen Capture also has an option to hide Dropshare's own windows from recordings.


Encrypt before the file leaves your Mac

With Upload Encryption, Dropshare encrypts files with AES on your Mac before they are uploaded. Your storage only ever holds the encrypted file (it gets an .enc suffix), so the content stays protected in transit and on the server. Turn it on in Settings > Uploads > Upload Encryption, or per connection.

The recipient doesn't need Dropshare. They open the landing page in their browser and click Download. The browser fetches the encrypted file, decrypts it and saves it under its original name. The key is part of the link, after #dec=.

  • Send the key separately: you can copy the link without the key and share the key through another channel. Without it, the landing page asks for the key.
  • Know the limits: anyone with the full link can decrypt the file, landing page previews aren't available for encrypted uploads, and the key is also kept in your upload history on your Mac.
  • Which connections: encryption needs a landing page, so it works with object storage and protocol connections such as Amazon S3 and other S3-compatible storage, SFTP, SCP, FTP and WebDAV.

The knowledge base explains how to use upload encryption in detail.


Most screen shots only need to work for a few days. Two features make sure they don't work forever:

  • Access-restricted URLs with Dropshare Safe:
    Right-click an upload and choose Create access-restricted URL. Set an expiry date, an optional password, and whether to track downloads. Dropshare Safe passes the download through without revealing the file's direct URL, so keep that URL to yourself. It is free and works for uploads to connections with a direct file URL (the same ones that support landing pages), but not for encrypted uploads. How Dropshare Safe works.
  • Automatic deletion:
    In Settings > Uploads (with Expert Mode on) you can delete uploads after 1, 3, 5, 7, 30, 90 or 365 days, from your upload history only or from the server too. This runs while Dropshare is running, on connections that support deleting files. Set up automatic deletion.

Hard-to-guess links help too. Custom filenames can add random characters to every upload, so nobody finds your files by guessing names.


Where your files live, and what names say

Dropshare uploads to storage you choose, not to a Dropshare silo. If it matters where your screen shots are stored, pick a provider and region that fit your requirements, for example one of the European providers in our guide to an EU-based setup, or your own server.

Filenames are part of the link, so they deserve a look as well. With AI-generated filenames you can let Apple Intelligence name screen shots on your Mac, without sending the image anywhere for naming. A descriptive name also tells anyone who sees the link what is inside, though, so for sensitive shares a random name may be the better choice.


A pre-share checklist

  1. Look at the whole screen shot, not just the part you wanted to show: sidebars, tabs, notifications, the menu bar.
  2. Run Auto-redact for card numbers, emails, phone numbers and URLs, and add custom rules for your own keys and IDs.
  3. Cover what text recognition can't find (names, faces, partial keys) with Pixelate by hand.
  4. For recordings, put pixelation overlays over sensitive areas and keep sensitive windows out of the recorded area.
  5. Turn on Upload Encryption for connections where files should never be readable on the server.
  6. For a password or an end date, create an access-restricted URL and share that instead of the direct link.
  7. Set automatic deletion so old uploads don't stay around forever.
  8. Check the filename: descriptive for your own archive, random for anything sensitive.
  9. Make sure the storage behind your connection is a place you are allowed to put this file.

Share with less to worry about

None of this slows down everyday sharing: set up encryption, deletion and your redaction rules once, and the shortcut you already use does the rest. See all Dropshare features, or get Dropshare and try it with your next screen shot.

Keep reading

More from the blog

All posts

Let's get started

Download the app and start sharing today. Free 7-day trial, no payment details required.

Get Dropshare

Mac

macOS 12.3+
Intel & Apple Silicon

Download for macOS

iPhone & iPad

iOS 14+

App Store

Android

Android 9+

Get it on Google Play
Newsletter

Stay in touch

Be the first to know about new app features and pre-release updates. Infrequent, and no spam, ever.

Subscribe
Go Up