DocSpring vs PDF.co
Compare a general PDF processing toolkit with a service built around reusable templates.
Our take
PDF.co is a Swiss Army knife. It fills AcroForm fields by name, overlays text at coordinates, converts HTML and Office files, merges, splits, renders page images, extracts data with AI, and runs OCR, all through one API with SOC 2 Type II, every major automation connector, and an open-source MCP server. If your pipeline starts with a scanned document and ends with a filled one, PDF.co covers steps DocSpring does not attempt.
It is not a template service. Field names or coordinates travel in every request, there is no field editor, no versioning, no forms, no signing workflow, the shared API is hosted in the US, and credits are charged per page per operation. Filling a one-page form costs 21 credits; a five-page contract costs 105. DocSpring stores the template instead. Upload a PDF once and AI field setup finds and names its fields, or fill a ready-made form from the Form Library in the US region, then send only the data. Choose PDF.co for varied processing. Choose DocSpring when the same documents are filled repeatedly, when non-developers maintain the templates, when people need to fill in or sign the document themselves, or when documents must stay in the EU.
PDF processing and template management
PDF.co covers a broad range of PDF operations, including conversion, extraction, OCR, merging, and adding content to files. Its PDF editing API can fill named form fields or place text and images at coordinates. DocSpring organizes filling around stored templates, with AI field setup, a field editor, and a data schema, and also builds new documents from Word, HTML, and page designs.
For a PDF you fill repeatedly, compare where the field mapping lives and who updates it. For a pipeline that starts with scanning or extracting a document, PDF.co handles processing steps outside DocSpring's document generation workflow.
Choose DocSpring for reusable document templates
Store field positions and types in a template, set them up with AI, validate incoming JSON, and let your team or customers edit fields visually. Build new documents in the Page Designer or from Word and HTML templates, and add web forms or signature requests when people need to complete the document.
Choose PDF.co for varied PDF processing operations
Your workflow needs OCR, data extraction, conversion, or file manipulation alongside filling. Evaluate the whole API pipeline and its credit usage rather than comparing only one fill request.
Feature comparison
Follow the feature links for details in DocSpring's documentation. Sources for each PDF.co cell are listed at the end of the page.
Scroll the table sideways to see both products.
| What you need | DocSpring | PDF.co |
|---|---|---|
| Templates | ||
| Fill an existing PDF | Yes Overlay fields on your PDF. Import its form fields, let AI find and name them, or place your own. | Yes The PDF edit endpoint fills existing fields by name or places text and images at coordinates. 21 credits per page. |
| AI field setup | Yes Finds the fields on flat and fillable PDFs. AI names them, sets their types, groups repeated rows into lists and adds conditional logic, then you review the changes. Every plan includes free AI pages each month. | No No field setup for filling. Its AI tools parse invoices, convert PDFs to JSON, and classify documents, and a form info reader lists a fillable PDF's existing field names. |
| Library of ready-made forms | Yes Fill tax, insurance, real estate, court and other forms from the DocSpring Form Library with your own API token. We keep them up to date. US region only. | No No ready-made forms. You supply each PDF and its field names or coordinates. |
| Visual document design | Yes Build a PDF on a blank page in the Page Designer, with text, images, tables, charts, QR codes, barcodes, fillable form fields, headers and footers. An AI assistant can build one too, through the MCP server. | No No document layout designer. The dashboard editor is for data extraction templates. |
| HTML to PDF | Yes HTML/CSS and Liquid templates, with code editors and a PDF preview. | Yes Converts raw HTML or a stored HTML template to PDF. 9 credits per page. |
| Repeat a list of items | Yes Tables and repeating sections in page designs, and Liquid loops in HTML and Word templates, carry on over as many pages as they need. Fields on an uploaded PDF can address array items. | Yes Handlebars each blocks repeat rows in stored HTML templates. |
| Conditional content | Yes Show or require PDF fields with conditional rules. Use Liquid conditions in page designs, HTML and Word templates. | Yes Handlebars if and unless blocks control content in HTML templates. |
| Word and PowerPoint templates | Conditions apply: Word only Upload a Word document (.docx) or OpenDocument file (.odt) with Liquid tags, and get a PDF, a Word document, an OpenDocument file, or more than one. No PowerPoint. | No Converts DOCX and PPTX files to PDF, but does not merge data into Office templates. |
| Template versioning | Yes Edit drafts, see what changed since the last version, publish numbered versions, and pin API requests to one. | No HTML templates are stored by ID and edited in place. No version history. |
| Editable PDF output | Yes Keep a PDF template's text and checkbox fields editable, or flatten the filled content. Page designs can add fillable text fields, checkboxes, radio buttons and drop-downs. | Yes Filled fields stay editable unless you add the flatten profile. |
| HTML template language | Yes: Liquid Store template logic with the layout and supply JSON data when generating a document. | Yes: Handlebars Stored HTML templates use Handlebars syntax with loops, conditionals, and helpers. |
| API integration | ||
| Synchronous generation | Yes Use sync.api.docspring.com to receive submission JSON and a PDF download URL in one request. | Yes Default sync mode returns the output URL, with a 30 second processing limit. |
| Asynchronous generation | Yes Send wait=false to return immediately. Receive a webhook or check the submission status later. | Yes Set async=true to receive a job ID and poll the job check endpoint, which costs 2 credits per call. |
| Webhooks | Yes Receive notifications about PDF generation and signature request events. | Yes A callback URL receives a POST when an async job finishes, retried up to three times. |
| Batch PDF generation | Yes Generate up to 50 PDFs in a request with different templates and data. | No One input per request. Run many async jobs from your workflow tool. |
| Combine PDFs | Yes Combine generated PDFs and other PDF files into one document. | Yes Merges PDFs for 2 credits per page. A separate endpoint also accepts Office files, images, and ZIP archives, at 35 credits per page. |
| Images of the pages | Yes Add png to a submission's output formats to get an image of each page of its PDF. | Yes Separate endpoints render PDF pages as PNG, JPG, WebP, or TIFF images, for 12 to 28 credits per page. |
| MCP server | Yes A hosted MCP server for Claude, ChatGPT, Cursor and other AI assistants, with OAuth sign-in and read-only, read and write, or full access. Open-source agent skills teach coding agents the API. | Conditions apply: Local server An open-source MCP server runs on your computer with your API key and gives Claude Desktop, Claude Code, Codex, Cursor, and VS Code 38 PDF.co tools. There is no hosted server for web assistants. |
| Integrations | ||
| AWS S3 | Yes Upload every generated PDF to your own S3 bucket, or to Cloudflare R2, Google Cloud Storage, Backblaze B2, Wasabi, DigitalOcean Spaces or MinIO. | No Output lands in PDF.co's temporary storage behind signed links. Copy it to your bucket with another step. |
| Google Drive, Dropbox and Box | Yes Save every generated PDF to a folder in Google Drive (shared drives too), Dropbox (team folders too) or Box, with file paths built from your data. | No No built-in uploads to Google Drive, Dropbox, or Box. Zapier, Make, and Power Automate workflows move files between them and PDF.co. |
| Zapier | Yes Generate PDFs and start signing workflows through the Zapier integration. | Yes Official app with PDF filler, HTML to PDF, merge, parse, and split actions. |
| n8n | Yes Community node for PDF generation and signing workflows. | Yes: Community node PDF.co publishes an n8n community node with fill, convert, merge, and parse operations. |
| Make.com | Yes DocSpring app for PDF generation, signature requests and templates. | Yes Verified app with 27 modules, maintained by Artifex, including Fill a PDF Form and Convert HTML to PDF. |
| Pipedream | Coming soon DocSpring integration is planned. | Yes Pipedream app with 17 actions. No triggers. |
| Forms and e-signatures | ||
| Embed the template editor | Yes Embed the template editor on any paid plan, from Starter, for PDF, Word, page design and HTML templates, and choose which controls your users can access. | No No embeddable editor. Field positions are passed in each request. |
| Collect data with forms | Yes Every template gets a web form you can share or embed, and a PDF template can also be filled in on the page. | No Creates fillable PDF fields but has no hosted web forms for collecting data. |
| Electronic signatures | Yes Signature requests support ESIGN/UETA signing workflows on every plan, live once your account has made a payment. Signers sign in order or all at once. | No Places a signature image on a PDF. No signer workflow, emails, or audit trail. |
| Embedded signing | Yes Show the signing form in your app with a short-lived authentication token. | No No signing workflow. |
| Security and deployment | ||
| SOC 2 Type II | Yes Completed audit. Request the report through our Trust Portal. | Yes SOC 2 Type II compliant, audited under Artifex Software. |
| GDPR compliance | Yes GDPR compliant. Our Trust Portal lists security controls and policies. | Conditions apply: DPA on request Relies on AWS standard contractual clauses and offers a DPA on request. Data is stored in the US. |
| HIPAA compliance | Yes HIPAA compliant, with a BAA on every paid plan, including Starter. Sign it before sending health records. | Not published The security page says AWS enables HIPAA workflows but PDF.co does not publish a BAA. |
| ISO 27001 | No Not certified. DocSpring's security controls are audited under SOC 2 Type II. | No Cites AWS data center ISO 27001 only. |
| Automatic document deletion | Yes Set an expiry per template for submission data, generated PDFs, and uploaded images. | Yes Output files expire after 60 minutes by default. An expiration parameter changes this within plan limits. |
| US and EU hosting | Yes Choose the US or EU service region. | Conditions apply: Enterprise The shared API runs in AWS Oregon. Enterprise customers can get a dedicated server in a chosen region. |
| Self-hosting | Yes: Enterprise Self-hosted enterprise licenses are available. | No The API runs in PDF.co's cloud, with a dedicated server for Enterprise customers. For self-hosted processing, PDF.co points to a separate library built on MuPDF. |
| Company | ||
| Founded | 2017 Launched as FormAPI in October 2017 and renamed DocSpring in 2019. | 2017 The earliest archived pdf.co page, from July 2017, shows a beta by ByteScout. Artifex Software has run PDF.co since July 2023. |
"Not published" means the vendor's public materials do not say either way, usually because it is handled on request. A dedicated integration is different from connecting an API through a generic HTTP action. Plan requirements and product boundaries are noted in the cells.
Fill the same PDF repeatedly from customer records
Take an application with a customer name and email. An existing AcroForm field and a blank space that needs a text overlay are different inputs; test both if your documents contain a mix.
In DocSpring
Upload the PDF once. AI field setup imports its form fields and finds the blank spaces that need new ones, then names and types them. Review them in the editor, with the two fields named customer_name and customer_email.
Send each customer's JSON to the stored template. The field mapping stays with the template instead of being repeated in every request. Publish a new version when the form changes.
In PDF.co
Supply the source PDF to the PDF editing endpoint. Address existing form fields by name, or pass annotations with coordinates for text and image overlays.
Save the output URL or track the asynchronous job. If the pipeline also needs OCR, extraction, or merging, add the relevant operations and account for their inputs, outputs, and credit costs.
Fill a stored DocSpring template
After creating the two fields, this request only needs the template ID and customer data. Field coordinates are stored in the template.
curl --fail-with-body \
"https://sync.api.docspring.com/api/v2/templates/${DOCSPRING_TEMPLATE_ID}/submissions" \
--user "${DOCSPRING_TEST_TOKEN_ID}:${DOCSPRING_TEST_TOKEN_SECRET}" \
--header 'Content-Type: application/json' \
--data '{
"test": true,
"data": {
"customer_name": "Mira Patel",
"customer_email": "mira@example.com"
}
}'
Set the environment variables to your template ID and test API credentials. Accounts in our EU region send requests to sync.api-eu.docspring.com instead. The response includes a download URL for a watermarked PDF. See the request and response guide.
Replace the source PDF with a revised form and check every field position. For a coordinate-based integration, verify the mapping and page dimensions instead of assuming the old positions still fit.
Credits per page per operation
DocSpring
The free Developer plan includes 200 credits a month. Paid plans start with Starter at $49 a month for 10,000 credits. A filled PDF form costs 20 credits (9.8¢ on Starter), a PDF from an HTML template or a page design 4, a Word document 20, and each person who signs a signature request 60; longer documents cost more, and keeping documents for more than 30 days uses a few storage credits a month. Larger plans lower the price to 0.9¢ per filled PDF form, unused paid-plan credits roll over for 12 months, and credit packs top up any plan. Every plan includes e-signatures, every paid plan includes the embedded template editor and a HIPAA BAA, and you can try a paid plan's features free for 14 days without a card.
See all DocSpring plansPDF.co
PDF.co's free trial lasts 30 days or 10,000 credits, whichever runs out first, and then you need a plan. Basic is $8.99 per month billed annually, or $9.99 monthly, for 16,500 credits. Filling or adding to a PDF costs 21 credits per page, HTML to PDF 9 per page, merging 2 per page, and checking an async job 2 per call. Credit packs top up an active plan, never expire, and cost up to 30% more than plan credits.
Because credits are per page, a five-page contract costs five times a one-page form. A plan's credits reset each month, and output links expire after 60 minutes on lower plans, so your workflow must fetch files promptly.
PDF.co pricing pageBasic's 16,500 credits cover about 785 one-page form fills a month, or about 157 five-page contracts. On DocSpring an ordinary filled PDF of up to 10 pages costs 20 credits, so 785 one-page fills cost $89 (the Starter plan with 20,000 credits) and 157 five-page contracts cost $29 (a 5,000-credit pack on the free Developer plan). PDF.co is cheaper for both; DocSpring stores the field mapping, so each request carries only the data. For a pipeline that also extracts or OCRs, price those PDF.co operations separately.
Moving PDF.co filling to DocSpring
Collect the original PDFs and the field names or coordinates used by your editing requests. Upload each PDF and let AI field setup import its form fields or find the blank spaces, then check the names against your application's data.
Replace source-file and annotation requests with a stored template ID and submission data. Update authentication, result URLs, and asynchronous job handling. Check fonts, checkbox values, images, and whether the output should remain editable. Stored HTML templates move to DocSpring HTML templates, with Liquid in place of Handlebars.
Keep extraction or OCR steps in PDF.co if the application still needs them. Switching the PDF filling component does not replace a broader document-processing pipeline.
Questions about PDF.co alternatives
Ask us about your documentsCan DocSpring replace PDF.co for OCR or extraction?
No. DocSpring generates and fills documents. Its AI field setup finds the fields on a scanned form so you can fill it, but it doesn't extract data from documents. Keep OCR and extraction steps in PDF.co or a similar service and send the extracted data to DocSpring to create the output document.
Is placing a signature image the same as an e-signature workflow?
No. A signing workflow also needs to identify the participant, capture their consent and actions, and retain the audit record. DocSpring's signature requests provide signing forms and audit events; PDF.co places an image.
Does PDF.co store my field layout?
Only for HTML templates. For PDF filling, field names or coordinates are sent with every request, so a changed form means changing code. DocSpring stores the layout in a versioned template edited in the browser.
Do PDF.co and DocSpring work with AI assistants?
Yes. PDF.co's MCP server runs on your computer with your API key and gives desktop and coding assistants tools to convert, extract, merge, and fill PDFs. DocSpring's MCP server is hosted, with OAuth sign-in, so it also works in Claude on the web, and it fills your templates, builds page designs, and sets up fields, making free test PDFs unless you ask for a live one.
About this comparison
We reviewed DocSpring's documentation and implementation alongside PDF.co's published product, API, pricing, and security information. Prices and plan limits were checked on the review date shown at the top of the page. The workflows describe documented behavior; they are not performance benchmarks. Features and plans can change after the review date.
Sources
- PDF.co API documentation
- PDF.co fill PDF forms endpoint
- PDF.co HTML template conversion
- PDF.co pricing and credit packs
- PDF.co credits per API function
- PDF.co sync and async modes
- PDF.co webhooks and callbacks
- PDF.co PDF to PNG
- PDF.co AI Invoice Parser
- PDF.co MCP server
- PDF.co security knowledge base
- PDF.co SOC 2 Type II under Artifex Software
- PDF.co dedicated server and MuPDF self-hosted library
- PDF.co on Zapier
- PDF.co on Make
- PDF.co n8n community node
- PDF.co on Pipedream
- Artifex Software takes over PDF.co and ByteScout
- pdf.co in July 2017 (Internet Archive)
Spotted something that needs correcting? Send us the detail and a source.
Product names, logos, and brands are the property of their respective owners and are used here for identification and comparison only. Their use does not imply any affiliation with or endorsement by those companies.
Related comparisons
Other products people compare with PDF.co.
Try filling a stored PDF template
Upload a PDF or a Word document, design a page, or write HTML, then send a test request. No credit card needed.
