DocSpring vs DocRaptor

Compare a Prince rendering API for HTML you already have with stored templates, a page designer, and PDF filling.

Our take

DocRaptor is a wrapper around Prince, a print engine with far more complete support for CSS paged media than any browser. If you publish reports with footnotes, running headers, and precise page breaks, and your application already produces the HTML, DocRaptor renders it better than a browser will. It is also cheap at low volume and has a long record of reliability.

It does one thing. There are no stored templates, no template language, no visual designer, no PDF form filling, no forms or signatures, no EU hosting, no batch or merge, and no delivery to your own storage. DocSpring renders HTML templates with Chromium rather than Prince. Chromium handles ordinary invoices and contracts well, but it supports less of the CSS paged-media specification, so complex print layouts need testing. DocSpring also has the Page Designer, where someone who doesn't write HTML can build a document. Choose DocRaptor for demanding print typography. Choose DocSpring when you want to send data instead of HTML, design documents visually, fill existing PDFs or Word templates, collect signatures, or keep documents in the EU.

Print layouts with Prince

DocRaptor renders HTML with Prince, a specialist print engine. That makes it a serious option for publications with footnotes, running content, or demanding pagination. DocSpring makes PDFs from HTML templates with a Chromium-based renderer, from page designs built in its drag-and-drop Page Designer, and from Word templates, and it also fills existing PDF forms.

If your source is an official PDF that must keep its layout, DocSpring lets you map fields onto that file. If your source is HTML, test the actual layout in both engines. Browser-compatible CSS and Prince-specific print rules are not interchangeable.

Choose DocSpring for stored templates and PDF forms

You need to fill supplied PDFs and generate new documents through the same service. Store HTML/CSS with Liquid or build a page design, send JSON data, publish template versions when a change is ready, and have each PDF saved to your own storage.

Choose DocRaptor for demanding print layouts

Your application produces HTML and needs Prince's paged-media features. A technical report with footnotes and carefully controlled page breaks is a better evaluation document than a one-page receipt.

Feature comparison

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

DocRaptor and DocSpring: rendering, templates, APIs, integrations, and security
What you need DocSpring DocRaptor
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. Each request sends HTML or a URL and Prince renders a new document.
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. You write the HTML and CSS in your own tools.
HTML to PDF Yes HTML/CSS and Liquid templates, with code editors and a PDF preview. Yes: Prince Converts HTML, CSS, and JavaScript with Prince, including paged-media CSS, footnotes, and running headers.
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 language. Your application renders repeated rows into the HTML before each request.
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 Conditional content is resolved in your application 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 No stored templates, so nothing to version. Pipeline versioning pins the rendering engine, not your layout.
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 HTML form elements become fillable PDF fields with a Prince-specific CSS property.
HTML rendering engine Yes: Chromium Browser-based rendering of HTML/CSS templates. Yes: Prince Prince supports CSS Paged Media features that browser engines do not. A pipeline setting pins the version.
HTML template language Yes: Liquid Store template logic with the layout and supply JSON data when generating a document. No No stored templates or template language. Your application sends finished HTML with every request.
API integration
Synchronous generation Yes Use sync.api.docspring.com to receive submission JSON and a PDF download URL in one request. Yes Synchronous creation is the default and returns the PDF bytes, with a 60 second limit.
Asynchronous generation Yes Send wait=false to return immediately. Receive a webhook or check the submission status later. Yes Set async=true to queue the job for up to 10 minutes, then poll the status URL.
Webhooks Yes Receive notifications about PDF generation and signature request events. Yes A callback URL receives a POST after an asynchronous job succeeds. Failures are not sent to the callback.
Batch PDF generation Yes Generate up to 50 PDFs in a request with different templates and data. No One document per request. Run parallel requests for volume.
Combine PDFs Yes Combine generated PDFs and other PDF files into one document. No No PDF merging. DocRaptor's own comparison pages list it as unsupported.
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. No DocRaptor publishes no MCP server or agent skills. Third-party platforms such as Composio offer DocRaptor tools for AI agents.
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 S3 delivery. Responses are PDF bytes, or a DocRaptor-hosted URL with the paid hosting add-on.
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. Your application receives the PDF and uploads it wherever it needs to go.
Zapier Yes Generate PDFs and start signing workflows through the Zapier integration. No No Zapier app. DocRaptor's guide uses Webhooks by Zapier to call the API.
n8n Yes Community node for PDF generation and signing workflows. No No n8n node. The integrations page lists Zapier, Drupal, and Kotive only.
Make.com Yes DocSpring app for PDF generation, signature requests and templates. No No Make app. Call the REST API with a generic HTTP module.
Pipedream Coming soon DocSpring integration is planned. Conditions apply: Auth only Pipedream lists DocRaptor for API-key authentication but has no prebuilt actions or 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 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. Generated PDFs can contain fillable fields, but nothing captures submissions.
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. Yes SOC 2 Type II, audited against the Security trust services criteria.
GDPR compliance Yes GDPR compliant. Our Trust Portal lists security controls and policies. Yes GDPR compliant, DPA on request, and a participant in the EU-US Data Privacy Framework.
HIPAA compliance Yes HIPAA compliant, with a BAA on every paid plan, including Starter. Sign it before sending health records. Conditions apply: Paid plans Available on any paid plan. Enable HIPAA mode, which disables document hosting, then sign the BAA.
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 Retention is configurable from 7 days down to deleting input on conversion and output within 15 minutes.
US and EU hosting Yes Choose the US or EU service region. No US only. Documents are rendered in the AWS us-east-1 region with no EU option.
Self-hosting Yes: Enterprise Self-hosted enterprise licenses are available. Not published No self-hosted option is published. DocRaptor is described only as a hosted API.
Company
Founded 2017 Launched as FormAPI in October 2017 and renamed DocSpring in 2019. 2010 Built in 2010. Part of Artifex Software since October 2025.

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

