What file size should I aim for?

Aim for the smallest size that passes the platform check while remaining readable. For most portals, 1-10 MB is typical; for email, 5-20 MB is common; and for forms with strict limits, 500 KB-2 MB may be required.

Will compression make my document blurry?

It can, if the tool downscales images too aggressively or applies heavy JPEG compression. Use moderate settings first, keep text as vector when possible, and preview at 100% zoom before submitting.

Why does my PDF get bigger after I edit it?

Many editors embed new resources (fonts, duplicated images, incremental save layers). A final optimisation pass and removing unused objects often restores a smaller file.

Is it better to split or compress?

Compress first if quality can be preserved. Split when the target limit is extremely low, when a portal rejects certain content types, or when you need separate uploads for different document categories.

Do online tools keep my files?

Policies vary. For sensitive files, avoid uploading personal documents to untrusted services, remove metadata, and consider local workflows when possible.

What’s the difference between DPI and quality?

DPI is resolution for print and scan; quality is the compression strength. A 300 DPI scan can still look poor if quality is too low. Conversely, 150-200 DPI at a reasonable quality can remain very readable.

Can I compress without losing text search?

Yes. If the PDF contains real text (not just images), keep it as text and only compress embedded images. If it is scanned, consider OCR to add searchable text while optimising the images.

What should I do if the portal still rejects my file?

Re-check allowed formats, remove passwords, flatten forms if required, ensure page count limits are met, and try exporting to PDF/A or standard PDF if the portal has strict validators.

How to Merge PDFs Without Increasing File Size

Combining two 1MB PDF files in standard desktop software often yields an output file of 3.5MB or 4MB. This counter-intuitive size inflation causes uploads to bounce against strict 2MB institutional submission thresholds. File bloat during merging is not inevitable: it stems from how legacy PDF engines duplicate embedded binary assets. Merging documents using clean structural referencing combines your files while maintaining strict byte economy.

Direct Utility: Use Merge PDF Online to combine multiple documents into a single compact file without copying duplicate system overhead.

The Anatomy of Merged PDF Bloat: Why 1MB + 1MB = 4MB

When software concatenates two PDF files, naive implementations treat each file as a closed black box. Instead of consolidating shared assets, legacy utilities append the complete internal data structures of File B to the end of File A, causing predictable file growth:

Duplicated Font Binary Subsets: If your resume, cover letter, and reference sheets all utilize Arial, Calibri, or Times New Roman, a naive merger writes three separate copies of the underlying TrueType font programs into the final PDF. Each embedded font program adds 40KB to 250KB of uncompressed binary data.
Redundant ICC Color Profiles: Scanned color documents contain International Color Consortium (ICC) profiles that define RGB or CMYK device characteristics. When combining four individually scanned certificates, legacy mergers embed four identical 500KB ICC color profiles into the /ColorSpace dictionary, wasting 1.5MB on duplicate color lookup tables.
Stacked XMP Metadata and Incremental Revision Trees: Every time a PDF is edited in desktop applications, historical change logs and Adobe Extensible Metadata Platform (XMP) XML packets are appended. Concatenating multiple edited files bundles years of discarded revision logs into your active upload.
Recursive Page Tree Nesting: Conforming PDF specifications require a balanced tree structure in the /Pages object. Sluggish merge routines nest dictionaries arbitrarily, bloating the cross-reference (XREF) table with thousands of unnecessary object byte pointers.

Clean Merge Mechanics: How In-Browser Assembly Prevents Bloat

Modern browser-based PDF engines operate directly on raw byte streams within local memory. Clean merging eliminates file inflation through three architectural steps:

Resource Dictionary Deduplication: Identical font programs, graphics state parameters (/ExtGState), and color maps are mapped to single shared object IDs. If ten pages use the same standard font dictionary, the font is stored once and referenced ten times.
Metadata Sanitation: Legacy document histories, discarded software revision logs, and oversized thumbnail image caches are stripped from the file trailer. Only essential document properties (such as title and page dimensions) are retained.
Flat Page Hierarchy Assembly: The /Pages dictionary is reconstructed as a clean, single-level array. This structure minimizes the cross-reference table footprint and accelerates rendering on mobile devices and browser preview plugins.

