Does editing PDF metadata on Windows change the visible PDF pages?

No. The tool changes standard document information only; it does not alter page text, images, annotations, or the filename.

Are my PDF files uploaded?

No. The selected PDF is read and saved locally in your browser, and the original file is not overwritten.

Can I clear the title or author?

Yes. Leave the relevant text field empty and save. The downloaded PDF receives an empty value for that entry.

Why was a date rejected?

Dates must be real calendar dates in YYYY-MM-DD format. The tool checks both the format and leap years before saving.

Edit PDF Metadata on Windows: Fields, Dates, and Checks

To edit PDF metadata on Windows, open PDF Metadata Editor in a browser, choose a PDF from your device, change the document-information fields you need, and download a separately named copy. The PDF Metadata Editor handles this local workflow without sending the PDF to a server. The browser reads common entries such as title, author, subject, keywords, creator, producer, creation date, and modification date. You can correct a misleading title or byline, add useful archive keywords, and save a clean copy while the original file remains unchanged. The operation changes information stored inside the document, not the visible words, images, or page layout, and it does not rename the file. No desktop PDF editor or separate installation is needed for this metadata-only workflow. Dates need special care: enter them as valid calendar dates in YYYY-MM-DD format, while a blank date preserves the existing date. Because viewers expose different subsets of metadata, check the downloaded copy in the viewer or archive system you actually use before it replaces anything in circulation.

Why a browser workflow fits Windows document cleanup

A PDF can look correct on screen while its document record still contains an outdated title, incorrect byline, or unhelpful search terms. On Windows, that can affect how people recognize a file in browser tabs, download lists, or internal search results. A browser-based workflow keeps the operation focused on that record and makes the finished copy available through a normal download.

The browser-side implementation uses the pdf-lib PDFDocument API for PDF document handling, while the selected file stays on your device. The original document is not overwritten. The tool is intentionally narrow: it leaves page artwork, form fields, bookmarks, links, and passwords alone. It does not redraw a cover page, change a heading, alter the filename, remove hidden content, or redact personal information.

Run the metadata edit on Windows

Choose the PDF and inspect the detected information. Open the linked tool in your Windows browser and select a PDF from the device with the file picker. Review the detected document information before making changes, checking the title, author, subject, keywords, creator, producer, creation date, and modification date. Leave the source file in place because the editor creates a separate download rather than overwriting it.
Edit only the entries you can verify. Update the title, author, subject, creator, or producer text in the matching box. Enter keywords as one comma-separated value, such as quarterly report, finance, sales review; the value is preserved in the saved document-information entry. For dates, use YYYY-MM-DD and make sure the date exists on the calendar because validation accounts for leap years. Leaving a text box empty writes an empty value for that field in the downloaded copy. Leaving a date box empty preserves the source date instead.
Save, download, and check the separate copy. Save the metadata and download the separately named PDF. Open that copy in your preferred PDF viewer and confirm the fields you changed. Check the values your delivery or archive destination actually displays. If they match your intent, use the downloaded copy for that job and keep the original available for comparison.

Decide which entries need changing

Choose each field according to the record you need to correct, rather than guessing from what one viewer happens to show.

Field	Useful edit	Important boundary
Title	Give the file a clearer label in viewers that display titles	Does not change the filename or a visible cover page
Author	Correct the author label shown in document information	Does not prove authorship or create a signature
Subject	Record a concise description of the document topic	May not be displayed by every viewer
Keywords	Add comma-separated terms for internal archive searches	Saved as a document-information entry
Creator	Apply a consistent creator label across a set of reports	Does not establish a digital signature
Producer	Update the producer information carried by the PDF	Some viewers do not display producer information
Creation and modification dates	Correct document timestamp entries	Must be real YYYY-MM-DD dates; a blank value preserves the source date

Viewer behavior varies. One viewer may prioritize the title over the filename, while an archive may read keywords but never display producer information. Check the destination application rather than assuming every field will be visible. If the only problem is the visible filename, rename the file in Windows File Explorer instead; renaming it does not edit the document information stored inside the PDF.

Handle empty fields and dates correctly

Text fields and dates do not follow the same blank-field rule. An empty title, author, subject, keyword, creator, or producer field is deliberately written as an empty value when you save. This is useful when you want to clear a wrong title or byline. Dates are different: because reliable date removal is not dependable in this local workflow, a blank date box means “leave unchanged,” not “remove this date.” To change a date, enter another valid value.

Supply dates in YYYY-MM-DD format exactly. The tool validates the actual calendar date, including leap years, before saving. If a recipient or archive relies on document timestamps, review the date values carefully in the downloaded copy.

Test the result in the application that matters

Verification belongs after the download, not only before the save. Open the separately named copy in the viewer, document-management application, or archive interface that will use it. Confirm the fields that system exposes and compare important values with the source document. Different interfaces expose different subsets, so checking one viewer cannot confirm every destination. Replace the working file only after the downloaded copy passes the relevant check.

Check the title in a viewer that prioritizes document titles, and check keywords in an internal archive that searches document information. If the destination never displays producer information, verify the saved copy through another available properties view rather than assuming the field was ignored during editing.

Keep signing, redaction, and protected files separate

Metadata editing is narrower than document sanitization. Changing the author field does not prove authorship or create a signature, and changing metadata does not redact confidential text, annotations, attachments, or other page content. Use a dedicated redaction workflow for removal tasks. Saving any changed PDF can also invalidate an existing digital signature even though the visible page artwork is unchanged. If signature validity matters, keep the original signed file and use a signature-aware workflow.

Protected or unreadable PDFs are rejected safely; the tool does not bypass protection. Files with malformed metadata, unusual vendor extensions, password protection, or damage may not load. It does not promise to repair a damaged document or normalize every vendor-specific field, so an error should be treated as a reason to keep the source intact rather than force the file through.

Use a dedicated workflow for page-level changes

Use the metadata editor only when the goal is to change standard information entries. It intentionally leaves page artwork, form fields, bookmarks, links, and passwords alone. If you need to add page numbers, rotate a scan, make form fields permanent, add a visible watermark, or merge documents, use the corresponding PDF utility. Those are page-content or document-structure jobs rather than document-information cleanup.

Make the cleanup repeatable

For recurring Windows work, keep the original file, inspect every detected entry, update only values you can verify, save a new copy, and check that copy in the destination application. A predictable title and creator convention can make documents easier to recognize in browser tabs, downloads, and internal search results. This inspect-edit-save-check routine also prevents a successful download from being mistaken for a successful metadata update in every viewer.