How to Compress a PDF to Under 15MB for Email Attachments and Uploads

LazyPDF's compression engine runs Ghostscript 10.02 on a dedicated server, applies RGB color conversion to prevent ICC profile failures, and returns your compressed file without adding watermarks or requiring payment. The entire process runs through an encrypted connection, and your uploaded file is deleted from server memory the moment compression finishes. Before you compress, check your current file size and identify why it exceeds 15MB. Right-click the file on Windows and select Properties, or select it in Finder on macOS and press Cmd+I. If the file is 16-25MB, a single compression pass at Ebook quality will almost certainly bring it under 15MB — the average reduction for mixed documents at this preset is 82%. If the file exceeds 50MB, you may need to evaluate whether Screen quality (72 DPI) is acceptable for your use case, or whether splitting the document into smaller sections is the better approach. The compression preset you select determines the output DPI, which directly controls the trade-off between file size and image sharpness. For email attachments headed to colleagues, clients, or vendors who will view the document on screen and possibly print on a standard office printer, Ebook quality (150 DPI) is the correct choice in approximately 90% of cases. A 150 DPI image prints cleanly on any printer up to 600 DPI — which covers every consumer and office laser printer on the market. Screen quality (72 DPI) produces the smallest files but introduces visible softness when printed, and should only be used for documents that will never leave a screen. Printer quality (300 DPI) preserves maximum detail but delivers less compression, typically 40-65% rather than the 75-90% that Ebook and Screen achieve. After compression, LazyPDF displays a summary showing the original size, compressed size, and percentage reduction. If the compressed file still exceeds your target size, you have three options: re-compress at Screen quality for more aggressive reduction, split the document into two parts using /en/split and send each part separately, or remove unnecessary pages before compressing using /en/organize. In practice, a file that does not compress below 15MB at Ebook quality is almost always a photo-heavy document (portfolio, catalog, or image gallery) that genuinely contains too much pixel data to fit in 15MB at readable quality — splitting is the correct solution for these cases. For phone-scanned documents specifically, our guide on <a href="/en/blog/scan-multiple-pages-to-pdf-mobile">scanning multiple pages to PDF on mobile</a> covers how to capture at optimal settings that result in smaller source files. If you need to compress a PDF directly on your device without a desktop computer, see our step-by-step guide on <a href="/en/blog/compress-pdf-on-iphone-ipad-without-app">compressing PDF on iPhone and iPad without an app</a>. For full technical details on compression presets, quality trade-offs, and benchmark data across 50 real-world documents, see our comprehensive guide on <a href="/en/blog/compress-pdf-without-losing-quality">PDF compression without quality loss</a>.

1. 1Step 1: Navigate to /en/compress on LazyPDF. The tool loads instantly with no login screen, no account creation, and no payment wall.
2. 2Step 2: Drag your oversized PDF into the upload zone or click Browse to select it from your file system. Files up to 200MB are accepted without restrictions.
3. 3Step 3: Select the Ebook compression preset (150 DPI). This is the default setting and produces the best balance between file size and visual quality for email and upload use cases.
4. 4Step 4: Click Compress PDF. Processing takes 3-15 seconds depending on page count and image complexity. A 50-page document with embedded photographs typically completes in under 8 seconds.
5. 5Step 5: Review the compression summary. Verify the output size is below your target (15MB for most email providers, 10MB for strict upload portals). Download the compressed file.
6. 6Step 6: Open the compressed PDF and scroll through all pages to confirm text readability and image quality before sending or uploading. Keep the original file until verification is complete.

