DocSpring vs PDFShift

Compare converting HTML you already have with sending data to a stored template or page design.

Our take

PDFShift is a good, inexpensive HTML and URL to PDF converter. It renders with Chromium, starts at $9 a month, can write output straight to S3, Google Cloud Storage, or Cloudflare R2, offers a BAA, and has a hosted MCP server. If your application already produces the HTML and you just need a PDF back, it is hard to fault.

It stops there. Templates store HTML, but no syntax for variables, loops, or conditions is documented and there are no versions, so in practice you send finished HTML every time. There is no visual designer, it cannot fill an existing PDF, has no forms or signatures, no US region, and its credits count file size rather than documents, so image-heavy PDFs cost more than you expect. Choose PDFShift for pure conversion at low cost. Choose DocSpring when the template should live outside your code, when someone needs to design documents without writing HTML, when you fill PDF forms or Word templates, or when the workflow continues into data collection and signing.

Converting an existing HTML view

PDFShift fits applications that already produce HTML or expose a page URL and want a PDF rendering API. It also has stored templates, although no template syntax is documented for them. DocSpring stores HTML/CSS templates with Liquid, page designs from its drag-and-drop Page Designer, and Word templates, and accepts JSON data. It also fills existing PDFs.

The integration boundary is different. With a web-page converter, your application owns the layout, asset access, and timing of JavaScript. With a DocSpring template, the layout and its fields live with the PDF service. Choose where you want those responsibilities to sit.

Choose DocSpring for reusable document templates

Your application sends structured data to a managed HTML template, page design, Word template, or PDF form. You also need embedded forms, signing, or PDFs saved to Google Drive, Dropbox, or Box, without maintaining a separate document layout for each workflow.

Choose PDFShift for HTML and URL conversion

Your application already has a working HTML view, or you need to render a URL with conversion options. Test pages with authentication, web fonts, and delayed content before committing to the integration.

Feature comparison

Follow the feature links for details in DocSpring's documentation. Sources for each PDFShift 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.

