DocSpring vs Plumsail Documents

Compare Plumsail's document processes and Microsoft 365 integrations with DocSpring's templates, signing, and API.

Our take

Plumsail Documents generates documents through processes. A process holds one or more templates (Word, Excel, PowerPoint, HTML, or a fillable PDF), fills them all from one set of data, and can merge the results into a single PDF. It builds a web form from the templates' fields and counts each process run as one document, however many templates the run fills. It works closely with Power Automate, SharePoint, OneDrive, and Teams, sends documents to DocuSign, Adobe Sign, and other signing services, and hosts accounts in the US, the EU, Australia, Switzerland, or Canada. For a team that works in Microsoft 365 and builds packets of Office documents, it is a strong fit.

DocSpring is built for developers who put documents inside their own product. AI field setup finds and names the fields on any PDF, scans included, where Plumsail fills only the form fields a PDF already has. The Page Designer lays out new documents on a blank page, templates have published versions you can pin requests to, the template editor embeds in your app, and signature requests with an audit trail and emails to your signers are built in. Plumsail fills a packet of templates in one request, while on DocSpring your app sends each template its data in a batch and then combines the PDFs. Choose Plumsail for Microsoft 365 workflows, PowerPoint and Excel templates, or packets billed as one document. Choose DocSpring if your documents start as PDF forms, your customers edit templates in your product, or you want signing, an embedded editor, and a HIPAA BAA from one vendor.

Document packets and Microsoft 365 workflows

Plumsail Documents suits teams that keep their templates in Word, Excel, or PowerPoint and run their work in Microsoft 365. Its Power Automate connector starts processes from any flow, and its deliveries save the results to SharePoint, OneDrive, Google Drive, Dropbox, or Box, email them, or send them for signature. DocSpring starts from a PDF form, a Word document, a page design, or an HTML/CSS template, and fills it from JSON sent by your application.

The biggest difference is the process. One Plumsail process can fill a Word cover letter, a fillable PDF application, and an HTML certificate from the same JSON and return them as one merged PDF, with one form and one set of fields for all three. DocSpring fills each template with its own submission. Send the submissions together in a batch, then combine the generated PDFs, with any other PDF files, into one document in the order you choose.

PDF forms work differently too. Plumsail fills the form fields a PDF already has, matched by name, so you add and name them in Acrobat or another PDF editor first. DocSpring imports a PDF's existing fields, or finds the fields on a flat or scanned PDF with AI and names them, and you can place more in its editor.

Choose DocSpring for PDF forms and documents inside your product

Fill official and customer PDFs whether or not they have form fields, design new documents in the Page Designer, Word, or HTML, and let your customers edit templates in an embedded editor. Collect signatures with DocSpring's own signature requests, pin API requests to a published template version, and save every PDF to S3, Google Drive, Dropbox, or Box.

Choose Plumsail Documents for Microsoft 365 and document packets

Your templates live in Word, Excel, or PowerPoint, your workflows run in Power Automate and SharePoint, or each record needs several documents merged into one PDF from one request and billed as one document. Its data centers in Australia, Switzerland, and Canada matter if your data has to stay in one of those countries.

Feature comparison

Follow the feature links for details in DocSpring's documentation. Sources for each Plumsail Documents cell are listed at the end of the page.

Available Not available Conditions apply Not published Coming soon

Scroll the table sideways to see both products.

