PDF Text Extractor — Text & Metadata from URLs
Download PDF files by URL and extract their text and metadata (page count, title, author) — whole-document or per-page. Honest per-URL status. No auth.
PDF Text Extractor — Text & Metadata from URLs returns 10 documented output fields, including url, status, pages, totalPages and page. Every field carries a declared type, a written description and an example value. 47 runs are recorded on Apify.
- 10
- Output fields
- 4
- Inputs
- 47
- Runs
- 2026-10-15
- Last run
01 — output
What it returns
Every field the extractor writes to its dataset, with its type, a written description and an example value.
| Field | Type | What it holds | Example |
|---|---|---|---|
| url | stringnull | The URL this row describes. | https://example.com/pricing |
| status | stringnull | Outcome recorded for this row. | ok |
| pages | integernull | Total pages seen or fetched. | 0 |
| totalPages | integernull | Total pages available or fetched. | 0 |
| page | integernull | Page number this record came from. 1-based. | 1 |
| title | stringnull | Title as the source writes it. | Wireless Bluetooth Headphones |
| author | stringnull | Author of this record, as the source publishes it. | jane.cooper |
| charCount | integernull | Number of characters in this record's text. | 4821 |
| text | stringnull | Plain text content of this record. | <text> |
| error | stringnull | Why this row failed, when it did. Null on success. | <error> |
02 — sample
One record
Assembled from the example values declared on the schema above, not invented at render time.
{
"url": "https://example.com/pricing",
"status": "ok",
"pages": 0,
"totalPages": 0,
"page": 1,
"title": "Wireless Bluetooth Headphones",
"author": "jane.cooper",
"charCount": 4821
}03 — input
What you give it
| Input | Type | Description |
|---|---|---|
| pdfUrls | arrayrequired | Direct links to PDF files. |
| perPage | booleanoptional | Off: one row per PDF (full text). On: one row per page. |
| useProxy | booleanoptional | For hosts that block datacenter IPs. |
| maxItems | integeroptional | Hard cap. |
04 — run
Run PDF Text Extractor on your own input
It runs in the cloud on Apify. Nothing to install, and you are billed per result returned rather than per attempt.
05 — questions
Asked before running it
10 of 10 fields described
- What does PDF Text Extractor — Text & Metadata from URLs return?
- It returns 10 documented output fields: url, status, pages, totalPages, page, title, author, charCount, text and error. Each field declares its type, a description of what it holds, and an example value.
- What input does PDF Text Extractor — Text & Metadata from URLs require?
- pdfUrls is required. A further 3 inputs are optional. The full input schema, with types and defaults, is below.
- Does PDF Text Extractor — Text & Metadata from URLs need an API key or login?
- No. None of its inputs is a credential, and it reads only public data. Nothing to sign up for before the first run.
- How do I run PDF Text Extractor — Text & Metadata from URLs?
- It runs on Apify. Start it from its listing with the inputs above, or call the Apify API with the Actor's ID. Results land in a dataset you can export as JSON, CSV or Excel, or read through the Apify API into your own pipeline.