PDF Tools
Merge, split, and compress PDF files directly in your browser. All processing happens locally on your device. No files are uploaded, no watermarks added, no daily limits.
Key features
- Seamlessly merge multiple PDFs with one click
- Split large files into page-based pieces
- Smart size reduction without sacrificing image quality
- Completely local processing without any data going to the server
Guide
PDF files are everywhere. They carry contracts, invoices, reports, manuals, tax forms, academic papers, and government documents. The format was created by Adobe in 1993 to preserve document layout across different operating systems and devices, and it succeeded so well that PDF became an ISO standard in 2008. Today, virtually every business and institution on the planet relies on PDFs for sharing finalized documents. But reading a PDF is easy. Doing something with it, like merging two files, pulling out specific pages, or shrinking a bloated file to fit an email attachment, typically requires specialized software. Most people reach for paid tools when they need to manipulate PDFs. Adobe Acrobat Pro costs around $20 per month. Nitro PDF runs about $14 per month. Even the popular web-based alternatives like Smallpdf and iLovePDF cap their free tiers at a handful of operations per day and then push you toward a subscription. For someone who merges PDFs once a week, paying for a subscription makes no sense. For someone who handles confidential documents, uploading files to a third-party server is a non-starter. WebRecast PDF Tools solve both problems by running entirely in your browser. Your files stay on your device, and there are no daily limits or watermarks. The merge function is the one most people need first. You have a cover letter and a resume as separate PDFs, and you need to combine them into a single file for a job application. Or you have five separate invoice PDFs from a vendor and you want one combined file for your records. With this tool, you drag in the files, arrange them in the order you want, and click merge. The output is a single PDF containing all pages from all input files, in the sequence you specified. The original formatting, fonts, images, and hyperlinks are preserved. This works because the tool uses pdf-lib, a JavaScript library that manipulates PDF structures directly without converting pages to images or re-encoding content. The merge operation handles more than simple concatenation. When you combine PDFs from different sources, each file may use different fonts, color profiles, and metadata structures. The tool resolves these differences by copying page objects into a new document and updating internal references. Bookmarks and table of contents entries from individual files are not merged into a combined outline, because automatic bookmark merging can create confusing navigation when the original documents have different organizational structures. If you need a combined table of contents, add it manually after merging. Splitting is the reverse operation. You have a 200-page manual and you only need chapter 3, which runs from page 45 to page 72. Instead of sending the entire file, you split out just those pages into their own PDF. You can split by specifying a page range, or you can split a PDF into individual single-page files. This is useful for distributing specific sections of a large document. Teachers split exam papers into individual questions. Lawyers split case files into exhibits. Project managers split combined reports into department-specific sections. The split function preserves the original page dimensions and content exactly as they appear in the source file. A common splitting scenario involves extracting specific forms from a multi-form PDF. Government agencies and insurance companies often distribute packets containing multiple forms in a single PDF. You only need to fill out and return two of the eight forms. Splitting lets you extract just those two forms without sending back the entire packet. Real estate transactions generate PDF packets with dozens of documents. Splitting the closing package into individual documents makes it easier to file and reference them later. Compression is where things get technically interesting. PDF files can be surprisingly large because they often contain high-resolution images embedded at full quality. A 50-page report with photos might weigh 30 MB or more. The compression function reduces file size by resampling embedded images to a lower resolution and applying more efficient encoding. Text content remains unchanged and fully searchable. The compression ratio depends on the content: image-heavy PDFs can shrink by 70% or more, while text-only PDFs may only drop by 10-15% since there is less to optimize. The important thing is that the tool does not flatten the PDF into an image. Text stays as text, hyperlinks remain clickable, and form fields continue to work. Understanding why PDFs get so large helps you use compression effectively. When you scan a document at 300 DPI, each page becomes a high-resolution image of about 8-10 MB. A 20-page scanned document easily reaches 200 MB. When you export a presentation with high-resolution photos on every slide, each embedded image adds several megabytes. When design software exports a PDF with CMYK images at print resolution, the file size reflects that quality level. The compression function targets these embedded images specifically, reducing their resolution and applying more efficient encoding while keeping text, vector graphics, and interactive elements untouched. Email attachment limits are one of the most common reasons people need PDF compression. Gmail limits attachments to 25 MB. Outlook limits them to 20 MB. Many corporate email servers set even lower limits. When your PDF exceeds these limits, you have three options: use a file sharing service, split the PDF into smaller parts, or compress it. Compression is the cleanest option because the recipient gets a single file without needing to access a separate sharing link or reassemble split parts. Privacy is a major concern with online PDF tools, and for good reason. When you upload a contract or tax return to a cloud-based PDF service, you are trusting that company to handle your sensitive data responsibly. Their servers store your file at least temporarily during processing, and their privacy practices vary widely. Some services retain uploaded files for hours or days. Some use uploaded content for analytics or machine learning. With WebRecast, this concern does not apply. The tool uses client-side JavaScript to process your files. The PDF data is read into your browser's memory, manipulated there, and the output is generated locally. Network traffic analysis will confirm that no file data leaves your machine during the operation. This local processing model has specific implications for regulated industries. Healthcare organizations subject to HIPAA cannot upload patient records to unvetted cloud services. Financial institutions subject to SOX and GLBA have strict rules about document handling. Legal firms bound by attorney-client privilege cannot risk exposing confidential documents to third-party servers. A browser-based tool that processes files locally avoids these compliance concerns entirely because the data never leaves the organization's device. The technical architecture uses Web Workers to handle PDF processing off the main thread. This means your browser stays responsive even when processing large files. The merge operation concatenates PDF page trees and resolves cross-references between objects. The split operation creates new PDF documents containing only the specified page objects and their dependencies. The compression operation iterates through embedded image streams and re-encodes them with optimized parameters. All of this happens in JavaScript using the pdf-lib library for structural operations and additional optimization routines for image compression. Let's walk through some real-world scenarios where these tools save significant time. Scenario one: a freelancer invoicing a client. You have your invoice as a PDF and your timesheet as another PDF. The client wants a single file. You open the merge tool, drop in both files, make sure the invoice is first and the timesheet is second, and merge them. Total time: about 15 seconds. Scenario two: a student submitting a homework assignment. The professor wants only the first three pages of your lab report. You open the split tool, upload the full report, enter the page range 1 to 3, and download the trimmed version. Total time: about 10 seconds. Scenario three: an accountant emailing tax documents. The compiled PDF with all supporting schedules is 25 MB, but the email provider caps attachments at 10 MB. You open the compression tool, upload the file, and the output comes back at 7 MB. The images are slightly lower resolution, but all text, tables, and form data are intact. Total time: about 20 seconds depending on file size. Scenario four: an HR department preparing onboarding packages. They need to merge a welcome letter, benefits summary, tax forms, and company policy document into a single PDF for each new hire. Doing this manually in Adobe Acrobat takes multiple steps. With the merge tool, they drop in all four files, arrange the order, and get one combined PDF. Scenario five: a real estate agent preparing listing presentations. Each listing requires a package with property photos, comparable sales, neighborhood data, and marketing materials from different sources. Merging these into a single polished PDF package, then compressing it for email distribution, takes under a minute with the merge and compress tools used in sequence. Scenario six: an academic researcher preparing a grant application. The funding agency requires a single PDF containing the proposal, budget spreadsheet export, CVs of all investigators, letters of support, and institutional authorization forms. Each document comes from a different person in a different format. Merging them into one file with the correct page order meets the submission requirement. There are some limitations to be aware of. Because processing happens in the browser, very large files (over 100 MB) may be slow on devices with limited memory. Encrypted or password-protected PDFs need to be unlocked before they can be processed. The compression function works best on PDFs that contain raster images. PDFs that are mostly vector graphics and text have less room for compression. The tool does not currently support adding passwords, editing text within a PDF, or converting PDFs to other formats like Word or Excel. It focuses on the three most common operations: merge, split, and compress. For developers interested in the technical details, the PDF format is essentially a structured collection of objects. Each page is an object that references content streams, font resources, and image resources. Merging two PDFs involves copying page objects from one file into another and updating the page tree to include them. This sounds simple, but PDFs can have complex cross-reference tables, shared resources, and nested object hierarchies. The pdf-lib library handles these complexities by parsing the full object graph and resolving references during copy operations. The PDF specification defines several types of content streams. Page content streams contain the drawing commands that produce the visible page. Font streams contain embedded font data. Image streams contain raster image data. Metadata streams contain document properties. During compression, the tool identifies image streams specifically and applies optimization to those while leaving other stream types unchanged. This targeted approach preserves document functionality while reducing the data that accounts for most of the file size. Compression works at the stream level. PDF images are stored as streams with various encoding filters. A common pattern is a JPEG image stored within a FlateDecode stream. The compression function decodes these streams, re-encodes the image data with optimized quality settings, and writes the compressed stream back. For images originally embedded at 300 DPI, reducing to 150 DPI can cut image data in half while remaining perfectly readable on screen. For images at 600 DPI (common in scanned documents), reducing to 200 DPI maintains excellent print quality while reducing the file to one-ninth of its original image data size. Here are some best practices for working with PDFs effectively. First, always keep original copies of your source files before merging or compressing. While the tool does not modify your original files (it creates new output files), maintaining source copies is good document management. Second, when merging many files, consider the page order carefully before processing. Rearranging pages after merging is harder than getting the order right upfront. Third, compress as a final step. If you are merging several files and the result is too large, run the merged output through compression. This can be more efficient than compressing each file individually because the compression pass can optimize shared resources across the combined document. Fourth, for repeated tasks, bookmark the tool in your browser. Having instant access to merge, split, and compress without navigating to a website, logging in, or checking remaining free uses removes friction from your workflow. When choosing compression levels, consider the end use. For PDFs that will only be viewed on screens, aggressive compression (lower quality images, lower DPI) is acceptable because screen resolution is limited to 72-150 DPI. For PDFs that will be printed, keep compression moderate to preserve image quality at print resolution (typically 150-300 DPI). For archival purposes, use minimal compression to preserve the highest quality. The right compression level depends on whether the recipient will be reading on screen, printing at home, or sending to a professional print shop. Batch processing is a workflow pattern that saves significant time for users who handle PDFs regularly. An office administrator who processes incoming documents daily might receive 20 separate scanned PDFs that need to be merged into a single file for archiving. A teacher preparing exam materials might need to split a question bank into individual questions, then merge selected questions into a custom exam. A marketing team distributing reports might need to compress 15 PDF presentations before emailing them to regional offices. In each case, the tool handles the individual operations quickly, and the browser-based workflow means there is no need to install software, sign into a service, or wait for uploads and downloads from cloud servers. A frequently asked question is whether merging or splitting PDFs affects the file's digital signatures. The answer is yes: any structural modification to a signed PDF invalidates its digital signature. This is by design. Digital signatures certify that the document has not been altered since signing. If you need to merge signed documents, the merged output will not carry the original signatures. For documents where signature validity matters (legal contracts, notarized forms), keep the signed originals intact and only merge unsigned copies for convenience. Another common question involves PDF/A, the archival variant of PDF. PDF/A files conform to strict standards for long-term preservation, including requirements about embedded fonts and color profiles. Merging two PDF/A files does not guarantee that the output is also PDF/A compliant, because the merge process may introduce elements that violate PDF/A requirements. If PDF/A compliance is required for your output, verify the merged file with a PDF/A validator after processing. For users who work with PDFs regularly, understanding the difference between a PDF that contains actual text and a PDF that contains images of text is important. A text-based PDF (created by exporting from Word, Google Docs, or a similar application) has selectable, searchable text. An image-based PDF (created by scanning a paper document) is essentially a series of photographs of pages. The merge, split, and compress tools work with both types, but compression behaves differently: text-based PDFs compress by optimizing images and removing redundant data structures, while image-based PDFs compress primarily by reducing image resolution and quality. If you need to make a scanned PDF searchable, you would need to run OCR on it first (using the OCR tool, for example) and then merge or split the OCR-processed version. The PDF format will continue to be the standard for document exchange for the foreseeable future. ISO 32000-2 (PDF 2.0), published in 2020, added features for accessibility, digital signatures, and 3D content. As the format evolves, browser-based tools will become more capable. Running these operations locally in the browser, using the device's own processing power, is both more private and more efficient than uploading files to a server. No waiting in upload queues, no worrying about server-side data retention, and no hitting daily free limits. Your PDFs stay on your device, and the tool is available whenever you need it.
Frequently asked questions
Is it safe for official documents?
Yes. Processing happens entirely in your browser. Your files are never uploaded to any server.
Is there a page limit?
We offer a wide capacity to meet standard user needs.
Is WebRecast a free Smallpdf or iLovePDF alternative?
Yes! Merge, split, and compress PDFs just like Smallpdf or iLovePDF - with no file uploads, no watermarks, and no daily limits.
