Free · Fast · Privacy-first

Compress Multiple PDFs Online

There is no single-pass batch PDF compression in a browser because each PDF must be processed individually.

⚡

No daily limit, compress as many PDFs as needed

🔒

Sequential workflow is faster than expected for most batches

✨

Browser-based, all files stay on your device

⚡

Consistent compression level applied to every file

Cost: Free forever
Sign-up: Not required
Processing: In your browser
Privacy: Files stay local

FreeNo signupWhite-label

Add this PDF Compressor to your website

Drop the PDF Compressor into any page — blog post, product docs, intranet, school portal — with a single line of HTML. Your visitors get the full tool, processed entirely in their browser. No backend, no uploads, no signup.

Files stay 100% in the visitor's browser
Responsive — adapts to any container width
Free forever, no API key needed

Embed code

<iframe
  src="https://www.fixtools.io/pdf/pdf-compressor?embed=1"
  width="100%"
  height="780"
  frameborder="0"
  style="border:0;border-radius:16px;max-width:900px;"
  title="PDF Compressor by FixTools"
  loading="lazy"
  allow="clipboard-write"
></iframe>

<iframe
  src="https://www.fixtools.io/pdf/pdf-compressor?embed=1"
  width="100%"
  height="780"
  frameborder="0"
  style="border:0;border-radius:16px;max-width:900px;"
  title="PDF Compressor by FixTools"
  loading="lazy"
  allow="clipboard-write"
></iframe>

Attribution-friendly: a small "Powered by FixTools" link appears in the embed footer.

Why browser tools process one PDF at a time and how to work efficiently with batches

Browser-based PDF compression uses JavaScript heap memory to load the entire PDF before processing begins. For a 10MB PDF, the browser allocates roughly 10 to 30MB of working memory for the compression pipeline (original bytes plus the decoded image data plus the output buffer). Modern browsers limit JavaScript heap memory to avoid crashing the user's computer, so attempting to load five 10MB PDFs simultaneously would require 50 to 150MB of simultaneous allocation. While technically possible on a high-RAM desktop, it introduces complexity that browser JavaScript engines are not optimised for and can cause instability. The simpler, more reliable model is sequential, where you process one file completely, free the memory, then start the next.

For a batch of 10 to 20 typical business PDFs at 5 to 15MB each, sequential processing in FixTools is practically fast. A 10MB PDF compresses in approximately 10 to 20 seconds on a modern desktop browser. Ten PDFs at this size take 2 to 4 minutes total. Twenty PDFs take 5 to 8 minutes. The workflow per file is simple: drag the file onto the tool, click compress, download. With practice and browser window positioning, a user can process a file every 30 to 45 seconds including the download step. The compressed files land in the Downloads folder in sequence, ready to batch-upload or archive after all files are done. The wall-clock time required is usually shorter than first-time users expect.

For batches above 30 to 50 files, or for automated recurring compression such as nightly compression of new scan output from a document management system, desktop command-line tools are more efficient. Ghostscript, available free for Windows, Mac, and Linux, can be scripted to compress an entire folder of PDFs in a single command. The equivalent Ghostscript command for medium compression is: gs -dBATCH -dNOPAUSE -sDEVICE=pdfwrite -dPDFSETTINGS=/ebook -sOutputFile=output.pdf input.pdf. A shell script using this command in a loop processes hundreds of PDFs unattended. For organisations that need automated batch compression, this is the appropriate tool. For individuals who occasionally need to compress 10 to 20 PDFs, FixTools sequential processing is faster to set up than installing Ghostscript.

The privacy advantages of in-browser compression apply equally to batch workflows. Each file is processed locally and never leaves the device, which means that even processing 50 sensitive documents in a single session does not result in any cloud transmission at any point. This is a meaningful differentiator for users in finance, healthcare, and legal contexts where uploading large numbers of client documents to a third-party cloud tool would trigger compliance reviews. The sequential workflow may take a few minutes longer than a batched cloud tool would, but the avoided compliance overhead and the freedom from per-file daily limits typically outweigh the time difference.

Ghostscript PDF compression documentation Browser JavaScript memory management (V8 blog)

How to use this tool

💡

Process each PDF one at a time: upload, set compression level, compress, download, then immediately upload the next. For consistency across a batch, use the same compression level for all files. Medium compression is appropriate for most business PDF batches.

