How to check a file before you share it
Files carry more than their visible contents. A photo can carry the exact place it was taken, a document can carry its author's name and old comments, and a text file can carry a password someone pasted in months ago. And the way you share matters as much as the file: a link that never expires can still be opened years from now, by people you never meant to reach. This tool checks both halves and gives one verdict.
- Drop the file in. Up to 5 files — photos, documents, spreadsheets, PDFs, archives, text or code. The tool reads them in your browser; nothing is uploaded.
- Read what the file reveals. GPS, camera and author details, secrets in text, macros and comments in Office files, risky extensions and double extensions — each finding comes with its cost and a fix.
- Answer the sharing plan honestly. What the file is, who receives it, how you will send it, when the link expires, how the password travels, and whether you checked the recipient's address.
- Read the verdict, then fix the top items. The fixes are ordered by impact — strip the GPS first, then tighten the link, then send the password separately. Re-check the cleaned copy before you send it.
- Keep the report. Copy or download it, so you have a record of what you checked before the file went out.
What each file type can reveal
Not every format hides the same things. This is what the tool looks for, and what it cannot see:
| File type | What the tool checks | What it cannot see |
|---|---|---|
| Photos (JPEG, PNG, WebP) | GPS coordinates, camera make and model, timestamps, editing software, embedded thumbnails, text chunks | Text inside the photo itself — there is no OCR here |
| Author, creator, JavaScript, embedded files, form fields, annotations | Text hidden under black boxes, or content in scanned pages | |
| Office (docx, xlsx, pptx) | Macros, comments, embedded objects — read from the file's entry names | Document contents, hidden sheets, or what a comment actually says |
| Text and code | Emails, phone numbers, API keys, passwords, private keys, card-like numbers (first 200 KB, matches masked) | Secrets split across lines, or in an encrypted file |
| Archives (ZIP) | Entry names — including any executable smuggled inside | Contents of the entries themselves |
| Executables and scripts | Flagged outright — a program can run code when opened | What the program actually does — only the recipient's own checks can tell |
Honest limitations
A clean result is not a guarantee
The tool only sees what it can parse. An encrypted file, a hidden sheet, or text inside a photo is "cannot confirm", never "clean". Look at the file yourself before sharing.
It cannot read the recipient's device
Once the file arrives, the recipient can forward it, screenshot it, or store it anywhere. The sharing plan scores the risk of that happening — it cannot prevent it.
A share cannot be retracted
Deleting a link stops future access, but it does not delete copies someone already downloaded. The cheapest fix is always before sending, not after.
Office checks read entry names only
Macros, comments and embedded objects are flagged from the file's entry names. The tool never opens the document content, so a comment's text or a hidden sheet stays unchecked.
Files over 25 MB are only partly checked
Large files get name, size and extension checks only — their contents are not parsed. Open a large file yourself and check it before sharing.