QQuickToolz
All tools
PDF Toolkit

Privacy first: every operation runs 100% in your browser via pdf-lib and pdf.js — your PDFs are never uploaded anywhere.

Merge PDFs

Files are processed in your browser — order stays as listed.

Drop PDF files here or click to choose

How it works

PDF Toolkit merges, splits, rotates, reorders and compresses PDF files, and can turn images into PDFs. Everything runs in your browser, with no files sent to a server, which matters for contracts, invoices, ID documents and anything else you'd rather keep private.

Quick start

  1. Add one or more PDF files, or images.
  2. Choose an action: merge, split, rotate, reorder or compress.
  3. Download the new file.

Frequently asked questions

Are my PDFs uploaded to a server?

No. Processing happens on your device.

Will compression damage my document?

Compression reduces file size, and images inside the document may lose a little quality. Check the result before you send it.

Can I change the order of pages?

Yes. You can rearrange pages before downloading.

Why PDFs get huge — and how to shrink them safely

Fonts, images and duplicate objects: where the megabytes actually hide in a PDF. · 6 min read

What is actually inside the file

A PDF is a container, not a single document stream. It bundles pages, fonts (often full, unsubsetted families), images, vector artwork, bookmarks, annotations, form fields, and sometimes an audit trail from the producing application. A two-page report that weighs 40 MB is almost never carrying two pages of text — it is carrying a handful of full-resolution images, one font per weight used, and whatever else the source application decided to embed.

Scanned documents are their own category: every page is a full-page photograph, typically at 300–600 dpi even though the content is just a letter. A 100-page scan at 600 dpi can easily run into gigabytes, and almost all of it is information a screen or a printer will never show.

The dpi you actually need

For content destined for a screen — email attachments, web uploads, archiving — 150 dpi is a comfortable target and 100 dpi remains readable for body text. Printing is the only context that genuinely wants 300 dpi. If your scans are at 600 dpi and their destination is a screen, you are carrying four times the pixels for no visible gain.

Image-heavy compression works by re-encoding those page images at a chosen dpi and quality. Text is untouched: it stays vector and selectable (if it was selectable before). This is why a good compression pass on a scan can shrink the file 5–20× while the reading experience stays identical, whereas the same pass on a text-only PDF changes almost nothing — there are no images to re-encode.

Splitting, rotating and organizing: the cheap wins

Splitting is the most effective tool people forget. A 50 MB job application that is 90% a certificate portfolio and 10% a letter splits into a 2 MB letter (what the recipient needs) and a separate certificate file (what they will ask for later). Sending only the relevant pages is both smaller and kinder.

Rotation metadata is another classic trap: a 'landscape' page that is really a portrait page with a /Rotate flag. Viewers honour the flag, some printers and parsers do not. Physically rotating the page content (as the organize tool does) bakes the orientation in, so the file behaves identically everywhere.

A sensible shrinking workflow

Order of operations matters: resize and split first, then compress what remains. Compressing a 100-page file you will only send 6 pages of wastes effort on pages that were about to be deleted. And keep the original: compression is lossy on images by design, so the archived master stays untouched while the shrunken copy travels.