PDFShift and DocSpring: rendering, templates, APIs, integrations, and security
What you need DocSpring PDFShift
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. No No PDF form filling. Converts HTML and URLs only.
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 visual designer. Prepare the HTML and CSS yourself or point the API at a URL.
HTML to PDF Yes HTML/CSS and Liquid templates, with code editors and a PDF preview. Yes: Chromium Converts HTML or a URL to PDF or images with headers, footers, watermarks, and encryption.
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. Conditions apply: In your app No template syntax for loops. Render repeated rows into the HTML in your application.
Conditional content Yes Show or require PDF fields with conditional rules. Use Liquid conditions in page designs, HTML and Word templates. Conditions apply: In your app No conditional syntax. Resolve optional content before sending the HTML.
Template versioning Yes Edit drafts, see what changed since the last version, publish numbered versions, and pin API requests to one. No Updating a stored template overwrites it. There is no version history or pinning.
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. No No fillable form output is documented. Chromium prints HTML inputs as static content.
HTML rendering engine Yes: Chromium Browser-based rendering of HTML/CSS templates. Yes: Chromium Renders with Chromium. A request header selects version 142 or 116.
HTML template language Yes: Liquid Store template logic with the layout and supply JSON data when generating a document. Conditions apply: Stored HTML Templates store HTML by slug, and an endpoint renders one with data, but no variable, loop, or condition syntax is documented.
API integration
Synchronous generation Yes Use sync.api.docspring.com to receive submission JSON and a PDF download URL in one request. Yes The default response is the PDF bytes, or JSON with a temporary URL when a filename is set.
Asynchronous generation Yes Send wait=false to return immediately. Receive a webhook or check the submission status later. Conditions apply: Paid plans Passing a webhook queues the conversion. Asynchronous responses are listed as a paid-plan feature.
Webhooks Yes Receive notifications about PDF generation and signature request events. Conditions apply: Paid plans A POST carries the result URL on success or an error on failure.
Batch PDF generation Yes Generate up to 50 PDFs in a request with different templates and data. Conditions apply: Paid plans Send an array of sources with a webhook for parallel conversion, up to 50 at a time.
Combine PDFs Yes Combine generated PDFs and other PDF files into one document. No No merge endpoint. Each request converts one source.
Images of the pages Yes Add png to a submission's output formats to get an image of each page of its PDF. Conditions apply: Screenshots Converts HTML or a URL to a PNG, JPEG, or WebP image of the viewport, the full page, or one element, rather than an image of each page of a PDF.
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. Yes A hosted MCP server, signed in with an API key, converts HTML and URLs and creates, edits, and renders stored templates.
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. Conditions apply: Paid plans Writes output directly to your S3 bucket or Google Cloud Storage, or to Cloudflare R2 through a presigned URL.
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 delivery to Google Drive, Dropbox, or Box. Storage options are S3, Google Cloud Storage, and R2.
Zapier Yes Generate PDFs and start signing workflows through the Zapier integration. No No Zapier app. PDFShift's guide calls the REST API through an API by Zapier action.
n8n Yes Community node for PDF generation and signing workflows. Yes: Community node PDFShift publishes an n8n-verified community node on npm for PDF and image conversion.
Make.com Yes DocSpring app for PDF generation, signature requests and templates. No No Make app. PDFShift's guide uses Make's HTTP module.
Pipedream Coming soon DocSpring integration is planned. No No Pipedream app. Call the API from a code step.
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 template editor exists to embed.
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 No hosted data collection.
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 No e-signature workflow.
Embedded signing Yes Show the signing form in your app with a short-lived authentication token. No No signing feature.
Security and deployment
SOC 2 Type II Yes Completed audit. Request the report through our Trust Portal. No No SOC 2 report is published. Its legal pages cover GDPR, a DPA, HIPAA, and a BAA.
GDPR compliance Yes GDPR compliant. Our Trust Portal lists security controls and policies. Yes GDPR page and a published DPA. Conversion runs in OVH data centers in France, and the DPA places files stored through the filename option on AWS S3 in Paris.
HIPAA compliance Yes HIPAA compliant, with a BAA on every paid plan, including Starter. Sign it before sending health records. Yes: With BAA A BAA is offered. HIPAA mode disables PDFShift-side storage, so stored output must go to your own bucket.
ISO 27001 No Not certified. DocSpring's security controls are audited under SOC 2 Type II. No No ISO 27001 certification is published.
Automatic document deletion Yes Set an expiry per template for submission data, generated PDFs, and uploaded images. Yes Documents are processed in memory by default. Using a filename or webhook keeps the file for 2 days.
US and EU hosting Yes Choose the US or EU service region. Conditions apply: EU only Conversion runs in France and stored files are kept on AWS S3 in Paris. There is no US region or region selection.
Self-hosting Yes: Enterprise Self-hosted enterprise licenses are available. Not published No self-hosted option is published. PDFShift is offered only as a hosted API.
Company
Founded 2017 Launched as FormAPI in October 2017 and renamed DocSpring in 2019. 2018 Launched in May 2018.

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

Turn a billing record into an invoice PDF

An invoice with a customer name and a variable number of line items can use either API. Decide whether your application will send finished HTML or data for a stored template.

In DocSpring

Create an HTML/CSS template with a Liquid loop for line items, or a page design with a table over them. Send the customer and items as JSON to the template's submission endpoint. The synchronous response includes a PDF download URL.

Publish a new template version after testing changes, and pin a version when an application release needs a fixed layout. Add png to the output formats if you also need an image of each page.

In PDFShift

Render the invoice HTML in your application and send it as the source of a conversion request. Configure page size, margins, headers, and asset access for the invoice.

A standard conversion returns binary PDF data. Use the webhook flow for background conversion on a paid plan, and set an S3 destination if you want the file written to your bucket.

Generate the invoice with a DocSpring template

Save this Liquid markup in an HTML template, and DocSpring adds the customer_name and items fields. The request sends data independently of the layout.

