Action

PDF compress

Shrink a PDF's file size

Shrinks a PDF's file size so it slips under email, upload, or fax size limits while staying readable. Drop it in just before a delivery step that has a size cap.

How it works

Scanned and image-heavy PDFs are often far bigger than they need to be. This node re-packs the file so it takes up less space, which is the difference between an email that sends and one that bounces back for being too large.

It aims to keep the document readable rather than squeeze it to the smallest possible size at the cost of legibility. Text stays sharp and pages stay in order; the savings mostly come from images.

Place it right before whatever has a size limit, most often an email or fax step, so the file is already trimmed by the time it needs to leave.

Common use cases

Real situations where this node earns its place in a flow.

Get under a size cap

Shrink a heavy PDF so it fits an email or fax size limit before you send it.

Cut storage costs

Compress documents before writing them to storage to reduce what you pay to keep them.

Speed up downloads

Slim a report so recipients open it quickly on any connection.

PDF compress in a workflow

A simple example of where this node sits in a flow.

PDF merge Combine N filled PDFs → 1 PDF compress Shrink a PDF's file size Email outbound Send report link

What you set up

  • Add it after the PDF is fully assembled but before it is sent out.
  • Point it at the file (or files) you want to shrink.
  • Choose how hard to compress if you want to trade a little quality for a smaller size.

Common questions

Will compressing blur my text?

No. Text stays crisp because it is not an image. The size reduction comes mostly from packing photos and scanned pages more efficiently.

Where should I put this in my flow?

Right before a delivery step that has a size cap, like emailing or faxing, so the file is already small enough when it goes out.