Test a multi-page invoice, not just a screenshot

Start with an invoice that grows from two rows to several pages. Keep the data, fonts, and page dimensions the same in both versions so differences in pagination are easy to spot.

In DocSpring

Create an HTML template and use a Liquid loop to render the rows. DocSpring adds the items list to the template's fields. Preview sample data before publishing a version, then send JSON to generate each invoice.

Use print CSS and the template's header and footer settings. Check the final page count with long item descriptions and a table that ends close to the bottom of a page. To compare a layout nobody has to code, build the same invoice in the Page Designer, where the items table carries on over the next page and can repeat its heading row.

In DocRaptor

Render the invoice HTML in your application, then submit it as document_content or supply a document URL. Configure the Prince options required by the layout.

The synchronous response is the PDF itself. For longer jobs, keep the status ID and fetch the output when the job finishes. A success callback does not replace checking failed jobs.

A Liquid invoice in DocSpring

Create an HTML template with this content, and DocSpring adds the customer_name and items fields when you save it. The request below supplies two items; use a longer array to exercise pagination.

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.

If you rely on Prince-specific footnotes, page selectors, or other print rules, test those first. Recreating the invoice successfully does not prove a complex publication will render identically.

Cheap per document, with nothing else included

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

DocRaptor

DocRaptor's free plan includes 5 production documents a month. Paid plans are billed monthly. Basic is $15 for 125 documents, then $29 for 325, $75 for 1,250, $149 for 5,000, $399 for 15,000, and $1,000 for 40,000. Overage runs from 12 cents per document on Basic down to 2.5 cents on the $1,000 plan. Watermarked test documents are free on every plan.

A document counts once regardless of page count or file size, which is generous for long reports. Document hosting costs extra, and there is no EU region at any price.

DocRaptor pricing page

A 40-page report and a one-page invoice each count as one document. For 2,000 reports a month, DocRaptor's $75-a-month plan plus overage comes to about $120. DocSpring charges 4 credits for each 10 pages of an HTML PDF, so 2,000 40-page reports need 32,000 credits: the Growth plan with 50,000 credits, at $149, more than DocRaptor. For 2,000 one-page invoices the order flips: DocRaptor's price is the same, and DocSpring needs 8,000 credits, at $49. Either DocSpring price includes stored templates, the Page Designer, form filling, and EU hosting, which DocRaptor does not offer at all. Test the largest report against both renderers before deciding.

Moving HTML generation from DocRaptor to DocSpring

Keep the original HTML, CSS, fonts, and representative outputs. Move the dynamic parts of your application template into Liquid if you want DocSpring to store the template. Keep calculations in your application when that makes them easier to test. A simple layout, such as a receipt or a certificate, can be rebuilt in the Page Designer instead.

Replace Prince-specific settings with supported CSS or DocSpring template settings. Pay particular attention to footnotes, page numbering, table breaks, margins, and font metrics. Some layouts need redesigning rather than a mechanical conversion.

Change response handling from raw PDF bytes to submission JSON and a download URL, or have DocSpring save each PDF to S3, Google Drive, Dropbox, or Box. For background jobs, map your existing status handling to DocSpring submissions and webhooks. Test rendering failures as well as completed documents.

Discuss your documents with us.

Questions about DocRaptor alternatives

Ask us about your documents

Will the same HTML produce the same PDF?

Not necessarily. Prince and Chromium handle some print CSS differently, and font measurements can change line and page breaks. Compare representative output before migrating, especially if your document uses Prince-specific features.

Can DocRaptor fill an existing government form?

No. Its API renders a new document from HTML. DocSpring keeps the original PDF as the background and places data into fields, which avoids rebuilding the form in HTML. When you upload the form, AI field setup finds and names its fields for you to review.

Can I design documents without writing HTML?

Not in DocRaptor, which renders the HTML you send. DocSpring's Page Designer places text, images, tables, QR codes, barcodes, headers, and footers on a page, with your data in them. For layouts that depend on Prince's paged-media features, HTML in DocRaptor is still the better tool.

Does DocRaptor offer EU hosting?

No. DocRaptor renders documents in the AWS us-east-1 region. DocSpring offers a choice of US or EU region.

About this comparison

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

Test your 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.