Copy Metadata Across Files - Free Online Browser Tool

Take the properties from one PDF and apply them to a whole batch, so a set stays consistent.

A bundle assembled from five sources can carry five different authors and five creation dates, which looks careless in a filing and occasionally causes a real problem. Applying one document’s properties across the set fixes that in a single run.

This copy metadata across files utility runs completely inside your web browser. Your document is opened locally and processed on your own device using JavaScript and WebAssembly, so your file is never uploaded to any server. There is no signup, no watermark and no limit on how many documents you can handle.

  • 100% client-side - files never leave your device
  • Instant processing, no upload wait
  • Works on desktop, tablet and mobile
  • Free forever, no account required

Common next steps: Edit PDF Metadata, Sanitize Tracking IDs, Remove / Clean Metadata, Bulk Edit PDF Metadata.

How to Use the Copy Metadata Across Files Tool

Four steps, and the whole thing runs locally on your own device.

  1. Add the source file first

    Its properties are read and become the template for everything after it.

  2. Add the files to update

    Any number of PDFs. Each is modified and left with its original filename.

  3. Choose the scope

    Safe subset copies only the meaningful fields. Full mode also copies the original creation date, which is sometimes what a bundle needs.

  4. Download the set

    You get every updated file plus a note of what was copied and what the source lacked.

Frequently Asked Questions

What if the source has no metadata at all?

You are told rather than receiving a set of silently emptied files. Copying nothing is almost never what someone meant to do.

Should I copy the original creation date?

Only if the bundle needs to preserve when each document was genuinely made. For most cases the safe subset is better, because copying one file’s date onto others asserts something untrue about them.

Do the page contents change?

No. Only the document properties are rewritten; not a single page is touched.

Why am I downloading an archive rather than the files?

Because a set of files is the natural output, and the bundle also carries a note listing what was applied to what — which is worth having when the set is going into a filing.

Can I run it repeatedly to layer changes?

Yes, and it composes: run it again with a different source to overwrite the earlier pass. Each run reports what it actually changed rather than assuming success.