Processed on-device · pdf.js + pdf-lib

Edit PDF Metadata Online — title, author, keywords, dates, and custom fields

See exactly what's already stored in a PDF's properties, correct it, or clear it before sharing — the page content itself is never touched.

See the four steps
Standard fields Custom fields supported Visual date pickers PDF stays in your browser
Built & maintained by Bhavin J. Sheth | Updated

The metadata console

Upload a PDF to see its current properties, then edit any field you need.

Drop your PDF here

or browse files

How metadata actually works

Metadata is the paperwork attached to the file, not the page

Open a PDF's properties dialog and you're not looking at the document — you're looking at a separate record that travels alongside it, describing who made it and when.

Properties, not content

Software that exports to PDF fills in an Info dictionary automatically — often with a generic title like "Untitled" or the exporting software's own name as Author. None of that is wrong exactly, it's just usually not what you'd actually want a recipient, a search engine, or a document management system to see.

This tool reads that dictionary with pdf-lib the moment you upload a file, fills every field with what's currently there, and lets you change any of it — including adding arbitrary key-value pairs that aren't part of the standard set at all. Nothing in the visible pages is touched; only the properties record changes.

Everything you can see and edit

Standard fields

Title, Author, Subject, Keywords, Creator, Producer, and both date fields — common PDF properties supported by many PDF readers.

Custom fields

Any key-value pair — Project ID, Client Name, Document Status — that isn't part of the standard set at all.

Date fields

Visual pickers for Creation and Modification dates — no manual date-string formatting to get wrong.

Existing values, shown first

Every field is pre-filled with whatever's already in the file, so you can see it before deciding to change anything.

Clearing a field

Delete a field's contents and leave it blank to remove identifying information before sharing a document publicly.

Four fields worth checking before you share a file

Title and Author are useful starting points when you want a PDF's properties to clearly identify the document.

1

Upload your PDF

Drag it onto the upload area, or click Select PDF. Supported metadata fields fill in automatically.

An empty field simply means no value was set in the original document.
2

Edit what needs changing

Adjust the fields directly:

Standard fields: Title, Author, Subject, Keywords, and more.
Date fields: use the picker for Creation and Modification dates.
Custom fields: click Add Custom Field for your own key-value pairs.
3

Update

Click Update Metadata to write a new PDF with the changed properties in place.

Processing runs in this tab, start to finish.
4

Download

Rename the output file if you like, then download the version with updated properties.

Content untouched Nothing uploaded

Same document, properties that actually describe it

The page content is identical — only the record attached to the file changes.

Before Generic export data
PDF Metadata Before Editing
After Clearer metadata
PDF Metadata After Editing

Documents where the properties panel matters as much as the content

Cases where what's in the Info dictionary affects search, organization, or how a file presents itself.

Common situations for editing PDF metadata, by user type
SituationWhat gets updatedTypical user
Published reportsA real title and author so a PDF's document properties look intentional.Marketers & publishers
Document management systemsCustom fields like Project ID or Department for internal search and filing.Office admins & IT teams
Public-facing downloadsCleared Author and Producer fields to avoid revealing internal software or names.Legal & compliance teams
Academic submissionsTitle, Author, and Subject that match a paper's actual citation details.Researchers & students
Client deliverablesCompany name as Author and a client-facing Title before sending final files.Freelancers & agencies
Version trackingA custom Version-Number or Document-Status field for internal review cycles.Teams with approval workflows
SEO-relevant PDFsDescriptive Title and accurate metadata that help identify and organize the document.Content & SEO teams
Archival collectionsAccurate Creation and Modification dates for clearer document history and organization.Archivists & librarians
Field reference

What each metadata field is actually for

Every field means something specific, even if PDF readers rarely bother to show all of them.

Title, Author, Subject

The three fields most PDF readers show in their window title or properties panel. Title is often shown instead of the filename — worth setting deliberately rather than leaving as the export tool's default.

Keywords

A comma-separated list some search tools and document management systems index directly — useful for internal search even when it doesn't affect public web search rankings.

Creator and Producer

Creator names the original application that made the content (like a word processor); Producer names whatever converted it to PDF. Clearing both removes a small trail of what software touched the file.

