Compress a PDF to under 2MB

Get a PDF under 2MB so it sends as an email attachment instead of bouncing. This is a generous budget compared with portal limits, so most documents come through looking essentially unchanged. Compression runs in your browser.

Compress PDF to 2MB

auto quality search · 2MB ceiling

Ready

Loading tool…

How to convert Compress PDF to 2MB

Add your PDF. Drag the file onto the drop zone. The current size is shown against the 2MB target.
Let it find the setting. The tool searches for the highest quality that still fits under 2MB, rather than compressing harder than necessary.
Check the result. Most documents look effectively identical at this size. The preview confirms it.
Download and send. Save the file and attach it.

Why 2MB is the practical email limit

Mail servers advertise larger limits than they reliably deliver. Gmail accepts 25MB, Outlook 20MB, and many corporate servers 10MB — but attachments are MIME-encoded in transit, which inflates them by roughly a third, and the message has to clear every server along the way, not just yours.

The result is that a message can be accepted by your provider and rejected by the recipient's, sometimes silently. Corporate mail gateways are frequently configured far more conservatively than the public defaults, and 5MB or 10MB caps are common.

2MB sits comfortably below essentially every gateway in normal use. An attachment that size arrives without drama, does not sit in someone's inbox quota, and downloads instantly on a phone. It is the size at which you stop having to think about it.

This limit is comfortable, not punishing

Unlike the 100KB and 200KB portal tiers, 2MB leaves real room, and it is worth knowing how much:

A 50 page text document — will very likely already be under 2MB. Compressing it may save almost nothing, and that is fine.
A 20 page scan — fits easily at good quality. Text stays sharp.
A 100 page scan — fits, with visible but acceptable softening.
A 500 page scan — around 4KB per page, which is below legibility. Split it and send in parts.

Consider whether to compress at all

If your file is already close to 2MB, think about whether you need this. Compression at these sizes is nearly lossless in practice, but nothing is always better than something when the file already fits.

The one case where compressing a file that already fits does pay off: sending several attachments in one message, where the total is what the gateway measures rather than the largest single file.

If your document is genuinely enormous — a 200MB scanned archive — email is the wrong channel. Compressing to 2MB would destroy it. Share a link instead, or use the P2P Share tool to send the full-quality file directly to the recipient's browser without an upload.

Frequently asked questions

Will my document lose quality at 2MB?

For most documents, barely. 2MB is a generous budget, so the tool applies only as much compression as it needs. A 20 page scan comes through looking essentially the same.

Is my file uploaded?

No. Compression runs entirely in your browser, so the attachment stays confidential even before you decide who to send it to.

My email provider allows 25MB. Why compress to 2MB?

Because the recipient's server also has to accept it, and corporate gateways are often capped at 5MB or 10MB. MIME encoding also inflates attachments by about a third in transit. 2MB clears essentially everything.

Will the text stay selectable?

At this size the tool usually compresses lightly enough that text pages stay crisp. Very large scans requiring heavier compression will have their text rendered into the page image.

My file is already under 2MB. Should I compress it?

Generally no. If it already fits, sending it as-is is the better choice. The exception is attaching several files at once, where the combined total is what gets measured.

What if my file is far too large to reach 2MB?

Split it and send in parts, or use P2P Share to send the full-quality file directly to the recipient's browser with no upload and no size limit.

Does compressing add a watermark?

No. The output is completely clean.