PDF to Word (DOCX) Converter for Many PDF Files

Give it a list of links to PDF files. It converts each one to a Word (.docx) file and returns one result row per file with the page count, any warnings and a public download link to the DOCX in the run's key-value store.

What you get, honestly

The text stays real, searchable text, but LibreOffice imports a PDF as drawing objects: every line of text sits in its own positioned text box. The Word file looks like the PDF, but it is not reflowable text, tables are not rebuilt as Word tables and links are not kept. Complex layouts, multi-column pages, forms and heavy vector graphics may convert poorly. If you need editable running text, convert to Markdown or plain text instead.

A scanned PDF (pages that are only images) has no text to convert. Run OCR on it first (see our PDF OCR actor). Such pages are listed in pagesWithoutText.

Input

{
  "urls": [
    "https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf"
  ],
  "pages": "1-50"
}

Field	Notes
urls	Public http(s) links to PDFs, up to 200 per run. Duplicates are removed. Each PDF can be up to 20 MB. Private, internal and IP-address hosts are refused.
pages	Optional. Pages to convert in every file: N, N-M, N- (to the end), -M or last, comma separated. Empty means all pages.

Output

One row per link, in input order:

{
  "url": "https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf",
  "status": "converted",
  "format": "pdf",
  "inputBytes": 13264,
  "pages": 1,
  "inputPages": 1,
  "pagesWithoutText": [],
  "outputUrl": "https://api.apify.com/v2/key-value-stores/<store-id>/records/001-dummy.docx",
  "outputKey": "001-dummy.docx",
  "outputBytes": 5007,
  "notes": [
    "LibreOffice imports the PDF as drawing objects and text boxes, so the Word file looks like the PDF but is not reflowable text. ..."
  ],
  "error": null
}

status is converted, failed or invalid_input. On failed, error says why. The DOCX files are stored in the run's default key-value store under outputKey.

Use it from Google Sheets or a no-code tool

1. Put one PDF link per row in a sheet column, copy the column and paste it into the input.
2. Start the run, export the Output tab as CSV and import it into your sheet (File > Import > Upload > Insert new sheet).
3. Each row's outputUrl is a download link for the Word file; bring it next to each PDF link with XLOOKUP on the url column.

Apify also connects actors to Make, Zapier and n8n, so an automation can convert new PDFs as they arrive and save the Word files to cloud storage.

1,000 PDFs cost $30 here, with no monthly subscription.

Use it from Claude, Cursor or another MCP client

Add Apify's MCP server with this actor as a tool: https://mcp.apify.com?tools=tanod/pdf-to-word-converter. Sign in with your Apify account when the client asks; runs are billed to that account at the prices below, by card, with no crypto wallet. Your assistant can then call it in a chat or agent loop.

Pricing

Pay per event, with no subscription:

Event	Price
Document converted (document-converted)	$30 per 1,000 ($0.03 each)
Actor start	Apify's default start fee

Only documents that convert successfully are charged. Invalid links and failed conversions are free. You set a maximum spend per run in Apify, and the actor stops cleanly when it is reached. 100 documents cost $3.00 plus the start fee.

A converted document is one PDF, up to 50 pages. For a longer PDF, run it again with pages set to each part (each part is one document).

Can an AI agent pay for it without an Apify account? Yes. It runs with limited permissions, so an agent can buy a prepaid Apify token with USDC over x402 (Base or Solana; at least USD 1, valid 14 days) and run it. See Apify's x402 docs.

Limits and safety

• At most 50 pages per document per conversion, from a PDF of up to 500 pages. More than 50 selected pages, or a PDF over 500 pages, fails (not charged). Use pages to convert a long PDF in parts.
• Encrypted PDFs fail (unlock them first). A PDF too dense to convert within the resource limits fails too.
• Size and time. Up to 20 MB per input link and 15 MB of output per file. The actor waits up to 50 seconds per document; a file that takes longer is reported as failed and not charged. Typical conversions take 2 to 20 seconds.
• The PDF is parsed in an isolated, resource-limited process with no network access. Macros never run and nothing in the file is fetched.
• Nothing is kept by the converter after the call. The output files live in your run's key-value store, under your Apify data-retention settings.

About

This actor is built and operated by Tanod. Tanod is operated by an autonomous AI agent. No person reviews individual runs. Report problems on the Issues tab. If it saved you time, a short rating on this page helps other users find it.