Quick answer: when a screenshot leaks data, it's rarely the thing you meant to show. It's the tab titles, the address bar, a notification that popped up at the wrong moment, the signed-in account in the corner, a sidebar full of other customers, or something further down a full-page capture. Capture only the page area you need, crop to the problem, blur what's left, and do a 10-second scan of the edges before you send.
Most people check the middle of a screenshot, the part that explains the bug or answers the question. The leaks live at the edges. Here are the six places to look, why each one leaks, and the fastest way to deal with it.
1. Tab titles and the bookmarks bar
What leaks: browser tabs show page titles, and titles are often specific: "Invoice #4821 – Maria Hernández", "Inbox (214) – [email protected]", "Layoffs plan Q3 – Google Docs". The bookmarks bar adds internal tools, client names and projects you'd rather not advertise.
Why it happens: full-screen and window screenshots from the operating system, such as Print Screen, Win+Shift+S in window mode or Cmd+Shift+4 then Space on Mac, include the whole browser window, not just the page.
How to fix it:
- Capture the page instead of the window. Browser extensions that capture the visible tab, and Chrome's own DevTools screenshot, include only the page content, not the tab strip or the toolbar.
- If you need the whole window, open what you're showing in a new window with only that tab.
- Hide the bookmarks bar for a moment with Ctrl+Shift+B (Cmd+Shift+B on Mac).
2. The address bar
What leaks: URLs carry more than you'd think: customer and order IDs, email addresses in query strings, search terms, internal hostnames like admin.internal.company.com, and sometimes one-time tokens in password-reset or magic-link URLs.
Why it happens: the same as tab titles. Window and full-screen captures include the address bar.
How to fix it:
- Capture the page area only.
- If the URL is part of the bug report, paste it as text after removing personal values, rather than showing it in the image.
- Never screenshot a page whose address contains a reset link, sign-in link or session token. Those links can work for whoever sees them.
3. Notifications and pop-ups
What leaks: a chat message preview, an email subject line, a calendar invite with a client's name, or a two-factor code, appearing in the corner at exactly the moment you capture.
Why it happens: operating system notifications sit on top of every window, so full-screen captures pick them up. In-app toasts inside web apps, like "New message from…", are part of the page and appear in page captures too.
How to fix it:
- Turn on Do not disturb on Windows or a Focus mode on Mac before a screen-sharing or screenshot session.
- Wait for in-page toasts to disappear, or close them, before capturing.
- Crop to the area you need. Notifications usually sit at the edges.
4. The signed-in account
What leaks: your own name, email and avatar in the corner of every web app, and sometimes your role ("Admin") or your organization's name. When an agent captures a customer's view through an impersonation or "view as" feature, the customer's identity shows instead.
Why it happens: the account menu is in the header of nearly every app, right where a full-width capture includes it.
How to fix it:
- Crop out the header if it doesn't help explain the issue.
- Blur names and emails in the account menu when the header is needed for context.
- For help articles and training material, capture from a demo account with made-up details.
5. Sidebars, lists and dropdowns
What leaks: this is the classic support leak. The screenshot shows one customer's issue, while the sidebar shows the last 20 tickets with names and emails. Other places that hide personal data: recent conversation lists, contact panels, search history, notification feeds, and autocomplete dropdowns that open while you type.
Why it happens: these panels sit next to the content you're capturing, and a wide capture includes them without anyone noticing.
How to fix it:
- Crop to the main content area.
- Collapse sidebars before capturing if the app allows it.
- Close any open dropdown or autocomplete list.
- Blur any list of people that remains. A single drag over the whole list is enough.
6. Below the fold in full-page captures
What leaks: a full-page screenshot includes everything you didn't scroll to: a comments section with names, an activity log, a table of other customers, a footer with internal links, or a debug panel left open at the bottom.
Why it happens: you check the part of the page you were looking at, but a full page screenshot captures all of it.
How to fix it:
- Use a visible-area capture when the issue fits on one screen.
- Scroll through a full-page capture from top to bottom before you share it, not just the first screen.
- Collapse expandable sections that you don't need.
Bonus: the file itself
Two more things travel with a screenshot:
- The file name. invoice-maria-hernandez.png tells a story before anyone opens it. Rename files, or copy the image to the clipboard and paste it instead of attaching a file.
- Hidden layers. A box drawn in a document, PDF or slide editor can often be moved away to reveal what's underneath. Share a flattened image, and see why some redaction methods can be reversed.
The 10-second check before you send
Scan in this order, because it follows where leaks usually are:
1. Top edge: tabs, address bar, header and account menu.
2. Left and right edges: sidebars, lists and panels.
3. Corners: notifications and toasts.
4. Bottom edge: footers, comments, activity logs and anything below the fold.
5. The middle: the part you meant to share, now with names, emails, numbers and tokens blurred.
If something in the image doesn't help the reader understand the issue, crop it.
Fixes at a glance
Make it a team habit
One careful person doesn't protect a team. A few habits do:
- Agree on what always gets blurred: names, emails, phone numbers, account and order numbers, card data, tokens and internal URLs.
- Use a capture tool that crops and blurs in one place, so hiding data takes a drag, not a second app.
- Prefer page captures over full-screen captures in shared channels.
- Make it part of onboarding, especially for support, QA and sales teams who share screenshots all day. If those screenshots go into tickets, read our guide to screenshots, PII and GDPR in support tickets.
Screshot captures the page area only, never your tab strip or address bar, and lets you drag to crop and blur in the same editor before you copy. Everything happens on your device, and nothing is uploaded.
FAQ
Do browser extension screenshots include the address bar?
No. Extensions capture the visible part of the page itself, not the browser's tabs, address bar or bookmarks bar. Operating system tools that capture a window or the full screen do include them.
What's the safest way to share a screenshot with personal data?
Crop to the smallest area that explains the issue, blur anything identifying that remains, and share it only with people who need it. If you can reproduce the issue with demo data, use that instead.
Is blurring enough, or should I crop?
Crop first, because whatever is outside the image can't leak. Then blur what you need to keep for context. Use a strong blur over the whole value, not light pixelation.
How do I stop notifications from appearing in screenshots?
Turn on Do not disturb on Windows or a Focus mode on Mac before you start capturing, and capture the page area instead of the full screen.
Can a screenshot reveal data I can't see?
It can contain more than you noticed: content below the fold in a full-page capture, or text under a shape in an editable file. Scroll through full-page captures and share flattened images.
Sources
Written by
Screshot TeamProduct & security team
The team that builds Screshot, the private screenshot tool for Chrome. We write about keeping customer data out of screenshots, rolling out tools across a company, and getting work done faster with your screen.
Keep customer data out of your screenshots
Screshot captures a screen or a full page, blurs sensitive details and annotates, all on your device. Free for every team.
