Your 40-page application needs every page routed for individual signatures. Or your archive system stores one document per page. Or you want each page available as a separate file for OCR pipelines.
Splitting every page is a 30-second job in Flint.
Drop, split, download
Open split PDF, drop the file, choose 'every page' mode. Flint produces N PDFs, one per page, numbered sequentially. Download as a ZIP. Inside: 'document-001.pdf', 'document-002.pdf', through 'document-040.pdf'.
Zero-padded numbering matters
Padding is the difference between sortable filenames ('001, 002, ... 010, 011') and the disaster of '1, 10, 11, 2, 20, 21'. Flint pads to the document's page count, so 40 pages get 2-digit numbers, 400 pages get 3-digit. Files sort correctly in every system.
Common downstream uses
OCR pipelines that work on single pages run faster in parallel. Signature workflows route page 3 to one signer and page 7 to another. Archive systems index by page. Single-page output is the right input for all of these. For per-page conversion to images, see PDF to JPG.
Putting them back together
If you need to re-merge after per-page processing, merge PDF accepts the whole batch in one drag. Filename order (preserved by Flint's padding) controls the merge sequence.
FAQ
Will pages keep their orientation?
Yes. Each output page has the same rotation, size, and content as the original.
Do bookmarks survive into single-page outputs?
Each split file only contains bookmarks pointing at that page (if any). Cross-page bookmarks naturally don't apply.
Maximum pages to split at once?
Browser-bound. Hundreds of pages is fine. Thousands may slow down your tab.
What about page numbers shown on each page?
Whatever was typed onto the page stays. Page labels (metadata) for each single-page file reflect its original label.
One file in, every page out. Split into single pages.