Plumsail Documents and DocSpring: templates, processes, APIs, integrations, signing, and security
What you need DocSpring Plumsail Documents
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 Fills a PDF's existing form fields, matched by name, including checkboxes, radio buttons, images, and QR codes. You create the fields in Acrobat or another PDF editor first.
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 AI field detection. Fields are added in a desktop PDF editor, and there is no online editor for PDF templates.
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. Conditions apply: Sample templates A gallery of sample templates, mostly Word documents with a few Excel, PowerPoint, and fillable PDF forms, each with a form for its data.
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. Conditions apply: Online Office editor Word, Excel, and PowerPoint templates can be edited online in an editor based on Google Docs. There is no drag-and-drop designer for building a page.
HTML to PDF Yes HTML/CSS and Liquid templates, with code editors and a PDF preview. Yes HTML templates with Handlebars-style tokens, converted to PDF.
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 A token over a list repeats a table row, list item, or section in Word templates, nested lists included, and each blocks repeat content in HTML templates.
Conditional content Yes Show or require PDF fields with conditional rules. Use Liquid conditions in page designs, HTML and Word templates. Yes If and else blocks and hide-if rules in templates, and process rules that fill a template only when the data meets its conditions.
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. Yes Fills Word (DOCX), Excel (XLSX), and PowerPoint (PPTX) templates, and converts them to PDF.
Template versioning Yes Edit drafts, see what changed since the last version, publish numbered versions, and pin API requests to one. No No template version history is published. A recycle bin keeps deleted processes for 30 days.
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 Fillable PDF templates lock their fields by default. Turn off Lock PDF form fields to keep them editable.
API integration
Synchronous generation Yes Use sync.api.docspring.com to receive submission JSON and a PDF download URL in one request. Yes Starting a process or generating a document returns a download link in the response, and fails after 30 seconds.
Asynchronous generation Yes Send wait=false to return immediately. Receive a webhook or check the submission status later. Yes Job endpoints return a location to poll, and can call a callback URL when the document is ready.
Webhooks Yes Receive notifications about PDF generation and signature request events. Yes A Webhook delivery posts the file's URL and JSON you configure, which can include the run's data, to your endpoint.
Batch PDF generation Yes Generate up to 50 PDFs in a request with different templates and data. Conditions apply: CSV or Excel upload Upload a CSV or Excel file in the dashboard to start one run per row. No batch API endpoint is published.
Combine PDFs Yes Combine generated PDFs and other PDF files into one document. Yes A process can merge its templates' documents into one PDF, and an API endpoint merges files you upload.
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. Not published Release notes mention an MCP server, but no documentation for one is published. Zapier offers MCP access to its actions through its own server.
Use the same data in several PDFs Yes Send the data to several templates in a batch. Your app controls the mapping; combine the outputs when needed. Yes One process fills several templates of different types from one set of data, and its auto-generated form covers the fields of all of them. Each run counts as one document.
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 No Amazon S3 or SFTP delivery. Upload the file from a webhook or an automation platform.
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. Yes Deliveries save documents to Google Drive, Dropbox, Box, OneDrive, or SharePoint.
Zapier Yes Generate PDFs and start signing workflows through the Zapier integration. Yes Official Zapier app that starts processes and runs PDF actions.
n8n Yes Community node for PDF generation and signing workflows. No No n8n node for Plumsail Documents.
Make.com Yes DocSpring app for PDF generation, signature requests and templates. Yes Official Make app that starts processes, including processes with several templates.
Pipedream Coming soon DocSpring integration is planned. No No Pipedream app.
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 template editor. Templates are edited in the Plumsail dashboard.
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. Yes Every process gets a web form built from its fields, to share as a link or embed. Plumsail Forms, a separate product, customizes it.
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. Conditions apply: Through other providers No signing of its own. Deliveries send documents to DocuSign, Adobe Sign, Dropbox Sign, SignNow, Xodo Sign, or Zoho Sign.
Embedded signing Yes Show the signing form in your app with a short-lived authentication token. No Documents go to the signature provider, which handles signing. Plumsail has no signing view to embed.
Signature audit trail Yes Records each email, authentication, viewing, signing, and completion event. When your app sends the links, it provides the authentication and notification details. Conditions apply: Signature provider's The signature provider keeps the audit trail. Plumsail's own audit log records account events.
Multiple signers Yes Assign fields to different people. Generate the final PDF once all signature requests are complete. Conditions apply: Through DocuSign The DocuSign delivery sets several recipients and roles from the data, in order if you choose.
Provider sends signer emails Yes Emails each signer their link, in order if you choose, with reminders, then the signed PDF. Your app can send the links instead. Conditions apply: Signature provider's The signature provider emails signers. The DocuSign delivery sets the message, reminders, and expiry.
Security and deployment
SOC 2 Type II Yes Completed audit. Request the report through our Trust Portal. Yes Completed a SOC 2 Type II assessment. The report is available under NDA from its Trust Center.
GDPR compliance Yes GDPR compliant. Our Trust Portal lists security controls and policies. Yes A data processing agreement with standard contractual clauses is part of its terms.
HIPAA compliance Yes HIPAA compliant, with a BAA on every paid plan, including Starter. Sign it before sending health records. Conditions apply: Ask about a BAA Completed a HIPAA assessment. No BAA offer is published, so ask before sending health information.
ISO 27001 No Not certified. DocSpring's security controls are audited under SOC 2 Type II. No ISO 27001 is not among the certifications in its Trust Center.
Automatic document deletion Yes Set an expiry per template for submission data, generated PDFs, and uploaded images. Yes The data used to fill templates is deleted once the document is made, and generated documents stay in the runs history for 24 hours.
US and EU hosting Yes Choose the US or EU service region. Yes Choose the US, the EU, Australia, Switzerland, or Canada when you sign up. An account can't move to another region.
Self-hosting Yes: Enterprise Self-hosted enterprise licenses are available. No Hosted service only.
Company
Founded 2017 Launched as FormAPI in October 2017 and renamed DocSpring in 2019. 2011 Plumsail began in 2011 with tools for SharePoint, and launched Plumsail Documents in 2019.

