Free · No Signup

How to Verify a Photo Was Actually Redacted — Not Just Previewed

A cover that looks solid in the editor can still fail. The test is the file you will send: zoomed pixels, contrast on the region, and a re-opened download — not the live canvas before you save.

🔒 No upload · Runs in your browser · Instant download

Redaction fails quietly. A box that looked complete at 40% zoom still shows a digit at 200%. A “blur” slider that looked muddy in a dark UI still reads under a brightness curve. A canvas that looks finished is not the same object as the PNG in your Downloads folder — and the PNG in Downloads is not the same object as a copy still sitting in clipboard history or a browser cache of the original you dropped. Verification is a sequence of checks on the bytes you will actually send, not a vibe from the editor.

HideShot bakes Black Box, Blur, or Pixelate into a downloaded PNG in this tab. Use that download as the subject of the tests below. If you are still choosing a cover method, start with the comparison of blur, mosaic, and opaque fill. If you need a general redaction pass, redact an image online free is the tool walkthrough. This page is the after-pass: how to know the cover is in the pixels.

Mode
Shape

Drop the image you think is already redacted

Or click to browse · Paste with Ctrl+V also works

PNG · JPG · WebP · GIF
How It Works
1

Open

Drop your image in or paste from clipboard.

2

Pick Mode

Black Box, Blur, or Pixelate.

3

Select Areas

Rectangle, oval, or freehand lasso — then hide what you selected.

4

Download

Hit Download PNG. Done.

SquooshNeed to shrink your image after editing? Squoosh is a free browser-based image compressor with no upload required.

Visit Squoosh →
Guide

Treat yourself as a mildly motivated stranger with a free image editor. That person will pinch-zoom, crank contrast, and try to read the edge of your box. They will not respect your preview. They will open whatever file you attached. Your job is to open that same file first, at a larger size than comfort, and fail the read before they get a chance to succeed.

A posting-oriented habit page is censor a photo before posting. A general cover session is redact an image online free. Neither replaces a verification pass. Stay here for the checks that catch incomplete coverage, export mix-ups, and leftover originals in caches.

Zoom past 100% and walk the perimeter

Open the downloaded file in any viewer that can zoom — Photos, Preview, a browser tab, an editor. Go past 100%. 150–200% is enough for most phone JPEGs and screenshots. You are not looking at composition. You are looking for readable residue: a stroke of a digit, a plate character, an eye, a window of a house number. Walk the edge of every covered region. Most failures are a box that is a few pixels short, a lasso that cut a jawline, or a blur that fades into readable type at the boundary.

If the region is text, look at the corners of each character cell. If it is a face, look at hairline and ear, not only the nose. If it is a barcode or QR code, look at the finder patterns; a partial code can still scan. If you can describe the hidden content in words after this zoom, the cover failed. Enlarge the region in HideShot and download again. Repeat the zoom on the new file. Do not “remember” that the last export was fine.

Stretch contrast and brightness on the covered region

Incomplete blur and thin marker-style covers often survive a glance and fail a histogram stretch. Duplicate the export (never the only copy). In any editor, raise contrast, lower or raise brightness, and try a simple sharpen. You are not trying to make a pretty picture. You are trying to see whether the hidden region still has structure. High-contrast originals — screenshots of accounts, photographed documents, license plates — are the ones this check exists for. A solid opaque fill should remain a flat plate of one color. If a ghost of a letter appears, the fill did not cover, or you are not looking at the file you think you are.

This check is adversarial, not decorative. If a light blur “comes back” under contrast, that blur was never a redaction. Switch to a heavier mosaic or a black box. The comparison of those modes is a separate page; the point here is that verification includes an unfriendly view of the region, not only the view you liked in the tool.

Re-open the saved file — do not trust the live preview