Creation and Modification dates

Creation and Modification timestamps are stored in the PDF's metadata rather than your operating system's file dates, so they can travel with the document when it is copied or shared.

When the properties don't update the way you expect

Identify the problem, then use the matching fix.

Symptom
Why it happens
Fix

Some fields loaded blank

The original PDF simply never had a value set for that property.

Expected — type in whatever value you want it to have going forward.

A custom field didn't appear after upload

Only non-standard Info dictionary entries show as custom fields — anything matching Title, Author, and the other standard names appears in the fields above instead.

Check the standard fields section first — it may already be there under its proper name.

Keywords look joined together

The field expects comma-separated values, and one long word without commas is treated as a single keyword.

Separate each keyword with a comma — "invoice, march, client-a" becomes three distinct keywords.

The date field shows the wrong time

The picker displays the date in your local timezone, converted from the stored value.

Expected behavior — set the date and time you actually want; it saves correctly regardless of timezone.

A PDF viewer still shows the old title

Some readers or browser tabs cache the previous file's properties.

Close and reopen the downloaded file, or open it in a different viewer.

A password-protected PDF won't load

Encrypted files can't be read by the in-browser rendering engine.

Remove the password with a PDF unlock tool first, then upload the unlocked copy.

Some fields loaded blank

Why: No value was ever set.

Fix: Type in the value you want.

Custom field missing

Why: It matched a standard field name.

Fix: Check the standard fields section.

Keywords look joined together

Why: No commas separating them.

Fix: Add commas between keywords.

Date field shows the wrong time

Why: Displayed in your local timezone.

Fix: Expected — set the value you want.

Viewer shows the old title

Why: The reader cached the previous file.

Fix: Close and reopen, or try another viewer.

Password-protected PDF won't load

Why: Some password-protected or encrypted PDFs cannot be opened by browser PDF libraries.

Fix: Unlock it first, then upload.

Setting metadata once, correctly

A working order that avoids the most common redo.

Always write a real title

Leaving Title blank or as "Untitled" is the single most common metadata mistake — it's the first thing most readers show.

Review Creator and Producer before sharing

These fields can identify the software used to create or convert a PDF. Clear them when that information is not needed in the shared file.

Use custom fields for tracking, not the standard ones

Repurposing Subject to store a Project ID gets confusing fast — a genuine custom field keeps the standard properties clean.

Keep keyword lists short and specific

Three to eight relevant keywords are more useful for internal search than a long list of generic terms.

Double-check dates before saving

A wrong Creation date can throw off archival sorting — confirm both date fields before clicking Update Metadata.

Keep the original file

The download is a new file — hold onto the source in case you want to try different metadata values later.

PDF metadata questions

If something's not covered here, the troubleshooting section above likely has it.

Is it safe to upload my PDF to edit its metadata?

Yes. The PDF is processed in your browser and is not uploaded to AllInOneTools' server.

Will editing the metadata change the visual content of my PDF?

No. Editing metadata only changes the document's properties, like Author or Title — it doesn't alter the visible text, images, or layout of any page.

Can I see the existing metadata before I make changes?

Yes. When you upload a PDF, the tool reads its existing metadata and fills in the fields automatically, so you can see what's already there before editing anything.

What are custom metadata fields used for?

Custom fields let you attach information the standard properties don't cover — a Project ID, Client Name, Document Status, or Version Number for internal tracking.

What happens to my file after I'm done?

Nothing — it was never uploaded. The PDF with updated metadata is generated in your browser and downloaded as a new file; the original stays untouched.

Build notes

The write-up on how this was built

Because reading, editing, and rewriting the Info dictionary all run client-side, I wrote up the implementation — how pdf-lib exposes standard fields, and how custom key-value entries get read and written back safely.

Published on freeCodeCamp

How to Build a Browser-Based PDF Metadata Editor Using JavaScript

Covers reading and editing PDF metadata with JavaScript, including title, author, subject, keywords, creator information, and client-side processing that keeps files private.

Read the write-up on freeCodeCamp

Written by Bhavin Sheth · Founder, AllInOneTools