Batch Metadata Removal
Clean up to 20 JPG, PNG, WebP, PDF or DOCX files in your browser. Save one cleaned copy directly, or download multiple copies in a ZIP. Each output is re-inspected; check warnings before sharing.
Drop up to 20 files here to clean them together
Everything happens in your browser. Nothing is uploaded.
or click to browse your files
How to remove metadata from multiple files
Choose the files you will share
Mix supported formats in one selection. Files rejected for format or size are listed separately; accepted files stay available. Use “Inspect metadata first” to review the original fields before cleaning. You can remove a file from the selection after inspection.
Clean and review every result
Start the batch and check each status. Verified means reinspection found no supported removable fields. A warning is not a verification success; a failed file has no cleaned output.
Download and check the delivery
Download individual copies or a ZIP when at least two outputs are available. Compare images, check document contents and review filenames. Save the optional report to identify output bytes by SHA-256.
Plan your batch
- Files per batch
- Up to 20
- Size per file
- Up to 25 MiB
- Combined size
- Up to 100 MiB
- Input
- Individual images, PDFs and DOCX files; ZIP archives are not accepted as input
- Output
- Separate cleaned copies, ZIP download and optional JSON report
What to review for each format
- JPG
- JPEG metadata segments are removed without re-encoding. Pixels and quality stay identical; an orientation flag and color profile are kept when present.
- PNG / WebP
- Supported metadata containers are removed. Visible watermarks and text remain.
- Supported Info and XMP metadata is targeted. Page text, annotations and attachments may retain private details; saving can invalidate signatures.
- DOCX
- Supported properties, comments and review traces are removed. Tracked changes resolve to the current visible document. Keep your original.
Bulk cleanup questions
Can I upload a ZIP or a folder?
Select the individual supported files inside it. BeforeShare creates a ZIP of the cleaned outputs; it does not inspect an uploaded ZIP or recursively read a folder.
Does the ZIP include failed or unverified files?
Failed files have no cleaned output and are excluded. Available outputs with incomplete verification or remaining fields are included and marked for review in the tool. Downloading a ZIP does not make those warnings disappear.
Does cleanup remove the filename?
By default, downloads keep the original name with a cleanup suffix. Turn on “Use neutral filenames” to download file-01, file-02… with the correct extensions instead. Preview each name in the file list; the same name is used for individual downloads, ZIP and mobile sharing. Your original files keep their names.
What does the batch report prove?
It records the available outputs’ SHA-256 fingerprints, reinspection status and removal counts. It excludes filenames and extracted values. It is an unsigned local record, not a certificate, signature validation or proof that visible content is private.
How do I batch remove metadata from multiple photos or files?
Choose up to 20 JPG, PNG, WebP, PDF, or DOCX files (25 MB each, 100 MB in total) in the batch tool. BeforeShare cleans them one after another in your browser and lets you download all clean copies as one ZIP with a local report.
BeforeShare practical guide · TuliAI
Check each result before treating a ZIP as ready to share
Illustrative example: a batch contains a camera JPEG, a PDF proposal and a reviewed DOCX. One successful file does not establish that the other two were cleaned. BeforeShare processes files locally and reports the outcome for each item, with a maximum of 20 files, 25 MB per file and 100 MB total.
| Data | What it means | What to do or expect |
|---|---|---|
| JPEG | GPS and camera fields | Open the clean picture and check its receipt |
| Author and XMP metadata | Review visible pages, annotations and attachments | |
| DOCX | Properties, comments and tracked edits | Review the current text after edits are resolved |
| A failed or unsupported item | No successful clean copy for that item | Resolve or retry it before sending the set |
The ZIP packages successful outputs; it is not a certification of the whole original batch. Read the per-file results and the batch report, then compare the expected files with the downloaded set. Output SHA-256 hashes identify the bytes you received. They do not prove authorship, legal compliance or the absence of private visible content.
Keep a repeatable handoff process
Keep originals in a separate folder. Use neutral output names when filenames could reveal a client or project. Extract the ZIP, open each output in the appropriate viewer, and recheck any file edited after cleanup. A mixed batch needs image, PDF and Word checks rather than one universal “safe” label. The document experiment below demonstrates why an author-free PDF can still show the same name on its page.
See test files, results and limits →
Sources and scope
Reviewed on . Examples explain the supported cleaner behavior; measured results are in the linked experiment. To report an error, contact us.
Predictable Local Batch Processing
Prepare a set of supported files without uploading them. BeforeShare processes each file sequentially to keep browser memory use controlled, preserves duplicate filenames safely in the ZIP, and shows any file it cannot clean.
Batch Use Cases We Support
- Legal teams preparing a small set of exhibit files for sharing
- E-Commerce teams cleaning a product-image batch before upload
- Digital Agencies securing campaign assets before client handoff
- Journalists protecting anonymous source documents in bulk
- Photographers & Creatives distributing scrubbed portfolios