Crypto wallet and exchange screenshots travel into places phone banking screenshots also go — support forms, Twitter/X bug threads, Discord server help channels, Telegram groups — with a sharper downside. A readable balance advertises holdings. A full receive address plus a public post can be scraped. A QR code in the corner encodes the same address. Token lists reveal tickers and sizes. None of that is required for “the swap button spun forever” or “KYC upload failed,” yet the default screenshot includes the home portfolio tile.
That is distinct from Venmo or Cash App redaction and from a traditional banking-app balance hide, even though the tool actions look similar. You are marking an exchange or self-custody wallet UI. HideShot works on the screenshot: black out balances, addresses, and QRs you do not intend to publish, leave the error state or transaction row you need visible, and download a PNG. Processing stays in this tab. Share the marked file, not the raw capture.
Guide
Wallet home screens are designed to show wealth at a glance: total portfolio in fiat, per-asset balances, 24-hour change, and a primary receive address or ENS-style name. Exchange apps add margin equity, open orders, and sometimes P&L for the day. When support asks for a screenshot, people capture the whole home view because it is already open. That habit publishes numbers that phishing channels screenshot and quote back to you later as fake “verification.”
Peer payment redaction is a cousin, not a twin. If the app is Venmo or Cash App, use blur a Venmo or Cash App screenshot instead. If the app is a bank or credit-union mobile app with routing and ledger balances, hide account balance in a banking app screenshot matches that chrome. Stay on this page for Coinbase, Binance-style exchange apps, MetaMask-style extension screenshots saved as images, hardware-wallet companion apps, and similar crypto portfolio UIs.
What to cover on a crypto wallet or exchange screenshot
Balances first: total equity, per-token amounts, fiat conversion lines, staking totals, and hidden-balance eye-toggle states that still leave numbers in another corner. Cover both crypto units and USD/EUR equivalents.
Addresses next: full receive addresses, truncated addresses that still show enough characters to match a known wallet, ENS or similar names that resolve to you, and QR codes that encode a receive URI. A QR left sharp undoes address coverage.
Seed phrases, private keys, and backup prompts: cover every word and every QR that encodes backup data. Prefer deleting the screenshot and starting over without the seed on screen. Support will never need your seed.
Also review: email or phone in the profile header, government ID images stuck in a KYC “retry” pane, API key fragments, withdrawal allow-list addresses, and chat panes that quote prior balances.
What you can often leave visible
Error banners, spinning buttons, transaction status labels (pending, failed), a single tx hash if support asked for it, network name (e.g. which chain), and anonymized UI chrome that shows the bug. If support asked for a partial address, leave only the characters they specified and cover the rest. When in doubt, cover more; they can ask again.
How to blur balances and addresses in the tool above
- Open the wallet or exchange screen that shows the problem. Hide balances in-app first if the app has an eye toggle — then screenshot. If the bug only appears with balances visible, screenshot once and plan to black-box totals here. HideShot edits the image, not the live wallet.
- Drop the PNG or JPEG on this page or paste with Ctrl+V / Cmd+V. Prefer Black Box for amounts, addresses, and QRs. Light blur on monospace addresses often leaves characters readable.
- Walk the screen: header equity, token list, chart tooltips that show values on hover-capture, receive tab QRs, and any notification shade that mirrored a deposit amount.
- If you attach multiple shots (home, activity, error), mark each one. A covered balance on the home tile can reappear in the activity row.
- Download the PNG. Zoom to 100%. If any digit of a balance or character of an address remains readable, enlarge the box. Upload or paste only that marked file into support or social. Keep the unmarked original offline if you need it for your own records.
Scenarios where a wallet screenshot overshares
A Discord “support” thread asking you to paste a MetaMask home screenshot. Real support channels rarely need full equity. Cover balances and the receive address; leave the error text. Treat cold DMs asking for screenshots as hostile until proven otherwise.
A Twitter/X bug report with your exchange portfolio tile still visible. Public posts are scraped. Cover totals and addresses. Describe holdings in words only if needed (“two-digit USD equity”), not with exact figures.
A Telegram group helping with a failed withdrawal. They may need a tx hash and destination truncation. They do not need your spot account balance. Cover equity and unrelated token rows.
A screenshot that also shows a seed backup modal behind the error toast. Stop. Black-box the entire seed region or discard the file and recapture without the modal.
Comparing this to a Venmo payment dispute screenshot. Different apps, different fields. Do not reuse a peer-payment habit of leaving dollar amounts visible “for context” on a crypto portfolio tile.
Common mistakes with crypto wallet screenshots
Covering the big portfolio total and leaving every token row sharp. Row amounts still sum to a doxxed portfolio. Cover the list.
Blurring an address but leaving the QR sharp. The QR is the address.
Assuming a truncated address is safe on a public post. Short prefixes plus your username often deanonymize active wallets. Cover unless support specified the format.
Sending an unmarked screenshot to a wallet-connect dapp “help desk” in chat. Phishing desks collect balances and then role-play urgency. Mark first, or refuse.
Keeping a camera-roll album of unmarked wallet homes. Phone backups sync. Delete unmarked captures after you save the marked PNG you actually need.