Split PDF Go

File to be converted. Value can be URL or file content.

Sets the password to open protected documents.

A comma-separated sequence of positive integers defining the size of each split segment. The PDF will be divided into consecutive chunks whose page counts follow the given pattern, repeating it until all pages are consumed. For a 10-page PDF with SplitByPattern = 3,2, the output will be four documents containing pages [1-3], [4-5], [6-8], and [9-10] (pattern repeats: 3,2,3,2).

Specify exactly which pages to extract by listing single pages or inclusive ranges. The API will emit one PDF per entry, in the order given. For a 10-page file with SplitByRange = 1-3,5,7-9, you receive three PDFs containing pages [1–3], [5], and [7–9].

Splits the PDF into separate output files by starting a new document at each page whose text matches the specified regular expression. With SplitByTextPattern = Chapter\s+\d+, the PDF will be split at every page where “Chapter 1”, “Chapter 2”, etc., appear. If “Chapter 1” is on page 1, “Chapter 2” on page 10, and “Chapter 3” on page 20 of a 25-page PDF, you’ll get four files containing pages [1–9], [10–19], [20–25], and any pages after the last match (if present).

Automatically splits a source PDF into individual documents, creating a new file at every bookmarked page. When nested bookmarks are present, splitting occurs at the deepest (child) level, and each output file is named to reflect the full bookmark hierarchy - for example: ParentBookmark-ChildBookmark.pdf. When the source PDF has no bookmarks, the original document is returned unchanged as no-bookmarks.pdf.

Specify a comma-separated list of pages or inclusive ranges ExtractPages = 1,3-5,7 to pull out from the source PDF. The API will emit one PDF per entry, each containing exactly the pages defined.

When set to true, all split output files (whether defined by page ranges, custom ranges, or text-pattern segments) will be merged into a single PDF. By default false, the API returns one PDF per specified range.

When the StoreFile parameter is set to True, your converted file is written to ConvertAPI’s encrypted, temporary storage and made available via a time-limited secure download URL, valid for up to 3 hours. After this period, the file is permanently deleted.

When StoreFile is set to False, conversion happens entirely in-memory. The raw file bytes are streamed back in the API response without touching disk or external storage, ensuring maximum security and zero persistence so that only you can access the content.