PDF Metadata Remover — Strip Properties
Strip all or selected metadata from a PDF including standard fields, XMP, and custom properties.
Drop your PDF file hereTap to select a file
Supports PDF, up to 200MB
What to do next
Related tools
PDF Metadata Editor
Edit PDF metadata fields including title, author, subject, keywords, creator, and producer.
pdfPDF Metadata Viewer
Upload a PDF to view its metadata — title, author, subject, keywords, creator, producer, dates, and page dimensions.
pdfRedact PDF
Automatically detect and redact sensitive data (SSN, email, phone numbers) from a PDF with black boxes.
pdfFlatten PDF
Flatten form fields, annotations, and layers in a PDF to make content non-editable and static.
pdfAbout PDF Metadata Remover
PDF Metadata Remover is shaped around how people actually use PDF document workflow utilities online: open the page, drop in a file, get the result. Strip all or selected metadata from a PDF including standard fields, XMP, and custom properties. The interface stays out of the way once the work begins so the engine can use the available CPU and memory for the actual transformation.
Anyone who works with PDF document workflow on a casual basis — HR teams handling onboarding documents, real-estate agents bundling disclosures, small-business owners sending invoices — finds PDF Metadata Remover a quick way to get the result. The page loads in under a second, the controls are visible from a single screen, and the result downloads or copies in one click.
PDF Metadata Remover runs the entire transformation inside your browser. The file is read by JavaScript running in the page, processed in-memory by the open-source pdf-lib JavaScript library, and written back as a download. The browser is the runtime; the page is the interface. You can confirm what the tool does by opening the developer-tools Network tab during a run — the only requests are for the page's own static assets.
Technically, the work is done by the open-source pdf-lib JavaScript library, loaded as part of the page. Inputs in PDF format are recognised automatically and validated before the engine begins processing. Files up to 200 MB are supported per run; that ceiling keeps browser memory usage stable on a wide range of devices.
PDF Metadata Remover is shaped for the gap between "I'll do it by hand" and "I'll script it." When the job is small enough that automating it would take longer than doing it, but annoying enough to want a focused tool — that is the situation this page is built for.
For multi-step jobs, PDF Metadata Remover sits next to PDF Metadata Editor, PDF Metadata Viewer, and Redact PDF. None of them depend on each other — you can use PDF Metadata Remover on its own — but together they cover the common variations of the task this page exists to handle.
The output handed back by PDF Metadata Remover is `{name}-metadata-stripped.pdf`. If you would prefer to keep the result in the browser instead of downloading it, you can copy it from the result panel and paste it directly into another tab — useful when the next tool in your workflow expects pasted text rather than a file.
The hard constraints are easy to remember. Maximum input: 200 MB. Multiple files per run: no — one input at a time, by design, to keep results predictable. The same controls apply on every run.
PDF Metadata Remover keeps the control set focused. Every option on the page is there because a real workflow needs it, and the defaults aim at the most common case so a first-time user can get the right output without changing any settings.
A short note on how PDF Metadata Remover came to look the way it does: every iteration started by watching how someone unfamiliar with the tool actually used it, then removing whatever got in their way. That is why the upload area dominates the screen, the run button is bigger than the secondary controls, and the result panel is unmissable when the job finishes.
Useful patterns when working with PDF Metadata Remover: keep the input file open in another tab so you can compare against the result; give the output file a descriptive name when saving so you can find it later (the default name is sensible but generic); and treat each run as independent — the tool has no concept of "history", which means you cannot accidentally pollute one job with leftovers from another.
If PDF Metadata Remover appears to hang, the engine is almost certainly still working — large inputs simply take longer to process inside a browser than they would on a server with multi-core scheduling. For inputs near the 200 MB cap, give it up to a minute on a typical laptop before assuming something is stuck.
As a single-page tool, PDF Metadata Remover stays focused on one PDF document workflow step. Multi-step workflows are composed by chaining adjacent tools — each tool produces a standard file the next one can read directly, so a longer pipeline is just a sequence of short tab-and-tab visits.
PDF Metadata Remover is one of many single-purpose tools in the catalog. Each is built around the same single-page model. Use this one, close the tab, and come back the next time you need the same job done. None of the tools require prior knowledge of the others — each page is self-contained.
How it works
- 1Open the PDF Metadata Remover workspace above. The interface is a single page, so there is nothing to navigate.
- 2Add your PDF input by dropping it onto the page or browsing for it.
- 3Adjust the options to match what you need. Sensible defaults cover the most common case, so you can usually skip this step.
- 4Trigger processing. the open-source pdf-lib JavaScript library reads your input, applies the transformation, and writes the result back into the page.
- 5Save the output (`{name}-metadata-stripped.pdf`) when it is ready.
- 6Run additional jobs as needed. The same controls and defaults apply on every run.
Common use cases
- Send a polished, print-ready PDF to a client without watermarks using PDF Metadata Remover.
- Convert a bundle of flyers into a single archival PDF.
- Strip blank or test pages from a scanned document.
- Extract a specific signed page from a long contract bundle.
- Split a 200-page exhibit bundle into one PDF per exhibit.
- Compress a marketing deck so the email send-out finishes in seconds.
- Reorder pages of a multi-chapter scan into the correct reading order.
- Rotate scanned pages that came in upside-down from the office scanner.
FAQ
What is removed?
Standard fields (title, author), XMP metadata, and custom document properties.
Why remove metadata?
PDFs may contain author names, software versions, and creation dates you want to strip before sharing.
Selective removal?
Choose to remove all, only standard, only XMP, or only custom properties.
Private?
Yes — runs locally.
Undo?
Metadata removal is permanent on the output file. Keep your original as backup.
Redaction?
For removing sensitive text content, use the Redact PDF tool instead.
Does PDF Metadata Remover work in Safari, Firefox, Chrome and Edge?
PDF Metadata Remover works in any modern browser released in the last few years — Chrome, Edge, Firefox, Safari, Brave, Arc and the major Chromium derivatives are all supported. The underlying engine relies on widely-supported web APIs, so there is nothing exotic to install. If you are on a very old browser version and the tool fails to load, updating to the latest release of your preferred browser is the only fix needed.
Can I trust the output of PDF Metadata Remover for important work?
PDF Metadata Remover is built on the open-source pdf-lib JavaScript library, which is the same class of engine used by professional PDF document workflow pipelines. For deterministic operations, the output is byte-identical to what an equivalent CLI run would produce; for operations involving a codec or a model, the result is well within the range of what comparable tools generate. If you have a specific reference output you need to match, run a small test job first to confirm the configuration produces what you expect.
How long does Favtoo retain my data after using PDF Metadata Remover?
Favtoo keeps no copy of your file because Favtoo never receives your file. PDF Metadata Remover runs entirely in your browser, the input is held only in your tab's memory, and closing the tab discards it. There is no opt-in cloud history, no "recent jobs" panel synced to an account, and no server-side retention to configure — the architecture simply has nowhere for your file to be stored.
Will PDF Metadata Remover keep working if my Wi-Fi drops mid-task?
Once the page is loaded, PDF Metadata Remover can complete jobs without an active internet connection — the engine is bundled with the page, so there is no per-job network call. The initial page load does require a connection (to fetch the static assets), but after that you can disconnect entirely and the tool will still work. This is a side-effect of the local-first architecture, not a deliberate "offline mode" feature.
Does PDF Metadata Remover have an API?
PDF Metadata Remover is a browser-only tool by design and does not expose a hosted API. The reason is the same as the privacy story: there is no Favtoo backend doing the work, so there is no service to call. If you need to script the same transformation, the underlying engine (the open-source pdf-lib JavaScript library) is open-source and can be used directly from your own code.
Does PDF Metadata Remover reduce quality of the result?
PDF Metadata Remover is built to preserve quality wherever the underlying PDF format allows it. Operations that are mathematically lossless (e.g. structural transformations, lossless re-encoding) round-trip with no perceptible change. Operations that involve a lossy codec inevitably introduce small artefacts at the byte level, but the defaults aim at the sweet spot where output looks or sounds the same to a normal viewer or listener while still being meaningfully smaller or faster than the input.
Why is my browser prompting me when I open PDF Metadata Remover?
PDF Metadata Remover only needs the standard web platform — file picker access for the inputs you choose to load, and optionally clipboard access if you copy the result rather than downloading it. There is no microphone, camera, geolocation or background-permission request, because none of those are needed for the work the tool does.