NoLogPDF
NoLogPDF
Local browser workspace
NoLogPDF

Fast, free, browser-only tools. Your files stay on your device.

61 browser tools Works on mobile Free to use

No File Logs

We do not upload, store, or track the files you process.

No Backend

All processing happens inside your browser.

100% Free

Every tool is free. No hidden costs.

Total Transparency

Built for trust with clear local limits.

Edit PDF / Stable

Edit PDF Metadata Online

Read and update PDF title, author, subject, keywords, creator, and producer fields.

Quick answer

What does PDF Metadata do?

Read and update PDF title, author, subject, keywords, creator, and producer fields. The selected PDF is processed locally in this browser without being sent to a backend conversion server. Custom XMP packets, attachments, revision history, or application-specific metadata may remain.

Use PDF Metadata when you need to read and edit common PDF document metadata fields. Common uses include correct a document title, add searchable subject keywords, review creator and producer fields before sharing.

Input
PDF
Processing
In this browser
File upload
No
Price
Free

Designed around the task

Why use PDF Metadata?

Focused controls, local processing, and clear limits help you finish the job without sending the document to a conversion server.

Focused results

Updates common document-information metadata fields in a new PDF copy.

Useful browser controls

Does not change visible page text or remove every possible embedded metadata source.

Desktop and mobile

Use PDF Metadata in a current desktop or mobile browser without installing a separate app.

Simple local workflow

Create an output you can inspect before sharing.

Private by design

The selected PDF is processed by JavaScript running in this browser for PDF Metadata. NoLogPDF does not send it to a backend conversion API, and file names, contents, form values, passwords, and output data are excluded from site analytics.

Automatic file recognition

NoLogPDF checks the selected file in your browser and shows the controls available for PDF Metadata.

How to use PDF Metadata

  1. Choose a PDF file.
  2. Review the current metadata fields.
  3. Edit title, author, subject, keywords, creator, or producer.
  4. Save and download the updated PDF.

What PDF Metadata changes

  • Updates common document-information metadata fields in a new PDF copy.
  • Does not change visible page text or remove every possible embedded metadata source.

Browser-only privacy

The selected PDF is processed by JavaScript running in this browser for PDF Metadata. NoLogPDF does not send it to a backend conversion API, and file names, contents, form values, passwords, and output data are excluded from site analytics.

Limits to know before using PDF Metadata

  • Custom XMP packets, attachments, revision history, or application-specific metadata may remain.
  • Changing author fields does not prove or transfer authorship.

Common uses for PDF Metadata

  • Correct a document title.
  • Add searchable subject keywords.
  • Review creator and producer fields before sharing.

PDF Metadata questions

How does PDF Metadata work?

Read and update PDF title, author, subject, keywords, creator, and producer fields. Choose a PDF file. Review the current metadata fields. Edit title, author, subject, keywords, creator, or producer.

Does PDF Metadata upload my PDF?

No. The selected PDF is read by code running in this browser for this operation. NoLogPDF does not send it to a backend conversion API or include document data in analytics.

What does PDF Metadata change in the output?

Updates common document-information metadata fields in a new PDF copy. Does not change visible page text or remove every possible embedded metadata source.

What limits should I know before using PDF Metadata?

Custom XMP packets, attachments, revision history, or application-specific metadata may remain. Changing author fields does not prove or transfer authorship.

Published and maintained by NoLogPDF

How this tool page is checked

The instructions describe this browser implementation, its expected output, and its known limits. Core workflows are exercised with local fixtures, output files are validated where the format allows, and mobile behavior is checked at a narrow viewport.