How to Take Your Name Off a PDF's Author Field

A PDF's Author metadata field is set independently of anything actually printed on the page - and it's frequently filled in automatically by whatever software created the document, using the name registered to that software license, not a name anyone deliberately typed. A document created on a company laptop can carry a specific employee's name in its Author field even if the visible document has no byline at all, which is exactly the kind of thing worth checking before sharing a file outside a small, trusted circle.

Upload the PDF and see what's actually there

On the PDF metadata tool, drop a PDF up to 80 MB. The form pre-fills with whatever's currently set: Title, Author, Subject, and Keywords as editable text fields, plus the Creation date and Last modified date shown as read-only values below them. This first step alone is often the useful part - seeing the current Author field is frequently the first time anyone's actually looked at it, since it's invisible unless you go looking through a reader's Document Properties dialog.

Clear or edit the field

Select the text in the Author field and delete it, or replace it with whatever name or organization you do want attached to the document instead. There's no special "remove" action needed for a single field - it's a plain text input, and an empty field simply means no author is recorded. If you want to clear every metadata field at once rather than editing them one at a time, the "Clear all metadata" button empties Title, Author, Subject, and Keywords together in a single click - useful when you want none of those fields to say anything. Many PDFs also keep a second copy of these details in an XMP metadata block, which this tool does not edit, so don't rely on it alone for a document that must be anonymous.

Field by field, then Save

Save and download

Click Save, and the updated PDF downloads with the new (or cleared) Author field. This runs entirely on your device - the file is never uploaded anywhere to make this change, which matters here specifically since the whole point of the exercise is often removing identifying information, not sending the identifying document to a third-party server to have it removed.

One real exception: a signed PDF

If the PDF you upload carries a digital signature, the tool detects that before Save is even offered and shows a plain warning: editing metadata means saving the file, and any save rewrites the document's underlying byte structure, which invalidates a digital signature's ability to verify, even though the visible content and the metadata edit itself are completely unrelated to what the signature was protecting. Save stays disabled until you explicitly check "Edit anyway (signature will no longer verify)" - never a silent pass-through that breaks a signature without telling you. If the document needs to stay verifiably signed, editing its metadata at all isn't compatible with that, and it's worth knowing that before you start rather than after downloading a result with a broken signature.

A related, milder warning: XFA forms

If the PDF contains an advanced interactive form (XFA, a less common but real format some government and enterprise PDF forms use), you'll see a separate notice that the form's interactive behavior may not survive the metadata edit. This is a genuinely different warning from the signature one - it's about form fields staying functional, not about a cryptographic signature - and it can appear on its own or alongside the signature warning depending on what the specific document contains.

What the "Created" and "Modified" dates tell you

Below the four editable fields, the tool shows the document's Creation date and Last modified date as plain read-only values - not something you can type over. These come from the PDF's own recorded history rather than anything the tool infers, and they stay accurate through a metadata edit: changing the Author field doesn't retroactively change when the document says it was created, and saving the file does update the modification date, the same way saving any file naturally would. If you're checking whether a document is what it claims to be - confirming a report really was created when someone says it was, for instance - these two dates are worth glancing at before you make any edits, since editing overwrites the modification timestamp going forward.

Doing this for more than one document

The tool processes one PDF at a time rather than a batch, which is the right shape for this specific task - metadata edits are usually deliberate, per-document decisions (this report's author should say the team name, not an individual; that one should stay attributed to whoever actually wrote it), not a uniform find-and-replace you'd want applied blindly across a folder of unrelated files. For a handful of documents that do need the exact same treatment - clearing every field on a batch of reports before a public release, say - running each one through in turn takes only as long as it takes to drop the next file and click Save.

Corrupt and password-protected files

If the file can't be opened at all - a genuinely corrupt PDF, or one damaged in transfer - the tool tells you plainly rather than showing a blank form and letting you edit fields that were never actually read correctly. A password-protected PDF is treated the same way: it's blocked with a message asking you to remove the password first, since the tool never attempts to read or bypass an encrypted document's contents. Neither case is common, but both are handled with an honest message rather than a confusing silent failure.

For the broader case of clearing every field at once before sharing a document publicly - not just the Author field - see stripping metadata before sharing. And for why this field is so often wrong or generic in the first place, see why your PDF shows the wrong title.