Redact & Blur Screenshot Online

Redact and blur a screenshot online, free and private, in your browser. We don't upload your images. Hide passwords, emails, names, and chats.

Same local editor as the homepage. This page is a deep link for one job, not a separate upload service.

FreePrivateNo upload
Stays in this browserNo upload

Blur

Softer cover. Raise the strength until text is unreadable.

Pixelate

Mosaic blocks for faces and photos. Larger blocks hide more.

Black Box

Solid cover for names, IDs, and anything that must not be readable.

This job

What to redact in a screenshot before you share it

Cover passwords, emails, names, and other people’s chats before a bug report, a Slack paste, or an email. The edit is free, it stays in this browser, and the screenshot is not uploaded. Then export a PNG and send that file.

Passwords, API tokens, and one-time codes need a black box, not a light blur. Letter shapes can survive a soft blur, and short secrets are easy to guess. Draw the box a little larger than the text so a character does not stick out at the edge.

Emails and real names show up in more places than the message body: the To line, a profile menu, a tab title, a CRM card, and the sender of a notification. A chat screenshot also includes the sidebar. Slack, email, and support threads often show other people’s names, avatars, and messages you did not intend to forward.

Bug reports are the same problem with a deadline. The URL, a DevTools header, and a customer id are not the bug. Cover those, leave the broken control visible, and say in the ticket what you removed. The checklist guide is the longer list of details that survive a quick crop.

Passwords and tokens

Black box the password field, the API key, the session id, and any one-time code.

Emails and names

Cover addresses, display names, and the tab or menu that repeats them.

Chats and Slack

Hide the sidebar, other threads, and avatars. Leave only the message you meant to share.

Bug-report extras

Query strings, Authorization headers, and customer ids. Leave the error that explains the bug.

How to redact a screenshot for a bug report

How to use

How do you redact this image locally?

Load the image in this browser, draw over each sensitive region, and export a PNG. The canvas edit does not upload the file. Paste a screenshot with Ctrl+V or Command-V, or drop a JPG, PNG, or WebP. Undo fixes a box without changing the original on your device.

  1. 1

    Open this page and paste the screenshot with Ctrl+V or Command-V, or drop the file from your device. The edit runs in your browser. The image is not uploaded.

  2. 2

    Read the frame before you draw: passwords, emails, names, chat sidebars, URL tokens, and notification banners are the usual leaks.

  3. 3

    Draw a box over each region. Use Black Box for a password, a token, or an email. Use Blur or Pixelate only after you have checked that the text is unreadable.

  4. 4

    Add another box for Slack or email threads you did not mean to include, and for the query string in a bug-report URL. Undo fixes a box without changing the original file.

  5. 5

    Click Export redacted PNG, open that file, and share it. The screenshot on your device stays as it was.

You can also paste a screenshot with Ctrl+V or ⌘V. Undo and Redo fix a box without changing the original file.

Why use this tool

Why does this stay in the browser?

This page is for images that already contain private material. Blur, pixelate, and black box run in your browser, so the file is not sent away to be cleaned. Use a black box for secrets that must not stay readable. Use blur or pixelate only after you have checked that the cover is enough.

Screenshots leak more than the field you meant to show. A password manager popup, an email in the corner, a customer name in a tab, or a Slack sidebar is enough to identify someone. Check those before a support ticket, a chat paste, or a public issue.

Bug reports and email forwards are the common cases. The address bar, DevTools, and the thread above the message are not the bug. Cover them, leave the part that explains the problem, and say in the message what you removed. Do not paste the secret into the comment after you took it out of the image.

This page is the same free editor as the homepage, aimed at screenshots. Blur, pixelate, and black box run in your browser. The image is not uploaded, and you do not create an account. Download the redacted PNG and send that.

Questions

What should you know before you export?

The image is processed locally, and export writes a new PNG. Blur is not the same cover as a black box. Paste works with Ctrl+V or Command-V. If your question is about a specific leak, such as a password, a face, or a sidebar, use the guides linked below before you send the file.

Can I blur a password visible in a screenshot?

Yes. Draw a box over the password field, the API key, or the one-time code. Prefer Black Box. A light blur can leave letter shapes, and short secrets are easy to guess.

How do I hide an email address or a name?

Cover the address and the display name, then check the tab title, the profile menu, and any notification that repeats them. One box on the message body is often not the only place the name appears.

What about a Slack, chat, or email thread in the screenshot?

Hide the sidebar, other people’s messages, avatars, and the subject lines you did not mean to forward. Leave only the part you intended to share. Black box is the safer cover for names and addresses in a thread.

How should I redact a screenshot for a bug report?

Cover the URL query string, Authorization headers, and customer ids. Leave the broken control and the error that explains the bug. Export a PNG and attach that file, not the original screenshot. The bug-report guide walks through the same pass.

Is a redacted blur enough, or should I use a black box?

Blur is a softer cover for context that only needs to be unreadable at a glance. For passwords, tokens, emails, and names, use a black box so the characters are gone from the exported PNG. If you can still read it, it is not done.

Does this upload my screenshot?

No. Pasting, dropping, and drawing all happen in your browser. hideimage.com does not receive the file in order to edit it. You download a new PNG when you are finished.

Is screenshot redaction free?

Yes. The editor is free, with no account. You can paste or drop as many screenshots as you need and export a redacted PNG each time.

Does this work on mobile screenshots and full-page captures?

Yes. Open this page on your phone, choose a screenshot from your gallery, draw over the sensitive parts, and download the result. A full-page capture is just a tall image and works the same way.

Is the original screenshot changed?

No. Export writes a new PNG. The file you pasted or dropped stays on your device. Share the redacted PNG, not the first image the share sheet offers.

Related workflows

Which related tool should you open next?

Every tool on this site is the same local editor with a different starting note. Open a related page when the job is narrower, such as faces, screenshots, or solid black text. You do not upload the image to a second service to switch jobs.

Guides

Which guide matches this job?

Read the guide that matches the mistake you are about to make. Text secrets usually need a black box, not a light blur. Faces, plates, and sidebars need their own pass. Local editing matters most when the file should not be uploaded in order to hide it.

Tool network

Where are the other free tools?

The list below is that same editor under different job names. Pick the name that matches what you need to hide. Processing stays in the browser on every page here, and none of these links is a separate upload form.