What is 'burst PDF'?

The verb comes from the pdftk command-line tool, which has had a 'burst' operation since the early 2000s. The name stuck because it's a vivid description of what happens: a single document is burst open into its component pages, like a piñata.

Burst: every page becomes its own PDF. No configuration. Split: pick a page range and get one PDF with just those pages. Extract: pick any combination of pages and get one PDF with those pages.

If you want every page broken out separately, burst. If you want a chunk of pages as one PDF, split. If you want a custom selection, extract.

Importing into document-management systems that want one file per page. E-signing tools that accept single-page uploads. Print shops that bill per-page-file. Archival workflows that store one page per record.

The free Burst PDF tool runs in your browser. Drop in the PDF, click Burst, and download a zip containing one PDF per page. There's no watermark and no page-count limit beyond your browser's memory.

Bursting a PDF means taking a multi-page document and producing one new PDF for every page in it. A 25-page input becomes 25 one-page output files, usually packaged as a zip so you can download them in one click. The word 'burst' comes from print production, where a 'burst' would split a continuous-form printout into individual sheets along its perforations.

It's distinct from splitting in one specific way: splitting lets you choose ranges and skip pages. Bursting always processes every page. If you find yourself splitting on every single page boundary, burst is the faster shortcut.

Bursting is the right operation whenever you have a document that's logically a stack of independent items printed together: event tickets, certificates, invoices, payslips, lab reports, course handouts, exam papers. The PDF is one file for convenience, but each page needs to leave the file separately. Burst once and you've got the right number of files at the right granularity.

It's also a useful preprocessing step before reordering. Burst into individual pages, then drag them into the Merge tool in the order you want, and you've effectively done a page-level rearrangement without needing a dedicated reorder UI.

Each output file is a valid, self-contained PDF. Text, fonts, images, form fields, annotations, and links anchored to the page travel with that page. Cross-page links and document-wide outlines are dropped, because they no longer make sense on a one-page document.

Bursting runs in your browser using WebAssembly. The PDF isn't uploaded — the page extraction happens locally and each output is built in memory before being added to the zip. The only practical limit is your device's memory; a modern laptop comfortably bursts documents in the hundreds of pages.

Bursting a PDF means taking a multi-page document and producing one new PDF for every page in it. A 25-page input becomes 25 one-page output files, usually packaged as a zip so you can download them in one click. The word 'burst' comes from print production, where a 'burst' would split a continuous-form printout into individual sheets along its perforations.

It's distinct from splitting in one specific way: splitting lets you choose ranges and skip pages. Bursting always processes every page. If you find yourself splitting on every single page boundary, burst is the faster shortcut.

Bursting is the right operation whenever you have a document that's logically a stack of independent items printed together: event tickets, certificates, invoices, payslips, lab reports, course handouts, exam papers. The PDF is one file for convenience, but each page needs to leave the file separately. Burst once and you've got the right number of files at the right granularity.

It's also a useful preprocessing step before reordering. Burst into individual pages, then drag them into the Merge tool in the order you want, and you've effectively done a page-level rearrangement without needing a dedicated reorder UI.

Each output file is a valid, self-contained PDF. Text, fonts, images, form fields, annotations, and links anchored to the page travel with that page. Cross-page links and document-wide outlines are dropped, because they no longer make sense on a one-page document.

Bursting runs in your browser using WebAssembly. The PDF isn't uploaded — the page extraction happens locally and each output is built in memory before being added to the zip. The only practical limit is your device's memory; a modern laptop comfortably bursts documents in the hundreds of pages.