Knowing the exact attachment ceiling for each email provider and upload portal prevents wasted time compressing to a size that still gets rejected. These limits apply to the total attachment size per message, not per file — sending three 8MB attachments in one Gmail message hits the 25MB wall. For a step-by-step walkthrough specifically for Gmail and Outlook workflows, see our dedicated guide on <a href="/en/blog/compress-pdf-for-email-gmail-outlook-free">compressing a PDF for email</a>. Gmail enforces a 25MB attachment limit per outgoing message. Files exceeding this threshold are automatically uploaded to Google Drive and replaced with a sharing link. While this workaround functions for personal emails, many corporate recipients have Google Drive links blocked by their organization's security policies. Compressing your PDF below 15MB ensures it arrives as a direct attachment that every recipient can open without clicking external links or requesting access permissions. Microsoft Outlook (both desktop and Outlook.com) imposes a 20MB limit for email attachments. The desktop application connected to an Exchange server may have an even lower limit — many enterprise IT departments configure Exchange to reject messages with attachments exceeding 10MB or 15MB. If you regularly email documents to corporate recipients, targeting 10MB rather than 15MB provides a safety margin against unknown server-side restrictions. Yahoo Mail allows 25MB per message, matching Gmail. Apple Mail (iCloud) supports up to 20MB for direct attachments but offers Mail Drop for files up to 5GB — however, Mail Drop links expire after 30 days and are not suitable for permanent document delivery. ProtonMail limits attachments to 25MB. Zoho Mail caps at 20MB for free accounts and 40MB for paid plans. Beyond email, file upload portals impose their own size restrictions. The US federal court PACER/CM-ECF system limits individual PDF uploads to 35MB. The IRS e-filing system caps document attachments at 15MB. Many university application portals (Common App, UCAS) limit supplementary document uploads to 10MB. Insurance claim portals frequently restrict uploads to 5-10MB per document. Real estate transaction platforms like Dotloop and DocuSign accept up to 25MB per document but process faster with smaller files. Compression to under 15MB covers the vast majority of these scenarios. For the strictest portals (5-10MB limits), LazyPDF's Screen quality preset (72 DPI) or a split-and-send approach handles edge cases. When your target is under 1 MB entirely — required by some WhatsApp workflows, insurance portals, or low-bandwidth upload systems — our dedicated guide on <a href="/en/blog/compress-pdf-to-under-1mb-free-online">compressing a PDF to under 1 MB free online</a> covers the exact settings that reach that threshold. The 15MB target specifically provides headroom below Gmail's 25MB and Outlook's 20MB limits while staying within IRS, university, and insurance portal requirements — it is the single most practical universal target for document compression.

Understanding why your PDF exceeded 15MB in the first place helps you prevent bloated files in future workflows and select the right compression strategy for the current file. The dominant cause of oversized PDFs is embedded raster images stored at excessive resolution. A 12-megapixel smartphone camera produces images at 4000x3000 pixels. When pasted into a Word document and exported to PDF, that single image occupies approximately 8MB of compressed JPEG data — or up to 36MB if stored as uncompressed TIFF inside the PDF wrapper. Microsoft Word, Google Docs, and Apple Pages all embed images at their native camera resolution regardless of the document's page dimensions. A photo displayed at 3x2 inches on the page is still stored at 4000x3000 pixels internally. Ghostscript compression solves this by downsampling the image to match the target output resolution: at 150 DPI, that same 3x2 inch image needs only 450x300 pixels — a 98.8% reduction in pixel count that translates directly to proportional file size savings. PowerPoint and Google Slides are the most prolific generators of bloated PDFs. These tools embed every image, icon, and background graphic at full original resolution and apply zero optimization during PDF export. A 30-slide deck with one background image per slide and six embedded photographs typically exports at 40-80MB. The same content compressed at Ebook quality (150 DPI) reaches 3-7MB — an order of magnitude smaller — because the screen-optimized images at 150 DPI contain all the detail a 1080p or 4K display can render. Scanned documents represent the second most common source of oversized PDFs. Flatbed scanners and multifunction office devices default to 300-600 DPI scanning resolution, which is appropriate for archival purposes but vastly exceeds the requirements for email distribution. A single page scanned at 600 DPI in color produces approximately 24MB of raw image data (TIFF). Even compressed as JPEG inside the PDF, each page occupies 1.5-3MB. A 20-page scanned document at 600 DPI reaches 30-60MB before any optimization. Downsampling to 150 DPI cuts the per-page size by approximately 75% while maintaining full readability for text, signatures, stamps, and standard business graphics. Font embedding contributes a smaller but consistent bloat factor. A PDF that uses the full Adobe Garamond Pro font family (regular, italic, bold, bold italic) embeds approximately 1.2MB of font data. If the document uses only 120 of the font's 2,400+ glyphs, font subsetting removes the unused glyphs and reduces the embedded font data to roughly 80KB. Ghostscript performs this font subsetting automatically during compression. For documents using multiple decorative or multilingual fonts — common in marketing materials, multilingual contracts, and design-heavy reports — font subsetting alone can reduce file size by 2-5MB. Duplicate embedded resources inflate PDFs exported from certain authoring tools. When a company logo appears in the header of every page, a naive PDF generator embeds the logo image independently on each page. A 200KB logo repeated across 50 pages adds 10MB of redundant data. Ghostscript's object deduplication detects these identical resources and stores them once with cross-references, eliminating the duplication entirely. This single optimization explains why some PDFs compress dramatically (80%+) even when their images are already at reasonable resolution — the compression is coming from deduplication rather than downsampling.

