Organize PDF files from one clean workspace. Combine documents in the right order, extract selected pages, or create a smaller sharing copy with transparent quality controlsβwithout installing desktop software.
Choose the job you need. Each tool has its own upload area and settings so files from one workflow do not accidentally carry into another.
Drag & Drop PDF files here
or click to select two or more documents
β Multiple .PDF FilesDrag & Drop a PDF here
or click to select one document
β One .PDF FileDrag & Drop a PDF here
or click to select one document
β One .PDF FileThe best PDF utility is not the one with the longest feature list. It is the one that makes the requested task obvious, protects the original document and explains exactly what will change in the output.
The interface changes with the selected tab, but the overall workflow stays predictable.
Merge, split and compress are often grouped under βPDF editing,β but they change a document in very different ways. Understanding those differences helps you pick the safest workflow.
A PDF is a document container that can hold page instructions, text, vector artwork, images, fonts, forms, annotations, links, attachments, metadata and security settings. A tool that merges PDF files usually copies pages from two or more source documents into a new container. A tool that splits a PDF copies only selected pages into one or more smaller documents. A tool that compresses a PDF has to change or remove somethingβcommonly image resolution, image quality, unused objects, duplicate resources or metadataβto reduce the number of bytes.
This page uses a conservative approach for merge and split operations: page objects are copied with PDF-lib rather than intentionally rendered as screenshots. That makes these two workflows suitable for ordinary page organization because they are designed to preserve the existing page appearance. The compression workflow is deliberately different. It renders selected pages with PDF.js, converts the rendered result to JPEG and creates a new image-based PDF. This can be effective for scans, photographed pages and image-heavy presentations, but it changes the document from a structured PDF into a visual copy.
PDF merging combines complete pages in a chosen sequence. Imagine that you have a cover letter, a report, several appendices and a signed approval page. Instead of sending five separate attachments, you can arrange the files and create one document. The first source file appears first, followed by the second and so on. Reordering before the merge is therefore important because the software cannot infer your intended reading order.
The merge tool on this page counts pages before creating the output and provides drag, up and down controls. It copies pages from each loaded document into a new PDF. The source files are never edited. This is useful for application packages, client deliverables, invoices, project records, class submissions and any situation where the recipient expects a single attachment.
Splitting is the reverse organizational task. A large document may contain chapters, account statements, forms or attachments that need to be distributed separately. Entering a range such as 1-3, 7, 10-12 tells the tool which pages to include. You can combine those selected pages into one new PDF, or create one small PDF per selected page and download the collection as a ZIP.
Page extraction is also useful when a portal has strict page limits, when a colleague needs only one section, or when a scan includes blank and irrelevant pages. However, page numbers should be checked carefully. The number printed on the page may not match the PDF viewerβs page index because a report can contain unnumbered covers or Roman-numeral front matter. The page range field uses the PDFβs actual sequence starting from page 1.
Compression is not a single universal operation. Some desktop tools inspect every object and selectively recompress images, subset fonts or remove unused data. A browser page without a full commercial PDF optimization engine has fewer safe options. This page therefore offers a clearly labeled rasterized compression method. Each page is rendered at a chosen scale, encoded as a JPEG and embedded into a new PDF page with the same approximate proportions.
The advantage is simplicity: image-heavy PDFs can become much smaller, especially when the source contains high-resolution scans. The tradeoff is equally important: text is no longer selectable or searchable unless a separate OCR layer is added, links and form controls disappear, signatures are no longer digitally valid, annotations become part of the picture, and fine vector lines may soften. Always keep the original master and use the compressed result as a delivery copy.
PDF is standardized through the ISO 32000 family. Readers who need the technical background can use the PDF Association specification index. This page uses the official Mozilla PDF.js project for browser rendering and the PDF-lib documentation for page copying and PDF creation. Temporary downloads use browser Blob URLs described by MDN Web Docs.
Users often need more than one operation. You might merge monthly reports, split out confidential pages and then make a smaller copy for email. A three-tab workspace keeps the visual language and settings consistent while preventing the tools from sharing the wrong file list. It also makes the tradeoffs visible in one place: merge and split are page-copy operations, while the compressor creates a rasterized derivative.
Use the table to choose the operation that matches your actual goal.
| Goal | Best Tool | What Changes | Main Caution |
|---|---|---|---|
| Combine several attachments | Merge PDF | Page order and document container | Check sequence before downloading |
| Send only selected pages | Split PDF | Only chosen pages are copied | Viewer page number may differ from printed number |
| Create one PDF per page | Split PDF to ZIP | Each chosen page becomes its own PDF | Many pages create many small files |
| Reduce a scan for email | Compress PDF | Pages are rasterized and JPEG-compressed | Text, links and forms are flattened |
| Preserve a signed archival master | Do not raster-compress | Use the original or specialist archival software | Any rewrite may invalidate signatures |
| Remove unnecessary pages before sharing | Split PDF | Creates a smaller document by excluding pages | Review for accidental omissions |
Merging is simple technically, but the quality of the final document depends on preparation and sequence.
Before uploading files, decide what the recipient should see first. A professional package often follows this order: cover, contents, main report, evidence, appendices and approvals. Rename local files with numbers such as 01-cover.pdf and 02-report.pdf if you manage many sources. The on-page order controls the final result, but clear local names reduce mistakes.
A merged PDF may contain portrait, landscape, A4, Letter and custom-sized pages. That is valid, but the viewer may zoom or rotate between sections. This tool preserves source page dimensions rather than forcing every page onto one paper size. Standardize pages in a dedicated editing workflow first when consistent printing is essential.
Copying PDF pages can preserve their visible appearance, but complex interactive behavior is not guaranteed across every source. Duplicate form field names from multiple documents may conflict. Document-level bookmarks and attachments may not transfer. Cryptographic signatures generally apply to the exact bytes of the signed document, so merging creates a new unsigned container and can invalidate original signature status. Keep signed originals for verification.
Names such as merged-document.pdf work for quick testing, but a meaningful delivery name is better. Include the project, client, period or version: annual-report-2026.pdf, rental-application-complete.pdf or invoice-supporting-documents.pdf. Avoid confidential details in filenames when the document may pass through shared systems.
Splitting can mean extracting a chapter, removing pages or creating one file per page. Choose the output mode that matches the next step.
Smaller files are useful, but a responsible compressor should explain exactly what is being sacrificed.
The Smaller preset uses a relatively low JPEG quality and modest render scale. It can substantially reduce some scanned PDFs, especially when the original pages contain camera photos or very high-resolution images. Fine print, thin diagrams and small screenshots may become soft. Use this setting only when accessibility and exact reproduction are less important than transfer size.
The Balanced preset aims for a middle ground. It renders pages at a moderate scale and uses medium JPEG quality. This is often suitable for visually reviewing scans, presentations, receipts and reference documents. It is not appropriate for documents that depend on searchable text, accessibility tagging, digital signatures or interactive form fields.
The Sharper preset uses a larger rendered image and higher JPEG quality. The output may still be smaller than a scan-heavy original, but the reduction can be limited. It is the safer choice for small type, tables and diagrams when a rasterized sharing copy is acceptable.
A source PDF may already be efficiently optimized. A text-heavy PDF with vector graphics and compressed fonts can be much smaller than page-sized JPEG images. Rebuilding such a file as images can increase the size. The page reports the final byte count after processing, but it cannot guarantee a smaller result before rendering. When the result is larger, keep the original or use a specialist optimizer that can preserve document structure.
Tagged PDFs can provide reading order, headings, language information and alternative text to assistive technology. Rasterizing pages removes that semantic structure. A screen reader may see only images unless OCR is added later. For public documents, educational materials, workplace accommodations or government forms, accessibility should take priority over aggressive size reduction.
| Preset | Likely Use | Visual Quality | File Size Goal |
|---|---|---|---|
| Smaller | Temporary preview, low-bandwidth transfer | Reduced | Smallest of the three presets |
| Balanced | Email, messaging, ordinary web upload | Moderate | Balanced reduction |
| Sharper | Small text and diagrams | Best of the three | Larger output |
When a document needs more than one change, the order of operations can affect quality, convenience and final file size.
If a 100-page document contains only six pages that must be emailed, extract those six pages first. This avoids rendering and encoding 94 unnecessary pages. It also reduces processing time, memory use and the possibility of accidentally sharing information the recipient does not need. After splitting, compress the smaller result only when it still exceeds the upload or email limit.
When several scans must be delivered together, arrange and merge them first, then compress the combined file. This gives the entire package one consistent compression preset and one filename. The disadvantage is that every page becomes rasterized in the compressed copy. Keep the merged non-rasterized version as a higher-quality master when storage allows.
Repeated lossy processing can compound artifacts. If each source file is compressed separately and the final merged document is compressed again, text edges and images can degrade twice. Prefer one lossy compression pass near the end of the workflow. Merge and split operations themselves are not intended to introduce JPEG loss, so they can generally be performed before the final sharing copy is made.
Compression does not remove hidden information safely and is not a redaction tool. A rasterized copy may visually flatten annotations, but relying on that behavior for confidential redaction is unsafe. When the goal is to share only approved pages, split the document and inspect the result. When sensitive text exists on a page that must remain, use professional redaction software that removes content rather than covering it visually.
Business records, legal evidence, research material and public documents may have retention, accessibility or PDF/A requirements. The browser tools on this page are designed for everyday organization and sharing copies. They do not claim to validate PDF/A, preserve every document-level feature or certify regulatory compliance. Retain the authoritative original and use approved records-management software when the PDF is part of a controlled archive.
| Scenario | Recommended Order | Reason |
|---|---|---|
| Only a few pages are needed | Split β optional compress | Avoids processing and sharing unnecessary pages |
| Several scans must become one email attachment | Merge β compress once | Creates one consistently encoded delivery copy |
| High-quality pages from several sources | Merge only | Preserves existing page objects instead of rasterizing |
| One large report must become chapters | Split by chapter | Produces focused documents with exact page copies |
| Archival or legally controlled document | Preserve original; use specialist software | Compliance features require controlled validation |
Local processing improves privacy, but it moves the workload to your own device. The practical limit depends on the PDF and available memory.
A 20 MB PDF is not always easier to process than a 60 MB PDF. Page count, image resolution, transparency, embedded fonts and internal object complexity all affect memory use. Merge and split operations must parse the source structure and build a new document. Compression is more demanding because each selected page is rendered to a canvas, encoded as JPEG and embedded into the output.
Modern desktop browsers normally handle ordinary office documents and moderate scans well. Phones and low-memory tablets can struggle with many high-resolution pages. A browser may slow down, show a memory warning or close the tab when the workload exceeds available resources. For large jobs, close unnecessary tabs, use a desktop device, process fewer pages at a time and start with the Smaller or Balanced compression preset.
The page intentionally processes compression pages one at a time and releases each canvas after it is embedded. This reduces peak memory compared with keeping every rendered page image on screen simultaneously, but the source PDF and growing output document still occupy memory. There is no universal maximum file size that can be promised across all devices.
Contracts, statements, applications and business files can contain sensitive information, so the processing path matters.
The page uses browser file APIs and JavaScript libraries for the core operations. Merge and split use PDF-lib to load and copy pages. Compression uses PDF.js to render selected pages and PDF-lib to create the image-based result. Downloads are generated with temporary browser object URLs.
A few checks before and after processing can prevent the most common document mistakes.
Save merge, split and compressed results as new files. Never treat a generated copy as the only master until you have reviewed it.
After merging, scroll through every transition between source documents and check that no cover, appendix or signature page is misplaced.
Use the page number shown by the PDF viewer, not only the number printed on the document page.
Compression creates a new visual copy and cannot preserve cryptographic signature validity. Keep the signed original separately.
Many high-resolution pages can consume significant memory. Close unused tabs and use a desktop browser for large scans.
Removing unnecessary pages can reduce size without flattening the pages you keep.
Zoom in on tables, footnotes, diagrams and screenshots before sending the compressed copy.
PDF/A, PDF/X, accessibility remediation, redaction and legally significant signatures need controlled professional software.
Use the focused pages when you want a single-purpose workspace or need to share a direct tool link.
Clear answers about file quality, privacy, page ranges, compression and browser limits.
Choose a tool above, process your document in the browser and download a new copy while keeping the original file unchanged.
π Open the PDF Workspace β