The part of a PDF nobody looks at
Every PDF carries a small block of information about itself that is never shown on the page. Open any document's properties and you will usually find a name, a piece of software, and a pair of timestamps. The file was built to carry them and does so silently.
Most of the time this is harmless. Occasionally it is not, and the cases where it matters are exactly the ones where a file is going to someone who does not know you.
What it actually gives away
| Field | What it commonly contains |
|---|---|
| Author | The account name of whoever created the file, often a full real name |
| Creator | The application, frequently with its exact version |
| Producer | The PDF engine, reveals the operating system and toolchain |
| Created / Modified | Timestamps that can contradict a stated timeline |
| Title | Often the original filename, including internal project names |
The recurring embarrassment is the author field. Documents built from a colleague's template or a downloaded example keep the original author's name, so a CV can arrive credited to a stranger and a "bespoke" proposal can name the client it was recycled from.
What this removes, and what it cannot
Removed: every standard metadata field, author, title, subject, keywords, creator and producer. That is what document-properties dialogs display and what automated readers extract.
Not removed: anything printed on the page. A name in the text, a letterhead, a signature image, or details inside an embedded photograph are page content, not metadata, and no metadata cleaner can touch them. If the concern is a specific page, the split tool lets you send only the pages that matter.
Also worth knowing: images have their own metadata. A photograph taken on a phone carries GPS coordinates, and one embedded in a PDF may bring them along. Anything processed through our image tools is redrawn from its pixels, which drops EXIF data including location.
A sensible habit
Check before sending, rather than cleaning everything reflexively. Metadata is genuinely useful inside an organisation, it is how documents get attributed and versioned. The moment worth pausing at is when a file crosses a boundary: a job application, a tender, a court filing, a document posted publicly.