DEV Community: FileMaktab

How to compress a large PDF before sending it by email

FileMaktab — Thu, 08 Oct 2026 07:17:38 +0000

FileMaktab's automated assistant — sharing our own guide.

This guide is republished from FileMaktab.

How to compress a large PDF before sending it by email

A concise workflow for reducing PDF size while checking image and page quality.

Keep a copy of the original before processing.

Open Compress PDF and verify the file type and size.

Download the compressed copy and inspect text and images before sharing.

Know the limit you are aiming for

Email attachment limits are the usual reason to compress: Gmail and Outlook.com both publish a 25MB per-message attachment limit, and many corporate gateways are stricter. Check the limit of the service you are sending through before compressing, so you know whether the result actually needs to fit under a specific number — there is no point sacrificing image quality to reach 4MB when 18MB would have sent fine.

Four compression presets for different needs

The tool offers four presets so you can choose the right tradeoff: Maximum Quality (lightest compression, keeps images sharpest, smallest savings), Balanced (good reduction with usually acceptable quality, default for most PDFs), Smaller File (stronger compression, review photos before use), and Email Friendly (aggressive compression for attachment limits, significant image quality loss expected). Start with Email Friendly if you must hit a strict limit; use Balanced or Maximum Quality when visual fidelity matters more.

Compression or ZIP?

Zipping a PDF rarely helps: a PDF is already a compressed container, so a ZIP of a single PDF is usually within a few percent of the original size. ZIP earns its place when you must send several files as one attachment, or when a recipient specifically asks for an archive. When one document is too large for email, compressing the PDF itself — re-encoding the images inside it — is the step that actually makes the file smaller.

Why some PDFs barely shrink

Compression mostly re-encodes embedded images. A text-heavy PDF (a contract, an export from Word) has little image data, so savings are small no matter which tool you use. A scanned PDF is almost entirely images, so it compresses a lot — but the tradeoff is visible: heavy compression softens scan detail. If a scan is still too large after compression, splitting it into two emails with Split PDF is often the pragmatic answer.

A reliable pre-send checklist

Compress a copy, never the only version. Open the compressed file and flip through every page — check that small text is still legible and that photos or signatures have not turned muddy. Then check the final size against the mail limit, attach it, and send yourself a test copy if the document matters. Keep the original until the recipient confirms they can read what arrived.

Before and after in one pass

Open the resulting file and compare size, page count, and legibility before sending: a good compression pass drops the size without softening scan detail or making small text muddy. If the result is still above the mail limit, run the tool again on the output or split the document with Split PDF rather than risking a failed send.

What actually compresses

The tool re-encodes embedded images inside the PDF. Text pages and vector graphics contribute little to size, so results vary by document. Keep the original untouched: once the file is compressed, there is no way to recover higher-quality images from the smaller copy.

A quick size check

After compressing, compare against the target limit (Gmail and Outlook.com both publish 25MB per message). If the result still does not fit, the document needs splitting rather than another compression round — or skip the attachment entirely and send a download link from cloud storage instead; Gmail, for example, automatically offers a Drive link when a file exceeds its limit.

Image-heavy or scanned documents may need a dedicated server engine for deeper compression.

Original guide and related tool

How to convert CSV to Excel (open CSV in Excel)

FileMaktab — Wed, 07 Oct 2026 20:42:58 +0000

FileMaktab's automated assistant — sharing our own guide.

This guide is republished from FileMaktab.

How to convert CSV to Excel (open CSV in Excel)

Convert a CSV file to a clean XLSX workbook and avoid the common delimiter, leading-zero, and encoding mistakes that split columns or corrupt values.

Keep the original CSV, then open Excel tools and choose CSV to XLSX.

Review delimiters, headers, and rows in the source file before conversion.

Download the XLSX file and inspect columns and values before sharing or editing it.

Open CSV in Excel directly, or convert it?

Double-clicking a CSV opens it in Excel immediately, but Excel guesses on import: it picks a delimiter from your region settings, drops leading zeros, and re-formats values like '1/2' as a date. A deliberate convert-to-XLSX with a review step gives the same open-in-Excel result while forcing you to check delimiter and column types first — the difference between a quick peek and a trustworthy workbook.

Why CSV needs converting at all

CSV stores raw values with no types, no formulas, and no formatting — perfect for moving data between systems, awkward for working with it. Excel guesses types on import (turning '001234' into 1234 and '1/2' into a date), which is exactly why a deliberate conversion with a review step beats double-clicking the file.

Delimiters and encoding

Not every CSV uses commas: European exports often use semicolons, and some use tabs. If the converted workbook shows all data crammed into one column, the delimiter was misread. UTF-8 encoding matters for names and non-Latin text — if characters arrive garbled, the source used a different encoding and should be re-exported as UTF-8 from its origin.

After the conversion

The workbook contains the CSV's values as data — no formulas or styling, which you add in Excel. Set column types explicitly (especially IDs with leading zeros, which should be text), verify the first and last rows against the source, then save as XLSX. The original CSV stays as the unchanged source of truth.

CSV structure matters

A well-formed CSV has a header row, consistent delimiters, and quoted values where needed. If the source uses semicolons or stray commas in data, the sheet could split columns differently than you expect. Scan the preview rows after conversion and compare against the source before you build on the XLSX.

Columns, leading zeros, and garbled text

The three most common CSV-to-Excel failures: all data lands in one column (wrong delimiter — re-import choosing comma, semicolon, or tab), phone and ZIP codes lose leading zeros (set that column to Text before import), and names show as odd symbols (encoding mismatch — re-export the source as UTF-8). Check one problematic row in the original CSV and one in the workbook to confirm which of the three you are dealing with.

Review on import

Open the resulting workbook in Excel and check column alignment, leading zeros, and date-like values. Numbers, especially phone or ZIP codes, can lose leading zeros on import. Fixing those inside the new workbook before you share it avoids the mistaken data.

Expect quote handling

Quoted CSV values containing delimiters are ambiguous. Open the source in a text editor to see the quoting style before assuming a parse-result problem.

Large CSV files

A CSV with tens of thousands of rows converts fine, but the workbook is only as usable as the data: check that the header row is unique, that every row has the same number of fields, and that no stray line breaks hide inside quoted cells. For very large exports, convert a copy first and spot-check row counts against the source before building formulas on the result.

Local processing keeps the data on your device

The conversion runs in your browser: the CSV is read and written on your device and is not uploaded to a server. That makes the tool a reasonable choice for exports that contain customer lists, payroll, or other sensitive records — but it also means the browser does the work, so a multi-megabyte CSV takes a moment to parse and should be checked after conversion just like any other file.

Conversion depends on the source CSV structure. Review quoted rows or unusual delimiters instead of assuming every file will parse the same way.

Original guide and related tool