A source in a screenshot is a byline you did not mean to publish: a WhatsApp name, a map pin, a 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. This is practical pixel hygiene for a deadline, not legal advice, and not a substitute for counsel, a newsroom lawyer, or your outlet’s safety desk.
Freedom of the Press Foundation’s digital security training exists because source protection starts before the first message. CPJ’s emergency desk exists for after something has already gone wrong. A barred PNG will not replace either. It will stop you from publishing a directory next to the quote.
Chat apps are identity machines
Open larger image in a new tabHeaders 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. Message headers and quoted numbers: WhatsApp captures.
Bar a source screenshot before it hits the CMS
- Work on a duplicate. Keep verification files in the newsroom’s restricted store, not in the production library.
- Crop maps, avatars, and wallpaper kids out when the story does not need them.
- Paint filled Black bar rectangles over names, numbers, emails, and any ID or workplace badge. Skip highlighter. Skip light Blur on digits.
- Cover the pin, street labels, and building numbers even if you already cropped the map. Cover your own assignment slug and CMS user chip if they landed in the frame.
- Export PNG. Check the live page and the social card after upload, because the CMS may recompress and shift a bar.
Open larger image in a new tabWhat you should see on the published page: enough chrome that readers understand it is a chat, with every identifier gone. What you should not see: a map sliver plus a distinctive storefront in the same frame.
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. Location in files: EXIF and GPS.
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. The ICO’s guidance on disclosing documents securely is a useful reminder that hidden personal information can still leak when redaction is weak.
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.
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. That is still not legal advice. Your editor and counsel set the on-the-record rule. The pixels should not freelance a second identity.
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.
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.
If the live page still shows a name
Pull the image. Replace it with a wider-bar PNG. Check AMP copies, newsletters, and the social card cache. If a stringer already forwarded the unbarred original in Slack, treat that channel as a second publication and follow your newsroom’s incident process. A blog post cannot tell you what that process is.
Signal chats, maps, and the stringer’s phone
Sources often send tips as screenshots of Signal or WhatsApp. Those frames include profile photos, last-seen status, and sometimes a pinned location. Cover the profile and the header number before the image enters the CMS. Map pins that show a home street are identities. Crop the map or bar the address chip. Do not “soft blur” a house number and call it protection.
Stringers working from a phone may air-drop the raw capture into a group. Ask for the barred PNG only. If you must edit locally on deadline, keep the file in the browser tab with BlurThis rather than uploading to a random web redactor. Newsroom policy still wins when it forbids consumer tools; this page is the pixel checklist, not a policy override.
