Guide
How to share a redacted image safely
The redaction fails at the moment of sending more often than at the moment of drawing. The original screenshot is still on the clipboard and still in your downloads folder. Attach the exported PNG after you have opened it. Do not paste the shot you took first.
Last updated
Should you copy or download the redacted image?
Download it, open it, and attach that file. Export writes PNG, JPG, or WebP on your device. Copy image places a PNG of the redacted canvas on the clipboard only when that button succeeds. Until then, the clipboard usually still holds the screenshot you took before you redacted anything.
Download is the slower habit, which is why it works. You get a file with a name, you can open it, and you can see that you are attaching redacted-image.png rather than Screenshot at 3.41.02 PM. Copy is one keystroke, and the keystroke people use is the one from muscle memory: they captured the screen, switched to the chat, and pasted. That paste is the unredacted shot. The careful edit in the browser never enters the message.
Copy image on this site changes the clipboard only if that button actually ran. A failed copy, a second screenshot, or a notification preview can put the original back. Even then, you cannot see a filename. Download-and-attach gives you an object you can inspect. Click Export redacted PNG (or JPG or WebP), wait for the download, and leave the paste shortcut alone until you have dealt with that file.
If you do need to paste, copy from the downloaded PNG after you have looked at it. On a desktop, open the file, confirm the bars are in the right places, then copy that image from the viewer. On a phone, share from the downloaded file in Files or the downloads list, not from the screenshot you just took in the photo grid. The recent thumbnail is a trap.
| Action | What the recipient gets | How it goes wrong |
|---|---|---|
| Attach the exported PNG | The redacted pixels, if you picked that file | A similarly named original sits next to it |
| Paste right after taking the screenshot | The original screenshot | The redaction never left the browser |
| Copy the exported PNG, then paste | The redacted file, if that is what you copied | The clipboard still holds the first shot |
| Forward a thread that has both | Both copies | The “just in case” original is the leak |
| Share a cloud editor link | Whatever that service stored | The image was uploaded before it was hidden |
Why is the original file still the leak?
The editor never replaces the file you dropped, pasted, or chose. Export writes a new PNG. The screenshot tool’s file, the camera original, and often the clipboard still contain the sensitive pixels. Sending any of those undoes the boxes you drew. Delete or archive the original only after you are sure you attached the export.
This is easy to get wrong because both files are images of the same screen, taken a minute apart. Operating systems name screenshots with the date. The export is redacted-image.png. If your mail client shows a preview the size of a postage stamp, the black bars and the real text look similar enough that you click the first row. Enlarge the preview. Read one string you know you covered. If you can read it, that is the original.
Do not email the original to yourself “so you have it” and then forward the message. Do not drop both files into a shared folder and rename the original to final. Do not paste the secret into the sentence that explains the redaction. Teams do this with tokens: the image is a clean black bar, and the comment underneath is the key. The comment is the publication.
Keeping the original on your own device is reasonable until the ticket is done. Keeping it is not the same as sending it. When you are finished, you can delete the screenshot you no longer need. You cannot delete the copy a chat server already stored. Decide before you press send, not after someone quotes the image back to you.
What do filenames and metadata give away?
A filename like Screenshot plus a timestamp is a hint that the file came straight from the capture tool. The export from this site is a new PNG named redacted-image.png. That PNG is built from the canvas, so the original JPEG’s metadata, including location, is not inside it. The camera file still has that metadata. Share the PNG.
You can rename the export if redacted-image.png is confusing next to other downloads. Name it for the ticket, not for the secret. invoice-redacted.png is fine. john-smith-account.png is a name you just published in the filename. Avoid putting the customer, the patient, or the token in the name of the file you are about to upload to a tracker that shows filenames in the open.
Metadata is the quieter copy of the same mistake. Phone photos carry location, device, and time. A canvas export does not copy the source JPEG’s EXIF into the new PNG, because the download is a new image of the pixels you see, not a resave of the original file. That is a property of how this export is built. It is not a promise that every tool on the internet strips metadata, and it does not change the original file still sitting in your camera roll.
If you must share a photo that started as a JPEG from a phone, share the PNG you exported after redaction, not the JPEG. If a workflow demands the original format, use a desktop tool you trust to export a flattened copy and then check the result. Do not upload the original to a random “EXIF remover” in order to hide a face. You would be sending the sensitive photo away so that a website can delete a side channel.
How should you share into chat, email, and public posts?
Attach the exported PNG in chat and email. In a public issue or a social post, assume the image will be copied forever, so black-box anything you would not want quoted later. Do not rely on “the channel is private” as the redaction. Write what you removed in a sentence that does not contain the secret.
Chat apps want a paste. Resist it until the file is right. Drag the PNG into the composer from the downloads folder, or use the paperclip and pick the file by name. Look at the preview the app generates. If the preview is too small to read, download is still your friend: you already opened the file at full size. Send. Then look at your own message. People catch the sidebar in the sent preview more honestly than in the editor, because the editor is where they were rushing.
Email attachments have the same trap plus threads. A reply-all includes every earlier attachment. If the first message had the original and the second had the redaction, the thread has both. Send one message, with the redacted file, and do not “update” it by forwarding the unredacted draft. For a support portal, use the uploader and confirm the filename it shows after the upload finishes.
Public posts and public issues are permanent in practice. Someone will save the image, a search engine may keep a copy, and you will not be in the room when it is read. Use black boxes for text secrets, pixelate or a strong blur for faces, and the checklist for sidebars and URLs. A marketplace listing has the same lifespan as a post. The buyer does not need your plate, your street number, or the paperwork on the passenger seat.
What is the last look before you send?
Open the PNG, zoom, and read every sharp string. Confirm the filename. Confirm you are not also attaching the original. Confirm the message text does not repeat a secret you just covered. Then send that one file. If you hesitate on a region, cover it again before the message exists.
Read the corners, the tab title, the smallest table row, and any banner at the edge. Pronounce names and numbers you can still see. Hesitation means draw another box. It is cheaper than a rotation of a credential or an apology to a customer. The editor is still the same local one: paste is for getting the image in, export is for getting the safe file out.
Check the sent state, not only the compose state. Some apps replace the preview after upload. If the uploaded image is the wrong file, delete the message if the product allows it, and assume someone may already have a notification with the preview. That is why the check happens before send. Deleting is a backup, not the process.
None of this requires an account on hideimage.com, and none of it uploads the image for editing. The part the site cannot do is choose the file in the share sheet. That choice is the whole remaining risk once the boxes are honest. Download the PNG, look at it once, and send the file you just looked at.
- The attachment name is the export, not the screenshot timestamp.
- A zoomed look shows no readable secret, name, or plate you meant to hide.
- The message body does not repeat the hidden text.
- The thread does not already contain the original.
- You are not pasting from the clipboard that still holds the first capture.
Questions about this
People ask whether they should copy or download, whether the original stays on the device, and whether a chat app will undo the redaction by compressing the image. Download, then attach that file. The original stays put until you send it. Compression does not put letters back under a black box.
Does hideimage.com copy the redacted image to the clipboard?
Only after you press Copy image and the browser accepts it. That copies a PNG of the redacted canvas. Export downloads redacted-image.png, redacted-image.jpg, or redacted-image.webp. Pasting immediately after you take a screenshot still pastes the original.
Will Slack or email undo the blur?
Recompression can make a photo look worse. It does not restore pixels that a black box replaced, and it does not bring back the original screenshot unless you attached the original. The failure to watch is the file you selected, not the codec.
Is a private channel safe for the original?
Treat it as a copy you no longer control. People forward threads, exports get archived, and a “quick look” screenshot of the original becomes the new leak. Send the redacted PNG only.
Where should you go next?
Apply the cover in the same local editor this guide describes. Paste a screenshot on the homepage, or open a related note if the leak is a different kind. These links are the next step. They are not separate tools that upload the file.