For files that remain above 15MB after standard Ebook compression — typically photo portfolios, product catalogs, and image-heavy reports exceeding 100MB — these advanced techniques provide additional reduction without requiring you to sacrifice content. The split-compress-merge workflow handles heterogeneous documents that contain a mix of text pages and photo-heavy pages. A 120-page annual report might have 100 pages of financial tables and narrative text alongside 20 pages of full-bleed executive photographs and office images. Compressing the entire document at 300 DPI (to preserve photo quality) wastes compression headroom on the 100 text pages that would compress identically at any DPI. Use /en/split to separate the document into a text section (pages 1-80, 95-120) and a photo section (pages 81-94). Compress the text section at Screen quality (72 DPI) and the photo section at Ebook quality (150 DPI). Merge the results with /en/merge. This segmented approach typically achieves 15-25% additional reduction compared to single-preset compression. For the annual report example, this means the difference between a 14MB file and a 10MB file. Removing unnecessary pages before compression amplifies the results. Business PDFs frequently contain blank separator pages, duplicate title pages, appendices the recipient does not need, or draft watermark pages left over from the review cycle. Use /en/organize to delete these pages before running compression. Eliminating 5 blank pages from a 30-page scanned document removes roughly 5-15MB of image data that would otherwise consume compression processing time and contribute to the final file size. For documents that absolutely must stay under a specific size limit but exceed that limit even at Screen quality, converting embedded color images to grayscale provides a final reduction lever. Color images store three channels (red, green, blue) of pixel data. Grayscale stores one channel. For scanned documents of originally black-and-white content — contracts, tax forms, invoices, typed letters — the color channels contain no meaningful information, and converting to grayscale reduces image data by approximately 60-67% with zero perceptible quality change. A 20MB color scan of a monochrome contract that compresses to 4.2MB at Ebook quality can reach 1.8MB with grayscale conversion applied first — a 57% additional saving. Image extraction and replacement is a manual but effective technique for extreme cases. If a single high-resolution photograph is responsible for most of a PDF's file size, use /en/extract-images to pull it out, resize it externally to the dimensions actually needed (matching the display size on the PDF page), and then reconstruct the document. A 25MB PDF containing one 20MB satellite image embedded at 8000x6000 pixels, where the image displays at 6x4 inches on the page, only needs a 900x600 pixel version at 150 DPI. Replacing the original with the correctly sized image reduces that single page from 20MB to approximately 200KB.

