Redacting a Screenshot When Monitoring Software Already Captured It

Every other page on this site starts from the same assumption: the screenshot you just opened in this editor is the only copy of that moment that exists. Cover what's sensitive, download, and the exposure through this particular image is closed. On a device that runs its own monitoring software, that assumption can be false before you've clicked anything. Time-tracking tools, remote-support software, and session-recording agents can capture the same screen on their own schedule, for reasons that have nothing to do with whether you ever open a redaction tool.

This isn't the live screen-share case covered elsewhere on this site, where a remote audience watches your screen during a call you joined on purpose. It's a background process that can run continuously, independent of any meeting, often without a visible indicator, and frequently without your explicit moment-by-moment consent, because the consent was given once, in an employment agreement or a device policy, long before this particular screenshot existed.

The practical consequence is a change to when the exposure happens, not how. If a monitoring tool already captured the frame while the sensitive value was on screen, covering that value in this tab afterward edits a copy that exists only here. It does not reach, delete, or redact whatever the other software already saved.

Drop your image here

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

PNG · JPG · WebP · GIF

How It Works

Open

Drop your image in or paste from clipboard.

Pick Mode

Black Box, Blur, or Pixelate.

Select Areas

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

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

One sentence carries this page: redacting a file only ever changes the copy you are holding, and on a device with monitoring software running, that may not be the only copy of the moment that exists.

A copy of the screen you don't control

Every page on this site, including the one about live screen-sharing, assumes you can enumerate where a screenshot's pixels go: this tab, a download, maybe a chat window you pasted into. A monitored device adds a channel that doesn't appear in that list at all, because it isn't started by you and doesn't ask. It also isn't the live-sharing case. Screen-sharing on a call needs you to join a meeting and, usually, click share; a monitoring agent installed on a device can run for the length of a shift, a day, or indefinitely, entirely separate from any call, any browser tab, or any action you take in this editor.

What this software actually does

The category is broad and well documented in its own industry: time-tracking and productivity-monitoring tools that take desktop screenshots on a timer, commonly every few minutes, with some products offering burst intervals as short as thirty to ninety seconds; remote-support and IT helpdesk tools that can record a session continuously for as long as a technician is connected; and call-center or compliance tools that record the screen for the duration of a call. Some of these tools apply their own redaction, such as excluding specific applications or blurring known-sensitive fields; many do not, and simply store whatever was visible. Exactly which of these, if any, runs on a given device is a function of that device's employer, IT department, or owner's choices, and not something a general page can tell you.

Why this breaks the usual order of operations

Every workflow on this site runs in the same order: something sensitive appears on screen, you capture it, you redact the capture, you send or publish the result. Monitoring software collapses the gap between the first two steps. If it's active, the capture already happened at the moment the value was on screen, in parallel with whatever you did next, including opening this editor. Redacting afterward still protects whoever receives your exported file. It does nothing about a parallel capture that already exists somewhere else, because that capture was never waiting for you to finish.

What this editor can and cannot reach

It's worth being precise about this tool's own boundaries, verified directly from its code rather than assumed. The editor has no fetch, XMLHttpRequest, WebSocket, or screen-capture call anywhere in it; it cannot take a screenshot of anything, cannot see any other window or process, and cannot detect whether monitoring software is running on the same device. It only ever has the one file you deliberately load, drop, or paste in, and loading a new one resets the undo history for the previous image immediately, with no prompt. That narrowness is also the honest answer to what it cannot do here: it has no way to know about, let alone reach, a capture made by a separate piece of software a few minutes earlier.

Finding out whether it applies to you

There's no reliable client-side test for this, and that's consistent with the previous section rather than a gap specific to this page: a tool that runs in a browser tab has no visibility into other processes on the machine, by design. The practical path is to ask rather than to detect. Read your employer's device-use, monitoring, or acceptable-use policy; check onboarding materials; or ask IT or HR directly whether screen-capture, session-recording, or activity-monitoring software is installed, and what it captures and keeps. On a personal device, the same question applies to parental-control software, remote-support tools you may have installed for a one-time fix and forgotten about, and security suites that bundle an activity-log or screen-recording feature. Don't try to detect or disable anything on a device you don't own outright; if the answer is unclear, treat the uncertainty itself as the answer and change what you do rather than what the software does.

What changes about your workflow

The useful response is to shrink the window during which something sensitive is visible at all, rather than to rely on cleaning up the exported file afterward. Bring the sensitive document or field to the foreground only for as long as you need it, close or minimize it immediately, and avoid leaving it open while you go do something else; several of these tools capture whatever is in the active window or across the whole desktop, so duration on screen, not just presence in a screenshot, is what counts. For anything genuinely personal rather than work-related, such as a medical letter, a bank statement, or a family photo, the more reliable move is to handle it on a device you're confident isn't monitored, rather than to redact it carefully on one that might be. None of this is a reason to skip redacting the file you do export: whoever receives that file still only ever sees what you chose to leave visible. It's a reason not to treat that export as the only copy that matters.

