Loading page
About this tool
What hidden metadata photos, documents, scans, screenshots, audio, video, resumes, design files, attachments and code repos leak, and how to strip it.
Files carry hidden details such as location, device, author names and edit history. Pick a file type to see what metadata it usually holds, how risky each field is, and how to remove it before you share. This page brings together 10 separate file metadata risk explainer pages (Attachments, Audio, Code repos, Design files, Documents, Photos, Resume, Scans, Screenshots, Video) so you can compare them without hunting for the right one.
Open File Metadata Risk Explainer on AltFTool — it loads instantly in your browser.
Choose your file type at the top: Attachments, Audio, Code repos, Design files and 6 more. On a phone it is a drop-down list.
Fill in the file metadata risk explainer for that file type; each of the 10 options keeps its own rules, data and defaults.
Read the result, then switch file type to compare. The page link keeps your file type (?v=attachments), so you can bookmark or share it.
Attachments, Audio, Code repos and the rest sit behind one picker, so switching file type takes a tap instead of a new search.
Every file type keeps its own rules, numbers and defaults rather than one generic template.
The link remembers the file type you picked, so a bookmark or a shared link opens straight on it.
10: Attachments, Audio, Code repos, Design files, Documents, Photos, Resume, Scans, Screenshots, Video. Pick one at the top of the tool; the page link updates (for example ?v=attachments) so you can bookmark or share that exact view.
No. Attachments are Base64-encoded for transport and decoded back to an identical file, so document properties, tracked changes, comments and image EXIF all arrive intact. Only a step you take before attaching, or a data-loss-prevention system your employer runs, changes the file.
Yes. Some apps and recorders can store location titles or GPS-like metadata, and the audio itself may contain announcements, traffic, room tone or background speech that reveals place.
Each commit records an author name, an author email and an author timestamp with the UTC offset of the machine that made it, plus the same three fields for the committer. All of it is published the moment the repository is pushed public, and it stays in the history after you change your git config.
Yes. Vector exporters turn layer and group names into element ids or class names, so an SVG is readable as text in any editor. Rename layers in the hand-off copy or use an export preset that generates neutral ids.
In docProps/core.xml: the author (dc:creator), the last person to save it (cp:lastModifiedBy), the revision number and the created and modified timestamps with a UTC offset. In docProps/app.xml: the Company from the Office licence, the Manager, the template name and TotalTime, the number of minutes the file has been edited. The body can also hold tracked changes, comments, hidden text and full-resolution originals of cropped images.
Typically the capture date and time to the second, the UTC offset, the camera make, model and software version, exposure settings, and — if location services were on — latitude, longitude and altitude in a separate GPS IFD. Cameras can also store an owner name, a copyright string and a body serial number, and photo libraries may write tagged people's names into XMP.
They can see the Author and 'Last modified by' properties, which hold the name registered in the copy of Office that created and last saved the file. If you started from someone else's document, their name travels with yours until you edit the properties.
Yes, if OCR was applied. Searchable scans draw the recognised words invisibly behind the page image using text render mode 3, so every word can be selected, copied and indexed by a search engine even though you only see a picture.
Screenshots do not record GPS coordinates, because no camera or location sensor is involved. They can still carry tags such as pixel dimensions, display DPI and a Software field naming the capture tool or OS build, plus the filename and file system timestamps.
It removes many container tags, but it does not remove what is visible in frames or audible in the soundtrack. It may also preserve subtitles, chapters or thumbnails depending on the pipeline.