To extract PDF pages in Bluebeam Revu, run the application's native Extract Pages command on the open document, type the page numbers or inclusive ranges in the order you want, and confirm — Revu writes a new PDF containing only the selected pages while leaving the source untouched on disk. Bluebeam Revu has long included page extraction as one of its document-management primitives, and most Revu users reach for it first because it lives inside the same application they already use for markup, takeoffs, and stamps. A local browser workflow built around the Extract PDF Pages tool delivers the same single-file result — only the chosen pages, copied as PDF objects rather than screenshots, in the exact order you type — without opening Revu, without uploading the source to a server, and without leaving your device. Both paths share the same core idea: you describe which pages to keep, in what order, and the tool produces a fresh, downloadable PDF. The remainder of this guide explains the Bluebeam desktop context first, then walks through the browser-based method step by step, and closes with the rules, limits, and verification habits that prevent wasted work on construction sets, legal exhibits, and other sensitive documents.
How Bluebeam Revu Handles Page Extraction
Bluebeam Revu is widely used in construction, architecture, engineering, and legal review workflows, and page extraction is one of its document-management primitives. Revu lets users pull selected pages out of a PDF into a new file while leaving the source untouched, and the result behaves like any other Revu document — openable, markup-ready, and compatible with Revu's other page-level commands. Because Revu treats the new file as a fresh PDF, the extraction does not carry markup history forward unless the user explicitly flattens or merges it as part of the workflow.
Revu's native path is the right choice when the desktop app is already open, when the source is part of a Studio session, or when downstream tools rely on Revu-specific features such as markups, layers, or tool chests that should travel with the file. The native command is less convenient when you are working on a machine that does not have Revu installed, when the source PDF lives on a phone or tablet, or when you simply want a quick extraction without launching a heavyweight desktop application. In those cases a browser-based tool that operates entirely on local files is a faster, lighter alternative.
A Browser-Based Method That Runs Alongside Bluebeam
The Extract PDF Pages tool runs entirely inside the current browser tab. You choose a local PDF, type the page numbers or ranges you want, and the browser reads the original bytes, copies the requested page objects into a fresh PDF, and exposes a temporary download link. The source file, the page expression you typed, and the output file never leave your device — no upload to a remote server. A local source link lets you compare the original against the new file without leaving the page, and temporary source and result URLs are released when they are replaced or when the tab closes.
The tool is built on pdf-lib, an open-source JavaScript PDF library that performs the actual page copying through its PDFDocument API. Because the copy step happens in the browser, the workflow matches the privacy expectations that lead many Revu users to disable cloud sync on sensitive construction sets, legal exhibits, or unreleased drawings. If you also work with Revu's Studio sessions, see our guide on using Bluebeam to compress a PDF for a related local-first workflow.
For users who need a different page-manipulation primitive, related browser tools cover the rest of the workflow: Split PDF divides a file into multiple smaller files, Merge PDF combines several files in a chosen order, and Rearrange PDF Pages changes the order without removing any pages. None of these tools uploads your file.
Extract PDF Pages Step by Step
- Choose an unencrypted PDF no larger than 50 MiB and with no more than 500 pages. The tool checks both the file size in bytes and the decoded page count after the document loads. A file at either boundary is accepted; anything larger is rejected without being shortened. Encrypted or password-protected files are not opened by bypassing encryption, so remove the password first if the source is protected.
- Enter one-based page numbers or inclusive ascending ranges in the output order you want, such as 5, 1-3. Token order becomes output order, so 5, 2-3 produces a PDF containing original page 5 followed by pages 2 and 3. Descending ranges such as 5-3 are rejected rather than silently reversed, and decimal values, negative values, malformed ranges, and pages outside the loaded document are also rejected with an explicit error.
- Extract the unique selected pages, review any duplicate-page notice, and download the new PDF. The browser copies each selected page as a PDF object, saves the result, and exposes a temporary download link. Changing the page expression immediately releases the previous result, and running extraction again replaces the previous output URL.
Page Selection Syntax at a Glance
The selection field accepts comma- or whitespace-separated tokens. A token is either a single page number or an inclusive ascending range joined by a hyphen. Page numbers are one-based, matching the ordinary page numbers shown by PDF viewers, and token order is significant: the parser preserves the order in which each page first appeared, which is also the order in which pages end up in the output.
| Input | Meaning | Output pages (one-based) |
|---|---|---|
| 5 | A single page | 5 |
| 1, 3, 7 | Three single pages in listed order | 1, 3, 7 |
| 1-3 | An inclusive ascending range | 1, 2, 3 |
| 5, 2-3 | Page 5, then the range 2-3 | 5, 2, 3 |
| 3, 1-3 | Range overlaps page 3 | 3, 1, 2 (duplicate of 3 ignored) |
| 5-3 | Descending range | Rejected with an error |
| 2.5 or -1 | Decimal or negative value | Rejected with an error |
The selection field accepts at most 4,000 characters. Over-limit input is not truncated or partly applied, so very long batch jobs are caught at the boundary instead of producing an incomplete file. Repeated pages follow a deliberate first-occurrence rule: the second occurrence of page 3 is ignored, and the result reports the duplicate. This prevents an accidental overlapping range from silently adding repeated output pages while preserving the exact order in which each page first appeared. If you intentionally need duplicate pages, use a PDF page-reordering or duplication workflow designed for that purpose.
Limits, Encryption, and What Gets Rejected
Three hard limits decide whether the tool can complete the task. The input boundary is 50 MiB, which is 52,428,800 bytes. The decoded document boundary is 500 pages. A file at either boundary is accepted; a larger file or document is rejected, not shortened, so the source stays intact on disk. Browser memory availability can also vary by device and tab workload, which is why the limits are stated explicitly rather than implied.
Encrypted PDFs are not opened by bypassing encryption, as the underlying pdf-lib encryption handling is configured to refuse them. If your source is password-protected, the tool will surface an explicit error and leave the source untouched. For password-protected files where you know the password, remove the password first with a dedicated tool, then return to Extract PDF Pages with an unencrypted copy. Damaged or unsupported files can fail to load with a parser-level error rather than a clean rejection.
The output can still be large even when only a handful of pages are selected, because fonts and images used by those pages are copied along with the page object. File size does not necessarily scale in direct proportion to page count, and extracting one page from a resource-heavy document can retain data needed by that page. If the output exceeds your downstream limit, run it through a PDF compressor designed for local processing.
What Survives Extraction and What Doesn't
Each selected page is copied as a PDF page object, not rasterized into a screenshot. A 90-degree rotation, crop box, media box, page graphics, and ordinary page resources travel with the page. The output page count equals the number of unique selected pages, and an integration test verifies that the right pages — in the right order, with the right dimensions — actually appear in the saved result.
Important PDF features can have document-wide relationships that do not survive page extraction cleanly. AcroForm fields, annotations, scripts, embedded files, layers, page labels, bookmarks, document outlines, cross-page destinations, and links may depend on objects outside the selected pages. Digital signatures will not remain valid after creating a different PDF. Dynamic XFA forms are not a supported preservation target in pdf-lib, which the underlying library documents on its PDFForm page. The tool therefore makes no promise that every interactive, navigational, signed, or archival property survives the extraction.
Verifying the Output Before You Save or Share
Before treating the extracted file as final, open it in the viewer your recipient will use, confirm the page order matches the token order you typed, and visually inspect each page for rotation and crop. Test any internal link or cross-reference that the source relied on, because links whose destinations live on pages you did not select will not resolve in the new document. If the source carried form fields or signatures, confirm that downstream consumers do not require those properties to remain valid.
A local source link lets you compare the original against the extraction without leaving the page, and temporary source and result URLs are released when they are replaced or when the page closes. Choosing another file clears the old bytes, selection, source link, result, and error. Job and mounted-state guards prevent an older asynchronous load or save from replacing newer state. For regulated archival work, signed contracts, or accessibility-tagged PDFs that must round-trip cleanly, retain the original PDF and use a specialist PDF editor designed for full document preservation rather than a general-purpose page extractor.