When you share a PDF, you're usually thinking about the words and images on the page. But tucked into the file's structure is a second layer of information that most people never see: metadata. It's the document quietly describing itself, and it goes along for the ride whether you meant to include it or not. Most of the time this is harmless, and you'll never think about it. Sometimes it isn't, especially when a file leaves your organization, gets posted publicly, or lands with someone who was never supposed to know who wrote it or when it was really finished.
What's actually hiding in the file
PDF metadata typically records a handful of fields, filled in automatically by whatever program created or last touched the file. You didn't type any of these in, which is exactly why they're so easy to forget about. Before you share anything important, it helps to know the usual suspects so you recognize them when you look. None of these appear on the visible page, yet all of them travel with every copy of the file you send.
- Author: often your real name or account name, pulled straight from your operating system.
- Title and subject: sometimes a leftover template name or an internal project code you forgot was there.
- Producer and creator: the exact software and version used to make the PDF.
- Creation and modification dates: when the file was first made and when it was last changed.
- Keywords: tags someone added that may quietly hint at internal categories or clients.
Why a little hidden text can matter
On its own, an author field seems trivial. In context it can say more than you'd like. A job applicant sending a resume may not want the author field to read a former employer's name. A company publishing a public statement may not want the modification date to reveal it was rewritten an hour before release. Over the years, metadata has quietly identified the source of supposedly anonymous documents and revealed which template a supposedly custom proposal was actually built from. None of that appears on the page, so nobody thinks to check it, and that invisibility is precisely the risk: it leaks because you never see it, and the recipient can look whenever they're curious.
Viewing and editing what's there
The first step is simply seeing what your file carries. Edit Metadata reads out the current fields so you know exactly what a recipient would find, and everything runs in your browser, so the file you're inspecting never gets uploaded anywhere. Open your PDF, review each field that's filled in, and then decide what to do with it: clear anything you don't want to share such as an author name or internal title, correct fields you do want to be accurate like a public-facing title for something you're publishing, and save the cleaned version to send in place of the original. It's a good habit for anything headed outside your own machine, the same quick glance you'd give the address on an envelope before dropping it in the mail.
Metadata is not the same as redaction
It's important to be clear about what stripping metadata does and doesn't do, because the two jobs are easy to confuse. Editing the metadata fields cleans up the document's descriptive information, the data about the file. It does not touch sensitive content sitting in the body of the page, such as a Social Security number, a salary figure, or a home address. For hiding content on the page, you need Redact, which permanently removes the text you mark and flattens the affected pages to images so the underlying words are genuinely destroyed rather than merely covered. Drawing a black box over text without redacting often leaves the real text selectable underneath, a classic and embarrassing leak that has burned plenty of careful people. And when you want annotations and layers merged permanently into the page, Flatten folds them in so nothing remains as separately editable content.
A simple pre-send checklist
You don't need a formal process, just a moment of attention before a file leaves your hands. Think of it as three questions rather than a chore. First, does the hidden metadata say anything I wouldn't want this recipient to know, and if so, clean it with Edit Metadata. Second, is there sensitive text on the page that must truly disappear, and if so, remove it with Redact rather than covering it with a shape. Third, am I actually sending the cleaned version and not the original I forgot to replace in the folder. Metadata is easy to ignore because it never shows up in front of you, but it travels with every copy of the file, effectively forever. A thirty-second review before you hit send is a small price for knowing exactly what you're handing over.