Every PDF carries a set of properties that never appear on any page. The account name of whoever made it. The application and version. When it was created and when it was last touched. And, more often than people expect, the full path of the folder it was saved from — which can name a client, a matter number, an internal project or a person’s home directory.
None of that is visible when you read the document, which is exactly why it survives. A file goes out to a customer, or gets attached to a tender, or is published on a website, and the properties go with it. The author field alone has embarrassed a great many organisations, usually by naming somebody who was never meant to be associated with the document.
Cleaning it is a small job with one important condition attached: metadata is not page content. If a name is printed in a paragraph, this tool will not touch it, and no amount of clearing properties will. That distinction is worth holding firmly because the two get confused constantly. Sanitising a document’s properties is housekeeping; taking a name out of a sentence is a different operation with different consequences, and it has its own tool.
What this shows you is the actual values in your own file rather than a generic list of what a PDF can contain. Empty fields are not offered, because there is nothing to decide. The title is kept as a separate choice from the rest, because a reader’s software often displays the title instead of the filename — clearing it is usually right, but not always, and it should be a decision rather than a side effect. Beyond those named fields a PDF often carries an XMP metadata block, a second structured copy of much the same information, and clearing that is offered alongside — its contents are not itemised the way the named fields are, so it is a single choice.
Everything happens in this browser. Nothing is uploaded, the original file on your disk is untouched, and there is no signup or limit.