PDF تقسیم کریں

Split PDF files — free, private, and without uploading

This free tool lets you split a PDF into multiple files or extract specific pages in seconds — and unlike almost every other online PDF splitter, your document is never uploaded. The splitting runs entirely in your browser using the open-source pdf-lib library, so contracts, bank statements, scans, and reports stay on your device from start to finish. Tools like iLovePDF, Smallpdf, PDF24, Sejda, and Adobe's free web splitter all upload your file to a remote server; this tool does not — open your browser's Network tab (F12) while splitting and you'll see zero outgoing file transfers.

Drop in a PDF and every page appears as a clickable thumbnail. Select pages visually, type a range like 1-3,7,11-, split every page into its own file, or break the document into every-N-page chunks. Single extractions download as one PDF; multi-file outputs arrive as a tidy ZIP. No sign-up, no watermark, no daily task limits — and no file-size caps imposed by a server.

Three ways to split: extract, every page, or chunks

Extract pages pulls your selection into one new PDF — perfect for saving a single page, sharing just the signed page of a contract, or trimming an appendix from a long report. Click thumbnails to toggle selection or type a range; the live page count confirms exactly what you're extracting.

Split every page turns an N-page document into N individual PDFs (zipped), the classic job for batch invoices or certificates. Split into chunks divides the file every N pages — break a 100-page scan into ten 10-page parts, or a duplex booklet every 2 pages. Set the chunk size to 1 and you get the same result as split-every-page, so every mode is covered from a single screen without navigating between different tool pages.

Why splitting in your browser is safer than uploading

Traditional sites like iLovePDF, Smallpdf, Sejda, and PDF24 upload your PDF to their servers, process it remotely, and promise deletion within an hour or two. For public documents that's often acceptable, but for sensitive paperwork — tax filings, medical records, legal contracts, HR documents — that's a trust exercise you don't need to make. This tool uses the open-source pdf-lib engine running in your own browser tab, so there is no upload at all.

Local processing is also why there are no limits. Server-based free tiers cap you at 2–3 tasks per day, 15–50 MB files, or 200 pages; here the only constraint is your device's RAM, so splitting large PDF files — hundreds of pages or hundreds of megabytes — just works, faster, because there is no upload round-trip adding latency before processing can even begin.

How to split PDF pages — step-by-step guide

1) Add your PDF — drag it onto the drop zone or click to browse. Page thumbnails render immediately using your browser's built-in PDF renderer. 2) Choose pages — click thumbnails to toggle selection (Select all / Clear help with big documents), or type a range like 1-5, 8, 11- (an open-ended range like '11-' means 'page 11 to the last page'). 3) Pick a mode — Extract for one combined PDF, Split every page for individual files, or Split into chunks for N-page batches. 4) Download — your file or ZIP arrives immediately, named after the original document.

