Can I crop away extra context instead of masking it?
Yes. Crop remains available here, which is often the cleanest way to remove surrounding screen context all at once.
Do I need to install anything?
No. The screenshot editor runs in the browser, so the workflow starts with upload and ends with a local export.
Will the exported file still include hidden metadata?
Common source metadata is stripped because the result is regenerated through a fresh browser canvas before download.
What is the safest way to hide information in a screenshot?
Crop it out of the frame. If it must stay in frame, cover it with an opaque black or white box. Both survive scrutiny because the export is a new flattened image. Blur and pixelate do not.
Is cropping really safer than masking?
Yes, because the pixels are never written into the exported file. A box replaces the pixels, which is also safe here, but crop removes the entire question by removing the region.
What do people most often forget to redact?
The chrome around the content: the browser tab, the URL, the window title, a notification banner, an autocomplete dropdown, the account name in a sidebar. The field they meant to hide gets covered; the one next to it does not.
I already shared a screenshot with an API key visible. Is redacting a new copy enough?
No. Once a key has been seen, it is compromised. Redact the image, and then rotate the key. A redaction fixes the file, not the leak.
Does the exported file carry the original metadata?
No. Re-encoding from a canvas produces a file with no EXIF, so any device or timestamp data the original carried is gone.