How to Extract Text from PDF URLs Without Code (Page by Page, to CSV, Excel or JSON) A developer built and maintains PDF Text Extractor, a hosted Apify tool that takes a list of PDF URLs and returns one row per page with columns for source URL, page number, total pages, extracted text, truncation and text-layer flags, and fetch time, exportable to CSV, Excel or JSON without code. A test run on a three-page Mozilla PDF.js sample finished in about six seconds and preserved line breaks and table-of-contents leaders, and a keyword filter lets users find which pages mention a term across multiple PDFs. The tool is paid per page with the first 25 pages of each run free, and the developer warns that scanned PDFs without a text layer return empty text flagged by hasText. You have a list of PDF links. Annual reports, product manuals, tender documents, research papers, policy PDFs on a government site. You need the text inside them in a spreadsheet, ideally one row per page so you can see where something was said, and you would rather not install Python, wrestle with a PDF library, or download fifty files by hand. This post shows the route I use: paste the URLs into a hosted tool, press Start, export a CSV. No code. I also cover the limits, because a PDF text tool that quietly returns empty rows for scanned files is worse than no tool at all. Disclosure: I built and maintain the tool used here, PDF Text Extractor - Extract Text from PDF URLs https://apify.com/ahmed.fouaad82/public-pdf-text on the Apify Store. It is paid per page, and the first 25 pages of every run are free. Everything below works inside that free slice, and I list the alternatives at the end. This article was written with AI assistance and checked against a real run. One row per PDF page, with these columns: | Column | Meaning | |---|---| | sourceUrl | The PDF the row came from | | pageNumber | Page number inside that PDF | | totalPages | How many pages the PDF has in total even if you only parsed the first few | | text | The selectable text of that page | | textTruncated | true if the page was longer than your character cap and got cut | | hasText | false if the page had no text layer typically a scanned image | | fetchedAt | When the page was read | Page-level rows matter more than they look. If you are checking where a supplier contract mentions "termination", or which page of a 120-page report has the revenue table, "page 47" is the answer you want, not one giant blob of text. Here is the output of an actual run 2026-11-09, run ID ywJjLIRlzLGA4VeGs on a small public test PDF from the Mozilla PDF.js repository. The input was just: { "urls": "https://raw.githubusercontent.com/mozilla/pdf.js/master/test/pdfs/basicapi.pdf" , "maxResults": 25 } The run took about 6 seconds and produced three rows, one per page. Exported as CSV four of the columns selected , it looks like this: "pageNumber","totalPages","hasText","text" "1","3","true","Table Of Content Chapter 1 .......................................................... 2 Paragraph 1.1 ...................................................... 3 page 1 / 3" "2","3","true","Chapter 1 page 2 / 3" "3","3","true","Paragraph 1.1 Powered by TCPDF www.tcpdf.org page 3 / 3" And one row as JSON: { "sourceUrl": "https://raw.githubusercontent.com/mozilla/pdf.js/master/test/pdfs/basicapi.pdf", "pageNumber": 1, "totalPages": 3, "text": "Table Of Content \nChapter 1 .......................................................... 2 \nParagraph 1.1 ...................................................... 3 \npage 1 / 3", "textTruncated": false, "hasText": true, "fetchedAt": "2026-11-09T22:44:55.773Z" } It is a deliberately tiny document. The point is the shape: line breaks are kept, the dotted table-of-contents leaders come through as they appear in the PDF, and nothing is reflowed or "summarised". You get the text that is in the file. totalPages still tells you the full length, so you can see what you skipped. That is the whole workflow. For a quick one-off job, stop here. The keyword filter turns the tool into a "which page says X" finder across a pile of PDFs. For example, to find every page in a set of supplier terms that mentions termination: { "urls": "https://example.com/terms/supplier-a.pdf", "https://example.com/terms/supplier-b.pdf" , "keyword": "termination", "maxPages": 100, "maxResults": 200 } The URLs above are placeholders; use your own. The output is one row per matching page, with sourceUrl and pageNumber , which you can paste straight into a review sheet. Some PDFs live at a fixed URL and get replaced: a monthly price list, a weekly report, a published policy. To re-read them automatically: 0 8 1 runs every Monday at 08:00 in the timezone you pick. Be honest with yourself about what this gives you: a fresh copy of the text on each run, page by page. It does not compute a diff for you. If you need "what changed", export both runs to a spreadsheet and compare, or connect the run to whatever tool you already use for comparisons. Also note that unnamed run datasets on Apify expire after 7 days. If you want to keep results, export them, or name the dataset. hasText: false and empty text. If your documents are scans, you need an OCR tool instead; several exist on the Store and elsewhere. textTruncated is set to true , so you can spot it. Prices can change; the Pricing tab on the Store page https://apify.com/ahmed.fouaad82/public-pdf-text is the authoritative source. pdftotext Poppler or Python libraries like pypdf do the same text extraction locally for free. A hosted tool saves you setup, scheduling and hosting, not magic. There is a ready-made example you can open and run as is: Extract text from public PDF URLs page by page https://apify.com/ahmed.fouaad82/public-pdf-text/examples/extract-text-from-pdf-urls . Swap in your links, keep "Maximum pages" at 25 for a free first test, and check the hasText column first. If most rows say false , your PDFs are scans and you need OCR, not this. If something breaks on a public PDF that opens fine in your browser, open an issue on the Store page with the URL. I read them.