The workflow is identical on Windows (which has no built-in PDF splitter beyond the Print dialog), Mac (where Preview handles basic splits but can't batch-export many files), Linux, and on iPhone or Android directly in the browser — no app download required. Unlike Adobe Acrobat, there is no subscription, no sign-in, and no cloud dependency.

Lossless splitting — quality preserved, original untouched

Splitting copies pages exactly as they appear in the source: fonts, images, vector graphics, form fields, annotations, and hyperlinks within extracted pages are preserved without re-encoding or re-compression. Output quality is identical to the original; only the page count and resulting file size change. Your original file is never modified — every operation produces new documents while leaving the source on your device exactly as it was.

This lossless behaviour is a property of the PDF specification itself — a well-implemented splitter just reorganises the page tree without touching content streams. Whether you split with this tool, iLovePDF, Adobe Acrobat, or any other standards-compliant splitter, splitting does not degrade PDF quality. The difference between tools lies in privacy, speed, and limits — not in output quality.

Splitting PDFs for specific workflows

Invoice processing: Many accounting systems export batches of invoices as a single multi-page PDF. Split every page to get individual per-invoice PDFs for filing or emailing to clients. Contracts: Extract just the signature page from a long agreement to send for review or wet signature. Scanned books: Split a scanned book into chapters using page ranges based on the table of contents. Presentations: Break a large deck PDF into per-section handouts for different audiences. Compliance and archiving: Separate multi-document bundles into individual records for a document management system.

Legal work: Many law firms receive large document bundles (discovery, court filings) that need to be split into individual exhibits. Client-side splitting is a compliance advantage — no document leaves the firm's devices before it needs to. HR and payroll: Payslip batches, P60s, and benefits documents are commonly exported as combined PDFs; splitting them per employee for distribution is a single-mode operation here. For any of these workflows, the no-upload architecture means the sensitive content is never exposed to a third-party service.

Merge PDF — the companion tool for putting PDFs back together

Need to undo a split, combine pages from multiple sources, or assemble a new document from pieces? UtiloKit's Merge PDF tool combines multiple PDFs — and even JPG/PNG images — into one file with the same no-upload privacy guarantee. Together, Split and Merge cover the two most common PDF workflow tasks entirely on your device, with no account, no subscription, and no file ever leaving your control.

Unlike cloud services such as Smallpdf, iLovePDF, or Adobe's web tools, both the Split and Merge tools work completely offline after the initial page load — making them suitable for secure, air-gapped environments or use on an aeroplane. All output files are downloaded directly to your device; nothing is stored on any server.

How PDF splitting works internally

A PDF file is not a linear stream of page data — it is a graph of cross-referenced objects. At the heart of every PDF is the cross-reference table (xref table), which maps each object number to its exact byte offset within the file. When a PDF reader opens a document, it reads the xref table first and builds an in-memory index — it can then jump directly to any page object without scanning the entire file. When a splitter extracts pages, it must construct a new xref table for the output document that references only the objects belonging to those pages and assigns them correct, contiguous byte offsets.

Pages in a PDF are organised as a page tree: the document's catalog points to a root /Pages node, which has children that are either further /Pages nodes (branches) or /Page nodes (leaves, the actual pages). Each /Page node holds a /Parent reference back up the tree. When a splitter extracts a subset of pages, it must rebuild this tree from scratch — creating a new root /Pages node, listing only the extracted /Page objects as children, and updating every /Parent pointer to match the new tree. Failing to do this correctly produces a PDF that appears to load but silently skips or repeats pages.

A subtler challenge is shared resources. Fonts, images, ICC colour profiles, and other objects are often shared across many pages in the original document — a single embedded font may serve every page in a report. A naive splitter that only copies the /Page node and its direct content stream will produce a broken PDF if the font or image it references was defined elsewhere in the file and not included in the output. A correct implementation walks each extracted page's resource dictionary (/Font, /XObject, /ColorSpace, /ExtGState) and traces every referenced object into the output, including transitively referenced objects. Linearized PDFs — a special layout that front-loads the first page's objects for fast web delivery — and documents with incremental updates (additional sections appended to the file after an edit) require the splitter to parse and flatten these structures before extraction can begin.

PDF splitting in professional workflows

In legal and compliance work, large multi-hundred-page PDFs arrive daily: contracts, court filings, and discovery productions that must be divided by section, exhibit, or bate-stamp range. E-discovery platforms such as Relativity and Everlaw perform automated PDF splitting and labeling at scale, but individual attorneys and paralegals often need quick manual splits for single matters. Client-side splitting tools are particularly valuable here because no document leaves the firm's devices until it needs to — a meaningful difference when dealing with privileged materials subject to attorney-client confidentiality. In healthcare, medical record compilations from hospitals and imaging centres arrive as large combined PDFs that must be split by provider, date range, or visit before submission to insurance carriers or transfer to treating clinicians. HIPAA requires appropriate access controls over protected health information; splitting records into patient-specific, encounter-specific files makes it far easier to apply those controls and reduces the risk of accidental disclosure.

In academic publishing, a journal issue delivered as a single PDF must be split into individual article PDFs for hosting on a publisher's article page or indexing in databases like PubMed. Textbook publishers and course instructors frequently extract chapters or sections for upload to a Learning Management System (LMS) such as Canvas or Moodle, where per-file size limits and per-chapter access controls make splitting necessary. In architecture, engineering, and construction, drawing sets of 50 or more sheets are routinely delivered as a single PDF and must be split by discipline — civil, structural, mechanical, electrical, plumbing — for distribution to the relevant subcontractors. Each trade receives only the sheets pertinent to their scope, reducing confusion, preventing accidental mark-up of another trade's drawings, and keeping proprietary design details off devices that don't need them. A page size-based split (detecting when the document alternates between letter-size and tabloid-size sheets) is a common variant here, since cover sheets are often letter-size while drawing sheets are ANSI D or E size.

In finance and accounting, ERP and payroll systems export batch PDF runs — bank statements for dozens of accounts, payslips for hundreds of employees, invoices for entire billing cycles — as single files. Splitting these into per-account, per-employee, or per-invoice files is a daily administrative task. Doing it client-side, without uploading payroll data or bank statements to a third-party server, is not just a convenience — it is the correct security posture for any organisation subject to data protection regulations. In government and public administration, meeting agenda packages (sometimes called board books) can run 300–500 pages covering dozens of agenda items; splitting them into per-item PDFs makes it easier for officials, staff, and the public to locate and share specific decisions without distributing the entire package.

Privacy and security when splitting PDFs

A common misconception is that splitting a document is equivalent to redacting it — it is not. Splitting creates a subset for sharing; it does not remove content from any file. If a document contains confidential sections that should not be disclosed, the correct tool is PDF redaction, which permanently deletes the underlying content stream for the sensitive portions. Critically, placing a black rectangle annotation over text is not redaction — the annotation is a separate layer that any PDF editor can remove in seconds, leaving the original text exposed. True redaction replaces the content stream data itself and must be performed with a tool that explicitly supports it (Adobe Acrobat Pro's Redact tool, or open-source equivalents like qpdf with content-stream editing). Splitting the document into a subset that does not include the confidential pages is a valid way to share the non-sensitive portion, but it does not alter the original file.

If the source PDF carries a digital signature that covers the entire document, any modification — including splitting — invalidates that signature. This is intentional: a digital signature proves that a specific byte sequence has not changed since it was signed, and extracting pages changes the byte sequence. The split output cannot be represented as a signed document; it is an unsigned derivative. If legal or regulatory workflows require a signed PDF, the original signed file must be kept intact and any derivative work clearly labeled as an unsigned excerpt. Metadata inheritance is another consideration: split PDFs inherit the original document's info dictionary — the /Author, /Creator, /Keywords, /Producer, and creation date fields — as well as any XMP metadata stream embedded in the file. This metadata may reveal the authoring software, the original author's name, or the document's creation timestamp, which could be undesirable when sharing an excerpt externally. A thorough workflow strips or updates these fields in the split output.

Finally, consider file size and embedded objects when assessing split output. A split document's file size is not proportionally smaller than the original when fonts and images are shared and embedded. A 10-page excerpt from a 100-page report that uses a 2 MB embedded font may itself be 2.5 MB while the original was 5 MB — because the font is fully copied into the output rather than being shared. Conversely, a 10-page excerpt containing many high-resolution images unique to those pages might be nearly as large as the full document. Understanding that embedded resources are duplicated rather than shared across split files helps set correct expectations about output file sizes — and explains why some split PDFs are surprisingly large relative to their page count.