1. 1Step 1: Compress the file at Ebook quality (150 DPI) first. Check the output size. If it is below 15MB, you are done — no advanced techniques needed.
2. 2Step 2: If the output exceeds 15MB, re-compress at Screen quality (72 DPI). This aggressive preset works for documents that will only be viewed on screens and never printed.
3. 3Step 3: If Screen quality still produces a file over 15MB, use /en/split to divide the document into sections of roughly equal page count. Compress each section separately and send them as separate attachments or upload them individually.
4. 4Step 4: For scanned documents of originally black-and-white content, convert color images to grayscale before compression. This removes redundant color channel data and typically saves an additional 50-67% on top of standard compression.
5. 5Step 5: As a last resort, use /en/extract-images to identify oversized embedded images, resize them externally to match their display dimensions on the page, and reconstruct the document using /en/image-to-pdf.

Concrete data removes guesswork from compression planning. These benchmarks were measured using LazyPDF's Ghostscript 10.02 engine at Ebook quality (150 DPI), the recommended default for email and upload scenarios. PowerPoint-to-PDF exports show the most dramatic compression results because presentation software embeds images at wildly excessive resolutions. A 30-slide sales deck with product photos: 42MB original, 4.8MB compressed (88.6% reduction). A 60-slide conference presentation with charts and screenshots: 55MB original, 6.1MB compressed (88.9% reduction). A 15-slide pitch deck with full-bleed background images: 28MB original, 3.2MB compressed (88.6% reduction). Every one of these files drops comfortably below 15MB in a single compression pass. Scanned documents compress reliably in the 78-92% range depending on scan resolution and color depth. A 25-page color scan at 300 DPI: 18MB original, 2.4MB compressed (86.7% reduction). A 50-page grayscale scan at 600 DPI: 35MB original, 3.8MB compressed (89.1% reduction). A 10-page mixed scan with photographs and handwritten notes: 12MB original, 1.9MB compressed (84.2% reduction). Scans originally captured at 600 DPI see the largest absolute reductions because the downsampling from 600 to 150 DPI discards 93.75% of pixel data that was invisible at normal viewing magnification. Word and Google Docs exports fall in the middle range. A 40-page report with six embedded charts: 15MB original, 1.8MB compressed (88% reduction). A 100-page legal contract (text-only, no images): 5.2MB original, 420KB compressed (91.9% reduction). A 25-page marketing proposal with product screenshots: 22MB original, 3.1MB compressed (85.9% reduction). Text-heavy documents consistently achieve 90%+ compression because font subsetting and stream deduplication handle the bulk of the reduction without touching any image data. Already-optimized PDFs from professional design tools offer limited headroom. An Adobe InDesign magazine layout: 18MB original, 15.2MB compressed (15.6% reduction). An Affinity Publisher brochure: 8MB original, 6.9MB compressed (13.8% reduction). These files were optimized during export by their authoring applications. Attempting aggressive compression risks introducing JPEG artifacts on images that were already carefully optimized, with minimal size benefit. For these files, the split-and-send approach is more effective than further compression. The critical insight from these benchmarks: if your file came from PowerPoint, Word, Google Slides, or Google Docs, compression at Ebook quality will almost certainly bring it under 15MB in a single pass. If your file came from Adobe InDesign, Affinity Publisher, or another professional design application, compression yields limited results and you should consider splitting the document instead.