What this editor does and does not do here

No screen-capture ability of its own. There is no call to any capture, recording, or device-media API anywhere in the editor; it can only process a file you hand it directly, by dropping, choosing, or pasting it in.

One file at a time. Loading a new image resets the undo history immediately, with no prompt, so download the finished PNG before moving to the next capture.

Regions only. Three modes, Black Box, Blur and Pixelate, across three shapes, with no text detection, no find-all, and no whole-image operation of any kind.

No crop, resize, or rotate. The canvas is created at the source image's exact pixel dimensions and nothing alters them.

Nothing leaves the browser. There is no fetch, XMLHttpRequest, or WebSocket call anywhere in the editor, and no browser storage of any kind; the image lives only in this tab.

Your clipboard still holds the original. If you pasted the capture in with Ctrl+V, there is no clipboard-write code in the editor, so pasting again anywhere else sends the unredacted image.

Common mistakes and misconceptions

"Redacting the file I downloaded means the exposure is fixed." It means the exposure through that file is fixed. A separate capture made by different software earlier in the session is a separate question with a separate answer.

"This is the same as the screen-sharing problem." Screen-sharing involves a remote audience watching a session you joined on purpose. Monitoring software can run continuously, attached to no particular call, without the moment-by-moment awareness a shared screen usually carries.

"If I can't see an indicator, nothing is capturing my screen." Many of these tools are designed to run without a visible indicator. Absence of a visible sign is not evidence of absence.

"This tool should be able to tell me if monitoring software is active." It can't, and that's the same boundary that keeps it from uploading anything of yours anywhere: a browser tab has no visibility into other processes on the device.

The Leak That Happens Before You Open This Tab

Redacting a screenshot in a browser tab only ever changes the one file you chose to open. On a device running time-tracking, remote-support, or session-recording software, that file may not be the only record of the moment it shows. These tools commonly take their own screenshots on a timer, independent of anything you do, which means the exposure can already be finished before you ever reach for a redaction tool.

This is a different problem from live screen-sharing, where a remote audience watches a call you joined on purpose. Monitoring software can run continuously, attached to no particular meeting, often with no visible indicator, under a consent that was given once, in a policy document, long before this screenshot existed.

There is no way to detect this from inside a browser tab, and that is a boundary this editor shares with every other client-side tool: it can only ever see the file you hand it. The practical response is to ask rather than to guess, and to shrink how long sensitive material sits on screen rather than to rely solely on cleaning up the exported file afterward.

Frequently asked questions

Can monitoring software see what I'm redacting before I cover it?

Yes, if it's running and configured to capture the screen, it can see the frame exactly as it appeared on your display at whatever moment it happened to take its own screenshot, which has nothing to do with whether you have a redaction tool open in a browser tab at the same time. Time-tracking and productivity-monitoring tools commonly take screenshots on a timer, anywhere from every few minutes to, in some products' burst modes, every thirty to ninety seconds; remote-support and helpdesk tools can record a session continuously while a technician is connected; call-center and compliance tools can record the screen for the length of a call. None of that activity is visible from inside a browser tab, and none of it asks your permission in the moment. If the capture already happened, it happened before you touched this editor, and nothing you do here reaches it.

If I redact the screenshot and then close the tab, is the original gone?

From this tab, yes, closing it discards the loaded image, the undo history and anything still in memory, because the editor keeps no persistent storage of any kind. But that only describes this one copy. If monitoring software had already captured the same screen earlier in the session, that capture is a separate file, usually sent somewhere you don't control, such as a management dashboard, a log server, or a support ticketing system, and closing your browser tab does nothing to it. The two copies don't know about each other.

How do I know if my device has this kind of software running?

Not reliably from inside the browser. A client-side tool like this one has no way to see other processes on your machine, and that's by design, not a gap specific to this page. The honest path is to ask: read your employer's device-use or monitoring policy, check onboarding materials, or ask IT or HR directly whether screen capture, session recording, or activity-monitoring software is installed and what it captures. Don't try to detect or disable it yourself on a device you don't own; if its presence or scope is unclear, treat that uncertainty as the answer and change what you do, not the software.

What should I actually do differently if I think I'm on a monitored device?

Shrink the window during which sensitive material is visible on screen at all, rather than relying on cleaning up the exported file afterward. Keep the sensitive document or field in the foreground only as long as you need it, close or minimize it right after, and avoid leaving it open while you do something else. For anything that is personal rather than work-related, such as a medical letter, a family photo, or your own banking, handle it on a personal device you're confident isn't monitored instead of on the managed one. Redacting the screenshot you choose to export is still worth doing for whoever receives that file; it just isn't a defense against a capture that may already have happened upstream of it.