Drop your image here
Or click to browse · Paste with Ctrl+V also works
Cover account and routing numbers in banking app captures before sending to accountants or support.
Or click to browse · Paste with Ctrl+V also works
Drop your image in or paste from clipboard.
Black Box, Blur, or Pixelate.
Rectangle, oval, or freehand lasso — then hide what you selected.
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 →Hiding bank account numbers means making them invisible in the version you share, even when the original photo or screenshot still exists on your device. On this page you'll hide a bank account number that typically appears in a direct-deposit setup page sent to HR or a direct-deposit setup page sent to HR. The fields that need attention usually include the account number printed under the routing number on a voided check and the account number printed under the routing number on a voided check — and any nearby context that helps a reader reconstruct them. Getting this right matters because exposed account numbers feed into 'credential stuffing' lists used against banking apps that allow account-number login.
People who reach this page are usually in one of three positions. The first is contractors confirming receipt of payment in a client thread. The second is new employees sending voided check screenshots to payroll. The third is new employees sending voided check screenshots to payroll. In all three, the screenshot or photo isn't the point — the work that needs to happen around it is — and hiding a bank account number cleanly is the unblocking step between 'I shouldn't share this yet' and 'okay, sending'. HideShot is built specifically for that gap: drag, mark, download, get on with the rest of your day.
The first job is to inventory what's actually visible. For a bank account number, the high-priority fields are the MICR-line account string on a check stub, the full digit string (often 10-12 digits), and the full digit string (often 10-12 digits). Less obvious but equally important is check numbers in the same MICR strip (they help identify the bank's check format) — it's the one most people forget on the first pass, and it tends to be the field that re-identifies everything you carefully covered above. Walk down the image once with a checklist mindset, marking each instance you find. Account numbers usually sit beside the bank's logo, your full name, and a transaction list — sweep all four with the same selection pass so the page can't be reassembled by cross-referencing identifying details.
The reason this matters is concrete. exposed account numbers feed into 'credential stuffing' lists used against banking apps that allow account-number login. That pattern is documented in fraud and harassment cases — not hypothetical. The two-minute redaction step you take before sharing is the single highest-leverage privacy move available for this kind of content.
HideShot handles a bank account number entirely inside your browser. The image is loaded from your device into a local canvas; the redaction tools draw on that canvas; the exported PNG is generated by your browser's own rendering code. Nothing about the source file is transmitted to any HideShot server, because there isn't one in the path — the page is static, the JavaScript runs locally, and the only network traffic during the redaction itself is the page load that happened before you uploaded anything. For hide account number screenshot, that means the original never leaves your machine, the redacted version is generated locally, and you can use the tool with Wi-Fi turned off if you want to prove it to yourself.
Trusting the bank's auto-mask in the screenshot when the full number was visible for a fraction of a second. Many online banking pages show the full account number briefly when you click 'reveal'. Screen-record auto-saves and screenshot apps with delayed capture can grab that frame. Inspect the entire image at 200% before publishing — and cover anything that ever flashed up, not just what is currently visible.
Sharing a screenshot in a screenshot — the inner image still contains the unredacted original. People paste a banking screenshot into a doc, then screenshot the doc to share. The inner pixels are still there at full resolution. Flatten and re-redact at the outer layer, not just the doc layer.
For hide account number screenshot, the three options behave differently. Blur is fast and visually soft, but at small radii the original shape of bank account numbers survives well enough for OCR or human reconstruction at 2x zoom. Pixelation breaks bank account numbers into colored blocks — at 12-16 pixel block size it defeats both human reading and modern depixelation models, and it's the right choice when you want visible 'something was here' without revealing the data. Black-out (solid opaque block) is the strongest option: there is no signal under the block to reconstruct, and reviewers immediately understand the field was intentionally hidden. Hiding bank account numbers with a solid block is the most reliable choice. Blur reads as softer but allows reconstruction at low radii.
To hide account number screenshot fields responsibly, redact both the account line and routing number if shown. Some apps stack them vertically — one rectangle may cover both. Verify with zoom before download.
Always prefer Black Box for financial identifiers. Blur can leave digit outlines under contrast enhancement. HideShot also lets you obscure IBAN blocks and reference numbers in separate passes.
Paste mobile banking screenshots directly from clipboard, apply redaction, export PNG for email. Undo supports tight adjustments around monospace digit columns.
Use Black Box for account and routing numbers. It provides stronger concealment than blur.
Yes. Draw separate regions for each account block before downloading.
No. HideShot runs locally in your browser.
Yes. Screenshot the PDF or export a page image, then upload or paste into HideShot.