Pre-Merge Optimization Checklist

Ensuring that your combined file stays below strict upload ceilings begins before clicking the merge button. Execute these preparatory checks:

Downscale Image Scans Prior to Assembly: An uncompressed 600 DPI document scan can weigh 8MB for a single page. Downscale color scans to 200 DPI or 300 DPI prior to merging. Text remains razor-sharp for human verification while file size drops by up to 80 percent.
Standardize Document Dimensions: Confirm that your component files share compatible dimensions. Mixing US Letter (8.5 x 11 inches) with European A4 (8.27 x 11.69 inches) can cause display inconsistencies in institutional viewers.
Eliminate Blank Separator Sheets: Office scanners often inject blank trailing pages at the end of double-sided scans. Remove these blank sheets using Delete PDF Pages to prevent wasted byte allocation.

Four-Document Application Bundle: Staying Under 2MB

Consider a standard consular visa or university submission requiring a cover letter, resume, passport scan, and two reference letters. The upload slot has a hard 2.0MB limit. Follow this exact workflow to guarantee compliance:

Audit Component Sizes: Ensure your cover letter (digital vector PDF) is under 100KB, your resume (vector PDF) is under 200KB, your reference letters are under 300KB, and your scanned passport bio page is under 800KB. Total initial weight should sit around 1.4MB.
Sequence the Files: Load all four documents into Merge PDF. Arrange them in logical reviewer order: Cover Letter first, followed by Resume, Passport Scan, and References.
Execute the Merge: Run the clean merge operation. Because the tool does not duplicate shared system fonts, the resulting document will weigh roughly 1.45MB, comfortably below the 2MB threshold.
Verify Binary Boundary: Open the file properties on your local device. Ensure the total file size does not exceed 2,097,152 bytes (2MB binary).

Platform Attachment and Upload Thresholds

Platform / Service	Hard Upload Ceiling	Format Constraints	Key Merging Consideration
Schengen Visa Portals (VFS, TLS)	2MB to 5MB per slot	PDF only, no password encryption	Keep scans at 200-300 DPI to avoid exceeding 2MB
Gmail / Yahoo Mail	25MB per email	Base64 encoding expands size by ~33%	Raw file should not exceed 18MB to pass attachment filter
Microsoft Outlook / Exchange	20MB default ceiling	Server-side Exchange message cap	Keep combined bundle under 15MB for enterprise relays
WhatsApp Document Sharing	2GB (Documents) / 16MB (Media)	Send as Document, not Image gallery	Documents retain 100% original quality without compression
US Visa Portal (DS-160 Photo)	240KB maximum (600 x 600 px)	JPEG color format, square 1:1 ratio	Must be uploaded separately from supporting PDF bundles

Troubleshooting Merged Files That Exceed Size Limits

If your merged document surpasses your portal limit, take these targeted corrective actions:

Execute a Single Browser Compression Pass: Do not compress files before merging. Merge your high-quality files first, then pass the combined document through Compress PDF once. Running compression on the unified document allows the algorithm to optimize images globally across the entire page collection.
Split Multi-Page Financial Records: If 12 months of bank statements tip the file over the 2MB ceiling, use Split PDF to divide the financial bundle into two sequential 6-month files.
Flatten Interactive Form Fields: Fillable PDF forms retain heavy Acrobat Forms (AcroForm) or XML Forms Architecture (XFA) schemas. Flattening form fields converts interactive boxes into standard page content, eliminating schema overhead.

Frequently Asked Questions

Does merging multiple PDFs degrade the resolution of embedded text or diagrams?

No. Clean merging does not alter vector line art, TrueType text layers, or embedded raster images. The tool recombines existing structural streams without applying lossy compression filters.

Can I merge encrypted or password-protected PDF files?

PDFs secured with an owner restriction (such as copy or print locks) can be merged if permissions allow reading. Documents protected with an open password (requiring a passphrase simply to view the document) must be decrypted using their password prior to merging.

Are my merged documents stored on any server during processing?

No. The merging algorithm operates entirely within your browser sandboxed JavaScript environment using WebAssembly. Your files remain on your local device and are never transmitted over the internet.