How It Works

Step-by-step guide to compress multiple pdfs online:

1
Organise your PDFs in a folder
Move all PDFs you need to compress into a single folder for easy access during the sequential workflow. Naming the folder to-compress and creating a sibling folder named compressed keeps the workflow tidy and prevents mixing originals with outputs.
2
Open the PDF Compressor
Go to fixtools.io/pdf/pdf-compressor in your browser. Keep the tab open throughout the entire batch so the compression library remains loaded and ready for each file.
3
Process the first PDF
Drag the first PDF onto the tool, select your compression level, click Compress PDF, and download the result. Note the compressed file size and confirm it meets your target before moving on to the next file.
4
Process remaining PDFs in sequence
Without refreshing the tab, drag the next PDF onto the upload area and repeat the compress-and-download step for each file. With practice the cadence settles into about 30 to 45 seconds per file.
5
Verify compressed sizes
After completing the batch, check the file sizes of the compressed PDFs to confirm all are within your target size. Sort the folder by file size to spot any outliers that may need a second pass at higher compression.

Real-world examples

Common situations where this approach makes a real difference:

An HR coordinator receives 18 candidate CV PDFs averaging 6MB each for an internal applicant tracking system capped at 2MB per file. Sequential compression in FixTools at medium level takes 22 minutes total including download and folder organisation. All 18 CVs reduce to an average of 1.4MB. The HR system accepts all imports without error. No software purchase or installation is needed, and no candidate files leave the local network during the entire process.

An accountant needs to upload 12 monthly bank statements to HMRC's online portal, each with a 3MB limit. Downloaded statements average 4.5MB each because they include high-resolution bank logos. Sequential medium compression in FixTools takes 15 minutes for all 12 files. Each compressed statement is between 1.8MB and 2.2MB, comfortably within the portal limit. All 12 upload to the portal within a single filing session, completing the tax submission ahead of the deadline.

A school administrator prepares 25 scanned parent consent form PDFs at 8MB each for a digital archive system with a 1MB per-file limit. High compression in FixTools sequentially reduces each to between 700KB and 900KB over 35 minutes. All forms upload cleanly to the archive system. Handwritten signatures and text remain legible in the compressed output, satisfying the school's record-keeping requirements without requiring re-collection from busy parents.

A property manager compresses 20 tenancy agreement PDFs at 7MB each before uploading to a cloud document management platform to reduce monthly storage costs. Sequential medium compression takes 28 minutes. The compressed set averages 1.9MB per file. Total storage consumption drops from 140MB to 38MB for the same 20 documents, saving cloud storage costs over time and improving document retrieval speed inside the property management dashboard.

Pro tips

Get better results with these expert suggestions:

Keep the FixTools tab open across the entire batch

Do not refresh or close the FixTools tab between files. The page stays in a ready state between compressions, so you only need to drag the next PDF onto the upload area. Refreshing the tab reloads the JavaScript compression library, adding 3 to 5 seconds of load time per file that compounds across a 20-file batch. Over a large batch the saved seconds add up to a meaningful amount of working time.

Use a dedicated Downloads subfolder for compressed files

Before starting a batch, create a subfolder in your Downloads folder named compressed or ready-to-upload. Configure your browser to ask where to save each download, or move each compressed file to the subfolder immediately after downloading. This prevents confusion between original and compressed files, especially for batches where filenames are similar between originals and outputs after the browser appends a download suffix.

Apply consistent compression across the batch

Choose a single compression level before starting and apply it to every file in the batch. Mixing compression levels with some at medium and some at high produces inconsistent quality across the batch which can be confusing for recipients. For archive collections or system imports where all files serve the same purpose, a uniform quality level is easier to document and audit later if questions arise about a specific file.

For batches above 30 files, consider Ghostscript

Ghostscript is a free command-line tool available for Windows from ghostscript.com, Mac via Homebrew, and Linux through standard package managers. A single terminal command compresses one PDF and a shell script wrapping the command in a loop processes an entire folder of PDFs automatically. Installation takes 10 minutes and the script setup another 10 minutes. For recurring batch compression needs, this one-time setup saves significant time over manual sequential processing of large folders.

FAQ

Frequently asked questions

