/// CONVERT
1 credit

Email to PDF API — archive a message as a PDF

Headers, the HTML body and a list of attachments, rendered to one PDF — with tracking pixels blocked by default.

/// Quick answer

Email to PDF renders an `.eml` message — From, To, Cc, Date and Subject (RFC 2047 encoded headers are decoded, so accented names and Unicode subjects come out correctly), then the HTML body, then a list of the attachments with their types and sizes. Remote images are **not** loaded by default: a message's tracking pixels and any externally hosted image are stripped before rendering, so converting a message can't signal the sender that it was opened. Set `allow_remote_images: true` to load them. Inline images carried inside the message itself (`cid:` parts) are always shown, since they need no outside request. Attachments are listed, not extracted — the PDF is the message, not its payload.

Try Email to PDF API — free →Read the docs

How does the Email to PDF API work?

One HTTP request from any language. Every ASHDOCS endpoint uses the same X-API-Key header.

curl -X POST 'https://api.ashdocs.com/api/v2/tools/email-to-pdf' \
  -H 'X-API-Key: ash_live_...' \
  -F 'file=@message.eml' -F 'options={"allow_remote_images":false}'

Common use cases

Frequently asked questions

How much does the Email to PDF API tool cost?+

1 credit per successful call. Sandbox keys (prefix ash_test_) run the tool end-to-end without ever consuming credits — use them in CI or for tuning.

What is the endpoint URL for this tool?+

The endpoint is documented in the curl example on this page. All ASHDOCS endpoints share the base URL https://www.ashdocs.com and require an X-API-Key header.

Can I run this tool inside Make, Zapier, or n8n?+

Yes — through each platform's built-in HTTP mechanism (Make's HTTP module, Webhooks by Zapier, n8n's HTTP Request node). Nothing to install: point it at this exact endpoint with your X-API-Key header. See /integrations/make, /integrations/zapier or /integrations/n8n for step-by-step setup.

Does this tool support batch or scheduled runs?+

Yes. POST /api/v1/batch runs any tool over up to 50 files with a single credit ledger entry, and pipeline schedules let you trigger the same tool on a cron. Both are documented in /docs.

RELATED TOOLS