# Convert Selected Pages of PDF to Excel, Not the Lot

- Author: FastBankConvert (https://fastbankconvert.com)
- Published: 2026-10-17
- Category: Speed, size and limits
- Canonical: https://fastbankconvert.com/blog/convert-selected-pages-of-pdf-to-excel

> Convert selected pages of a PDF to Excel to save time: pick page ranges, extract them to a new file, and keep page numbers for reference.
To convert selected pages of a PDF to Excel, first save just those pages as a new PDF, using a print dialog's page range or a tool such as qpdf, then convert that smaller file. Excel's PDF import in Microsoft 365 on Windows can take a start and end page instead. Record each row's source page for later checks.

## Why convert selected pages of a PDF instead of the whole file?

Converting only the pages you need means less to upload, less to read and less to clean up afterwards. A long PDF often holds cover letters, terms, adverts and summary pages around the few pages of data you want. Leaving them out speeds up the conversion and stops their text from turning into junk rows in the spreadsheet.

The saving is clearest in documents where the data sits in one part of the file:

- **Annual statement bundles.** You need March only, but the file has twelve months.
- **Reports with appendices.** A 60-page annual report may have its financial tables on five pages.
- **Credit reports.** The account details you want sit in one section, with pages of explanation before and after. [Converting a credit report PDF to Excel](/blog/credit-report-pdf-to-excel) covers how to turn that section into one table.
- **Scanned bundles.** Every scanned page needs text recognition, so dropping pages you do not need saves the most time of all.

There is also a quality reason. Many converters read layout across the whole file. Pages of prose or charts can confuse the column detection for the pages that matter, and a focused file gives a cleaner result.

## Printed page numbers versus PDF page positions

A page range uses the page's position in the PDF file, counted from 1, not the number printed in the footer. The two often differ. A statement bundle may restart its printed numbering each month, and a report may have a cover and contents before "page 1". Check the position in your viewer before typing a range.

Most PDF viewers show both. The page box in the toolbar usually shows the position, such as "14 of 60", even when the printed footer says "Page 2 of 5". Some viewers can display printed page labels instead, so if a range picks the wrong pages, that is the first thing to check.

A quick way to find positions in a long file:

1. Open the thumbnails panel in your viewer.
2. Scroll to the first page you want and note the position shown under the thumbnail.
3. Do the same for the last page.
4. Write the range down as positions, such as 14 to 18.

For a statement bundle, note the page where each wanted month starts, including its summary page. The summary carries the opening and closing balance you will need to check the result.

## Extracting selected PDF pages into a new file

You can extract pages either through a print dialog or with a dedicated tool. Printing to PDF with a page range is built into most systems and needs no install. A tool such as qpdf copies the chosen pages without redrawing them, which keeps the text exactly as it was. Both give you a smaller file to convert.

**Through the print dialog.** Open the PDF, choose Print, select a PDF printer such as Microsoft Print to PDF on Windows or Save as PDF on a Mac, type the range in the Pages box, and save. Afterwards, search the new file for a word you can see. If search finds nothing, the printer turned the pages into images, and a converter will need to run text recognition on them.

**With qpdf.** The [qpdf command-line documentation](https://qpdf.readthedocs.io/en/stable/cli.html) describes a `--pages` option that builds a new file from chosen pages and ranges. A dot stands for the input file, numbers separated by commas pick single pages, a dash gives an inclusive range, `z` means the last page and `r` counts from the end.

The table shows example ranges for a made-up 60-page statement bundle:

| What you want (example) | qpdf command | Print dialog Pages box |
| --- | --- | --- |
| Pages 14 to 18 | `qpdf bundle.pdf --pages . 14-18 -- march.pdf` | 14-18 |
| Pages 3, 7 and 9 | `qpdf bundle.pdf --pages . 3,7,9 -- picked.pdf` | 3,7,9 |
| Page 41 to the end | `qpdf bundle.pdf --pages . 41-z -- tail.pdf` | 41-60 |
| The last three pages | `qpdf bundle.pdf --pages . r3-r1 -- last3.pdf` | 58-60 |

If the PDF is password protected, qpdf needs the password, and a print dialog may refuse to print at all. Unlock it first with the password the bank gave you.

For paper statements, the same thinking applies before you scan. Scan only the pages you need. A scanner that feeds pages automatically makes it tempting to scan everything, and [whether a sheet feeder scanner is worth it for statements](/blog/sheet-feeder-scanner-for-statements) weighs that against the time it saves.

## Can Excel convert only some pages of a PDF?

Yes, in Microsoft 365 on Windows. Excel's Get Data from PDF import, built on Power Query, lets you pick individual tables and pages in the Navigator window, and its underlying function accepts a start page and an end page. Setting those limits means Excel examines only that range, which is quicker on a long file than reading every page.

Excel 2016 and 2019, Excel for Mac and Excel for the web do not offer this import, so on those versions extract the pages to a new file instead. In the Navigator, Excel lists each table and page it found, labelled with names such as Page001 or Table003. Ticking only the pages you want loads just those. For a long file, finding the right entries in that list can take a while, so setting a page range is often easier.

The [Pdf.Tables function reference](https://learn.microsoft.com/en-us/powerquery-m/pdf-tables) lists the options. `StartPage` is the first page to examine, defaulting to 1, and `EndPage` is the last, defaulting to the end of the document. To apply them, open the query in the Power Query Editor, open the Advanced Editor and add the options to the `Pdf.Tables` line. An example for pages 14 to 18:

```
Pdf.Tables(File.Contents("C:\Statements\bundle.pdf"), [StartPage=14, EndPage=18])
```

The page numbers here are positions in the file, as described above. The same reference notes a `MultiPageTables` option, on by default, that joins similar tables on consecutive pages into one. That suits a statement whose transactions run across several pages.

## Keeping source page numbers beside the converted rows

Add a column that records the PDF page each row came from. When a figure looks wrong in Excel, that column tells you exactly which page to open, instead of searching a 60-page file. It also makes it easy to confirm that every selected page produced rows, and that none were skipped.

How you add it depends on the route:

1. **One page at a time.** If you convert pages separately, type the page number in a new column next to each block of rows before you stack them.
2. **Power Query.** When you load several pages from the Navigator or from the full table list, the Name column holds labels like Page014. Keep that column when you expand the data, then split off the number.
3. **An extracted file.** Remember the offset. If page 1 of `march.pdf` was page 14 of the bundle, add 13 to every page number to get back to the original.
4. **Converted output with no page markers.** Note the first and last transaction on each page as you check them, and fill the page number down between them.

Keep the original PDF alongside the spreadsheet. A page column only helps if you can open the page it points to.

## Statement context lost when pages are converted alone

A selected page may lack information printed elsewhere in the PDF. The account number, statement period and opening balance usually sit on the first page. Dates printed without a year rely on the period at the top. Converting a middle page on its own can leave rows with no year, no account and no balance to check against.

Watch for these gaps:

- **Missing year.** If dates are printed as day and month only, the converter has to infer the year from the statement period. Without the header page, include the period yourself in a note or a column.
- **Missing opening balance.** A page from the middle of a month starts with a running balance that only makes sense next to the previous page. Include the page before, or the summary page, so you can check the arithmetic.
- **Missing column headings.** Some statements print them only on the first page, so a later page alone may come back with columns in the wrong order.
- **Tables that span pages.** If a table starts on page 17 and ends on page 19, selecting only page 18 gives you its middle with no top or bottom.

The simple rule is to include the page that holds the summary or header for any month you convert, even if you then delete its rows. It costs one page and gives the converter, and you, the context the other pages depend on.

If the converted file then fails to appear, the page selection is rarely the cause; [what to check when a converted file is not downloading](/blog/converted-file-not-downloading) runs through browser and storage problems. FastBankConvert is built to check that each statement's balances add up and to flag one that does not, which is the quickest way to notice a page left out. [The get-started page](/get-started) is where to ask for access.