How journalists cover a source in a screenshot
Names, numbers, and map pins in a reporting screenshot. Black bars beat a light blur.
A source in a screenshot is a byline you did not mean to publish: WhatsApp name, map pin, unique turn of phrase in a quoted reply.
Newsroom CMS tools love a chat capture. So do lawyers and people who reverse-search a crop. Black bars. Not highlighter. Not a finger over the laptop camera in a photo of the photo. If the CMS recompresses, start from PNG and check the live page, including social cards.
Cover display names, numbers, avatars that are recognizable, location sharing, email headers, and any ID or workplace badge that appeared because someone proved they were real. Cover the journalist’s own internal notes if those notes name the source. The story can quote the claim. The pixels should not double as a directory.
Chat apps are identity machines
Headers repeat the number. Quoted replies repeat it. Status text and a group title can identify a beat or a city. Bar the chrome, then read the remaining bubble: is that sentence unique enough to search? If yes, paraphrase in text instead of publishing the bubble.
Disappearing messages do not save you after a screenshot. The PNG is the archive. Treat it as a document you will have to defend. If you only need to show that a threat arrived, keep the timestamp and the threatening sentence, not the profile.
Documents, cafés, and metadata
Photographing a printout in a neighborhood café can GPS the café. A photo of a screen is a photo: location, device, reflection. Prefer a digital capture, then bars, then a clean PNG. Do not upload the raw camera roll to a random “background remover” on deadline.
Maps in the chat are addresses. Live location is an address with a clock. Cover the pin, the street labels, and the building number even if you already cropped the map. A sliver of a street name plus a distinctive storefront in the same frame is enough.
What to bar on a source screenshot
- Names, handles, phone numbers, and emails
- Avatars, workplace IDs, uniforms with names
- Home or office addresses, map pins, license plates
- Salary, contract, or ID numbers in a leaked HR or billing shot
- Other participants in a group who did not agree to be named
- Your own notes, assignment slugs, and CMS user chips
Government IDs and pay stubs show up when a source proves employment. You may need to verify. You do not need to publish the ID. Bar the number, the address, and the photo. Describe the document in prose if the public needs to know that a document existed.
Should the unbarred original live in the CMS?
No. The CMS is where interns, stringers, and syndication partners wander. Keep verification files in the newsroom’s restricted store. The asset that goes to production is the barred PNG. Check previews, because a crop tool in the CMS can reveal a bar you placed too close to the edge after an automatic resize.
FAQ: the source said I could show the chat
Consent to “show we talked” is not consent to publish their number, their kids in the wallpaper, or the group members. Re-bar for the public version. If they want to go on the record, use a name they chose, in text, not a WhatsApp header.
FAQ: can I blur instead of a bar so the layout still looks like a phone?
Layout is not a source-protection method. Blur on digits and names fails after social networks recompress. Use black rectangles. Keep enough chrome that readers understand it is a chat. Check the published JPEG. If glyphs ghost through, enlarge the bars.
FAQ: what about a screenshot of a public official’s post?
Public posts can still include other people’s replies, tagged photos, and a private account you quoted via a forwarded capture. Bar the bystanders. The official’s public handle can stay. Do not launder a private group into “public” by screenshotting it.
Location in files: EXIF and GPS. Message headers and quoted numbers: WhatsApp captures. On deadline, bar the source locally so the image never hits a random upload site before it hits the CMS.