When standard compression does not achieve your target size, systematic diagnosis identifies the bottleneck and points to the correct solution. These troubleshooting steps cover every scenario users encounter in practice. The most common reason a compressed file stays large is that the document contains a small number of very high-resolution photographs that dominate the total file size. A 100-page document might have 95 text pages contributing 500KB total and 5 photo pages contributing 14MB. Compressing the entire document at Ebook quality reduces those 5 photo pages by roughly 80% (from 14MB to 2.8MB) — but if the photos were taken at 50 megapixels or embedded from a professional camera RAW export, even the compressed images remain substantial. For these cases, use /en/pdf-to-jpg to export the photo pages as images, resize them to the actual dimensions needed, convert them back with /en/image-to-pdf, and merge with the text pages using /en/merge. Password-protected PDFs that fail to compress are another frequent issue. Ghostscript cannot process PDFs encrypted with a user password (the type that requires a password to open). The compression tool will return an error or produce no size reduction. Solution: use /en/unlock to remove the password, compress the unlocked file, then re-protect with /en/protect if security is required for the final distribution. Corrupted or malformed PDFs sometimes resist compression. If a PDF was generated by a non-standard tool, web scraper, or older software version, the internal structure may contain errors that prevent Ghostscript from optimizing effectively. Symptoms include minimal compression (under 5% reduction) or a compressed file that is larger than the original. For these files, open the PDF in a standards-compliant viewer (Adobe Acrobat, macOS Preview, or Chrome's built-in PDF viewer), use the Print to PDF function to regenerate a clean PDF from the rendered output, and then compress the regenerated file. This re-rendering fixes most structural issues and restores normal compression behavior. Files containing embedded multimedia (audio, video, 3D models) will not compress significantly because Ghostscript processes image and text streams but does not re-encode multimedia content. A PDF with an embedded video will retain the full video file size regardless of compression settings. The solution is to remove the multimedia elements, host them separately (YouTube, Vimeo, cloud storage), and replace them with hyperlinks in the PDF. If your compressed file lands at 16-17MB — tantalizingly close to the 15MB target — switching from Ebook to Screen quality (72 DPI) typically provides the additional 15-30% reduction needed. The quality trade-off is visible softness in photographs when zoomed past 50% or when printed, but for email attachments viewed on screen at normal magnification, the difference is imperceptible to most recipients. For a file at 16.5MB after Ebook compression, Screen quality would typically produce an 11-12MB output.

Compression is a corrective measure. Preventing bloated PDFs during document creation eliminates the compression step entirely and produces cleaner, faster-loading files from the start. In Microsoft Word, resize images before inserting them into the document. Right-click any image, select Size and Position, and set dimensions to match the actual display size on the page. Then use File, Options, Advanced, and under Image Size and Quality, check the box for "Do not compress images in this document" to disable Word's own low-quality compression — but set the Default Resolution to 150 PPI. This combination ensures Word stores images at a reasonable resolution without applying its own aggressive JPEG compression that degrades quality without optimizing file size effectively. A document created with 150 PPI image resolution from the start will export to PDF at 2-5MB instead of 20-50MB. In Google Slides, avoid dragging full-resolution photographs directly onto slides. Instead, resize images to 1920x1080 pixels (matching standard presentation resolution) before inserting them. A 12-megapixel photograph at 4000x3000 pixels occupies 8MB. The same photograph resized to 1920x1080 occupies 600KB — a 92.5% reduction before the PDF export even occurs. For a 30-slide deck, pre-resizing images can reduce the export size from 60MB to 6MB. Scanner settings directly control output file size. For documents intended for email distribution rather than archival storage, scan at 150 DPI instead of the default 300 or 600 DPI. Scan in grayscale instead of color for black-and-white documents. These two changes alone reduce per-page file size by 75-90% at the source. A 20-page document scanned at 150 DPI grayscale produces a 2-3MB PDF — no compression needed. The same document scanned at 600 DPI color produces a 40-60MB PDF that requires compression to become email-friendly. When exporting from Adobe InDesign or Illustrator, use the Smallest File Size preset in the PDF export dialog. This applies intelligent compression during export, producing a file that is already optimized and will see minimal additional benefit from post-export compression tools. For web-distribution PDFs, select the resolution at 72 DPI in the Compression panel. For print-and-screen hybrid distribution, select 150 DPI. For teams that regularly share PDFs via email, establishing a company-wide standard of 150 DPI for all non-archival PDF exports eliminates the vast majority of oversized file incidents. A single line in a document template guide — "Export all PDFs at 150 DPI unless destined for commercial printing" — prevents hundreds of compression workflows per year across a typical 50-person office.