Why this workflow exists
Reporters routinely receive photos, screenshots, and documents from sources who expect their identity to stay protected. A modern phone photo carries more than the visible frame. Embedded EXIF fields can include precise GPS coordinates, the device serial number, the original capture timestamp, and software versions that narrow the universe of possible authors. Removing a face from a photo without also stripping these fields can still betray a source’s location.
This workflow gives newsroom staff a local image-handling routine. VaultTools runs in your browser through WebAssembly, which means the source file never travels to a third-party conversion service during routine sanitization. That property matters in environments where material may later be subject to legal demands or unwanted access. Start with EXIF Viewer & Stripper on every inbound image before it enters a shared drive.
The risks hidden in source images
Most editorial pipelines focus on the visible content of an image. The invisible layer often gets ignored.
- GPS coordinates can place a source at a specific building, residence, or border crossing.
- Device serial fields can correlate one photo to other photos taken by the same device, even on other accounts.
- Timestamps can confirm or contradict an alibi a source needs to keep intact.
- Software version strings can narrow down the device model and operating system.
- Camera maker notes sometimes contain unique identifiers that survive ordinary “save as” operations.
Stripping these fields is operational hygiene, not a guarantee. It removes one common leakage path. It does not replace your wider source protection process.
Core workflow before publication
1. Inspect every inbound image
Open inbound files in EXIF Viewer & Stripper before they touch any shared workspace. Read what is in the file, then export a clean version. Treat the original as evidence and store it separately, only if the source is comfortable with that.
2. Downsize for safer publication
A full-resolution photo carries detail that can be reverse-engineered (window reflections, ambient signage, screens visible in the background). Use Image Compressor to reduce resolution and quality for the published version when fidelity is not editorially required. The smaller the published file, the harder it is to recover incidental detail.
3. Normalize formats from mobile sources
Sources often shoot on iPhone, which produces HEIC files. Convert these to a widely supported format with Image Converter before they pass through your CMS or social tools. Doing this locally avoids handing the original capture file to an unrelated upload service.
4. Crop sensitive areas before export
Use Image Transform to crop badges, screens, license plates, building numbers, or any frame edges that might re-identify a location or person. Crop before compression so the discarded pixels are not encoded into the output.
5. Mark review copies
When circulating an image internally for legal or editorial review, Image Watermark lets you label the file as DRAFT, EMBARGO, or LEGAL REVIEW. This avoids confusion about which copy is publishable and which is internal.
A practical operating routine
- Receive images through a channel your newsroom has approved.
- Inspect EXIF before opening the file in any tool that touches the network.
- Strip metadata into a clean copy, then handle that copy from then on.
- Downsize and crop before adding text overlays or watermarks.
- Keep watermarked review copies in a folder separate from publication exports.
- Confirm metadata one more time on the file you actually plan to publish.
Why local processing matters here
Newsroom material is often subpoena-sensitive. A screenshot uploaded to an unrelated online compressor can persist on third-party infrastructure, in cache layers, or in vendor logs. That creates an operational record outside your control. Running these transformations in the browser keeps the working copy on your machine and removes one common external hop from the chain.
This is not a substitute for source-protection training, secure messaging choices, or counsel review. It is a way to keep the small, repeatable image steps inside your own environment.
FAQ
Does stripping EXIF guarantee a source cannot be identified?
No. EXIF removal eliminates one common signal. Visual content, network metadata, distribution channel, and timing can still expose a source. Treat metadata stripping as one step among several.
Should we keep the original file with EXIF intact?
That depends on the source’s expectations and your newsroom’s retention policy. In some cases keeping the original is editorially valuable, in others it is itself a risk.
Can I publish straight from the EXIF stripper output?
You can, but a typical pipeline also applies cropping and downsizing before publication. The exact order depends on the story and the format the publishing platform expects.
Is this legal advice?
No. This page describes operational image handling. Coordinate with counsel and your editor on anything that involves source protection obligations, retention, or response to legal process.
Recommended Next Step
For inbound source material, begin with EXIF Viewer & Stripper before the file enters any shared workspace. Once a sanitized copy exists, Image Compressor is the most useful second step for reducing incidental detail in the version you publish.