# Changelog of PDF Text Extractor - Upload & Base64 (`automa-flow/pdf-text-extractor`) Actor

- **URL**: https://apify.com/automa-flow/pdf-text-extractor/changelog.md
- **Full Actor documentation**: https://apify.com/automa-flow/pdf-text-extractor.md

## What's new

### 24 September 2026: More reliable batch completion

**0.1, private release candidate**

- Large batches keep extracted text on temporary disk so later duplicates can reuse it without retaining every document in memory.
- When time runs out, remaining document statuses are saved in batches. If their storage cannot be confirmed, the run reports `SYSTEM_FAILURE` and lists unconfirmed inputs in `RUN_SUMMARY`. Confirmed results remain available.
- A stopped or crashed parser no longer prevents the next document from being processed.
- HTTP-compressed downloads are rejected. Serve the PDF without HTTP content compression; compression inside a PDF remains supported.
- Uploads and public URLs use separate download authorization. A public URL cannot reuse a privately downloaded upload.

No input migration is required. There is no `pdf-extracted` fee for failures or duplicates. The start fee and platform usage still apply.

### 23 September 2026: Extract text from a digital PDF

**0.1, initial private candidate**

Send public PDF URLs, upload one PDF, or pass base64. Each document gets a Dataset row with its status, text, page count and basic metadata. Scans return `NO_TEXT_LAYER`; OCR and password removal are not supported.

Runs accept up to 200 documents in total, including at most 32 base64 files and one upload. File, page, text and parser-time limits keep unusually large documents bounded. Duplicates within a run reuse the first result without another extraction fee.

Set `maxTotalChargeUsd` before an API or agent run. At the default 1 GB memory, allow $0.01 to start plus $0.003 per unique successful PDF, with platform usage billed separately.