A 300-page course pack is a well-meaning obstacle. It contains everything the course might need, which means it contains far more than any student was assigned this week, and it arrives as a file too large to email comfortably, too long to print casually, and too daunting to open. Most students respond rationally: they do not open it at all, or they open it, scroll, and give up. The assigned reading is in there somewhere, but "somewhere" is not a reading instruction. Extracting the assigned pages into a small, single file turns the obstacle back into an assignment.
Extract Pages pulls chosen pages out of a PDF into one new document, in the order you list them. For a course pack, that means this week's reading, and only this week's reading, as a file a student can open on a phone, print without guilt, and actually finish. The original pack stays intact for reference. Nothing is deleted, and nothing needs to be re-bought or re-scanned. The change is purely one of presentation: from everything, to what was assigned.
Why the whole pack fails as a weekly assignment
The failure is not about student diligence. It is about friction, and friction compounds. A large file downloads slowly on a weak connection, which is exactly the connection many students have. A long document has no obvious starting point: a student who opens page one faces 299 pages before the assigned chapter, and the table of contents, if one exists, is itself several pages in. Printing the whole pack wastes paper and money, so students print nothing and read on screen, where a 300-page scroll is harder to navigate than a 12-page one. Each friction is small. Together, they are enough to turn an assignment into a postponement.
There is also a fairness point. Students with fast connections, large screens, and cheap printing absorb the friction easily. Students without those advantages absorb it fully. Sending only the assigned pages removes most of the friction for everyone at once, and it costs the sender minutes. When the barrier is the file rather than the reading, fixing the file is the teacher's job, not the student's test.
Build the weekly file in three steps
First, identify the exact pages. Check the assignment against the pack's own pagination, not against the PDF viewer's page counter, because the two often differ: a pack whose printed page 1 is the PDF's page 5 will mislead anyone who lists pages from the viewer. Write down the printed page numbers, then translate them to PDF pages if they differ, and double-check the first and last pages of the range. An off-by-one error at either end either cuts a paragraph mid-thought or includes a page that was not assigned, and students notice both.
Second, list the pages in reading order. Assigned pages are not always consecutive: a chapter may run from pages 44 to 51, with a two-page case study on pages 88 and 89 assigned alongside it. Listing 44-51 and 88-89 in one extraction produces a single file in reading order, which is far more usable than two separate files that a student must juggle. If the assignment includes a page from a different document entirely, extract that separately and join the files afterwards, rather than forcing one extraction to cover two sources.
Third, name the file for the week it belongs to. A file called "week-4-reading.pdf" is findable in a downloads folder in December. A file called "extracted-pages.pdf" is not. Add a one-line cover note inside the file's first page if you can, or in the message that sends it, stating the source, the pages, and the week. That note also protects you: if a student queries a passage, you can point to the exact source pages without reconstructing the selection from memory.
Worked example: a fictional tutor's weekly reading
The example is fictional: an invented tutor, an invented course, and invented page numbers. Imagine a tutor, whom we will call Helen Marsh, teaching a fictional local-history course, correspondence via helen@example.org. The course pack is a 280-page PDF assembled from several out-of-print booklets. For week five, Helen assigns chapter three of one booklet, printed pages 112 to 123, plus a two-page map appendix on printed pages 240 and 241.
Helen checks the pagination first and finds the pack's printed page 112 is the PDF's page 118, because the pack's front matter adds six pages. She translates carefully: printed 112-123 becomes PDF 118-129, and printed 240-241 becomes PDF 246-247. She extracts those pages in reading order, chapter first and maps second, into one 14-page file named "week-5-reading.pdf", and sends it with a note naming the source booklet, the printed pages, and the week. Students open a 14-page file, not a 280-page one. The student who wants the full booklet can still open the original pack, which Helen keeps available. The student who only needs this week's assignment has exactly that, and nothing else competing for attention.
The same pattern scales across a term. Each week gets its own small file, each named for its week, each drawn from the same intact pack. By the end of term, students hold a set of weekly files that together cover the course, in an order that matches how the course was actually taught, rather than one monolith that matches how the pack was assembled.
Check the small file before you send it
A small file deserves the same check as a large one, because its errors are more visible. Open the extracted file and read the first line of the first page and the last line of the last page of each section. Confirm no section starts or ends mid-sentence because a page boundary was misjudged. Confirm the maps, tables, and figures the text refers to are actually included: a chapter that says "see figure 3 on the following page" fails if the following page was not assigned and not extracted. If a referred-to page is essential, include it even if it was not strictly assigned, and note why. A reading that refers to a missing figure is worse than a reading one page longer.
Also confirm the file size. A 14-page extraction from a scanned pack can still be large if the scans are high-resolution, and a file that is small in pages but large in megabytes has only solved half the problem. If the extracted file is still too large to send comfortably, Compress PDF shrinks it afterwards, with a lossless mode that keeps text selectable and a smallest mode that rebuilds pages as images. Check legibility after compressing a scanned extraction, because small print in scans is the first thing a rebuild softens.
Honest limitations
Extraction copies pages as they are. It does not renumber them, so a weekly file drawn from scattered pages keeps the original printed numbers, which jump around; the cover note explaining this is not optional decoration, it is what makes the file usable. Extraction does not summarise or simplify the reading, so a dense chapter stays dense, just shorter in file terms. And extraction cannot fix a pack whose scans are illegible or whose pages are out of order in the source; those problems need fixing at the source, not at extraction time. If the assigned pages need converting to editable text for notes afterwards, PDF to Markdown extracts the text layer as Markdown with headings and lists preserved. For the broader workflow of dividing and joining PDFs, see how to merge and split PDFs.
FAQs
How do I extract only the assigned pages from a course pack?
List the assigned pages, such as 44-51 and 88-89, in Extract Pages, in reading order. You get one new file with exactly those pages, and the original pack is unchanged. Name the file for the week it belongs to.
Can I extract pages that are not consecutive?
Yes. A page list can mix single pages and ranges, and the result follows the order you list them. A chapter plus a separate appendix, or pages from different sections, can form one file in reading order.
Will extracted pages keep their original quality?
Yes. Extraction copies pages as they are, so their appearance is preserved. Printed page numbers on the pages stay as they were, so include a short note telling students which source and pages the file came from.
Should I send the whole course pack or just the assigned pages?
Send the assigned pages as the weekly file, and keep the whole pack available for reference. Students open, print, and finish a small file far more reliably than a 300-page pack, and anyone who wants full context can still find it in the original.
human review pending client designation