The canvas in the tab is a working surface. Layers, undo stacks, and display color management can show a cover that is not yet in a file. Download. Close the tab or at least hide the canvas. Open the file from disk by its name. Confirm dimensions: if a tool silently exported a tiny preview (a 200-pixel-wide thumbnail) you may have a useless small redaction and a full-size original still sitting next to it. Confirm format: you wanted a PNG with the cover flattened; if the share sheet still offers the original HEIC or JPEG, you are about to send the wrong object.

If you edited in more than one app, confirm which file is which with timestamps and byte size, not thumbnails. Thumbnails of a black-boxed image and the original can look similar at 32 pixels. Name the verified export clearly (share-redacted.png) and move it into a folder that does not also contain the camera-roll original.

Caches, clipboards, and “the same photo” that is not

Browsers cache originals you dropped onto a page. Clipboard history on Windows and some phones keeps recent copies. iOS Photos may still surface the unmarked original in Recents while the redacted PNG sits in Files. Email and chat composers often prefer the last image you copied, not the last file you verified. After a successful zoom-and-contrast pass, attach by browsing to the named export. Do not paste “the photo” from memory of having just redacted it.

A silent downgrade is a related trap: some share paths re-encode a small JPEG for “quality” while a cloud album still holds the full original. The small JPEG might be redacted; the album original might not. Verification is per copy. The copy you send is the one you opened and zoomed. Other copies are out of scope until you treat them as new jobs.

How to run the check with HideShot on this page

  1. If the cover is not done yet, drop the source image, mark regions, and download a PNG.
  2. Open that PNG from disk. Zoom past 100%. Walk every edge.
  3. On a duplicate of the PNG, stretch contrast on the covered area. A flat black (or a coarse mosaic with no readable feature) should hold. Ghosted text means you go back to the canvas with a larger region or a stronger mode.
  4. Confirm width and height are the image you intended to share, not a thumbnail.
  5. Attach only that named file. Leave originals out of the folder you pick from.

These checks confirm pixels. They do not confirm that GPS was stripped. A redacted PNG can still carry tags if the export path copied headers — or you may still have the tagged original beside it. Inspect metadata separately if location or device tags matter.

False all-clears

The canvas looked covered, so you posted from Recents. Recents was the original. Open the download by name.

You zoomed the live editor but never opened the file. Export can differ. Re-open disk.

You checked one region and skipped the reflection in a window or a second card in the same frame. Walk the whole image at 100%.

You verified a small compressed copy and emailed a larger original “for quality.” The larger file is the one an adversary will use. Verify that one, or do not send it.

Verify the File You Will Send, Not the Editor Preview

Zoom the downloaded image past 100% and inspect the edges of every covered region. Then stretch contrast on a copy of that same file. A real opaque fill stays flat. A weak blur often gives the text back.

Close the working canvas and open the PNG from disk. Check that you are not about to attach a thumbnail, a clipboard original, or a camera-roll duplicate. HideShot bakes the cover into a local download; the checks are yours.

Pixel verification is not a metadata check. If GPS still matters, inspect tags on the copy you will send, as a separate step.

Frequently asked questions

Why isn’t the on-screen preview enough?

Editors show a working buffer. Layers, masks, and “privacy filters” can look burned in while the file on disk still has the original region, or while export still writes a different raster than you are staring at. Verification means closing that session and opening the downloaded PNG or JPEG as a new file.

What does zooming past 100% catch that a normal view misses?

Small leaks: a serif outside the box, a plate character in a one-pixel gap, anti-aliased edges, or a faint digit that only appears when you stretch contrast. Phone-sized previews average those failures into “looks covered.”

Could a browser cache or clipboard still hold the original?

Yes. The redacted download and the original you dropped are different objects. Recents, Downloads, clipboard history, and back-forward cache can still offer the unmarked file when you go to attach something. Attach by filename from a folder that only contains the verified export.

Does HideShot send the photo out so a server can “confirm” redaction?

No. You inspect pixels on your device. HideShot never receives the image. The checks on this page are things you do to the file in hand.