"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.

One record, three documents, one PDF

Suppose each approved loan needs a cover letter written in Word, a filled PDF application form, and a one-page certificate, delivered as one PDF. Both products can produce it. The difference is where the packet is defined.

In DocSpring

Upload the cover letter as a Word template with Liquid tags, set to make a PDF, upload the application PDF and let AI field setup find and name its fields, and lay out the certificate in the Page Designer. Each template has its own fields, so your app maps the record's values to each one.

Send the three submissions in one batch request, then combine the three PDFs into one. Have DocSpring save the combined PDF to S3 or Google Drive, or send the application for signature first with a signature request.

In Plumsail Documents

Create a process and add the three templates to it. Write the cover letter and the certificate as Word or HTML templates with tokens, and name the application PDF's form fields to match your data. The process collects every token into one set of fields and builds a form from them.

Set the output to Merged PDF and start the process with one request that holds all the data, from your code, Power Automate, Zapier, or Make. Add a delivery to save the PDF or send it to DocuSign for signature.

Fill three templates and combine them with DocSpring

Once the three templates have their fields, these two requests make the packet. Test submissions are free and watermarked, but combining PDFs uses credits even with a test API token.

Shell
# 1. Fill the three templates from the same record, in one batch
curl --fail-with-body \
  "https://sync.api.docspring.com/api/v2/submissions/batches" \
  --user "${DOCSPRING_TEST_TOKEN_ID}:${DOCSPRING_TEST_TOKEN_SECRET}" \
  --header 'Content-Type: application/json' \
  --data '{
    "test": true,
    "output_formats": ["pdf"],
    "submissions": [
      {
        "template_id": "tpl_1234567890abcdef01",
        "data": { "customer_name": "Mira Patel", "loan_amount": 25000 }
      },
      {
        "template_id": "tpl_1234567890abcdef02",
        "data": { "customer_name": "Mira Patel", "customer_email": "mira@example.com" }
      },
      {
        "template_id": "tpl_1234567890abcdef03",
        "data": { "customer_name": "Mira Patel", "approved_on": "2026-11-12" }
      }
    ]
  }'

# 2. Combine the three PDFs into one, in order, using the IDs in the batch's "submissions"
curl --fail-with-body \
  "https://sync.api.docspring.com/api/v2/combined_pdfs" \
  --user "${DOCSPRING_TEST_TOKEN_ID}:${DOCSPRING_TEST_TOKEN_SECRET}" \
  --header 'Content-Type: application/json' \
  --data '{
    "source_pdfs": [
      { "type": "submission", "id": "sub_1234567890abcdef01" },
      { "type": "submission", "id": "sub_1234567890abcdef02" },
      { "type": "submission", "id": "sub_1234567890abcdef03" }
    ],
    "metadata": { "pdf_filename": "loan_packet_mira_patel" }
  }'

