Your 200-page training manual needs to go to participants as digestible chapters of 10 pages each. Splitting at every chapter break would mean configuring 20 ranges. Splitting every 10 pages takes one number.
Flint does fixed-interval splits in a single setting.
One field, batched output
Open split PDF, drop your manual, switch to 'every N pages', type 10. Flint produces 20 files: pages 1-10, 11-20, all the way to 191-200. You download them all in one ZIP. Each is a real PDF you can open, share, or further process.
When N doesn't divide evenly
If your manual is 207 pages and you split every 10, the last file is pages 201-207 — seven pages, not ten. Flint doesn't pad or stretch. The output is honest: chunks of N except the last.
Use case: distribution-friendly batches
Email attachment limits, learning-management chunking, mobile-reader friendliness. Splitting a 200-page PDF into 10-page chunks turns one hard-to-share file into 20 easy ones. Recipients can merge them back if they need a single file again.
Combine with smart naming
Flint names the outputs with their page range built in. Set a custom prefix ('Module-') and you get Module-001-010.pdf, Module-011-020.pdf, and so on. These sort correctly in any file system and tell a participant exactly where they are in the manual.
FAQ
Can I split every 1 page?
Yes — that's single-page split, one PDF per page. Common for batch-OCR or per-page archival.
Does Flint split at scene breaks or just by count?
By count, fixed. For content-based splitting (chapter breaks), use range mode and specify each range, or use bookmark-based split.
Maximum N?
Any value up to your file's page count. N larger than the file gives you one output (the whole file).
Are the splits efficient on file size?
Each output is just the pages you asked for. They aren't padded with extra data.
Pick a number, get evenly-sized PDFs. Split every N pages.