Skip to content
Alternative · Nutrient (formerly PSPDFKit)

AttachKit vs. Nutrient — an agent that plans before it edits, not after

Nutrient (formerly PSPDFKit): An enterprise-grade PDF SDK that product teams embed into their own apps — now with agentic document editing you build with.

Nutrient (formerly PSPDFKit) is a genuinely strong enterprise PDF SDK — if you're a developer or product team embedding document editing and agentic workflows into your own application at scale, it's built exactly for that. But it's a component you integrate, not an app you open, and its 2025 agentic editing runs the edits end-to-end and presents the results for review afterward, routing your document to an external LLM provider. AttachKit is the opposite shape: a ready-to-use, in-browser app whose agent proposes a reviewable plan of operations that you approve before a single change is applied. And your PDF never leaves your browser — provable in DevTools → Network — while the AI only ever sees extracted text, never the file itself.

Why pick AttachKit for these cases

  • Plan-first agent: you see and approve every proposed operation before anything is applied — no post-hoc 'here's what I already did.'
  • Zero-upload by architecture: the PDF stays in your browser (verifiable in DevTools → Network); only extracted text ever reaches the AI.
  • Nothing to build: it's a working app for fill, edit, redact, sign, OCR, convert, and compare — not an SDK you have to integrate.
  • Local AI mode routes AI through your own Ollama, so no third-party model sees even the extracted text.
  • Public, self-serve pricing starting at Free $0 with {FREE_AI} AI actions/mo — no sales call, no quote.

Side-by-side

A marks the side with the genuine advantage on that row — honestly, including the few where Nutrient (formerly PSPDFKit) wins.

Where your file goes
Nutrient (formerly PSPDFKit)An SDK you embed; in the agentic flow the document is routed to an external LLM provider.
AttachKit100% client-side. The PDF never leaves your browser — provable in DevTools → Network. Only extracted text is sent to the AI, never the file.
AI agent approach
Nutrient (formerly PSPDFKit)The agent executes the edits end-to-end, then presents the results for you to review after the fact (post-hoc review).
AttachKitThe agent proposes a reviewable plan of operations first. Nothing is mutated until you accept the plan (propose-then-apply).
Embeddable SDK / enterprise integration
Nutrient (formerly PSPDFKit)Purpose-built to embed document editing and agentic workflows into your own product at scale, with mature developer tooling.
AttachKitA finished app, not a component. There's a Max-tier API and embeddable verifier, but it's not an SDK you build a product on top of.
Ready to use vs. build with
Nutrient (formerly PSPDFKit)You integrate it into an application — engineering work is required before anyone can use it.
AttachKitOpen a URL and go. Fill, edit, redact, sign, OCR, convert, and drive the agent in natural language — no install, no integration.
Price / buyer
Nutrient (formerly PSPDFKit)Developer-SDK / enterprise pricing (contact sales for a quote); plans and terms are negotiated, not a public consumer subscription.
AttachKitPublic consumer pricing: Free $0, Pro $12/mo (~$120/yr), Max $19/mo (~$192/yr). Prices change — check the pricing page.
Who it's for
Nutrient (formerly PSPDFKit)Developers and product teams building document features into their own software.
AttachKitIndividuals and small teams who need to get a PDF task done now, privately, without writing code.
AI privacy options
Nutrient (formerly PSPDFKit)Agentic editing routes document content to an external LLM provider.
AttachKitAI is metered on every tier and sends only extracted text to Claude. A 'Local AI mode' can run against your own Ollama so no third-party AI sees anything.
Signature depth
Nutrient (formerly PSPDFKit)An SDK — signing behavior depends on what you build and integrate.
AttachKitPAdES-aligned, content-bound, verifiable e-signatures — but not QES. If you need qualified electronic signatures, neither this nor an out-of-box SDK path replaces a QES provider.

Switching questions, answered

Is AttachKit a drop-in replacement for Nutrient?
Not if you're a developer embedding PDF features into your own product — that's Nutrient's core job, and AttachKit is a finished app, not an SDK. But if you just need to edit, redact, sign, or run an AI agent over a PDF yourself, AttachKit does that with no integration work and keeps the file in your browser.
Both have an AI agent — what's actually different?
The timing of your control and where the file goes. Nutrient's agent executes the edits and shows you the result afterward, routing the document to an external LLM. AttachKit's agent proposes a reviewable plan you approve before any change, and only extracted text — never the file — is sent to the AI.
Does my document get uploaded when I use the AI?
In AttachKit, no. Every engine runs in your browser and the AI receives only extracted text — you can confirm the file never leaves via DevTools → Network. With Local AI mode, even that text stays on your own machine via your Ollama instance.
Which should I choose?
Choose Nutrient if you're building document editing and agentic workflows into your own application and want an enterprise SDK to embed at scale. Choose AttachKit if you want a private, ready-to-use app where the agent plans before it edits and your PDF never leaves the browser.

Try AttachKit now

Drop a PDF — no signup. Unlimited fill & redact in your browser, plus 10 free signed PDFs every month.

Sign a PDFFill a formRedact PIISee all forms

Switching for good? Save your details once — every future form auto-fills.