Replace the template IDs with your own, and the submission IDs with the ones the first request returns, then set the environment variables to your 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.

Test a record with a long name and one with missing optional fields, and check that the page order, page sizes, and page numbers in the combined PDF are what you expect.

Documents per month against credits per document

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 plans

Plumsail Documents

Plumsail Documents publishes three plans. Folder is $29 a month for 200 documents, Drawer is $99 for 1,000, and Cabinet is $299 for 3,500, or $25, $84, and $249 a month billed annually. Extra documents cost $15 per 100 and roll over to the next month, an SLA comes only with Cabinet, and there is a free 30-day trial.

Plumsail counts each process run, Power Automate action, or API call as one document. A run that fills three templates and merges them into one PDF is still one document, and test runs are free with a watermark.

Plumsail Documents pricing page

For 500 loan packets a month like the one above, Plumsail needs 500 documents: the $29 Folder plan with 300 extra documents, about $74 a month, or the $99 Drawer plan. On DocSpring each packet is three documents plus combining them: 500 Word cover letters, 500 filled application forms, 500 one-page certificates, and 500 combined PDFs need 30,000 credits, which is the Starter plan with 20,000 credits plus a 10,000-credit pack, at $144. Plumsail is cheaper for packets like this. For 1,000 single PDFs a month from a page design or an HTML template, Plumsail's Drawer plan is $99 a month, and DocSpring needs 4,000 credits, a 5,000-credit pack on the free Developer plan, at $29.

Moving Plumsail Documents processes to DocSpring

Start with each process's templates and a sample of the data it runs with. A Word template moves over as a Word template once its tokens are rewritten as Liquid tags, and an HTML template moves over with the same change. Excel and PowerPoint templates need a new home, so export a fixed layout to PDF or rebuild it in the Page Designer.

Upload each fillable PDF as a PDF template. Choose Preserve form field names when you upload it, and DocSpring keeps the PDF's field names, so your data keys can stay the same. For a process with several templates, send the templates' submissions in one batch and combine the PDFs, and decide which of your app's values go to each template.

List every delivery before switching: storage folders, emails, webhooks, and signing services. DocSpring saves PDFs to S3, Google Drive, Dropbox, and Box, sends webhooks, and collects signatures itself, so a DocuSign step can become a signature request on a PDF template. Rebuild the rest in your app or automation platform, and replace Power Automate steps with DocSpring's Zapier or Make apps or an HTTP request to the API.

Discuss your documents with us.

Questions about Plumsail Documents alternatives

Ask us about your documents

Can DocSpring fill several templates with one request?

Not as one templated packet yet. A batch request fills up to 50 templates in one call, each with its own data, and the combine endpoint merges the generated PDFs, uploaded files, and PDFs from URLs into one document. Your app decides which values go to each template. Plumsail's processes keep that mapping in the template setup.

Does DocSpring work with Power Automate and SharePoint?

DocSpring has no Power Automate connector. Flows can call its REST API with an HTTP action, and its Zapier and Make apps connect it to Microsoft 365 apps. DocSpring saves PDFs to Google Drive, Dropbox, Box, and S3, not to SharePoint or OneDrive.

Can I use PDF forms that have no form fields?

In DocSpring, yes. AI field setup finds the fields on a flat or scanned PDF, names them, and adds conditional logic for you to review, and you can place fields by hand. Plumsail fills only form fields the PDF already has, so a flat PDF needs its fields added in a PDF editor before Plumsail can use it.

Which one can collect signatures?

DocSpring sends signature requests on PDF templates itself, emails signers their links in order if you choose, embeds signing in your app, and adds an audit trail. Plumsail sends documents to a signature service you already pay for, such as DocuSign or Adobe Sign, which handles the signing and the audit trail.

About this comparison

We reviewed DocSpring's documentation and implementation alongside Plumsail Documents'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

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.

Fill your PDF form or Word template in DocSpring

Upload a PDF or a Word document, design a page, or write HTML, then send a test request. No credit card needed.

Product news by email

New features and changes, once a month.