Liquid
<h1>Invoice for {{ customer_name | escape }}</h1>
<table>
  <tr><th>Description</th><th>Amount (USD)</th></tr>
  {% for item in items %}
    <tr>
      <td>{{ item.description | escape }}</td>
      <td>{{ item.amount | currency }}</td>
    </tr>
  {% endfor %}
</table>
Shell
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",
      "items": [
        { "description": "Annual inspection", "amount": 120 },
        { "description": "Replacement filter", "amount": 35 }
      ]
    }
  }'

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.

Test an invoice with large images as well as many rows. A document can be short in pages but large in bytes, which affects PDFShift credit usage and download time.

Credits by file size against credits by page count

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

PDFShift

PDFShift's free plan includes 50 credits a month with a 15 MB file limit. Billed monthly, Starter is $9 for 500 credits, then $24 for 2,500, $39 for 5,000, and $99 for 25,000, with larger plans up to $999 for 1,000,000. Yearly billing gives two months free. Overage is 4 cents per credit on Starter and falls with volume, but has to be switched on, and unused credits don't roll over. Webhooks, batch, and S3 delivery need a paid plan.

One credit covers a document up to 5 MB, rounded up per document. PDFShift's own example is a 14 MB PDF costing 3 credits, so estimate from real output files rather than page counts.

PDFShift pricing page

At 12 MB each, 1,000 PDFs use 3,000 PDFShift credits and need the $39-a-month plan. At 2 MB each they use 1,000 credits on the $24-a-month plan. DocSpring's price also rises with file size, but in much larger steps, so most documents are priced by page count: 1,000 one-page PDFs from an HTML template or a page design need 4,000 credits, at $29 for a 5,000-credit pack on the free Developer plan. For conversion alone the prices are close. DocSpring's credits also pay for page designs, PDF form filling, and signing, and paid plans add hosted forms without the DocSpring logo.

Moving a PDFShift integration to DocSpring

Collect the HTML, stylesheets, fonts, and conversion options used by your current request. Convert variable values and repeated sections to Liquid so DocSpring can store the template. A URL conversion is not a drop-in match for a template ID plus JSON. A simple layout can be rebuilt in the Page Designer instead.

Move header, footer, margin, and page-size settings into the DocSpring template. Test pages that depend on JavaScript or authenticated resources; do not assume the same timing or asset access rules apply.

Replace binary-response handling with the submission download URL, or have DocSpring save each PDF to your S3-compatible bucket, Google Drive, Dropbox, or Box. For asynchronous work, save the DocSpring submission ID and handle completion through webhooks or status checks. Both services render HTML with Chromium, so the output should be close once you set the font, background, and page margins that DocSpring's normalize.css and default styles would otherwise supply.

Discuss your documents with us.

Questions about PDFShift alternatives

Ask us about your documents

Does PDFShift have stored templates?

Yes. Templates store HTML by slug, and an endpoint renders one with data, but there is no documented syntax for variables, loops, or conditions, so most integrations render the HTML in the application and send it each time. DocSpring templates use Liquid, with a field for each value, and its page designs are built in a drag-and-drop editor.

Can I use PDFShift for HIPAA workflows?

Yes. PDFShift offers a BAA and a HIPAA request mode that disables its own storage, so you must supply your own S3 destination. DocSpring signs a BAA on every paid plan, including Starter. Review the full data path for either service.

Can an AI assistant work with either service?

Yes. PDFShift's hosted MCP server uses your API key to convert HTML and manage its templates. DocSpring's MCP server signs in with OAuth, with read-only, read and write, or full access, and can create HTML templates and page designs, set up fields, publish versions, and create signature requests and their signing links. Assistants make free test PDFs unless you ask for a live one.

Will my PDFs look the same after switching?

Usually, once the page settings match. Both services render HTML with Chromium, but DocSpring adds normalize.css and default styles for the font, background, and page margins. Set those explicitly, and check custom fonts, header and footer settings, and any PDFShift-specific options such as watermarks or encryption that need equivalents in DocSpring.

About this comparison

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

Try a stored HTML 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.