LocalUtils logo
LocalUtils
Files stay local for processing. Account, billing, and ads use separate network services. Learn more

Merge, split, rotate, and clean PDF metadata

A review-first workflow for merging, splitting, rotating, and cleaning PDFs

PDF preparation looks simple until page order, signatures, metadata, forms, and unusual document structures collide. This guide turns the common operations into a reviewable workflow.

Written and reviewed by LocalUtilsPublished: Last reviewed:

Merge, split, rotate, and clean PDF metadata

The PDF toolbox is intended for document preparation rather than page-level editing. It can arrange several PDFs into one file, rotate every page in a selected document, divide one document into complete page ranges, and clear common document-information fields.

Start with a copy of the source. PDF structures vary widely, and an encrypted, malformed, form-heavy, or digitally signed document may not behave like a simple scanned handout. The downloaded result is a newly produced file and should be reviewed independently.

Begin with a document plan, not the merge button

Write down the intended file order, output name, page count, and whether the result needs rotation, splitting, or metadata cleanup. This small plan catches mistakes that a visual queue can hide, especially when source filenames are similar.

Preserve untouched originals. A merged or rebuilt PDF is a derivative document, and operations can affect signatures, interactive fields, bookmarks, annotations, and internal object relationships even when the visible pages look unchanged.

Understand what each operation changes

Merging copies pages into a new container in queue order. Rotation changes page rotation values for the selected document. Splitting copies complete ranges into separate files. Metadata cleanup targets common document-information fields exposed by the library.

None of these actions is page-content redaction. A name printed in a scan, a hidden attachment, a comment, or an identifier in an unsupported metadata object needs a separate inspection workflow.

Treat splitting as an accounting exercise

Complete, non-overlapping ranges make missing pages visible. If the source has twelve pages, a plan such as 1-3, 4-9, 10-12 can be checked before export. Ambiguous or incomplete ranges are a warning rather than a convenience.

After extracting the ZIP, open every part and compare its first page, last page, and count with the written plan. Do not rely only on generated filenames.

Review the rebuilt file in another viewer

Use a second PDF viewer to reduce the chance that the same rendering assumption hides a problem in both preview and review. Check order, rotation, crop boundaries, links, forms, annotations, and high-zoom rendering on representative pages.

Open document properties to check the fields you intended to clear. If the document has legal, archival, accessibility, or signature requirements, use the specialist validation appropriate to that requirement.

Keep a simple chain of custody for important documents

For work that may need to be explained later, record the source filenames, source page counts, planned order, operation performed, output filename, and review date. A checksum of each untouched source and the final output can help distinguish versions, although it does not prove that the document is correct. Avoid overwriting the originals or using vague names such as final-new-2.pdf. A short text record beside the files makes it easier for another person to reproduce the assembly, identify the authoritative copy, and understand why a page was rotated, removed, or placed in a particular position.

Quick start: LocalUtils

  1. Add one PDF to inspect its page count and metadata. Use the single-file controls for rotation, metadata cleanup, or splitting.
  2. For a split, enter ranges that account for every page exactly once. The tool rejects missing, duplicated, reversed, or out-of-range pages and packages valid parts in a ZIP archive.
  3. Add two or more PDFs to enter merge mode. Arrange the queue in the intended reading order before creating the combined file.
  4. Download the result, open it in a second PDF viewer, and only then clear the queue. The queue is stored in this browser's IndexedDB until it is cleared.

What the browser does

PDF.js reads the selected document for previews and metadata in the browser. PDF-lib creates the changed output by copying or rebuilding pages. The selected PDFs are not posted to a LocalUtils document-processing API.

Metadata cleanup clears the title, author, subject, keywords, producer, and creator fields exposed by PDF-lib. It does not remove words printed on a page, annotations that contain identifying information, embedded attachments, or every possible private object in a complex PDF.

Inputs and outputs

  • Input: one or more PDF files that PDF.js and PDF-lib can open.
  • Merge output: one PDF containing copied pages in queue order.
  • Split output: a ZIP archive containing one PDF for each complete page range.
  • Rotate or metadata output: one rebuilt PDF downloaded by the browser.

Limits to know before you start

  • Password-protected or damaged PDFs may fail to open.
  • Rotation applies 90 degrees clockwise to every page, not a hand-picked subset.
  • Splitting requires all pages to be assigned; it is not a page-deletion shortcut.
  • Rebuilding a signed PDF invalidates the original signature relationship, and interactive features should be retested.

Verification checklist

  • Compare the page count and page order with the intended plan.
  • Check a selection of pages at high zoom for clipping, rotation, form, and annotation problems.
  • Open document properties in another viewer to confirm the targeted metadata fields are empty.

Troubleshooting

  • If a preview is blank, try opening the source in a desktop viewer and saving a clean copy before retrying.
  • If merge order is wrong, reorder the queue before processing; changing filenames does not change queue order.
  • If the result is unexpectedly large, inspect whether the source contains high-resolution scans or embedded resources.

Questions people ask

Should metadata be removed before or after merging?

Cleaning the final merged file is easier to verify as one output, but source-specific metadata or attachments may require inspection before merging too.

Can a merge preserve digital signatures?

A newly assembled PDF does not preserve the original signed byte relationship. Treat signatures as requiring a dedicated signing workflow after preparation.

Why keep the original?

It provides the reference needed to detect missing pages, altered features, quality changes, and metadata differences.