FixTools processes one PDF at a time in the browser. To compress multiple PDFs, process each file sequentially: upload, compress, download, then upload the next. For a batch of 10 to 20 files, this typically takes 15 to 30 minutes depending on file sizes. There is no daily limit, so you can process as many files as needed in a single session without any usage restrictions. The sequential model is faster in practice than first-time users expect because the cadence becomes very efficient after the first few files.

For typical business PDFs of 5 to 10MB each, each file compresses in 10 to 20 seconds. Including the upload drag-and-drop and download click, each file takes 30 to 45 seconds of active time. A batch of 20 files takes approximately 10 to 15 minutes. For larger PDFs above 20MB, allow 45 to 90 seconds per file. The tab can be left running while you work on other tasks, returning periodically to handle the next file in the sequence.

Ghostscript is the best free tool for single-command batch compression of multiple PDFs. It runs from the command line and can process an entire folder in one operation. On Windows, download Ghostscript from ghostscript.com. On Mac, install via Homebrew with brew install ghostscript. PDF24 Desktop on Windows also supports batch compression via a graphical interface. For users who prefer a browser, sequential processing in FixTools remains free and requires no installation, which is often the deciding factor for casual users.

If you apply the same compression level to every file in the batch, yes. FixTools applies the selected level consistently to each PDF regardless of its original content. However, the visual outcome varies by content type because a scanned PDF compressed at medium may show more softening than a text-heavy PDF compressed at the same setting. The compression level setting is consistent; the visual result is content-dependent because different source materials respond differently to the same algorithm.

Without software installation, the only option is sequential browser-based processing in FixTools. True folder-level batch processing requires a desktop application or command-line tool. Ghostscript provides this capability free of charge. For a one-time batch, sequential FixTools processing is typically faster to start than installing Ghostscript. For recurring batch needs, Ghostscript is the better long-term choice because the upfront install pays off across many subsequent batches.

Before starting a batch, move all PDFs to compress into a to-compress folder. After compressing each one and downloading the result, move the original from the to-compress folder to an originals folder. This simple folder workflow tracks progress clearly and prevents re-compressing already-compressed files. Name compressed files consistently by adding a _small or _compressed suffix to distinguish them from originals in the Downloads folder.

No. FixTools processes all files in the browser. Nothing is uploaded to any server at any point in the batch. Each compressed PDF is generated as a browser download directly from the local processing. After you navigate away from the tab or close your browser, no record of your files exists outside your own device. This is a significant privacy advantage when working with batches of sensitive or regulated documents.

Yes, for several reasons. Smaller files upload faster, take less storage, and load faster in the document viewer. Most document management systems including SharePoint, Google Drive, Dropbox, Laserfiche, and DocuWare charge storage costs that scale with total data volume. Compressing PDFs before archiving reduces long-term storage costs and improves retrieval speed. A five-times reduction in average PDF size from a medium compression routine meaningfully reduces storage costs over time for organisations that archive thousands of documents per year.

Yes, but with caveats. Browsers may suspend background tabs to save resources, which can interrupt an unattended batch workflow. For overnight batches, disable any browser settings that suspend background tabs, plug the device into power, and disable system sleep. Even then, a true unattended large batch is better handled by a scripted desktop tool like Ghostscript that does not depend on browser foreground activity to keep running. Batch compression is the standard workflow for archival projects, legal e-discovery, and bulk content publishing on knowledge base platforms with size limits.

Use a consistent naming convention before compression. Add a suffix like _compressed or _small to output files, or keep the original filename and place compressed versions in a separate folder. For large batches, generate a manifest CSV listing original filename, original size, compressed size, and compression ratio for each file. This audit trail is essential for legal discovery, archival projects, or any workflow where you need to prove the relationship between original and compressed versions. Most batch tools generate this manifest automatically when requested in the export settings.

Use parallel batch processing. Most desktop tools support folder-watch mode that auto-compresses any new PDF dropped into a watched directory. For one-off large batches, command-line tools like Ghostscript can be wrapped in a simple script that processes files in parallel using xargs (Linux/Mac) or PowerShell ForEach-Object -Parallel (Windows). This typically completes 100+ PDFs in minutes rather than hours. Browser-based tools work well for smaller batches (5-20 files) where the convenience outweighs the per-file overhead of running each through the browser interface.